Regenerate integrations docs (#22034)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
Netdata bot committed
Mar 24, 2026 at 17:07 UTC
68014b1996dda15159a8724389f26ca69777c0c7
482 files changed
+23160
-23152
src/collectors/apps.plugin/integrations/applications.md
+31
-31
@@ -44,6 +44,37 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+There are no alerts configured by default for this integration.
76
+
77
+
78
## Metrics
79
80
Metrics grouped by *scope*.
@@ -85,34 +116,3 @@ Metrics:
116
| app.uptime_summary | min, avg, max | seconds |
117
118
88
-
89
-## Alerts
90
-
91
-There are no alerts configured by default for this integration.
92
-
93
-
94
-## Setup
95
-
96
-
97
-### Prerequisites
98
-
99
-No action required.
100
-
101
-### Configuration
102
-
103
-#### Options
104
-
105
-
106
-
107
-There are no configuration options.
108
-
109
-
110
-
111
-#### via File
112
-
113
-There is no configuration file.
114
-
115
-##### Examples
116
-There are no configuration examples.
117
-
118
-
src/collectors/apps.plugin/integrations/user_groups.md
+31
-31
@@ -44,6 +44,37 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+There are no alerts configured by default for this integration.
76
+
77
+
78
## Metrics
79
80
Metrics grouped by *scope*.
@@ -85,34 +116,3 @@ Metrics:
116
| usergroup.uptime_summary | min, avg, max | seconds |
117
118
88
-
89
-## Alerts
90
-
91
-There are no alerts configured by default for this integration.
92
-
93
-
94
-## Setup
95
-
96
-
97
-### Prerequisites
98
-
99
-No action required.
100
-
101
-### Configuration
102
-
103
-#### Options
104
-
105
-
106
-
107
-There are no configuration options.
108
-
109
-
110
-
111
-#### via File
112
-
113
-There is no configuration file.
114
-
115
-##### Examples
116
-There are no configuration examples.
117
-
118
-
src/collectors/apps.plugin/integrations/users.md
+31
-31
@@ -44,6 +44,37 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+There are no alerts configured by default for this integration.
76
+
77
+
78
## Metrics
79
80
Metrics grouped by *scope*.
@@ -85,34 +116,3 @@ Metrics:
116
| user.uptime_summary | min, avg, max | seconds |
117
118
88
-
89
-## Alerts
90
-
91
-There are no alerts configured by default for this integration.
92
-
93
-
94
-## Setup
95
-
96
-
97
-### Prerequisites
98
-
99
-No action required.
100
-
101
-### Configuration
102
-
103
-#### Options
104
-
105
-
106
-
107
-There are no configuration options.
108
-
109
-
110
-
111
-#### via File
112
-
113
-There is no configuration file.
114
-
115
-##### Examples
116
-There are no configuration examples.
117
-
118
-
src/collectors/cgroups.plugin/integrations/aws_ecs_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/containerd_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/docker_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/kubernetes_containers.md
+39
-39
@@ -54,6 +54,45 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
+## Setup
58
+
59
+
60
+### Prerequisites
61
+
62
+No action required.
63
+
64
+### Configuration
65
+
66
+#### Options
67
+
68
+
69
+
70
+There are no configuration options.
71
+
72
+
73
+
74
+#### via File
75
+
76
+There is no configuration file.
77
+
78
+##### Examples
79
+There are no configuration examples.
80
+
81
+
82
+
83
+## Alerts
84
+
85
+
86
+The following alerts are available:
87
+
88
+| Alert name | On metric | Description |
89
+|:------------|:----------|:------------|
90
+| [ k8s_cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
91
+| [ k8s_cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.mem_usage | cgroup memory utilization |
92
+| [ k8s_cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
93
+| [ k8s_cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
94
+
95
+
96
## Metrics
97
98
Metrics grouped by *scope*.
@@ -155,42 +194,3 @@ Metrics:
194
| k8s.cgroup.net_mtu | mtu | octets |
195
196
158
-
159
-## Alerts
160
-
161
-
162
-The following alerts are available:
163
-
164
-| Alert name | On metric | Description |
165
-|:------------|:----------|:------------|
166
-| [ k8s_cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
167
-| [ k8s_cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.mem_usage | cgroup memory utilization |
168
-| [ k8s_cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
169
-| [ k8s_cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
170
-
171
-
172
-## Setup
173
-
174
-
175
-### Prerequisites
176
-
177
-No action required.
178
-
179
-### Configuration
180
-
181
-#### Options
182
-
183
-
184
-
185
-There are no configuration options.
186
-
187
-
188
-
189
-#### via File
190
-
191
-There is no configuration file.
192
-
193
-##### Examples
194
-There are no configuration examples.
195
-
196
-
src/collectors/cgroups.plugin/integrations/libvirt_vms_and_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/lxc_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/nomad_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/openshift_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ k8s_cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ k8s_cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.mem_usage | cgroup memory utilization |
84
+| [ k8s_cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ k8s_cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -147,42 +186,3 @@ Metrics:
186
| k8s.cgroup.net_mtu | mtu | octets |
187
188
150
-
151
-## Alerts
152
-
153
-
154
-The following alerts are available:
155
-
156
-| Alert name | On metric | Description |
157
-|:------------|:----------|:------------|
158
-| [ k8s_cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
159
-| [ k8s_cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.mem_usage | cgroup memory utilization |
160
-| [ k8s_cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
161
-| [ k8s_cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | k8s.cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
162
-
163
-
164
-## Setup
165
-
166
-
167
-### Prerequisites
168
-
169
-No action required.
170
-
171
-### Configuration
172
-
173
-#### Options
174
-
175
-
176
-
177
-There are no configuration options.
178
-
179
-
180
-
181
-#### via File
182
-
183
-There is no configuration file.
184
-
185
-##### Examples
186
-There are no configuration examples.
187
-
188
-
src/collectors/cgroups.plugin/integrations/openstack_vms.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/ovirt_vms.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/podman_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/proxmox_vms_and_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/systemd-nspawn_containers.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/cgroups.plugin/integrations/systemd_services.md
+31
-31
@@ -46,6 +46,37 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+There are no alerts configured by default for this integration.
78
+
79
+
80
## Metrics
81
82
Metrics grouped by *scope*.
@@ -84,34 +115,3 @@ Metrics:
115
| systemd.service.pids.current | pids | pids |
116
117
87
-
88
-## Alerts
89
-
90
-There are no alerts configured by default for this integration.
91
-
92
-
93
-## Setup
94
-
95
-
96
-### Prerequisites
97
-
98
-No action required.
99
-
100
-### Configuration
101
-
102
-#### Options
103
-
104
-
105
-
106
-There are no configuration options.
107
-
108
-
109
-
110
-#### via File
111
-
112
-There is no configuration file.
113
-
114
-##### Examples
115
-There are no configuration examples.
116
-
117
-
src/collectors/cgroups.plugin/integrations/virtual_machines.md
+39
-39
@@ -46,6 +46,45 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+
78
+The following alerts are available:
79
+
80
+| Alert name | On metric | Description |
81
+|:------------|:----------|:------------|
82
+| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
83
+| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
84
+| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
85
+| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -133,42 +172,3 @@ Metrics:
172
| cgroup.net_mtu | mtu | octets |
173
174
136
-
137
-## Alerts
138
-
139
-
140
-The following alerts are available:
141
-
142
-| Alert name | On metric | Description |
143
-|:------------|:----------|:------------|
144
-| [ cgroup_10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.cpu_limit | average cgroup CPU utilization over the last 10 minutes |
145
-| [ cgroup_ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.mem_usage | cgroup memory utilization |
146
-| [ cgroup_1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | average number of packets received by the network interface ${label:device} over the last minute |
147
-| [ cgroup_10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cgroups.conf) | cgroup.net_packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
148
-
149
-
150
-## Setup
151
-
152
-
153
-### Prerequisites
154
-
155
-No action required.
156
-
157
-### Configuration
158
-
159
-#### Options
160
-
161
-
162
-
163
-There are no configuration options.
164
-
165
-
166
-
167
-#### via File
168
-
169
-There is no configuration file.
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/charts.d.plugin/libreswan/integrations/libreswan.md
+28
-28
@@ -44,34 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per IPSEC tunnel
56
-
57
-Metrics related to IPSEC tunnels. Each tunnel provides its own set of the following metrics.
58
-
59
-This scope has no labels.
60
-
61
-Metrics:
62
-
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| libreswan.net | in, out | kilobits/s |
66
-| libreswan.uptime | uptime | seconds |
67
-
68
-
69
-
70
-## Alerts
71
-
72
-There are no alerts configured by default for this integration.
73
-
74
-
47
## Setup
48
49
@@ -176,6 +148,34 @@ libreswan_sudo=0
148
```
149
150
151
+## Alerts
152
+
153
+There are no alerts configured by default for this integration.
154
+
155
+
156
+## Metrics
157
+
158
+Metrics grouped by *scope*.
159
+
160
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
161
+
162
+
163
+
164
+### Per IPSEC tunnel
165
+
166
+Metrics related to IPSEC tunnels. Each tunnel provides its own set of the following metrics.
167
+
168
+This scope has no labels.
169
+
170
+Metrics:
171
+
172
+| Metric | Dimensions | Unit |
173
+|:------|:----------|:----|
174
+| libreswan.net | in, out | kilobits/s |
175
+| libreswan.uptime | uptime | seconds |
176
+
177
+
178
+
179
## Troubleshooting
180
181
### Debug Mode
src/collectors/charts.d.plugin/opensips/integrations/opensips.md
+45
-45
@@ -44,51 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per OpenSIPS instance
56
-
57
-These metrics refer to the entire monitored application.
58
-
59
-This scope has no labels.
60
-
61
-Metrics:
62
-
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| opensips.dialogs_active | active, early | dialogs |
66
-| opensips.users | registered, location, contacts, expires | users |
67
-| opensips.registrar | accepted, rejected | registrations/s |
68
-| opensips.transactions | UAS, UAC | transactions/s |
69
-| opensips.core_rcv | requests, replies | queries/s |
70
-| opensips.core_fwd | requests, replies | queries/s |
71
-| opensips.core_drop | requests, replies | queries/s |
72
-| opensips.core_err | requests, replies | queries/s |
73
-| opensips.core_bad | bad_URIs_rcvd, unsupported_methods, bad_msg_hdr | queries/s |
74
-| opensips.tm_replies | received, relayed, local | replies/s |
75
-| opensips.transactions_status | 2xx, 3xx, 4xx, 5xx, 6xx | transactions/s |
76
-| opensips.transactions_inuse | inuse | transactions |
77
-| opensips.sl_replies | 1xx, 2xx, 3xx, 4xx, 5xx, 6xx, sent, error, ACKed | replies/s |
78
-| opensips.dialogs | processed, expire, failed | dialogs/s |
79
-| opensips.net_waiting | UDP, TCP | kilobytes |
80
-| opensips.uri_checks | positive, negative | checks / sec |
81
-| opensips.traces | requests, replies | traces / sec |
82
-| opensips.shmem | total, used, real_used, max_used, free | kilobytes |
83
-| opensips.shmem_fragment | fragments | fragments |
84
-
85
-
86
-
87
-## Alerts
88
-
89
-There are no alerts configured by default for this integration.
90
-
91
-
47
## Setup
48
49
@@ -174,6 +129,51 @@ opensips_cmd=/opt/opensips/bin/opensipsctl
129
```
130
131
132
+## Alerts
133
+
134
+There are no alerts configured by default for this integration.
135
+
136
+
137
+## Metrics
138
+
139
+Metrics grouped by *scope*.
140
+
141
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
142
+
143
+
144
+
145
+### Per OpenSIPS instance
146
+
147
+These metrics refer to the entire monitored application.
148
+
149
+This scope has no labels.
150
+
151
+Metrics:
152
+
153
+| Metric | Dimensions | Unit |
154
+|:------|:----------|:----|
155
+| opensips.dialogs_active | active, early | dialogs |
156
+| opensips.users | registered, location, contacts, expires | users |
157
+| opensips.registrar | accepted, rejected | registrations/s |
158
+| opensips.transactions | UAS, UAC | transactions/s |
159
+| opensips.core_rcv | requests, replies | queries/s |
160
+| opensips.core_fwd | requests, replies | queries/s |
161
+| opensips.core_drop | requests, replies | queries/s |
162
+| opensips.core_err | requests, replies | queries/s |
163
+| opensips.core_bad | bad_URIs_rcvd, unsupported_methods, bad_msg_hdr | queries/s |
164
+| opensips.tm_replies | received, relayed, local | replies/s |
165
+| opensips.transactions_status | 2xx, 3xx, 4xx, 5xx, 6xx | transactions/s |
166
+| opensips.transactions_inuse | inuse | transactions |
167
+| opensips.sl_replies | 1xx, 2xx, 3xx, 4xx, 5xx, 6xx, sent, error, ACKed | replies/s |
168
+| opensips.dialogs | processed, expire, failed | dialogs/s |
169
+| opensips.net_waiting | UDP, TCP | kilobytes |
170
+| opensips.uri_checks | positive, negative | checks / sec |
171
+| opensips.traces | requests, replies | traces / sec |
172
+| opensips.shmem | total, used, real_used, max_used, free | kilobytes |
173
+| opensips.shmem_fragment | fragments | fragments |
174
+
175
+
176
+
177
## Troubleshooting
178
179
### Debug Mode
src/collectors/cups.plugin/integrations/cups.md
+43
-43
@@ -44,49 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per CUPS instance
56
-
57
-
58
-
59
-This scope has no labels.
60
-
61
-Metrics:
62
-
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| cups.dests_state | idle, printing, stopped | dests |
66
-| cups.dests_option | total, acceptingjobs, shared | dests |
67
-| cups.job_num | pending, held, processing | jobs |
68
-| cups.job_size | pending, held, processing | KB |
69
-
70
-### Per destination
71
-
72
-
73
-
74
-This scope has no labels.
75
-
76
-Metrics:
77
-
78
-| Metric | Dimensions | Unit |
79
-|:------|:----------|:----|
80
-| cups.destination_job_num | pending, held, processing | jobs |
81
-| cups.destination_job_size | pending, held, processing | KB |
82
-
83
-
84
-
85
-## Alerts
86
-
87
-There are no alerts configured by default for this integration.
88
-
89
-
47
## Setup
48
49
@@ -144,3 +101,46 @@ sudo ./edit-config netdata.conf
101
There are no configuration examples.
102
103
104
+
105
+## Alerts
106
+
107
+There are no alerts configured by default for this integration.
108
+
109
+
110
+## Metrics
111
+
112
+Metrics grouped by *scope*.
113
+
114
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
115
+
116
+
117
+
118
+### Per CUPS instance
119
+
120
+
121
+
122
+This scope has no labels.
123
+
124
+Metrics:
125
+
126
+| Metric | Dimensions | Unit |
127
+|:------|:----------|:----|
128
+| cups.dests_state | idle, printing, stopped | dests |
129
+| cups.dests_option | total, acceptingjobs, shared | dests |
130
+| cups.job_num | pending, held, processing | jobs |
131
+| cups.job_size | pending, held, processing | KB |
132
+
133
+### Per destination
134
+
135
+
136
+
137
+This scope has no labels.
138
+
139
+Metrics:
140
+
141
+| Metric | Dimensions | Unit |
142
+|:------|:----------|:----|
143
+| cups.destination_job_num | pending, held, processing | jobs |
144
+| cups.destination_job_size | pending, held, processing | KB |
145
+
146
+
src/collectors/debugfs.plugin/integrations/linux_zswap.md
+34
-34
@@ -50,40 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-Monitor the performance statistics of zswap.
60
-
61
-### Per Linux ZSwap instance
62
-
63
-Global zswap performance metrics.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| system.zswap_pool_compression_ratio | compression_ratio | ratio |
72
-| system.zswap_pool_compressed_size | compressed_size | bytes |
73
-| system.zswap_pool_raw_size | uncompressed_size | bytes |
74
-| system.zswap_rejections | compress_poor, kmemcache_fail, alloc_fail, reclaim_fail | rejections/s |
75
-| system.zswap_pool_limit_hit | limit | events/s |
76
-| system.zswap_written_back_raw_bytes | written_back | bytes/s |
77
-| system.zswap_same_filled_raw_size | same_filled | bytes |
78
-| system.zswap_duplicate_entry | duplicate | entries/s |
79
-
80
-
81
-
82
-## Alerts
83
-
84
-There are no alerts configured by default for this integration.
85
-
86
-
53
## Setup
54
55
@@ -142,3 +108,37 @@ sudo ./edit-config netdata.conf
108
There are no configuration examples.
109
110
111
+
112
+## Alerts
113
+
114
+There are no alerts configured by default for this integration.
115
+
116
+
117
+## Metrics
118
+
119
+Metrics grouped by *scope*.
120
+
121
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
122
+
123
+Monitor the performance statistics of zswap.
124
+
125
+### Per Linux ZSwap instance
126
+
127
+Global zswap performance metrics.
128
+
129
+This scope has no labels.
130
+
131
+Metrics:
132
+
133
+| Metric | Dimensions | Unit |
134
+|:------|:----------|:----|
135
+| system.zswap_pool_compression_ratio | compression_ratio | ratio |
136
+| system.zswap_pool_compressed_size | compressed_size | bytes |
137
+| system.zswap_pool_raw_size | uncompressed_size | bytes |
138
+| system.zswap_rejections | compress_poor, kmemcache_fail, alloc_fail, reclaim_fail | rejections/s |
139
+| system.zswap_pool_limit_hit | limit | events/s |
140
+| system.zswap_written_back_raw_bytes | written_back | bytes/s |
141
+| system.zswap_same_filled_raw_size | same_filled | bytes |
142
+| system.zswap_duplicate_entry | duplicate | entries/s |
143
+
144
+
src/collectors/debugfs.plugin/integrations/power_capping.md
+28
-28
@@ -50,34 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-Monitor the Intel RAPL zones Consumption.
60
-
61
-### Per Power Capping instance
62
-
63
-Global Intel RAPL zones.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| cpu.powercap_intel_rapl_zone | Power | Watts |
72
-| cpu.powercap_intel_rapl_subzones | dram, core, uncore | Watts |
73
-
74
-
75
-
76
-## Alerts
77
-
78
-There are no alerts configured by default for this integration.
79
-
80
-
53
## Setup
54
55
@@ -136,3 +108,31 @@ sudo ./edit-config netdata.conf
108
There are no configuration examples.
109
110
111
+
112
+## Alerts
113
+
114
+There are no alerts configured by default for this integration.
115
+
116
+
117
+## Metrics
118
+
119
+Metrics grouped by *scope*.
120
+
121
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
122
+
123
+Monitor the Intel RAPL zones Consumption.
124
+
125
+### Per Power Capping instance
126
+
127
+Global Intel RAPL zones.
128
+
129
+This scope has no labels.
130
+
131
+Metrics:
132
+
133
+| Metric | Dimensions | Unit |
134
+|:------|:----------|:----|
135
+| cpu.powercap_intel_rapl_zone | Power | Watts |
136
+| cpu.powercap_intel_rapl_subzones | dram, core, uncore | Watts |
137
+
138
+
src/collectors/debugfs.plugin/integrations/system_memory_fragmentation.md
+33
-33
@@ -49,39 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-Monitor the overall memory fragmentation of the system.
59
-
60
-### Per node
61
-
62
-Memory fragmentation statistics for each NUMA node in the system.
63
-
64
-Labels:
65
-
66
-| Label | Description |
67
-|:-----------|:----------------|
68
-| numa_node | The NUMA node the metrics are associated with. |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| mem.fragmentation_index_dma | order0, order1, order2, order3, order4, order5, order6, order7, order8, order9, order10 | index |
75
-| mem.fragmentation_index_dma32 | order0, order1, order2, order3, order4, order5, order6, order7, order8, order9, order10 | index |
76
-| mem.fragmentation_index_normal | order0, order1, order2, order3, order4, order5, order6, order7, order8, order9, order10 | index |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-There are no alerts configured by default for this integration.
83
-
84
-
52
## Setup
53
54
@@ -140,3 +107,36 @@ sudo ./edit-config netdata.conf
107
There are no configuration examples.
108
109
110
+
111
+## Alerts
112
+
113
+There are no alerts configured by default for this integration.
114
+
115
+
116
+## Metrics
117
+
118
+Metrics grouped by *scope*.
119
+
120
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
121
+
122
+Monitor the overall memory fragmentation of the system.
123
+
124
+### Per node
125
+
126
+Memory fragmentation statistics for each NUMA node in the system.
127
+
128
+Labels:
129
+
130
+| Label | Description |
131
+|:-----------|:----------------|
132
+| numa_node | The NUMA node the metrics are associated with. |
133
+
134
+Metrics:
135
+
136
+| Metric | Dimensions | Unit |
137
+|:------|:----------|:----|
138
+| mem.fragmentation_index_dma | order0, order1, order2, order3, order4, order5, order6, order7, order8, order9, order10 | index |
139
+| mem.fragmentation_index_dma32 | order0, order1, order2, order3, order4, order5, order6, order7, order8, order9, order10 | index |
140
+| mem.fragmentation_index_normal | order0, order1, order2, order3, order4, order5, order6, order7, order8, order9, order10 | index |
141
+
142
+
src/collectors/diskspace.plugin/integrations/disk_space.md
+40
-40
@@ -48,46 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per mount point
60
-
61
-
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| mount_point | Path used to mount a filesystem |
68
-| filesystem | The filesystem used to format a partition. |
69
-| mount_root | Root directory where mount points are present. |
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| disk.space | avail, used, reserved_for_root | GiB |
76
-| disk.inodes | avail, used, reserved_for_root | inodes |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-
83
-The following alerts are available:
84
-
85
-| Alert name | On metric | Description |
86
-|:------------|:----------|:------------|
87
-| [ disk_space_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.space | disk ${label:mount_point} space utilization |
88
-| [ disk_inode_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.inodes | disk ${label:mount_point} inode utilization |
89
-
90
-
51
## Setup
52
53
@@ -148,3 +108,43 @@ sudo ./edit-config netdata.conf
108
There are no configuration examples.
109
110
111
+
112
+## Alerts
113
+
114
+
115
+The following alerts are available:
116
+
117
+| Alert name | On metric | Description |
118
+|:------------|:----------|:------------|
119
+| [ disk_space_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.space | disk ${label:mount_point} space utilization |
120
+| [ disk_inode_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.inodes | disk ${label:mount_point} inode utilization |
121
+
122
+
123
+## Metrics
124
+
125
+Metrics grouped by *scope*.
126
+
127
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
128
+
129
+
130
+
131
+### Per mount point
132
+
133
+
134
+
135
+Labels:
136
+
137
+| Label | Description |
138
+|:-----------|:----------------|
139
+| mount_point | Path used to mount a filesystem |
140
+| filesystem | The filesystem used to format a partition. |
141
+| mount_root | Root directory where mount points are present. |
142
+
143
+Metrics:
144
+
145
+| Metric | Dimensions | Unit |
146
+|:------|:----------|:----|
147
+| disk.space | avail, used, reserved_for_root | GiB |
148
+| disk.inodes | avail, used, reserved_for_root | inodes |
149
+
150
+
src/collectors/ebpf.plugin/integrations/ebpf_cachestat.md
+68
-68
@@ -52,74 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per eBPF Cachestat instance
64
-
65
-These metrics show total number of calls to functions inside kernel.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| mem.cachestat_ratio | ratio | % |
74
-| mem.cachestat_dirties | dirty | page/s |
75
-| mem.cachestat_hits | hit | hits/s |
76
-| mem.cachestat_misses | miss | misses/s |
77
-
78
-### Per apps
79
-
80
-These Metrics show grouped information per apps group.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| app_group | The name of the group defined in the configuration. |
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| app.ebpf_cachestat_hit_ratio | ratio | % |
93
-| app.ebpf_cachestat_dirty_pages | pages | page/s |
94
-| app.ebpf_cachestat_access | hits | hits/s |
95
-| app.ebpf_cachestat_misses | misses | misses/s |
96
-
97
-### Per cgroup
98
-
99
-
100
-
101
-This scope has no labels.
102
-
103
-Metrics:
104
-
105
-| Metric | Dimensions | Unit |
106
-|:------|:----------|:----|
107
-| cgroup.cachestat_ratio | ratio | % |
108
-| cgroup.cachestat_dirties | dirty | page/s |
109
-| cgroup.cachestat_hits | hit | hits/s |
110
-| cgroup.cachestat_misses | miss | misses/s |
111
-| services.cachestat_ratio | a dimension per systemd service | % |
112
-| services.cachestat_dirties | a dimension per systemd service | page/s |
113
-| services.cachestat_hits | a dimension per systemd service | hits/s |
114
-| services.cachestat_misses | a dimension per systemd service | misses/s |
115
-
116
-
117
-
118
-## Alerts
119
-
120
-There are no alerts configured by default for this integration.
121
-
122
-
55
## Setup
56
57
@@ -197,3 +129,71 @@ sudo ./edit-config ebpf.d/cachestat.conf
129
There are no configuration examples.
130
131
132
+
133
+## Alerts
134
+
135
+There are no alerts configured by default for this integration.
136
+
137
+
138
+## Metrics
139
+
140
+Metrics grouped by *scope*.
141
+
142
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
143
+
144
+
145
+
146
+### Per eBPF Cachestat instance
147
+
148
+These metrics show total number of calls to functions inside kernel.
149
+
150
+This scope has no labels.
151
+
152
+Metrics:
153
+
154
+| Metric | Dimensions | Unit |
155
+|:------|:----------|:----|
156
+| mem.cachestat_ratio | ratio | % |
157
+| mem.cachestat_dirties | dirty | page/s |
158
+| mem.cachestat_hits | hit | hits/s |
159
+| mem.cachestat_misses | miss | misses/s |
160
+
161
+### Per apps
162
+
163
+These Metrics show grouped information per apps group.
164
+
165
+Labels:
166
+
167
+| Label | Description |
168
+|:-----------|:----------------|
169
+| app_group | The name of the group defined in the configuration. |
170
+
171
+Metrics:
172
+
173
+| Metric | Dimensions | Unit |
174
+|:------|:----------|:----|
175
+| app.ebpf_cachestat_hit_ratio | ratio | % |
176
+| app.ebpf_cachestat_dirty_pages | pages | page/s |
177
+| app.ebpf_cachestat_access | hits | hits/s |
178
+| app.ebpf_cachestat_misses | misses | misses/s |
179
+
180
+### Per cgroup
181
+
182
+
183
+
184
+This scope has no labels.
185
+
186
+Metrics:
187
+
188
+| Metric | Dimensions | Unit |
189
+|:------|:----------|:----|
190
+| cgroup.cachestat_ratio | ratio | % |
191
+| cgroup.cachestat_dirties | dirty | page/s |
192
+| cgroup.cachestat_hits | hit | hits/s |
193
+| cgroup.cachestat_misses | miss | misses/s |
194
+| services.cachestat_ratio | a dimension per systemd service | % |
195
+| services.cachestat_dirties | a dimension per systemd service | page/s |
196
+| services.cachestat_hits | a dimension per systemd service | hits/s |
197
+| services.cachestat_misses | a dimension per systemd service | misses/s |
198
+
199
+
src/collectors/ebpf.plugin/integrations/ebpf_dcstat.md
+66
-66
@@ -52,72 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per apps
64
-
65
-These Metrics show grouped information per apps group.
66
-
67
-Labels:
68
-
69
-| Label | Description |
70
-|:-----------|:----------------|
71
-| app_group | The name of the group defined in the configuration. |
72
-
73
-Metrics:
74
-
75
-| Metric | Dimensions | Unit |
76
-|:------|:----------|:----|
77
-| app.ebpf_dc_ratio | ratio | % |
78
-| app.ebpf_dc_reference | files | files |
79
-| app.ebpf_dc_not_cache | files | files |
80
-| app.ebpf_dc_not_found | files | files |
81
-
82
-### Per filesystem
83
-
84
-These metrics show total number of calls to functions inside kernel.
85
-
86
-This scope has no labels.
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| filesystem.dc_reference | reference, slow, miss | files |
93
-| filesystem.dc_hit_ratio | ratio | % |
94
-
95
-### Per cgroup
96
-
97
-
98
-
99
-This scope has no labels.
100
-
101
-Metrics:
102
-
103
-| Metric | Dimensions | Unit |
104
-|:------|:----------|:----|
105
-| cgroup.dc_ratio | ratio | % |
106
-| cgroup.dc_reference | reference | files |
107
-| cgroup.dc_not_cache | slow | files |
108
-| cgroup.dc_not_found | miss | files |
109
-| services.dc_ratio | a dimension per systemd service | % |
110
-| services.dc_reference | a dimension per systemd service | files |
111
-| services.dc_not_cache | a dimension per systemd service | files |
112
-| services.dc_not_found | a dimension per systemd service | files |
113
-
114
-
115
-
116
-## Alerts
117
-
118
-There are no alerts configured by default for this integration.
119
-
120
-
55
## Setup
56
57
@@ -195,3 +129,69 @@ sudo ./edit-config ebpf.d/dcstat.conf
129
There are no configuration examples.
130
131
132
+
133
+## Alerts
134
+
135
+There are no alerts configured by default for this integration.
136
+
137
+
138
+## Metrics
139
+
140
+Metrics grouped by *scope*.
141
+
142
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
143
+
144
+
145
+
146
+### Per apps
147
+
148
+These Metrics show grouped information per apps group.
149
+
150
+Labels:
151
+
152
+| Label | Description |
153
+|:-----------|:----------------|
154
+| app_group | The name of the group defined in the configuration. |
155
+
156
+Metrics:
157
+
158
+| Metric | Dimensions | Unit |
159
+|:------|:----------|:----|
160
+| app.ebpf_dc_ratio | ratio | % |
161
+| app.ebpf_dc_reference | files | files |
162
+| app.ebpf_dc_not_cache | files | files |
163
+| app.ebpf_dc_not_found | files | files |
164
+
165
+### Per filesystem
166
+
167
+These metrics show total number of calls to functions inside kernel.
168
+
169
+This scope has no labels.
170
+
171
+Metrics:
172
+
173
+| Metric | Dimensions | Unit |
174
+|:------|:----------|:----|
175
+| filesystem.dc_reference | reference, slow, miss | files |
176
+| filesystem.dc_hit_ratio | ratio | % |
177
+
178
+### Per cgroup
179
+
180
+
181
+
182
+This scope has no labels.
183
+
184
+Metrics:
185
+
186
+| Metric | Dimensions | Unit |
187
+|:------|:----------|:----|
188
+| cgroup.dc_ratio | ratio | % |
189
+| cgroup.dc_reference | reference | files |
190
+| cgroup.dc_not_cache | slow | files |
191
+| cgroup.dc_not_found | miss | files |
192
+| services.dc_ratio | a dimension per systemd service | % |
193
+| services.dc_reference | a dimension per systemd service | files |
194
+| services.dc_not_cache | a dimension per systemd service | files |
195
+| services.dc_not_found | a dimension per systemd service | files |
196
+
197
+
src/collectors/ebpf.plugin/integrations/ebpf_disk.md
+27
-27
@@ -47,33 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
This thread will add overhead every time that an internal kernel function monitored by this thread is called.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per disk
59
-
60
-These metrics measure latency for I/O events on every hard disk present on host.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| disk.latency_io | latency | calls/s |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
50
## Setup
51
52
@@ -150,3 +123,30 @@ sudo ./edit-config ebpf.d/disk.conf
123
There are no configuration examples.
124
125
126
+
127
+## Alerts
128
+
129
+There are no alerts configured by default for this integration.
130
+
131
+
132
+## Metrics
133
+
134
+Metrics grouped by *scope*.
135
+
136
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
137
+
138
+
139
+
140
+### Per disk
141
+
142
+These metrics measure latency for I/O events on every hard disk present on host.
143
+
144
+This scope has no labels.
145
+
146
+Metrics:
147
+
148
+| Metric | Dimensions | Unit |
149
+|:------|:----------|:----|
150
+| disk.latency_io | latency | calls/s |
151
+
152
+
src/collectors/ebpf.plugin/integrations/ebpf_filedescriptor.md
+66
-66
@@ -52,72 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
Depending of kernel version and frequency that files are open and close, this thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per cgroup
64
-
65
-These Metrics show grouped information per cgroup/service.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| cgroup.fd_open | open | calls/s |
74
-| cgroup.fd_open_error | open | calls/s |
75
-| cgroup.fd_closed | close | calls/s |
76
-| cgroup.fd_close_error | close | calls/s |
77
-| services.file_open | a dimension per systemd service | calls/s |
78
-| services.file_open_error | a dimension per systemd service | calls/s |
79
-| services.file_closed | a dimension per systemd service | calls/s |
80
-| services.file_close_error | a dimension per systemd service | calls/s |
81
-
82
-### Per eBPF Filedescriptor instance
83
-
84
-These metrics show total number of calls to functions inside kernel.
85
-
86
-This scope has no labels.
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| filesystem.file_descriptor | open, close | calls/s |
93
-| filesystem.file_error | open, close | calls/s |
94
-
95
-### Per apps
96
-
97
-These Metrics show grouped information per apps group.
98
-
99
-Labels:
100
-
101
-| Label | Description |
102
-|:-----------|:----------------|
103
-| app_group | The name of the group defined in the configuration. |
104
-
105
-Metrics:
106
-
107
-| Metric | Dimensions | Unit |
108
-|:------|:----------|:----|
109
-| app.ebpf_file_open | calls | calls/s |
110
-| app.ebpf_file_open_error | calls | calls/s |
111
-| app.ebpf_file_closed | calls | calls/s |
112
-| app.ebpf_file_close_error | calls | calls/s |
113
-
114
-
115
-
116
-## Alerts
117
-
118
-There are no alerts configured by default for this integration.
119
-
120
-
55
## Setup
56
57
@@ -195,3 +129,69 @@ sudo ./edit-config ebpf.d/fd.conf
129
There are no configuration examples.
130
131
132
+
133
+## Alerts
134
+
135
+There are no alerts configured by default for this integration.
136
+
137
+
138
+## Metrics
139
+
140
+Metrics grouped by *scope*.
141
+
142
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
143
+
144
+
145
+
146
+### Per cgroup
147
+
148
+These Metrics show grouped information per cgroup/service.
149
+
150
+This scope has no labels.
151
+
152
+Metrics:
153
+
154
+| Metric | Dimensions | Unit |
155
+|:------|:----------|:----|
156
+| cgroup.fd_open | open | calls/s |
157
+| cgroup.fd_open_error | open | calls/s |
158
+| cgroup.fd_closed | close | calls/s |
159
+| cgroup.fd_close_error | close | calls/s |
160
+| services.file_open | a dimension per systemd service | calls/s |
161
+| services.file_open_error | a dimension per systemd service | calls/s |
162
+| services.file_closed | a dimension per systemd service | calls/s |
163
+| services.file_close_error | a dimension per systemd service | calls/s |
164
+
165
+### Per eBPF Filedescriptor instance
166
+
167
+These metrics show total number of calls to functions inside kernel.
168
+
169
+This scope has no labels.
170
+
171
+Metrics:
172
+
173
+| Metric | Dimensions | Unit |
174
+|:------|:----------|:----|
175
+| filesystem.file_descriptor | open, close | calls/s |
176
+| filesystem.file_error | open, close | calls/s |
177
+
178
+### Per apps
179
+
180
+These Metrics show grouped information per apps group.
181
+
182
+Labels:
183
+
184
+| Label | Description |
185
+|:-----------|:----------------|
186
+| app_group | The name of the group defined in the configuration. |
187
+
188
+Metrics:
189
+
190
+| Metric | Dimensions | Unit |
191
+|:------|:----------|:----|
192
+| app.ebpf_file_open | calls | calls/s |
193
+| app.ebpf_file_open_error | calls | calls/s |
194
+| app.ebpf_file_closed | calls | calls/s |
195
+| app.ebpf_file_close_error | calls | calls/s |
196
+
197
+
src/collectors/ebpf.plugin/integrations/ebpf_filesystem.md
+53
-53
@@ -47,59 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per filesystem
59
-
60
-Latency charts associate with filesystem actions.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| filesystem.read_latency | latency period | calls/s |
69
-| filesystem.open_latency | latency period | calls/s |
70
-| filesystem.sync_latency | latency period | calls/s |
71
-
72
-### Per iilesystem
73
-
74
-
75
-
76
-This scope has no labels.
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| filesystem.write_latency | latency period | calls/s |
83
-
84
-### Per eBPF Filesystem instance
85
-
86
-
87
-
88
-This scope has no labels.
89
-
90
-Metrics:
91
-
92
-| Metric | Dimensions | Unit |
93
-|:------|:----------|:----|
94
-| filesystem.attributte_latency | latency period | calls/s |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-There are no alerts configured by default for this integration.
101
-
102
-
50
## Setup
51
52
@@ -176,3 +123,56 @@ sudo ./edit-config ebpf.d/filesystem.conf
123
There are no configuration examples.
124
125
126
+
127
+## Alerts
128
+
129
+There are no alerts configured by default for this integration.
130
+
131
+
132
+## Metrics
133
+
134
+Metrics grouped by *scope*.
135
+
136
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
137
+
138
+
139
+
140
+### Per filesystem
141
+
142
+Latency charts associate with filesystem actions.
143
+
144
+This scope has no labels.
145
+
146
+Metrics:
147
+
148
+| Metric | Dimensions | Unit |
149
+|:------|:----------|:----|
150
+| filesystem.read_latency | latency period | calls/s |
151
+| filesystem.open_latency | latency period | calls/s |
152
+| filesystem.sync_latency | latency period | calls/s |
153
+
154
+### Per iilesystem
155
+
156
+
157
+
158
+This scope has no labels.
159
+
160
+Metrics:
161
+
162
+| Metric | Dimensions | Unit |
163
+|:------|:----------|:----|
164
+| filesystem.write_latency | latency period | calls/s |
165
+
166
+### Per eBPF Filesystem instance
167
+
168
+
169
+
170
+This scope has no labels.
171
+
172
+Metrics:
173
+
174
+| Metric | Dimensions | Unit |
175
+|:------|:----------|:----|
176
+| filesystem.attributte_latency | latency period | calls/s |
177
+
178
+
src/collectors/ebpf.plugin/integrations/ebpf_hardirq.md
+27
-27
@@ -47,33 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
This thread will add overhead every time that an internal kernel function monitored by this thread is called.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per eBPF Hardirq instance
59
-
60
-These metrics show latest timestamp for each hardIRQ available on host.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| system.hardirq_latency | hardirq names | milliseconds |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
50
## Setup
51
52
@@ -150,3 +123,30 @@ sudo ./edit-config ebpf.d/hardirq.conf
123
There are no configuration examples.
124
125
126
+
127
+## Alerts
128
+
129
+There are no alerts configured by default for this integration.
130
+
131
+
132
+## Metrics
133
+
134
+Metrics grouped by *scope*.
135
+
136
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
137
+
138
+
139
+
140
+### Per eBPF Hardirq instance
141
+
142
+These metrics show latest timestamp for each hardIRQ available on host.
143
+
144
+This scope has no labels.
145
+
146
+Metrics:
147
+
148
+| Metric | Dimensions | Unit |
149
+|:------|:----------|:----|
150
+| system.hardirq_latency | hardirq names | milliseconds |
151
+
152
+
src/collectors/ebpf.plugin/integrations/ebpf_mdflush.md
+27
-27
@@ -47,33 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
This thread will add overhead every time that `md_flush_request` is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per eBPF MDflush instance
59
-
60
-Number of times md_flush_request was called since last time.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| mdstat.mdstat_flush | disk | flushes |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
50
## Setup
51
52
@@ -145,3 +118,30 @@ sudo ./edit-config ebpf.d/mdflush.conf
118
There are no configuration examples.
119
120
121
+
122
+## Alerts
123
+
124
+There are no alerts configured by default for this integration.
125
+
126
+
127
+## Metrics
128
+
129
+Metrics grouped by *scope*.
130
+
131
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
132
+
133
+
134
+
135
+### Per eBPF MDflush instance
136
+
137
+Number of times md_flush_request was called since last time.
138
+
139
+This scope has no labels.
140
+
141
+Metrics:
142
+
143
+| Metric | Dimensions | Unit |
144
+|:------|:----------|:----|
145
+| mdstat.mdstat_flush | disk | flushes |
146
+
147
+
src/collectors/ebpf.plugin/integrations/ebpf_mount.md
+28
-28
@@ -47,34 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per eBPF Mount instance
59
-
60
-Calls for syscalls mount an umount.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| mount_points.call | mount, umount | calls/s |
69
-| mount_points.error | mount, umount | calls/s |
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
50
## Setup
51
52
@@ -153,3 +125,31 @@ sudo ./edit-config ebpf.d/mount.conf
125
There are no configuration examples.
126
127
128
+
129
+## Alerts
130
+
131
+There are no alerts configured by default for this integration.
132
+
133
+
134
+## Metrics
135
+
136
+Metrics grouped by *scope*.
137
+
138
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
139
+
140
+
141
+
142
+### Per eBPF Mount instance
143
+
144
+Calls for syscalls mount an umount.
145
+
146
+This scope has no labels.
147
+
148
+Metrics:
149
+
150
+| Metric | Dimensions | Unit |
151
+|:------|:----------|:----|
152
+| mount_points.call | mount, umount | calls/s |
153
+| mount_points.error | mount, umount | calls/s |
154
+
155
+
src/collectors/ebpf.plugin/integrations/ebpf_oomkill.md
+44
-44
@@ -52,50 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per cgroup
64
-
65
-These metrics show cgroup/service that reached OOM.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| cgroup.oomkills | cgroup name | kills |
74
-| services.oomkills | a dimension per systemd service | kills |
75
-
76
-### Per apps
77
-
78
-These metrics show cgroup/service that reached OOM.
79
-
80
-Labels:
81
-
82
-| Label | Description |
83
-|:-----------|:----------------|
84
-| app_group | The name of the group defined in the configuration. |
85
-
86
-Metrics:
87
-
88
-| Metric | Dimensions | Unit |
89
-|:------|:----------|:----|
90
-| app.oomkill | kills | kills |
91
-
92
-
93
-
94
-## Alerts
95
-
96
-There are no alerts configured by default for this integration.
97
-
98
-
55
## Setup
56
57
@@ -160,6 +116,50 @@ There are no configuration examples.
116
117
118
119
+## Alerts
120
+
121
+There are no alerts configured by default for this integration.
122
+
123
+
124
+## Metrics
125
+
126
+Metrics grouped by *scope*.
127
+
128
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
129
+
130
+
131
+
132
+### Per cgroup
133
+
134
+These metrics show cgroup/service that reached OOM.
135
+
136
+This scope has no labels.
137
+
138
+Metrics:
139
+
140
+| Metric | Dimensions | Unit |
141
+|:------|:----------|:----|
142
+| cgroup.oomkills | cgroup name | kills |
143
+| services.oomkills | a dimension per systemd service | kills |
144
+
145
+### Per apps
146
+
147
+These metrics show cgroup/service that reached OOM.
148
+
149
+Labels:
150
+
151
+| Label | Description |
152
+|:-----------|:----------------|
153
+| app_group | The name of the group defined in the configuration. |
154
+
155
+Metrics:
156
+
157
+| Metric | Dimensions | Unit |
158
+|:------|:----------|:----|
159
+| app.oomkill | kills | kills |
160
+
161
+
162
+
163
## Troubleshooting
164
165
### update every
src/collectors/ebpf.plugin/integrations/ebpf_process.md
+32
-32
@@ -46,67 +46,67 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
49
+## Setup
50
51
-Metrics grouped by *scope*.
51
53
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
+### Prerequisites
53
54
+#### Netdata flags.
55
56
+To have these charts you need to compile netdata with flag `NETDATA_DEV_MODE`.
57
57
-### Per eBPF Process instance
58
59
-How plugin is allocating memory.
59
+### Configuration
60
61
-This scope has no labels.
61
+#### Options
62
63
-Metrics:
63
65
-| Metric | Dimensions | Unit |
66
-|:------|:----------|:----|
67
-| netdata.ebpf_aral_stat_size | memory | bytes |
68
-| netdata.ebpf_aral_stat_alloc | aral | calls |
69
-| netdata.ebpf_threads | total, running | threads |
70
-| netdata.ebpf_pids | user, kernel | pids |
71
-| netdata.ebpf_load_methods | legacy, co-re | methods |
72
-| netdata.ebpf_kernel_memory | memory_locked | bytes |
73
-| netdata.ebpf_hash_tables_count | hash_table | hash tables |
74
-| netdata.ebpf_hash_tables_insert_pid_elements | thread | rows |
75
-| netdata.ebpf_hash_tables_remove_pid_elements | thread | rows |
76
-| netdata.ebpf_ipc_usage | positions | % |
64
65
+There are no configuration options.
66
67
80
-## Alerts
68
82
-There are no alerts configured by default for this integration.
69
+#### via File
70
71
+There is no configuration file.
72
85
-## Setup
73
+##### Examples
74
+There are no configuration examples.
75
76
88
-### Prerequisites
77
90
-#### Netdata flags.
78
+## Alerts
79
92
-To have these charts you need to compile netdata with flag `NETDATA_DEV_MODE`.
80
+There are no alerts configured by default for this integration.
81
82
95
-### Configuration
83
+## Metrics
84
97
-#### Options
85
+Metrics grouped by *scope*.
86
87
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
88
89
101
-There are no configuration options.
90
91
+### Per eBPF Process instance
92
93
+How plugin is allocating memory.
94
105
-#### via File
95
+This scope has no labels.
96
107
-There is no configuration file.
97
+Metrics:
98
109
-##### Examples
110
-There are no configuration examples.
99
+| Metric | Dimensions | Unit |
100
+|:------|:----------|:----|
101
+| netdata.ebpf_aral_stat_size | memory | bytes |
102
+| netdata.ebpf_aral_stat_alloc | aral | calls |
103
+| netdata.ebpf_threads | total, running | threads |
104
+| netdata.ebpf_pids | user, kernel | pids |
105
+| netdata.ebpf_load_methods | legacy, co-re | methods |
106
+| netdata.ebpf_kernel_memory | memory_locked | bytes |
107
+| netdata.ebpf_hash_tables_count | hash_table | hash tables |
108
+| netdata.ebpf_hash_tables_insert_pid_elements | thread | rows |
109
+| netdata.ebpf_hash_tables_remove_pid_elements | thread | rows |
110
+| netdata.ebpf_ipc_usage | positions | % |
111
112
src/collectors/ebpf.plugin/integrations/ebpf_processes.md
+71
-71
@@ -52,77 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per eBPF Processes instance
64
-
65
-These metrics show total number of calls to functions inside kernel.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| system.process_thread | process | calls/s |
74
-| system.process_status | process, zombie | difference |
75
-| system.exit | process | calls/s |
76
-| system.task_error | task | calls/s |
77
-
78
-### Per apps
79
-
80
-These Metrics show grouped information per apps group.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| app_group | The name of the group defined in the configuration. |
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| app.process_create | calls | calls/s |
93
-| app.thread_create | call | calls/s |
94
-| app.task_exit | call | calls/s |
95
-| app.task_close | call | calls/s |
96
-| app.task_error | app | calls/s |
97
-
98
-### Per cgroup
99
-
100
-These Metrics show grouped information per cgroup/service.
101
-
102
-This scope has no labels.
103
-
104
-Metrics:
105
-
106
-| Metric | Dimensions | Unit |
107
-|:------|:----------|:----|
108
-| cgroup.process_create | process | calls/s |
109
-| cgroup.thread_create | thread | calls/s |
110
-| cgroup.task_exit | exit | calls/s |
111
-| cgroup.task_close | process | calls/s |
112
-| cgroup.task_error | process | calls/s |
113
-| services.process_create | a dimension per systemd service | calls/s |
114
-| services.thread_create | a dimension per systemd service | calls/s |
115
-| services.task_close | a dimension per systemd service | calls/s |
116
-| services.task_exit | a dimension per systemd service | calls/s |
117
-| services.task_error | a dimension per systemd service | calls/s |
118
-
119
-
120
-
121
-## Alerts
122
-
123
-There are no alerts configured by default for this integration.
124
-
125
-
55
## Setup
56
57
@@ -205,3 +134,74 @@ sudo ./edit-config ebpf.d/process.conf
134
There are no configuration examples.
135
136
137
+
138
+## Alerts
139
+
140
+There are no alerts configured by default for this integration.
141
+
142
+
143
+## Metrics
144
+
145
+Metrics grouped by *scope*.
146
+
147
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
148
+
149
+
150
+
151
+### Per eBPF Processes instance
152
+
153
+These metrics show total number of calls to functions inside kernel.
154
+
155
+This scope has no labels.
156
+
157
+Metrics:
158
+
159
+| Metric | Dimensions | Unit |
160
+|:------|:----------|:----|
161
+| system.process_thread | process | calls/s |
162
+| system.process_status | process, zombie | difference |
163
+| system.exit | process | calls/s |
164
+| system.task_error | task | calls/s |
165
+
166
+### Per apps
167
+
168
+These Metrics show grouped information per apps group.
169
+
170
+Labels:
171
+
172
+| Label | Description |
173
+|:-----------|:----------------|
174
+| app_group | The name of the group defined in the configuration. |
175
+
176
+Metrics:
177
+
178
+| Metric | Dimensions | Unit |
179
+|:------|:----------|:----|
180
+| app.process_create | calls | calls/s |
181
+| app.thread_create | call | calls/s |
182
+| app.task_exit | call | calls/s |
183
+| app.task_close | call | calls/s |
184
+| app.task_error | app | calls/s |
185
+
186
+### Per cgroup
187
+
188
+These Metrics show grouped information per cgroup/service.
189
+
190
+This scope has no labels.
191
+
192
+Metrics:
193
+
194
+| Metric | Dimensions | Unit |
195
+|:------|:----------|:----|
196
+| cgroup.process_create | process | calls/s |
197
+| cgroup.thread_create | thread | calls/s |
198
+| cgroup.task_exit | exit | calls/s |
199
+| cgroup.task_close | process | calls/s |
200
+| cgroup.task_error | process | calls/s |
201
+| services.process_create | a dimension per systemd service | calls/s |
202
+| services.thread_create | a dimension per systemd service | calls/s |
203
+| services.task_close | a dimension per systemd service | calls/s |
204
+| services.task_exit | a dimension per systemd service | calls/s |
205
+| services.task_error | a dimension per systemd service | calls/s |
206
+
207
+
src/collectors/ebpf.plugin/integrations/ebpf_shm.md
+65
-65
@@ -52,71 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per cgroup
64
-
65
-These Metrics show grouped information per cgroup/service.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| cgroup.shmget | get | calls/s |
74
-| cgroup.shmat | at | calls/s |
75
-| cgroup.shmdt | dt | calls/s |
76
-| cgroup.shmctl | ctl | calls/s |
77
-| services.shmget | a dimension per systemd service | calls/s |
78
-| services.shmat | a dimension per systemd service | calls/s |
79
-| services.shmdt | a dimension per systemd service | calls/s |
80
-| services.shmctl | a dimension per systemd service | calls/s |
81
-
82
-### Per apps
83
-
84
-These Metrics show grouped information per apps group.
85
-
86
-Labels:
87
-
88
-| Label | Description |
89
-|:-----------|:----------------|
90
-| app_group | The name of the group defined in the configuration. |
91
-
92
-Metrics:
93
-
94
-| Metric | Dimensions | Unit |
95
-|:------|:----------|:----|
96
-| app.ebpf_shmget_call | calls | calls/s |
97
-| app.ebpf_shmat_call | calls | calls/s |
98
-| app.ebpf_shmdt_call | calls | calls/s |
99
-| app.ebpf_shmctl_call | calls | calls/s |
100
-
101
-### Per eBPF SHM instance
102
-
103
-These Metrics show number of calls for specified syscall.
104
-
105
-This scope has no labels.
106
-
107
-Metrics:
108
-
109
-| Metric | Dimensions | Unit |
110
-|:------|:----------|:----|
111
-| system.shared_memory_calls | get, at, dt, ctl | calls/s |
112
-
113
-
114
-
115
-## Alerts
116
-
117
-There are no alerts configured by default for this integration.
118
-
119
-
55
## Setup
56
57
@@ -203,3 +138,68 @@ sudo ./edit-config ebpf.d/shm.conf
138
There are no configuration examples.
139
140
141
+
142
+## Alerts
143
+
144
+There are no alerts configured by default for this integration.
145
+
146
+
147
+## Metrics
148
+
149
+Metrics grouped by *scope*.
150
+
151
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
152
+
153
+
154
+
155
+### Per cgroup
156
+
157
+These Metrics show grouped information per cgroup/service.
158
+
159
+This scope has no labels.
160
+
161
+Metrics:
162
+
163
+| Metric | Dimensions | Unit |
164
+|:------|:----------|:----|
165
+| cgroup.shmget | get | calls/s |
166
+| cgroup.shmat | at | calls/s |
167
+| cgroup.shmdt | dt | calls/s |
168
+| cgroup.shmctl | ctl | calls/s |
169
+| services.shmget | a dimension per systemd service | calls/s |
170
+| services.shmat | a dimension per systemd service | calls/s |
171
+| services.shmdt | a dimension per systemd service | calls/s |
172
+| services.shmctl | a dimension per systemd service | calls/s |
173
+
174
+### Per apps
175
+
176
+These Metrics show grouped information per apps group.
177
+
178
+Labels:
179
+
180
+| Label | Description |
181
+|:-----------|:----------------|
182
+| app_group | The name of the group defined in the configuration. |
183
+
184
+Metrics:
185
+
186
+| Metric | Dimensions | Unit |
187
+|:------|:----------|:----|
188
+| app.ebpf_shmget_call | calls | calls/s |
189
+| app.ebpf_shmat_call | calls | calls/s |
190
+| app.ebpf_shmdt_call | calls | calls/s |
191
+| app.ebpf_shmctl_call | calls | calls/s |
192
+
193
+### Per eBPF SHM instance
194
+
195
+These Metrics show number of calls for specified syscall.
196
+
197
+This scope has no labels.
198
+
199
+Metrics:
200
+
201
+| Metric | Dimensions | Unit |
202
+|:------|:----------|:----|
203
+| system.shared_memory_calls | get, at, dt, ctl | calls/s |
204
+
205
+
src/collectors/ebpf.plugin/integrations/ebpf_socket.md
+85
-85
@@ -52,91 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per eBPF Socket instance
64
-
65
-These metrics show total number of calls to functions inside kernel.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| ip.inbound_conn | connection_tcp | connections/s |
74
-| ip.tcp_outbound_conn | received | connections/s |
75
-| ip.tcp_functions | received, send, closed | calls/s |
76
-| ip.total_tcp_bandwidth | received, send | kilobits/s |
77
-| ip.tcp_error | received, send | calls/s |
78
-| ip.tcp_retransmit | retransmited | calls/s |
79
-| ip.udp_functions | received, send | calls/s |
80
-| ip.total_udp_bandwidth | received, send | kilobits/s |
81
-| ip.udp_error | received, send | calls/s |
82
-
83
-### Per apps
84
-
85
-These metrics show grouped information per apps group.
86
-
87
-Labels:
88
-
89
-| Label | Description |
90
-|:-----------|:----------------|
91
-| app_group | The name of the group defined in the configuration. |
92
-
93
-Metrics:
94
-
95
-| Metric | Dimensions | Unit |
96
-|:------|:----------|:----|
97
-| app.ebpf_call_tcp_v4_connection | connections | connections/s |
98
-| app.ebpf_call_tcp_v6_connection | connections | connections/s |
99
-| app.ebpf_sock_total_bandwidth | received, sent | kilobits/s |
100
-| app.ebpf_call_tcp_sendmsg | calls | calls/s |
101
-| app.ebpf_call_tcp_cleanup_rbuf | calls | calls/s |
102
-| app.ebpf_call_tcp_retransmit | calls | calls/s |
103
-| app.ebpf_call_udp_sendmsg | calls | calls/s |
104
-| app.ebpf_call_udp_recvmsg | calls | calls/s |
105
-
106
-### Per cgroup
107
-
108
-
109
-
110
-This scope has no labels.
111
-
112
-Metrics:
113
-
114
-| Metric | Dimensions | Unit |
115
-|:------|:----------|:----|
116
-| cgroup.net_conn_ipv4 | connections | connections/s |
117
-| cgroup.net_conn_ipv6 | connections | connections/s |
118
-| cgroup.net_total_bandwidth | received, sent | kilobits/s |
119
-| cgroup.net_tcp_recv | calls | calls/s |
120
-| cgroup.net_tcp_send | calls | calls/s |
121
-| cgroup.net_retransmit | calls | calls/s |
122
-| cgroup.net_udp_send | calls | calls/s |
123
-| cgroup.net_udp_recv | calls | calls/s |
124
-| services.net_conn_ipv4 | connections | connections/s |
125
-| services.net_conn_ipv6 | connections | connections/s |
126
-| services.net_total_bandwidth | received, sent | kilobits/s |
127
-| services.net_tcp_recv | calls | calls/s |
128
-| services.net_tcp_send | calls | calls/s |
129
-| services.net_tcp_retransmit | calls | calls/s |
130
-| services.net_udp_send | calls | calls/s |
131
-| services.net_udp_recv | calls | calls/s |
132
-
133
-
134
-
135
-## Alerts
136
-
137
-There are no alerts configured by default for this integration.
138
-
139
-
55
## Setup
56
57
@@ -217,3 +132,88 @@ sudo ./edit-config ebpf.d/network.conf
132
There are no configuration examples.
133
134
135
+
136
+## Alerts
137
+
138
+There are no alerts configured by default for this integration.
139
+
140
+
141
+## Metrics
142
+
143
+Metrics grouped by *scope*.
144
+
145
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
146
+
147
+
148
+
149
+### Per eBPF Socket instance
150
+
151
+These metrics show total number of calls to functions inside kernel.
152
+
153
+This scope has no labels.
154
+
155
+Metrics:
156
+
157
+| Metric | Dimensions | Unit |
158
+|:------|:----------|:----|
159
+| ip.inbound_conn | connection_tcp | connections/s |
160
+| ip.tcp_outbound_conn | received | connections/s |
161
+| ip.tcp_functions | received, send, closed | calls/s |
162
+| ip.total_tcp_bandwidth | received, send | kilobits/s |
163
+| ip.tcp_error | received, send | calls/s |
164
+| ip.tcp_retransmit | retransmited | calls/s |
165
+| ip.udp_functions | received, send | calls/s |
166
+| ip.total_udp_bandwidth | received, send | kilobits/s |
167
+| ip.udp_error | received, send | calls/s |
168
+
169
+### Per apps
170
+
171
+These metrics show grouped information per apps group.
172
+
173
+Labels:
174
+
175
+| Label | Description |
176
+|:-----------|:----------------|
177
+| app_group | The name of the group defined in the configuration. |
178
+
179
+Metrics:
180
+
181
+| Metric | Dimensions | Unit |
182
+|:------|:----------|:----|
183
+| app.ebpf_call_tcp_v4_connection | connections | connections/s |
184
+| app.ebpf_call_tcp_v6_connection | connections | connections/s |
185
+| app.ebpf_sock_total_bandwidth | received, sent | kilobits/s |
186
+| app.ebpf_call_tcp_sendmsg | calls | calls/s |
187
+| app.ebpf_call_tcp_cleanup_rbuf | calls | calls/s |
188
+| app.ebpf_call_tcp_retransmit | calls | calls/s |
189
+| app.ebpf_call_udp_sendmsg | calls | calls/s |
190
+| app.ebpf_call_udp_recvmsg | calls | calls/s |
191
+
192
+### Per cgroup
193
+
194
+
195
+
196
+This scope has no labels.
197
+
198
+Metrics:
199
+
200
+| Metric | Dimensions | Unit |
201
+|:------|:----------|:----|
202
+| cgroup.net_conn_ipv4 | connections | connections/s |
203
+| cgroup.net_conn_ipv6 | connections | connections/s |
204
+| cgroup.net_total_bandwidth | received, sent | kilobits/s |
205
+| cgroup.net_tcp_recv | calls | calls/s |
206
+| cgroup.net_tcp_send | calls | calls/s |
207
+| cgroup.net_retransmit | calls | calls/s |
208
+| cgroup.net_udp_send | calls | calls/s |
209
+| cgroup.net_udp_recv | calls | calls/s |
210
+| services.net_conn_ipv4 | connections | connections/s |
211
+| services.net_conn_ipv6 | connections | connections/s |
212
+| services.net_total_bandwidth | received, sent | kilobits/s |
213
+| services.net_tcp_recv | calls | calls/s |
214
+| services.net_tcp_send | calls | calls/s |
215
+| services.net_tcp_retransmit | calls | calls/s |
216
+| services.net_udp_send | calls | calls/s |
217
+| services.net_udp_recv | calls | calls/s |
218
+
219
+
src/collectors/ebpf.plugin/integrations/ebpf_softirq.md
+27
-27
@@ -47,33 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
This thread will add overhead every time that an internal kernel function monitored by this thread is called.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per eBPF SoftIRQ instance
59
-
60
-These metrics show latest timestamp for each softIRQ available on host.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| system.softirq_latency | soft IRQs | milliseconds |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
50
## Setup
51
52
@@ -150,3 +123,30 @@ sudo ./edit-config ebpf.d/softirq.conf
123
There are no configuration examples.
124
125
126
+
127
+## Alerts
128
+
129
+There are no alerts configured by default for this integration.
130
+
131
+
132
+## Metrics
133
+
134
+Metrics grouped by *scope*.
135
+
136
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
137
+
138
+
139
+
140
+### Per eBPF SoftIRQ instance
141
+
142
+These metrics show latest timestamp for each softIRQ available on host.
143
+
144
+This scope has no labels.
145
+
146
+Metrics:
147
+
148
+| Metric | Dimensions | Unit |
149
+|:------|:----------|:----|
150
+| system.softirq_latency | soft IRQs | milliseconds |
151
+
152
+
src/collectors/ebpf.plugin/integrations/ebpf_swap.md
+59
-59
@@ -52,65 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per cgroup
64
-
65
-These Metrics show grouped information per cgroup/service.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| cgroup.swap_read | read | calls/s |
74
-| cgroup.swap_write | write | calls/s |
75
-| services.swap_read | a dimension per systemd service | calls/s |
76
-| services.swap_write | a dimension per systemd service | calls/s |
77
-
78
-### Per apps
79
-
80
-These Metrics show grouped information per apps group.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| app_group | The name of the group defined in the configuration. |
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| app.ebpf_call_swap_readpage | a dimension per app group | calls/s |
93
-| app.ebpf_call_swap_writepage | a dimension per app group | calls/s |
94
-
95
-### Per eBPF SWAP instance
96
-
97
-These metrics show total number of calls to functions inside kernel.
98
-
99
-This scope has no labels.
100
-
101
-Metrics:
102
-
103
-| Metric | Dimensions | Unit |
104
-|:------|:----------|:----|
105
-| mem.swapcalls | write, read | calls/s |
106
-
107
-
108
-
109
-## Alerts
110
-
111
-There are no alerts configured by default for this integration.
112
-
113
-
55
## Setup
56
57
@@ -188,3 +129,62 @@ sudo ./edit-config ebpf.d/swap.conf
129
There are no configuration examples.
130
131
132
+
133
+## Alerts
134
+
135
+There are no alerts configured by default for this integration.
136
+
137
+
138
+## Metrics
139
+
140
+Metrics grouped by *scope*.
141
+
142
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
143
+
144
+
145
+
146
+### Per cgroup
147
+
148
+These Metrics show grouped information per cgroup/service.
149
+
150
+This scope has no labels.
151
+
152
+Metrics:
153
+
154
+| Metric | Dimensions | Unit |
155
+|:------|:----------|:----|
156
+| cgroup.swap_read | read | calls/s |
157
+| cgroup.swap_write | write | calls/s |
158
+| services.swap_read | a dimension per systemd service | calls/s |
159
+| services.swap_write | a dimension per systemd service | calls/s |
160
+
161
+### Per apps
162
+
163
+These Metrics show grouped information per apps group.
164
+
165
+Labels:
166
+
167
+| Label | Description |
168
+|:-----------|:----------------|
169
+| app_group | The name of the group defined in the configuration. |
170
+
171
+Metrics:
172
+
173
+| Metric | Dimensions | Unit |
174
+|:------|:----------|:----|
175
+| app.ebpf_call_swap_readpage | a dimension per app group | calls/s |
176
+| app.ebpf_call_swap_writepage | a dimension per app group | calls/s |
177
+
178
+### Per eBPF SWAP instance
179
+
180
+These metrics show total number of calls to functions inside kernel.
181
+
182
+This scope has no labels.
183
+
184
+Metrics:
185
+
186
+| Metric | Dimensions | Unit |
187
+|:------|:----------|:----|
188
+| mem.swapcalls | write, read | calls/s |
189
+
190
+
src/collectors/ebpf.plugin/integrations/ebpf_sync.md
+35
-35
@@ -47,41 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per eBPF Sync instance
59
-
60
-These metrics show total number of calls to functions inside kernel.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| mem.file_sync | fsync, fdatasync | calls/s |
69
-| mem.memory_map | msync | calls/s |
70
-| mem.sync | sync, syncfs | calls/s |
71
-| mem.file_segment | sync_file_range | calls/s |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-
78
-The following alerts are available:
79
-
80
-| Alert name | On metric | Description |
81
-|:------------|:----------|:------------|
82
-| [ sync_freq ](https://github.com/netdata/netdata/blob/master/src/health/health.d/synchronization.conf) | mem.sync | number of sync() system calls. Every call causes all pending modifications to filesystem metadata and cached file data to be written to the underlying filesystems. |
83
-
84
-
50
## Setup
51
52
@@ -170,3 +135,38 @@ sudo ./edit-config ebpf.d/sync.conf
135
There are no configuration examples.
136
137
138
+
139
+## Alerts
140
+
141
+
142
+The following alerts are available:
143
+
144
+| Alert name | On metric | Description |
145
+|:------------|:----------|:------------|
146
+| [ sync_freq ](https://github.com/netdata/netdata/blob/master/src/health/health.d/synchronization.conf) | mem.sync | number of sync() system calls. Every call causes all pending modifications to filesystem metadata and cached file data to be written to the underlying filesystems. |
147
+
148
+
149
+## Metrics
150
+
151
+Metrics grouped by *scope*.
152
+
153
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
154
+
155
+
156
+
157
+### Per eBPF Sync instance
158
+
159
+These metrics show total number of calls to functions inside kernel.
160
+
161
+This scope has no labels.
162
+
163
+Metrics:
164
+
165
+| Metric | Dimensions | Unit |
166
+|:------|:----------|:----|
167
+| mem.file_sync | fsync, fdatasync | calls/s |
168
+| mem.memory_map | msync | calls/s |
169
+| mem.sync | sync, syncfs | calls/s |
170
+| mem.file_segment | sync_file_range | calls/s |
171
+
172
+
src/collectors/ebpf.plugin/integrations/ebpf_vfs.md
+83
-83
@@ -52,6 +52,89 @@ The default configuration for this integration does not impose any limits on dat
52
53
This thread will add overhead every time that an internal kernel function monitored by this thread is called. The estimated additional period of time is between 90-200ms per call on kernels that do not have BTF technology.
54
55
+## Setup
56
+
57
+
58
+### Prerequisites
59
+
60
+#### Compile kernel
61
+
62
+Check if your kernel was compiled with necessary options (CONFIG_KPROBES, CONFIG_BPF, CONFIG_BPF_SYSCALL, CONFIG_BPF_JIT) in `/proc/config.gz` or inside /boot/config file. Some cited names can be different accoring preferences of Linux distributions.
63
+When you do not have options set, it is necessary to get the kernel source code from https://kernel.org or a kernel package from your distribution, this last is preferred. The kernel compilation has a well definedd pattern, but distributions can deliver their configuration files
64
+with different names.
65
+
66
+Now follow steps:
67
+1. Copy the configuration file to /usr/src/linux/.config.
68
+2. Select the necessary options: make oldconfig
69
+3. Compile your kernel image: make bzImage
70
+4. Compile your modules: make modules
71
+5. Copy your new kernel image for boot loader directory
72
+6. Install the new modules: make modules_install
73
+7. Generate an initial ramdisk image (`initrd`) if it is necessary.
74
+8. Update your boot loader
75
+
76
+
77
+
78
+### Configuration
79
+
80
+#### Options
81
+
82
+All options are defined inside section `[global]`.
83
+
84
+
85
+<details open><summary>Config options</summary>
86
+
87
+
88
+
89
+| Option | Description | Default | Required |
90
+|:-----|:------------|:--------|:---------:|
91
+| update every | Data collection frequency. | 10 | no |
92
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
93
+| apps | Enable or disable integration with apps.plugin | no | no |
94
+| cgroups | Enable or disable integration with cgroup.plugin | no | no |
95
+| pid table size | Number of elements stored inside hash tables used to monitor calls per PID. | 32768 | no |
96
+| ebpf type format | Define the file type to load an eBPF program. Three options are available: `legacy` (Attach only `kprobe`), `co-re` (Plugin tries to use `trampoline` when available), and `auto` (plugin check OS configuration before to load). | auto | no |
97
+| ebpf co-re tracing | Select the attach method used by plugin when `co-re` is defined in previous option. Two options are available: `trampoline` (Option with lowest overhead), and `probe` (the same of legacy code). | trampoline | no |
98
+| maps per core | Define how plugin will load their hash maps. When enabled (`yes`) plugin will load one hash table per core, instead to have centralized information. | yes | no |
99
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
100
+
101
+
102
+</details>
103
+
104
+
105
+
106
+#### via File
107
+
108
+The configuration file name for this integration is `ebpf.d/vfs.conf`.
109
+
110
+The file format is a modified INI syntax. The general structure is:
111
+
112
+```ini
113
+[section1]
114
+ option1 = some value
115
+ option2 = some other value
116
+
117
+[section2]
118
+ option3 = some third value
119
+```
120
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
121
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
122
+
123
+```bash
124
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
125
+sudo ./edit-config ebpf.d/vfs.conf
126
+```
127
+
128
+##### Examples
129
+There are no configuration examples.
130
+
131
+
132
+
133
+## Alerts
134
+
135
+There are no alerts configured by default for this integration.
136
+
137
+
138
## Metrics
139
140
Metrics grouped by *scope*.
@@ -147,86 +230,3 @@ Metrics:
230
| app.ebpf_call_vfs_create_error | calls | calls/s |
231
232
150
-
151
-## Alerts
152
-
153
-There are no alerts configured by default for this integration.
154
-
155
-
156
-## Setup
157
-
158
-
159
-### Prerequisites
160
-
161
-#### Compile kernel
162
-
163
-Check if your kernel was compiled with necessary options (CONFIG_KPROBES, CONFIG_BPF, CONFIG_BPF_SYSCALL, CONFIG_BPF_JIT) in `/proc/config.gz` or inside /boot/config file. Some cited names can be different accoring preferences of Linux distributions.
164
-When you do not have options set, it is necessary to get the kernel source code from https://kernel.org or a kernel package from your distribution, this last is preferred. The kernel compilation has a well definedd pattern, but distributions can deliver their configuration files
165
-with different names.
166
-
167
-Now follow steps:
168
-1. Copy the configuration file to /usr/src/linux/.config.
169
-2. Select the necessary options: make oldconfig
170
-3. Compile your kernel image: make bzImage
171
-4. Compile your modules: make modules
172
-5. Copy your new kernel image for boot loader directory
173
-6. Install the new modules: make modules_install
174
-7. Generate an initial ramdisk image (`initrd`) if it is necessary.
175
-8. Update your boot loader
176
-
177
-
178
-
179
-### Configuration
180
-
181
-#### Options
182
-
183
-All options are defined inside section `[global]`.
184
-
185
-
186
-<details open><summary>Config options</summary>
187
-
188
-
189
-
190
-| Option | Description | Default | Required |
191
-|:-----|:------------|:--------|:---------:|
192
-| update every | Data collection frequency. | 10 | no |
193
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
194
-| apps | Enable or disable integration with apps.plugin | no | no |
195
-| cgroups | Enable or disable integration with cgroup.plugin | no | no |
196
-| pid table size | Number of elements stored inside hash tables used to monitor calls per PID. | 32768 | no |
197
-| ebpf type format | Define the file type to load an eBPF program. Three options are available: `legacy` (Attach only `kprobe`), `co-re` (Plugin tries to use `trampoline` when available), and `auto` (plugin check OS configuration before to load). | auto | no |
198
-| ebpf co-re tracing | Select the attach method used by plugin when `co-re` is defined in previous option. Two options are available: `trampoline` (Option with lowest overhead), and `probe` (the same of legacy code). | trampoline | no |
199
-| maps per core | Define how plugin will load their hash maps. When enabled (`yes`) plugin will load one hash table per core, instead to have centralized information. | yes | no |
200
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
201
-
202
-
203
-</details>
204
-
205
-
206
-
207
-#### via File
208
-
209
-The configuration file name for this integration is `ebpf.d/vfs.conf`.
210
-
211
-The file format is a modified INI syntax. The general structure is:
212
-
213
-```ini
214
-[section1]
215
- option1 = some value
216
- option2 = some other value
217
-
218
-[section2]
219
- option3 = some third value
220
-```
221
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
222
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
223
-
224
-```bash
225
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
226
-sudo ./edit-config ebpf.d/vfs.conf
227
-```
228
-
229
-##### Examples
230
-There are no configuration examples.
231
-
232
-
src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md
+27
-27
@@ -43,33 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per dev.cpu.0.freq instance
55
-
56
-The metric shows status of CPU frequency, it is direct affected by system load.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| cpu.scaling_cur_freq | frequency | MHz |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-There are no alerts configured by default for this integration.
71
-
72
-
46
## Setup
47
48
@@ -114,3 +87,30 @@ sudo ./edit-config Config options
87
There are no configuration examples.
88
89
90
+
91
+## Alerts
92
+
93
+There are no alerts configured by default for this integration.
94
+
95
+
96
+## Metrics
97
+
98
+Metrics grouped by *scope*.
99
+
100
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
101
+
102
+
103
+
104
+### Per dev.cpu.0.freq instance
105
+
106
+The metric shows status of CPU frequency, it is direct affected by system load.
107
+
108
+This scope has no labels.
109
+
110
+Metrics:
111
+
112
+| Metric | Dimensions | Unit |
113
+|:------|:----------|:----|
114
+| cpu.scaling_cur_freq | frequency | MHz |
115
+
116
+
src/collectors/freebsd.plugin/integrations/dev.cpu.temperature.md
+27
-27
@@ -43,33 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per dev.cpu.temperature instance
55
-
56
-This metric show latest CPU temperature.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| cpu.temperature | a dimension per core | Celsius |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-There are no alerts configured by default for this integration.
71
-
72
-
46
## Setup
47
48
@@ -123,3 +96,30 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per dev.cpu.temperature instance
114
+
115
+This metric show latest CPU temperature.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| cpu.temperature | a dimension per core | Celsius |
124
+
125
+
src/collectors/freebsd.plugin/integrations/devstat.md
+51
-51
@@ -43,57 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per devstat instance
55
-
56
-These metrics give a general vision about I/O events on disks.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.io | io, out | KiB/s |
65
-
66
-### Per disk
67
-
68
-
69
-
70
-This scope has no labels.
71
-
72
-Metrics:
73
-
74
-| Metric | Dimensions | Unit |
75
-|:------|:----------|:----|
76
-| disk.io | reads, writes, frees | KiB/s |
77
-| disk.ops | reads, writes, other, frees | operations/s |
78
-| disk.qops | operations | operations |
79
-| disk.util | utilization | % of time working |
80
-| disk.iotime | reads, writes, other, frees | milliseconds/s |
81
-| disk.await | reads, writes, other, frees | milliseconds/operation |
82
-| disk.avgsz | reads, writes, frees | KiB/operation |
83
-| disk.svctm | svctm | milliseconds/operation |
84
-
85
-
86
-
87
-## Alerts
88
-
89
-
90
-The following alerts are available:
91
-
92
-| Alert name | On metric | Description |
93
-|:------------|:----------|:------------|
94
-| [ 10min_disk_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.util | average percentage of time ${label:device} disk was busy over the last 10 minutes |
95
-
96
-
46
## Setup
47
48
@@ -158,3 +107,54 @@ sudo ./edit-config netdata.conf
107
There are no configuration examples.
108
109
110
+
111
+## Alerts
112
+
113
+
114
+The following alerts are available:
115
+
116
+| Alert name | On metric | Description |
117
+|:------------|:----------|:------------|
118
+| [ 10min_disk_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.util | average percentage of time ${label:device} disk was busy over the last 10 minutes |
119
+
120
+
121
+## Metrics
122
+
123
+Metrics grouped by *scope*.
124
+
125
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
126
+
127
+
128
+
129
+### Per devstat instance
130
+
131
+These metrics give a general vision about I/O events on disks.
132
+
133
+This scope has no labels.
134
+
135
+Metrics:
136
+
137
+| Metric | Dimensions | Unit |
138
+|:------|:----------|:----|
139
+| system.io | io, out | KiB/s |
140
+
141
+### Per disk
142
+
143
+
144
+
145
+This scope has no labels.
146
+
147
+Metrics:
148
+
149
+| Metric | Dimensions | Unit |
150
+|:------|:----------|:----|
151
+| disk.io | reads, writes, frees | KiB/s |
152
+| disk.ops | reads, writes, other, frees | operations/s |
153
+| disk.qops | operations | operations |
154
+| disk.util | utilization | % of time working |
155
+| disk.iotime | reads, writes, other, frees | milliseconds/s |
156
+| disk.await | reads, writes, other, frees | milliseconds/operation |
157
+| disk.avgsz | reads, writes, frees | KiB/operation |
158
+| disk.svctm | svctm | milliseconds/operation |
159
+
160
+
src/collectors/freebsd.plugin/integrations/getifaddrs.md
+57
-57
@@ -43,63 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per getifaddrs instance
55
-
56
-General overview about network traffic.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.net | received, sent | kilobits/s |
65
-| system.packets | received, sent, multicast_received, multicast_sent | packets/s |
66
-| system.ipv4 | received, sent | kilobits/s |
67
-| system.ipv6 | received, sent | kilobits/s |
68
-
69
-### Per network device
70
-
71
-
72
-
73
-This scope has no labels.
74
-
75
-Metrics:
76
-
77
-| Metric | Dimensions | Unit |
78
-|:------|:----------|:----|
79
-| net.net | received, sent | kilobits/s |
80
-| net.packets | received, sent, multicast_received, multicast_sent | packets/s |
81
-| net.errors | inbound, outbound | errors/s |
82
-| net.drops | inbound, outbound | drops/s |
83
-| net.events | collisions | events/s |
84
-
85
-
86
-
87
-## Alerts
88
-
89
-
90
-The following alerts are available:
91
-
92
-| Alert name | On metric | Description |
93
-|:------------|:----------|:------------|
94
-| [ interface_speed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | network interface ${label:device} current speed |
95
-| [ inbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | ratio of inbound dropped packets for the network interface ${label:device} over the last 10 minutes |
96
-| [ outbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | ratio of outbound dropped packets for the network interface ${label:device} over the last 10 minutes |
97
-| [ 1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.packets | average number of packets received by the network interface ${label:device} over the last minute |
98
-| [ 10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
99
-| [ interface_inbound_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.errors | number of inbound errors for the network interface ${label:device} in the last 10 minutes |
100
-| [ interface_outbound_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.errors | number of outbound errors for the network interface ${label:device} in the last 10 minutes |
101
-
102
-
46
## Setup
47
48
@@ -164,3 +107,60 @@ sudo ./edit-config netdata.conf
107
There are no configuration examples.
108
109
110
+
111
+## Alerts
112
+
113
+
114
+The following alerts are available:
115
+
116
+| Alert name | On metric | Description |
117
+|:------------|:----------|:------------|
118
+| [ interface_speed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | network interface ${label:device} current speed |
119
+| [ inbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | ratio of inbound dropped packets for the network interface ${label:device} over the last 10 minutes |
120
+| [ outbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | ratio of outbound dropped packets for the network interface ${label:device} over the last 10 minutes |
121
+| [ 1m_received_packets_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.packets | average number of packets received by the network interface ${label:device} over the last minute |
122
+| [ 10s_received_packets_storm ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.packets | ratio of average number of received packets for the network interface ${label:device} over the last 10 seconds, compared to the rate over the last minute |
123
+| [ interface_inbound_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.errors | number of inbound errors for the network interface ${label:device} in the last 10 minutes |
124
+| [ interface_outbound_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.errors | number of outbound errors for the network interface ${label:device} in the last 10 minutes |
125
+
126
+
127
+## Metrics
128
+
129
+Metrics grouped by *scope*.
130
+
131
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
132
+
133
+
134
+
135
+### Per getifaddrs instance
136
+
137
+General overview about network traffic.
138
+
139
+This scope has no labels.
140
+
141
+Metrics:
142
+
143
+| Metric | Dimensions | Unit |
144
+|:------|:----------|:----|
145
+| system.net | received, sent | kilobits/s |
146
+| system.packets | received, sent, multicast_received, multicast_sent | packets/s |
147
+| system.ipv4 | received, sent | kilobits/s |
148
+| system.ipv6 | received, sent | kilobits/s |
149
+
150
+### Per network device
151
+
152
+
153
+
154
+This scope has no labels.
155
+
156
+Metrics:
157
+
158
+| Metric | Dimensions | Unit |
159
+|:------|:----------|:----|
160
+| net.net | received, sent | kilobits/s |
161
+| net.packets | received, sent, multicast_received, multicast_sent | packets/s |
162
+| net.errors | inbound, outbound | errors/s |
163
+| net.drops | inbound, outbound | drops/s |
164
+| net.events | collisions | events/s |
165
+
166
+
src/collectors/freebsd.plugin/integrations/getmntinfo.md
+34
-34
@@ -43,40 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per mount point
55
-
56
-These metrics show detailss about mount point usages.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| disk.space | avail, used, reserved_for_root | GiB |
65
-| disk.inodes | avail, used, reserved_for_root | inodes |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-
72
-The following alerts are available:
73
-
74
-| Alert name | On metric | Description |
75
-|:------------|:----------|:------------|
76
-| [ disk_space_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.space | disk ${label:mount_point} space utilization |
77
-| [ disk_inode_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.inodes | disk ${label:mount_point} inode utilization |
78
-
79
-
46
## Setup
47
48
@@ -134,3 +100,37 @@ sudo ./edit-config netdata.conf
100
There are no configuration examples.
101
102
103
+
104
+## Alerts
105
+
106
+
107
+The following alerts are available:
108
+
109
+| Alert name | On metric | Description |
110
+|:------------|:----------|:------------|
111
+| [ disk_space_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.space | disk ${label:mount_point} space utilization |
112
+| [ disk_inode_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.inodes | disk ${label:mount_point} inode utilization |
113
+
114
+
115
+## Metrics
116
+
117
+Metrics grouped by *scope*.
118
+
119
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
120
+
121
+
122
+
123
+### Per mount point
124
+
125
+These metrics show detailss about mount point usages.
126
+
127
+This scope has no labels.
128
+
129
+Metrics:
130
+
131
+| Metric | Dimensions | Unit |
132
+|:------|:----------|:----|
133
+| disk.space | avail, used, reserved_for_root | GiB |
134
+| disk.inodes | avail, used, reserved_for_root | inodes |
135
+
136
+
src/collectors/freebsd.plugin/integrations/hw.intrcnt.md
+28
-28
@@ -43,34 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per hw.intrcnt instance
55
-
56
-These metrics show system interrupts frequency.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.intr | interrupts | interrupts/s |
65
-| system.interrupts | a dimension per interrupt | interrupts/s |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-There are no alerts configured by default for this integration.
72
-
73
-
46
## Setup
47
48
@@ -124,3 +96,31 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per hw.intrcnt instance
114
+
115
+These metrics show system interrupts frequency.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.intr | interrupts | interrupts/s |
124
+| system.interrupts | a dimension per interrupt | interrupts/s |
125
+
126
+
src/collectors/freebsd.plugin/integrations/ipfw.md
+31
-31
@@ -43,37 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per ipfw instance
55
-
56
-Theese metrics show FreeBSD firewall statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipfw.mem | dynamic, static | bytes |
65
-| ipfw.packets | a dimension per static rule | packets/s |
66
-| ipfw.bytes | a dimension per static rule | bytes/s |
67
-| ipfw.active | a dimension per dynamic rule | rules |
68
-| ipfw.expired | a dimension per dynamic rule | rules |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
46
## Setup
47
48
@@ -129,3 +98,34 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per ipfw instance
116
+
117
+Theese metrics show FreeBSD firewall statistics.
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| ipfw.mem | dynamic, static | bytes |
126
+| ipfw.packets | a dimension per static rule | packets/s |
127
+| ipfw.bytes | a dimension per static rule | bytes/s |
128
+| ipfw.active | a dimension per dynamic rule | rules |
129
+| ipfw.expired | a dimension per dynamic rule | rules |
130
+
131
+
src/collectors/freebsd.plugin/integrations/kern.cp_time.md
+47
-47
@@ -43,53 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per kern.cp_time instance
55
-
56
-These metrics show CPU usage statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.cpu | nice, system, user, interrupt, idle | percentage |
65
-
66
-### Per core
67
-
68
-
69
-
70
-This scope has no labels.
71
-
72
-Metrics:
73
-
74
-| Metric | Dimensions | Unit |
75
-|:------|:----------|:----|
76
-| cpu.cpu | nice, system, user, interrupt, idle | percentage |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-
83
-The following alerts are available:
84
-
85
-| Alert name | On metric | Description |
86
-|:------------|:----------|:------------|
87
-| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU utilization over the last 10 minutes (excluding iowait, nice and steal) |
88
-| [ 10min_cpu_iowait ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU iowait time over the last 10 minutes |
89
-| [ 20min_steal_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU steal time over the last 20 minutes |
90
-| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU utilization over the last 10 minutes (excluding nice) |
91
-
92
-
46
## Setup
47
48
@@ -142,3 +95,50 @@ sudo ./edit-config netdata.conf
95
There are no configuration examples.
96
97
98
+
99
+## Alerts
100
+
101
+
102
+The following alerts are available:
103
+
104
+| Alert name | On metric | Description |
105
+|:------------|:----------|:------------|
106
+| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU utilization over the last 10 minutes (excluding iowait, nice and steal) |
107
+| [ 10min_cpu_iowait ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU iowait time over the last 10 minutes |
108
+| [ 20min_steal_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU steal time over the last 20 minutes |
109
+| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU utilization over the last 10 minutes (excluding nice) |
110
+
111
+
112
+## Metrics
113
+
114
+Metrics grouped by *scope*.
115
+
116
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
117
+
118
+
119
+
120
+### Per kern.cp_time instance
121
+
122
+These metrics show CPU usage statistics.
123
+
124
+This scope has no labels.
125
+
126
+Metrics:
127
+
128
+| Metric | Dimensions | Unit |
129
+|:------|:----------|:----|
130
+| system.cpu | nice, system, user, interrupt, idle | percentage |
131
+
132
+### Per core
133
+
134
+
135
+
136
+This scope has no labels.
137
+
138
+Metrics:
139
+
140
+| Metric | Dimensions | Unit |
141
+|:------|:----------|:----|
142
+| cpu.cpu | nice, system, user, interrupt, idle | percentage |
143
+
144
+
src/collectors/freebsd.plugin/integrations/kern.ipc.msq.md
+29
-29
@@ -43,35 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per kern.ipc.msq instance
55
-
56
-These metrics show statistics IPC messages statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.ipc_msq_queues | queues | queues |
65
-| system.ipc_msq_messages | messages | messages |
66
-| system.ipc_msq_size | allocated, used | bytes |
67
-
68
-
69
-
70
-## Alerts
71
-
72
-There are no alerts configured by default for this integration.
73
-
74
-
46
## Setup
47
48
@@ -125,3 +96,32 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per kern.ipc.msq instance
114
+
115
+These metrics show statistics IPC messages statistics.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.ipc_msq_queues | queues | queues |
124
+| system.ipc_msq_messages | messages | messages |
125
+| system.ipc_msq_size | allocated, used | bytes |
126
+
127
+
src/collectors/freebsd.plugin/integrations/kern.ipc.sem.md
+34
-34
@@ -43,40 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per kern.ipc.sem instance
55
-
56
-These metrics shows counters for semaphores on host.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.ipc_semaphores | semaphores | semaphores |
65
-| system.ipc_semaphore_arrays | arrays | arrays |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-
72
-The following alerts are available:
73
-
74
-| Alert name | On metric | Description |
75
-|:------------|:----------|:------------|
76
-| [ semaphores_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipc.conf) | system.ipc_semaphores | IPC semaphore utilization |
77
-| [ semaphore_arrays_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipc.conf) | system.ipc_semaphore_arrays | IPC semaphore arrays utilization |
78
-
79
-
46
## Setup
47
48
@@ -130,3 +96,37 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ semaphores_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipc.conf) | system.ipc_semaphores | IPC semaphore utilization |
108
+| [ semaphore_arrays_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipc.conf) | system.ipc_semaphore_arrays | IPC semaphore arrays utilization |
109
+
110
+
111
+## Metrics
112
+
113
+Metrics grouped by *scope*.
114
+
115
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
116
+
117
+
118
+
119
+### Per kern.ipc.sem instance
120
+
121
+These metrics shows counters for semaphores on host.
122
+
123
+This scope has no labels.
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| system.ipc_semaphores | semaphores | semaphores |
130
+| system.ipc_semaphore_arrays | arrays | arrays |
131
+
132
+
src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md
+28
-28
@@ -43,34 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per kern.ipc.shm instance
55
-
56
-These metrics give status about current shared memory segments.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.ipc_shared_mem_segs | segments | segments |
65
-| system.ipc_shared_mem_size | allocated | KiB |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-There are no alerts configured by default for this integration.
72
-
73
-
46
## Setup
47
48
@@ -124,3 +96,31 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per kern.ipc.shm instance
114
+
115
+These metrics give status about current shared memory segments.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.ipc_shared_mem_segs | segments | segments |
124
+| system.ipc_shared_mem_size | allocated | KiB |
125
+
126
+
src/collectors/freebsd.plugin/integrations/net.inet.icmp.stats.md
+29
-29
@@ -43,35 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet.icmp.stats instance
55
-
56
-These metrics show ICMP connections statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv4.icmp | received, sent | packets/s |
65
-| ipv4.icmp_errors | InErrors, OutErrors, InCsumErrors | packets/s |
66
-| ipv4.icmpmsg | InEchoReps, OutEchoReps, InEchos, OutEchos | packets/s |
67
-
68
-
69
-
70
-## Alerts
71
-
72
-There are no alerts configured by default for this integration.
73
-
74
-
46
## Setup
47
48
@@ -127,3 +98,32 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per net.inet.icmp.stats instance
116
+
117
+These metrics show ICMP connections statistics.
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| ipv4.icmp | received, sent | packets/s |
126
+| ipv4.icmp_errors | InErrors, OutErrors, InCsumErrors | packets/s |
127
+| ipv4.icmpmsg | InEchoReps, OutEchoReps, InEchos, OutEchos | packets/s |
128
+
129
+
src/collectors/freebsd.plugin/integrations/net.inet.ip.stats.md
+30
-30
@@ -43,36 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet.ip.stats instance
55
-
56
-These metrics show IPv4 connections statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv4.packets | received, sent, forwarded, delivered | packets/s |
65
-| ipv4.fragsout | ok, failed, created | packets/s |
66
-| ipv4.fragsin | ok, failed, all | packets/s |
67
-| ipv4.errors | InDiscards, OutDiscards, InHdrErrors, OutNoRoutes, InAddrErrors, InUnknownProtos | packets/s |
68
-
69
-
70
-
71
-## Alerts
72
-
73
-There are no alerts configured by default for this integration.
74
-
75
-
46
## Setup
47
48
@@ -129,3 +99,33 @@ sudo ./edit-config netdata.conf
99
There are no configuration examples.
100
101
102
+
103
+## Alerts
104
+
105
+There are no alerts configured by default for this integration.
106
+
107
+
108
+## Metrics
109
+
110
+Metrics grouped by *scope*.
111
+
112
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
113
+
114
+
115
+
116
+### Per net.inet.ip.stats instance
117
+
118
+These metrics show IPv4 connections statistics.
119
+
120
+This scope has no labels.
121
+
122
+Metrics:
123
+
124
+| Metric | Dimensions | Unit |
125
+|:------|:----------|:----|
126
+| ipv4.packets | received, sent, forwarded, delivered | packets/s |
127
+| ipv4.fragsout | ok, failed, created | packets/s |
128
+| ipv4.fragsin | ok, failed, all | packets/s |
129
+| ipv4.errors | InDiscards, OutDiscards, InHdrErrors, OutNoRoutes, InAddrErrors, InUnknownProtos | packets/s |
130
+
131
+
src/collectors/freebsd.plugin/integrations/net.inet.tcp.states.md
+32
-32
@@ -43,38 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet.tcp.states instance
55
-
56
-A counter for TCP connections.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv4.tcpsock | connections | active connections |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-
71
-The following alerts are available:
72
-
73
-| Alert name | On metric | Description |
74
-|:------------|:----------|:------------|
75
-| [ tcp_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_conn.conf) | ipv4.tcpsock | IPv4 TCP connections utilization |
76
-
77
-
46
## Setup
47
48
@@ -128,3 +96,35 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ tcp_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_conn.conf) | ipv4.tcpsock | IPv4 TCP connections utilization |
108
+
109
+
110
+## Metrics
111
+
112
+Metrics grouped by *scope*.
113
+
114
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
115
+
116
+
117
+
118
+### Per net.inet.tcp.states instance
119
+
120
+A counter for TCP connections.
121
+
122
+This scope has no labels.
123
+
124
+Metrics:
125
+
126
+| Metric | Dimensions | Unit |
127
+|:------|:----------|:----|
128
+| ipv4.tcpsock | connections | active connections |
129
+
130
+
src/collectors/freebsd.plugin/integrations/net.inet.tcp.stats.md
+42
-42
@@ -43,48 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet.tcp.stats instance
55
-
56
-These metrics show TCP connections statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv4.tcppackets | received, sent | packets/s |
65
-| ipv4.tcperrors | InErrs, InCsumErrors, RetransSegs | packets/s |
66
-| ipv4.tcphandshake | EstabResets, ActiveOpens, PassiveOpens, AttemptFails | events/s |
67
-| ipv4.tcpconnaborts | baddata, userclosed, nomemory, timeout, linger | connections/s |
68
-| ipv4.tcpofo | inqueue | packets/s |
69
-| ipv4.tcpsyncookies | received, sent, failed | packets/s |
70
-| ipv4.tcplistenissues | overflows | packets/s |
71
-| ipv4.ecnpkts | InCEPkts, InECT0Pkts, InECT1Pkts, OutECT0Pkts, OutECT1Pkts | packets/s |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-
78
-The following alerts are available:
79
-
80
-| Alert name | On metric | Description |
81
-|:------------|:----------|:------------|
82
-| [ 1m_ipv4_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of sent TCP RESETS over the last minute |
83
-| [ 10s_ipv4_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of sent TCP RESETS over the last 10 seconds. This can indicate a port scan, or that a service running on this host has crashed. Netdata will not send a clear notification for this alarm. |
84
-| [ 1m_ipv4_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of received TCP RESETS over the last minute |
85
-| [ 10s_ipv4_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of received TCP RESETS over the last 10 seconds. This can be an indication that a service this host needs has crashed. Netdata will not send a clear notification for this alarm. |
86
-
87
-
46
## Setup
47
48
@@ -145,3 +103,45 @@ sudo ./edit-config netdata.conf
103
There are no configuration examples.
104
105
106
+
107
+## Alerts
108
+
109
+
110
+The following alerts are available:
111
+
112
+| Alert name | On metric | Description |
113
+|:------------|:----------|:------------|
114
+| [ 1m_ipv4_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of sent TCP RESETS over the last minute |
115
+| [ 10s_ipv4_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of sent TCP RESETS over the last 10 seconds. This can indicate a port scan, or that a service running on this host has crashed. Netdata will not send a clear notification for this alarm. |
116
+| [ 1m_ipv4_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of received TCP RESETS over the last minute |
117
+| [ 10s_ipv4_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ipv4.tcphandshake | average number of received TCP RESETS over the last 10 seconds. This can be an indication that a service this host needs has crashed. Netdata will not send a clear notification for this alarm. |
118
+
119
+
120
+## Metrics
121
+
122
+Metrics grouped by *scope*.
123
+
124
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
125
+
126
+
127
+
128
+### Per net.inet.tcp.stats instance
129
+
130
+These metrics show TCP connections statistics.
131
+
132
+This scope has no labels.
133
+
134
+Metrics:
135
+
136
+| Metric | Dimensions | Unit |
137
+|:------|:----------|:----|
138
+| ipv4.tcppackets | received, sent | packets/s |
139
+| ipv4.tcperrors | InErrs, InCsumErrors, RetransSegs | packets/s |
140
+| ipv4.tcphandshake | EstabResets, ActiveOpens, PassiveOpens, AttemptFails | events/s |
141
+| ipv4.tcpconnaborts | baddata, userclosed, nomemory, timeout, linger | connections/s |
142
+| ipv4.tcpofo | inqueue | packets/s |
143
+| ipv4.tcpsyncookies | received, sent, failed | packets/s |
144
+| ipv4.tcplistenissues | overflows | packets/s |
145
+| ipv4.ecnpkts | InCEPkts, InECT0Pkts, InECT1Pkts, OutECT0Pkts, OutECT1Pkts | packets/s |
146
+
147
+
src/collectors/freebsd.plugin/integrations/net.inet.udp.stats.md
+34
-34
@@ -43,40 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet.udp.stats instance
55
-
56
-These metrics show UDP connections statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv4.udppackets | received, sent | packets/s |
65
-| ipv4.udperrors | InErrors, NoPorts, RcvbufErrors, InCsumErrors, IgnoredMulti | events/s |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-
72
-The following alerts are available:
73
-
74
-| Alert name | On metric | Description |
75
-|:------------|:----------|:------------|
76
-| [ 1m_ipv4_udp_receive_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP receive buffer errors over the last minute |
77
-| [ 1m_ipv4_udp_send_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP send buffer errors over the last minute |
78
-
79
-
46
## Setup
47
48
@@ -131,3 +97,37 @@ sudo ./edit-config netdata.conf
97
There are no configuration examples.
98
99
100
+
101
+## Alerts
102
+
103
+
104
+The following alerts are available:
105
+
106
+| Alert name | On metric | Description |
107
+|:------------|:----------|:------------|
108
+| [ 1m_ipv4_udp_receive_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP receive buffer errors over the last minute |
109
+| [ 1m_ipv4_udp_send_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP send buffer errors over the last minute |
110
+
111
+
112
+## Metrics
113
+
114
+Metrics grouped by *scope*.
115
+
116
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
117
+
118
+
119
+
120
+### Per net.inet.udp.stats instance
121
+
122
+These metrics show UDP connections statistics.
123
+
124
+This scope has no labels.
125
+
126
+Metrics:
127
+
128
+| Metric | Dimensions | Unit |
129
+|:------|:----------|:----|
130
+| ipv4.udppackets | received, sent | packets/s |
131
+| ipv4.udperrors | InErrors, NoPorts, RcvbufErrors, InCsumErrors, IgnoredMulti | events/s |
132
+
133
+
src/collectors/freebsd.plugin/integrations/net.inet6.icmp6.stats.md
+33
-33
@@ -43,39 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet6.icmp6.stats instance
55
-
56
-Collect IPv6 ICMP traffic statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv6.icmp | received, sent | messages/s |
65
-| ipv6.icmpredir | received, sent | redirects/s |
66
-| ipv6.icmperrors | InErrors, OutErrors, InCsumErrors, InDestUnreachs, InPktTooBigs, InTimeExcds, InParmProblems, OutDestUnreachs, OutTimeExcds, OutParmProblems | errors/s |
67
-| ipv6.icmpechos | InEchos, OutEchos, InEchoReplies, OutEchoReplies | messages/s |
68
-| ipv6.icmprouter | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
69
-| ipv6.icmpneighbor | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
70
-| ipv6.icmptypes | InType1, InType128, InType129, InType136, OutType1, OutType128, OutType129, OutType133, OutType135, OutType143 | messages/s |
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
46
## Setup
47
48
@@ -135,3 +102,36 @@ sudo ./edit-config netdata.conf
102
There are no configuration examples.
103
104
105
+
106
+## Alerts
107
+
108
+There are no alerts configured by default for this integration.
109
+
110
+
111
+## Metrics
112
+
113
+Metrics grouped by *scope*.
114
+
115
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
116
+
117
+
118
+
119
+### Per net.inet6.icmp6.stats instance
120
+
121
+Collect IPv6 ICMP traffic statistics.
122
+
123
+This scope has no labels.
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| ipv6.icmp | received, sent | messages/s |
130
+| ipv6.icmpredir | received, sent | redirects/s |
131
+| ipv6.icmperrors | InErrors, OutErrors, InCsumErrors, InDestUnreachs, InPktTooBigs, InTimeExcds, InParmProblems, OutDestUnreachs, OutTimeExcds, OutParmProblems | errors/s |
132
+| ipv6.icmpechos | InEchos, OutEchos, InEchoReplies, OutEchoReplies | messages/s |
133
+| ipv6.icmprouter | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
134
+| ipv6.icmpneighbor | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
135
+| ipv6.icmptypes | InType1, InType128, InType129, InType136, OutType1, OutType128, OutType129, OutType133, OutType135, OutType143 | messages/s |
136
+
137
+
src/collectors/freebsd.plugin/integrations/net.inet6.ip6.stats.md
+30
-30
@@ -43,36 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.inet6.ip6.stats instance
55
-
56
-These metrics show general information about IPv6 connections.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ipv6.packets | received, sent, forwarded, delivers | packets/s |
65
-| ipv6.fragsout | ok, failed, all | packets/s |
66
-| ipv6.fragsin | ok, failed, timeout, all | packets/s |
67
-| ipv6.errors | InDiscards, OutDiscards, InHdrErrors, InAddrErrors, InTruncatedPkts, InNoRoutes, OutNoRoutes | packets/s |
68
-
69
-
70
-
71
-## Alerts
72
-
73
-There are no alerts configured by default for this integration.
74
-
75
-
46
## Setup
47
48
@@ -129,3 +99,33 @@ sudo ./edit-config netdata.conf
99
There are no configuration examples.
100
101
102
+
103
+## Alerts
104
+
105
+There are no alerts configured by default for this integration.
106
+
107
+
108
+## Metrics
109
+
110
+Metrics grouped by *scope*.
111
+
112
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
113
+
114
+
115
+
116
+### Per net.inet6.ip6.stats instance
117
+
118
+These metrics show general information about IPv6 connections.
119
+
120
+This scope has no labels.
121
+
122
+Metrics:
123
+
124
+| Metric | Dimensions | Unit |
125
+|:------|:----------|:----|
126
+| ipv6.packets | received, sent, forwarded, delivers | packets/s |
127
+| ipv6.fragsout | ok, failed, all | packets/s |
128
+| ipv6.fragsin | ok, failed, timeout, all | packets/s |
129
+| ipv6.errors | InDiscards, OutDiscards, InHdrErrors, InAddrErrors, InTruncatedPkts, InNoRoutes, OutNoRoutes | packets/s |
130
+
131
+
src/collectors/freebsd.plugin/integrations/net.isr.md
+46
-46
@@ -43,52 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per net.isr instance
55
-
56
-These metrics show statistics about softnet stats.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.softnet_stat | dispatched, hybrid_dispatched, qdrops, queued | events/s |
65
-
66
-### Per core
67
-
68
-
69
-
70
-This scope has no labels.
71
-
72
-Metrics:
73
-
74
-| Metric | Dimensions | Unit |
75
-|:------|:----------|:----|
76
-| cpu.softnet_stat | dispatched, hybrid_dispatched, qdrops, queued | events/s |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-
83
-The following alerts are available:
84
-
85
-| Alert name | On metric | Description |
86
-|:------------|:----------|:------------|
87
-| [ 1min_netdev_backlog_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of dropped packets in the last minute due to exceeded net.core.netdev_max_backlog |
88
-| [ 1min_netdev_budget_ran_outs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of times ksoftirq ran out of sysctl net.core.netdev_budget or net.core.netdev_budget_usecs with work remaining over the last minute (this can be a cause for dropped packets) |
89
-| [ 10min_netisr_backlog_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of drops in the last minute due to exceeded sysctl net.route.netisr_maxqlen (this can be a cause for dropped packets) |
90
-
91
-
46
## Setup
47
48
@@ -143,3 +97,49 @@ sudo ./edit-config netdata.conf
97
There are no configuration examples.
98
99
100
+
101
+## Alerts
102
+
103
+
104
+The following alerts are available:
105
+
106
+| Alert name | On metric | Description |
107
+|:------------|:----------|:------------|
108
+| [ 1min_netdev_backlog_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of dropped packets in the last minute due to exceeded net.core.netdev_max_backlog |
109
+| [ 1min_netdev_budget_ran_outs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of times ksoftirq ran out of sysctl net.core.netdev_budget or net.core.netdev_budget_usecs with work remaining over the last minute (this can be a cause for dropped packets) |
110
+| [ 10min_netisr_backlog_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of drops in the last minute due to exceeded sysctl net.route.netisr_maxqlen (this can be a cause for dropped packets) |
111
+
112
+
113
+## Metrics
114
+
115
+Metrics grouped by *scope*.
116
+
117
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
118
+
119
+
120
+
121
+### Per net.isr instance
122
+
123
+These metrics show statistics about softnet stats.
124
+
125
+This scope has no labels.
126
+
127
+Metrics:
128
+
129
+| Metric | Dimensions | Unit |
130
+|:------|:----------|:----|
131
+| system.softnet_stat | dispatched, hybrid_dispatched, qdrops, queued | events/s |
132
+
133
+### Per core
134
+
135
+
136
+
137
+This scope has no labels.
138
+
139
+Metrics:
140
+
141
+| Metric | Dimensions | Unit |
142
+|:------|:----------|:----|
143
+| cpu.softnet_stat | dispatched, hybrid_dispatched, qdrops, queued | events/s |
144
+
145
+
src/collectors/freebsd.plugin/integrations/system.ram.md
+36
-36
@@ -43,42 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per system.ram instance
55
-
56
-This metric shows RAM usage statistics.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.ram | free, active, inactive, wired, cache, laundry, buffers | MiB |
65
-| mem.available | avail | MiB |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-
72
-The following alerts are available:
73
-
74
-| Alert name | On metric | Description |
75
-|:------------|:----------|:------------|
76
-| [ ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | system.ram | system memory utilization |
77
-| [ ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | system.ram | system memory utilization |
78
-| [ ram_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | mem.available | percentage of estimated amount of RAM available for userspace processes, without causing swapping |
79
-| [ ram_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | mem.available | percentage of estimated amount of RAM available for userspace processes, without causing swapping |
80
-
81
-
46
## Setup
47
48
@@ -132,3 +96,39 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | system.ram | system memory utilization |
108
+| [ ram_in_use ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | system.ram | system memory utilization |
109
+| [ ram_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | mem.available | percentage of estimated amount of RAM available for userspace processes, without causing swapping |
110
+| [ ram_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | mem.available | percentage of estimated amount of RAM available for userspace processes, without causing swapping |
111
+
112
+
113
+## Metrics
114
+
115
+Metrics grouped by *scope*.
116
+
117
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
118
+
119
+
120
+
121
+### Per system.ram instance
122
+
123
+This metric shows RAM usage statistics.
124
+
125
+This scope has no labels.
126
+
127
+Metrics:
128
+
129
+| Metric | Dimensions | Unit |
130
+|:------|:----------|:----|
131
+| system.ram | free, active, inactive, wired, cache, laundry, buffers | MiB |
132
+| mem.available | avail | MiB |
133
+
134
+
src/collectors/freebsd.plugin/integrations/uptime.md
+27
-27
@@ -43,33 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per uptime instance
55
-
56
-How long the system is running.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.uptime | uptime | seconds |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-There are no alerts configured by default for this integration.
71
-
72
-
46
## Setup
47
48
@@ -123,3 +96,30 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per uptime instance
114
+
115
+How long the system is running.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.uptime | uptime | seconds |
124
+
125
+
src/collectors/freebsd.plugin/integrations/vm.loadavg.md
+35
-35
@@ -43,41 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.loadavg instance
55
-
56
-Monitoring for number of threads running or waiting.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.load | load1, load5, load15 | load |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-
71
-The following alerts are available:
72
-
73
-| Alert name | On metric | Description |
74
-|:------------|:----------|:------------|
75
-| [ load_cpu_number ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | number of active CPU cores in the system |
76
-| [ load_average_15 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | system fifteen-minute load average |
77
-| [ load_average_5 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | system five-minute load average |
78
-| [ load_average_1 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | system one-minute load average |
79
-
80
-
46
## Setup
47
48
@@ -131,3 +96,38 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ load_cpu_number ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | number of active CPU cores in the system |
108
+| [ load_average_15 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | system fifteen-minute load average |
109
+| [ load_average_5 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | system five-minute load average |
110
+| [ load_average_1 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/load.conf) | system.load | system one-minute load average |
111
+
112
+
113
+## Metrics
114
+
115
+Metrics grouped by *scope*.
116
+
117
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
118
+
119
+
120
+
121
+### Per vm.loadavg instance
122
+
123
+Monitoring for number of threads running or waiting.
124
+
125
+This scope has no labels.
126
+
127
+Metrics:
128
+
129
+| Metric | Dimensions | Unit |
130
+|:------|:----------|:----|
131
+| system.load | load1, load5, load15 | load |
132
+
133
+
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_intr.md
+27
-27
@@ -43,33 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.stats.sys.v_intr instance
55
-
56
-The metric show device interrupt frequency.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.dev_intr | interrupts | interrupts/s |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-There are no alerts configured by default for this integration.
71
-
72
-
46
## Setup
47
48
@@ -123,3 +96,30 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per vm.stats.sys.v_intr instance
114
+
115
+The metric show device interrupt frequency.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.dev_intr | interrupts | interrupts/s |
124
+
125
+
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_soft.md
+27
-27
@@ -43,33 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.stats.sys.v_soft instance
55
-
56
-This metric shows software interrupt frequency.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.soft_intr | interrupts | interrupts/s |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-There are no alerts configured by default for this integration.
71
-
72
-
46
## Setup
47
48
@@ -123,3 +96,30 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per vm.stats.sys.v_soft instance
114
+
115
+This metric shows software interrupt frequency.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.soft_intr | interrupts | interrupts/s |
124
+
125
+
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_swtch.md
+28
-28
@@ -43,34 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.stats.sys.v_swtch instance
55
-
56
-The metric count the number of context switches happening on host.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.ctxt | switches | context switches/s |
65
-| system.forks | started | processes/s |
66
-
67
-
68
-
69
-## Alerts
70
-
71
-There are no alerts configured by default for this integration.
72
-
73
-
46
## Setup
47
48
@@ -124,3 +96,31 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per vm.stats.sys.v_swtch instance
114
+
115
+The metric count the number of context switches happening on host.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| system.ctxt | switches | context switches/s |
124
+| system.forks | started | processes/s |
125
+
126
+
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_pgfaults.md
+27
-27
@@ -43,33 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.stats.vm.v_pgfaults instance
55
-
56
-The number of page faults happened on host.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| mem.pgfaults | memory, io_requiring, cow, cow_optimized, in_transit | page faults/s |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-There are no alerts configured by default for this integration.
71
-
72
-
46
## Setup
47
48
@@ -123,3 +96,30 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+There are no alerts configured by default for this integration.
103
+
104
+
105
+## Metrics
106
+
107
+Metrics grouped by *scope*.
108
+
109
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
110
+
111
+
112
+
113
+### Per vm.stats.vm.v_pgfaults instance
114
+
115
+The number of page faults happened on host.
116
+
117
+This scope has no labels.
118
+
119
+Metrics:
120
+
121
+| Metric | Dimensions | Unit |
122
+|:------|:----------|:----|
123
+| mem.pgfaults | memory, io_requiring, cow, cow_optimized, in_transit | page faults/s |
124
+
125
+
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_swappgs.md
+32
-32
@@ -43,38 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.stats.vm.v_swappgs instance
55
-
56
-This metric shows events happening on SWAP.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| mem.swapio | io, out | KiB/s |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-
71
-The following alerts are available:
72
-
73
-| Alert name | On metric | Description |
74
-|:------------|:----------|:------------|
75
-| [ 30min_ram_swapped_out ](https://github.com/netdata/netdata/blob/master/src/health/health.d/swap.conf) | mem.swapio | percentage of the system RAM swapped in the last 30 minutes |
76
-
77
-
46
## Setup
47
48
@@ -128,3 +96,35 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ 30min_ram_swapped_out ](https://github.com/netdata/netdata/blob/master/src/health/health.d/swap.conf) | mem.swapio | percentage of the system RAM swapped in the last 30 minutes |
108
+
109
+
110
+## Metrics
111
+
112
+Metrics grouped by *scope*.
113
+
114
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
115
+
116
+
117
+
118
+### Per vm.stats.vm.v_swappgs instance
119
+
120
+This metric shows events happening on SWAP.
121
+
122
+This scope has no labels.
123
+
124
+Metrics:
125
+
126
+| Metric | Dimensions | Unit |
127
+|:------|:----------|:----|
128
+| mem.swapio | io, out | KiB/s |
129
+
130
+
src/collectors/freebsd.plugin/integrations/vm.swap_info.md
+32
-32
@@ -43,38 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.swap_info instance
55
-
56
-This metric shows the SWAP usage.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| mem.swap | free, used | MiB |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-
71
-The following alerts are available:
72
-
73
-| Alert name | On metric | Description |
74
-|:------------|:----------|:------------|
75
-| [ used_swap ](https://github.com/netdata/netdata/blob/master/src/health/health.d/swap.conf) | mem.swap | swap memory utilization |
76
-
77
-
46
## Setup
47
48
@@ -128,3 +96,35 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ used_swap ](https://github.com/netdata/netdata/blob/master/src/health/health.d/swap.conf) | mem.swap | swap memory utilization |
108
+
109
+
110
+## Metrics
111
+
112
+Metrics grouped by *scope*.
113
+
114
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
115
+
116
+
117
+
118
+### Per vm.swap_info instance
119
+
120
+This metric shows the SWAP usage.
121
+
122
+This scope has no labels.
123
+
124
+Metrics:
125
+
126
+| Metric | Dimensions | Unit |
127
+|:------|:----------|:----|
128
+| mem.swap | free, used | MiB |
129
+
130
+
src/collectors/freebsd.plugin/integrations/vm.vmtotal.md
+34
-34
@@ -43,40 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per vm.vmtotal instance
55
-
56
-These metrics show an overall vision about processes running.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.active_processes | active | processes |
65
-| system.processes | running, blocked | processes |
66
-| mem.real | used | MiB |
67
-
68
-
69
-
70
-## Alerts
71
-
72
-
73
-The following alerts are available:
74
-
75
-| Alert name | On metric | Description |
76
-|:------------|:----------|:------------|
77
-| [ active_processes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/processes.conf) | system.active_processes | system process IDs (PID) space utilization |
78
-
79
-
46
## Setup
47
48
@@ -132,3 +98,37 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+
105
+The following alerts are available:
106
+
107
+| Alert name | On metric | Description |
108
+|:------------|:----------|:------------|
109
+| [ active_processes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/processes.conf) | system.active_processes | system process IDs (PID) space utilization |
110
+
111
+
112
+## Metrics
113
+
114
+Metrics grouped by *scope*.
115
+
116
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
117
+
118
+
119
+
120
+### Per vm.vmtotal instance
121
+
122
+These metrics show an overall vision about processes running.
123
+
124
+This scope has no labels.
125
+
126
+Metrics:
127
+
128
+| Metric | Dimensions | Unit |
129
+|:------|:----------|:----|
130
+| system.active_processes | active | processes |
131
+| system.processes | running, blocked | processes |
132
+| mem.real | used | MiB |
133
+
134
+
src/collectors/freebsd.plugin/integrations/zfs.md
+59
-59
@@ -43,65 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per zfs instance
55
-
56
-These metrics show detailed information about ZFS filesystem.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| zfs.arc_size | arcsz, target, min, max | MiB |
65
-| zfs.l2_size | actual, size | MiB |
66
-| zfs.reads | arc, demand, prefetch, metadata, l2 | reads/s |
67
-| zfs.bytes | read, write | KiB/s |
68
-| zfs.hits | hits, misses | percentage |
69
-| zfs.hits_rate | hits, misses | events/s |
70
-| zfs.dhits | hits, misses | percentage |
71
-| zfs.dhits_rate | hits, misses | events/s |
72
-| zfs.phits | hits, misses | percentage |
73
-| zfs.phits_rate | hits, misses | events/s |
74
-| zfs.mhits | hits, misses | percentage |
75
-| zfs.mhits_rate | hits, misses | events/s |
76
-| zfs.l2hits | hits, misses | percentage |
77
-| zfs.l2hits_rate | hits, misses | events/s |
78
-| zfs.list_hits | mfu, mfu_ghost, mru, mru_ghost | hits/s |
79
-| zfs.arc_size_breakdown | recent, frequent | percentage |
80
-| zfs.memory_ops | throttled | operations/s |
81
-| zfs.important_ops | evict_skip, deleted, mutex_miss, hash_collisions | operations/s |
82
-| zfs.actual_hits | hits, misses | percentage |
83
-| zfs.actual_hits_rate | hits, misses | events/s |
84
-| zfs.demand_data_hits | hits, misses | percentage |
85
-| zfs.demand_data_hits_rate | hits, misses | events/s |
86
-| zfs.prefetch_data_hits | hits, misses | percentage |
87
-| zfs.prefetch_data_hits_rate | hits, misses | events/s |
88
-| zfs.hash_elements | current, max | elements |
89
-| zfs.hash_chains | current, max | chains |
90
-| zfs.trim_bytes | TRIMmed | bytes |
91
-| zfs.trim_requests | successful, failed, unsupported | requests |
92
-
93
-
94
-
95
-## Alerts
96
-
97
-
98
-The following alerts are available:
99
-
100
-| Alert name | On metric | Description |
101
-|:------------|:----------|:------------|
102
-| [ zfs_memory_throttle ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfs.memory_ops | number of times ZFS had to limit the ARC growth in the last 10 minutes |
103
-
104
-
46
## Setup
47
48
@@ -155,3 +96,62 @@ sudo ./edit-config netdata.conf
96
There are no configuration examples.
97
98
99
+
100
+## Alerts
101
+
102
+
103
+The following alerts are available:
104
+
105
+| Alert name | On metric | Description |
106
+|:------------|:----------|:------------|
107
+| [ zfs_memory_throttle ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfs.memory_ops | number of times ZFS had to limit the ARC growth in the last 10 minutes |
108
+
109
+
110
+## Metrics
111
+
112
+Metrics grouped by *scope*.
113
+
114
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
115
+
116
+
117
+
118
+### Per zfs instance
119
+
120
+These metrics show detailed information about ZFS filesystem.
121
+
122
+This scope has no labels.
123
+
124
+Metrics:
125
+
126
+| Metric | Dimensions | Unit |
127
+|:------|:----------|:----|
128
+| zfs.arc_size | arcsz, target, min, max | MiB |
129
+| zfs.l2_size | actual, size | MiB |
130
+| zfs.reads | arc, demand, prefetch, metadata, l2 | reads/s |
131
+| zfs.bytes | read, write | KiB/s |
132
+| zfs.hits | hits, misses | percentage |
133
+| zfs.hits_rate | hits, misses | events/s |
134
+| zfs.dhits | hits, misses | percentage |
135
+| zfs.dhits_rate | hits, misses | events/s |
136
+| zfs.phits | hits, misses | percentage |
137
+| zfs.phits_rate | hits, misses | events/s |
138
+| zfs.mhits | hits, misses | percentage |
139
+| zfs.mhits_rate | hits, misses | events/s |
140
+| zfs.l2hits | hits, misses | percentage |
141
+| zfs.l2hits_rate | hits, misses | events/s |
142
+| zfs.list_hits | mfu, mfu_ghost, mru, mru_ghost | hits/s |
143
+| zfs.arc_size_breakdown | recent, frequent | percentage |
144
+| zfs.memory_ops | throttled | operations/s |
145
+| zfs.important_ops | evict_skip, deleted, mutex_miss, hash_collisions | operations/s |
146
+| zfs.actual_hits | hits, misses | percentage |
147
+| zfs.actual_hits_rate | hits, misses | events/s |
148
+| zfs.demand_data_hits | hits, misses | percentage |
149
+| zfs.demand_data_hits_rate | hits, misses | events/s |
150
+| zfs.prefetch_data_hits | hits, misses | percentage |
151
+| zfs.prefetch_data_hits_rate | hits, misses | events/s |
152
+| zfs.hash_elements | current, max | elements |
153
+| zfs.hash_chains | current, max | chains |
154
+| zfs.trim_bytes | TRIMmed | bytes |
155
+| zfs.trim_requests | successful, failed, unsupported | requests |
156
+
157
+
src/collectors/freeipmi.plugin/integrations/intelligent_platform_management_interface_ipmi.md
+58
-58
@@ -47,64 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
Linux kernel module for IPMI can create big overhead.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-The plugin does a speed test when it starts, to find out the duration needed by the IPMI processor to respond. Depending on the speed of your IPMI processor, charts may need several seconds to show up on the dashboard.
57
-
58
-
59
-### Per Intelligent Platform Management Interface (IPMI) instance
60
-
61
-These metrics refer to the entire monitored application.
62
-
63
-This scope has no labels.
64
-
65
-Metrics:
66
-
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| ipmi.sel | events | events |
70
-
71
-### Per sensor
72
-
73
-
74
-
75
-Labels:
76
-
77
-| Label | Description |
78
-|:-----------|:----------------|
79
-| sensor | The sensor name |
80
-| type | One of 45 recognized sensor types (Battery, Voltage...) |
81
-| component | One of 25 recognized components (Processor, Peripheral). |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| ipmi.sensor_state | nominal, critical, warning, unknown | state |
88
-| ipmi.sensor_temperature_c | temperature | Celsius |
89
-| ipmi.sensor_temperature_f | temperature | Fahrenheit |
90
-| ipmi.sensor_voltage | voltage | Volts |
91
-| ipmi.sensor_ampere | ampere | Amps |
92
-| ipmi.sensor_fan_speed | rotations | RPM |
93
-| ipmi.sensor_power | power | Watts |
94
-| ipmi.sensor_reading_percent | percentage | % |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-
101
-The following alerts are available:
102
-
103
-| Alert name | On metric | Description |
104
-|:------------|:----------|:------------|
105
-| [ ipmi_sensor_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipmi.conf) | ipmi.sensor_state | IPMI sensor ${label:sensor} (${label:component}) state |
106
-
107
-
50
## Setup
51
52
@@ -268,6 +210,64 @@ ID | Name | Type | State | Reading | Unit
210
211
212
213
+## Alerts
214
+
215
+
216
+The following alerts are available:
217
+
218
+| Alert name | On metric | Description |
219
+|:------------|:----------|:------------|
220
+| [ ipmi_sensor_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipmi.conf) | ipmi.sensor_state | IPMI sensor ${label:sensor} (${label:component}) state |
221
+
222
+
223
+## Metrics
224
+
225
+Metrics grouped by *scope*.
226
+
227
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
228
+
229
+The plugin does a speed test when it starts, to find out the duration needed by the IPMI processor to respond. Depending on the speed of your IPMI processor, charts may need several seconds to show up on the dashboard.
230
+
231
+
232
+### Per Intelligent Platform Management Interface (IPMI) instance
233
+
234
+These metrics refer to the entire monitored application.
235
+
236
+This scope has no labels.
237
+
238
+Metrics:
239
+
240
+| Metric | Dimensions | Unit |
241
+|:------|:----------|:----|
242
+| ipmi.sel | events | events |
243
+
244
+### Per sensor
245
+
246
+
247
+
248
+Labels:
249
+
250
+| Label | Description |
251
+|:-----------|:----------------|
252
+| sensor | The sensor name |
253
+| type | One of 45 recognized sensor types (Battery, Voltage...) |
254
+| component | One of 25 recognized components (Processor, Peripheral). |
255
+
256
+Metrics:
257
+
258
+| Metric | Dimensions | Unit |
259
+|:------|:----------|:----|
260
+| ipmi.sensor_state | nominal, critical, warning, unknown | state |
261
+| ipmi.sensor_temperature_c | temperature | Celsius |
262
+| ipmi.sensor_temperature_f | temperature | Fahrenheit |
263
+| ipmi.sensor_voltage | voltage | Volts |
264
+| ipmi.sensor_ampere | ampere | Amps |
265
+| ipmi.sensor_fan_speed | rotations | RPM |
266
+| ipmi.sensor_power | power | Watts |
267
+| ipmi.sensor_reading_percent | percentage | % |
268
+
269
+
270
+
271
## Troubleshooting
272
273
### Debug Mode
src/collectors/guides/proxmox/integrations/proxmox_ve_monitoring.md
+11
-11
@@ -81,17 +81,6 @@ The default configuration for this integration does not impose any limits on dat
81
82
The default configuration for this integration is not expected to impose a significant performance impact on the system.
83
84
-## Metrics
85
-
86
-This guide does not collect metrics directly. Metrics are collected by the related integrations listed above. See each integration's page for detailed metric documentation.
87
-
88
-
89
-
90
-## Alerts
91
-
92
-There are no alerts configured by default for this integration.
93
-
94
-
84
## Setup
85
86
@@ -126,6 +115,17 @@ There are no configuration examples.
115
116
117
118
+## Alerts
119
+
120
+There are no alerts configured by default for this integration.
121
+
122
+
123
+## Metrics
124
+
125
+This guide does not collect metrics directly. Metrics are collected by the related integrations listed above. See each integration's page for detailed metric documentation.
126
+
127
+
128
+
129
## Troubleshooting
130
131
### VM or container names not resolved
src/collectors/idlejitter.plugin/integrations/idle_os_jitter.md
+27
-27
@@ -46,33 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-Metrics grouped by *scope*.
52
-
53
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
54
-
55
-
56
-
57
-### Per Idle OS Jitter instance
58
-
59
-
60
-
61
-This scope has no labels.
62
-
63
-Metrics:
64
-
65
-| Metric | Dimensions | Unit |
66
-|:------|:----------|:----|
67
-| system.idlejitter | min, max, average | microseconds lost/s |
68
-
69
-
70
-
71
-## Alerts
72
-
73
-There are no alerts configured by default for this integration.
74
-
75
-
49
## Setup
50
51
@@ -122,3 +95,30 @@ sudo ./edit-config netdata.conf
95
There are no configuration examples.
96
97
98
+
99
+## Alerts
100
+
101
+There are no alerts configured by default for this integration.
102
+
103
+
104
+## Metrics
105
+
106
+Metrics grouped by *scope*.
107
+
108
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
109
+
110
+
111
+
112
+### Per Idle OS Jitter instance
113
+
114
+
115
+
116
+This scope has no labels.
117
+
118
+Metrics:
119
+
120
+| Metric | Dimensions | Unit |
121
+|:------|:----------|:----|
122
+| system.idlejitter | min, max, average | microseconds lost/s |
123
+
124
+
src/collectors/ioping.plugin/integrations/ioping.md
+32
-32
@@ -43,38 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per disk
55
-
56
-
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| ioping.latency | latency | microseconds |
65
-
66
-
67
-
68
-## Alerts
69
-
70
-
71
-The following alerts are available:
72
-
73
-| Alert name | On metric | Description |
74
-|:------------|:----------|:------------|
75
-| [ ioping_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ioping.conf) | ioping.latency | average I/O latency over the last 10 seconds |
76
-
77
-
46
## Setup
47
48
@@ -141,3 +109,35 @@ destination="/dev/sda"
109
</details>
110
111
112
+
113
+## Alerts
114
+
115
+
116
+The following alerts are available:
117
+
118
+| Alert name | On metric | Description |
119
+|:------------|:----------|:------------|
120
+| [ ioping_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ioping.conf) | ioping.latency | average I/O latency over the last 10 seconds |
121
+
122
+
123
+## Metrics
124
+
125
+Metrics grouped by *scope*.
126
+
127
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
128
+
129
+
130
+
131
+### Per disk
132
+
133
+
134
+
135
+This scope has no labels.
136
+
137
+Metrics:
138
+
139
+| Metric | Dimensions | Unit |
140
+|:------|:----------|:----|
141
+| ioping.latency | latency | microseconds |
142
+
143
+
src/collectors/macos.plugin/integrations/macos.md
+115
-115
@@ -50,121 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per macOS instance
62
-
63
-These metrics refer to hardware and network monitoring.
64
-
65
-
66
-This scope has no labels.
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| system.cpu | user, nice, system, idle | percentage |
73
-| system.ram | active, wired, throttled, compressor, inactive, purgeable, speculative, free | MiB |
74
-| mem.swapio | io, out | KiB/s |
75
-| mem.pgfaults | memory, cow, pagein, pageout, compress, decompress, zero_fill, reactivate, purge | faults/s |
76
-| system.load | load1, load5, load15 | load |
77
-| mem.swap | free, used | MiB |
78
-| system.ipv4 | received, sent | kilobits/s |
79
-| ipv4.tcppackets | received, sent | packets/s |
80
-| ipv4.tcperrors | InErrs, InCsumErrors, RetransSegs | packets/s |
81
-| ipv4.tcphandshake | EstabResets, ActiveOpens, PassiveOpens, AttemptFails | events/s |
82
-| ipv4.tcpconnaborts | baddata, userclosed, nomemory, timeout | connections/s |
83
-| ipv4.tcpofo | inqueue | packets/s |
84
-| ipv4.tcpsyncookies | received, sent, failed | packets/s |
85
-| ipv4.ecnpkts | CEP, NoECTP | packets/s |
86
-| ipv4.udppackets | received, sent | packets/s |
87
-| ipv4.udperrors | RcvbufErrors, InErrors, NoPorts, InCsumErrors, IgnoredMulti | events/s |
88
-| ipv4.icmp | received, sent | packets/s |
89
-| ipv4.icmp_errors | InErrors, OutErrors, InCsumErrors | packets/s |
90
-| ipv4.icmpmsg | InEchoReps, OutEchoReps, InEchos, OutEchos | packets/s |
91
-| ipv4.packets | received, sent, forwarded, delivered | packets/s |
92
-| ipv4.fragsout | ok, failed, created | packets/s |
93
-| ipv4.fragsin | ok, failed, all | packets/s |
94
-| ipv4.errors | InDiscards, OutDiscards, InHdrErrors, OutNoRoutes, InAddrErrors, InUnknownProtos | packets/s |
95
-| ipv6.packets | received, sent, forwarded, delivers | packets/s |
96
-| ipv6.fragsout | ok, failed, all | packets/s |
97
-| ipv6.fragsin | ok, failed, timeout, all | packets/s |
98
-| ipv6.errors | InDiscards, OutDiscards, InHdrErrors, InAddrErrors, InTruncatedPkts, InNoRoutes, OutNoRoutes | packets/s |
99
-| ipv6.icmp | received, sent | messages/s |
100
-| ipv6.icmpredir | received, sent | redirects/s |
101
-| ipv6.icmperrors | InErrors, OutErrors, InCsumErrors, InDestUnreachs, InPktTooBigs, InTimeExcds, InParmProblems, OutDestUnreachs, OutTimeExcds, OutParmProblems | errors/s |
102
-| ipv6.icmpechos | InEchos, OutEchos, InEchoReplies, OutEchoReplies | messages/s |
103
-| ipv6.icmprouter | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
104
-| ipv6.icmpneighbor | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
105
-| ipv6.icmptypes | InType1, InType128, InType129, InType136, OutType1, OutType128, OutType129, OutType133, OutType135, OutType143 | messages/s |
106
-| system.uptime | uptime | seconds |
107
-| system.io | in, out | KiB/s |
108
-
109
-### Per disk
110
-
111
-
112
-
113
-This scope has no labels.
114
-
115
-Metrics:
116
-
117
-| Metric | Dimensions | Unit |
118
-|:------|:----------|:----|
119
-| disk.io | read, writes | KiB/s |
120
-| disk.ops | read, writes | operations/s |
121
-| disk.util | utilization | % of time working |
122
-| disk.iotime | reads, writes | milliseconds/s |
123
-| disk.await | reads, writes | milliseconds/operation |
124
-| disk.avgsz | reads, writes | KiB/operation |
125
-| disk.svctm | svctm | milliseconds/operation |
126
-
127
-### Per mount point
128
-
129
-
130
-
131
-This scope has no labels.
132
-
133
-Metrics:
134
-
135
-| Metric | Dimensions | Unit |
136
-|:------|:----------|:----|
137
-| disk.space | avail, used, reserved_for_root | GiB |
138
-| disk.inodes | avail, used, reserved_for_root | inodes |
139
-
140
-### Per network device
141
-
142
-
143
-
144
-This scope has no labels.
145
-
146
-Metrics:
147
-
148
-| Metric | Dimensions | Unit |
149
-|:------|:----------|:----|
150
-| net.net | received, sent | kilobits/s |
151
-| net.packets | received, sent, multicast_received, multicast_sent | packets/s |
152
-| net.errors | inbound, outbound | errors/s |
153
-| net.drops | inbound | drops/s |
154
-| net.events | frames, collisions, carrier | events/s |
155
-
156
-
157
-
158
-## Alerts
159
-
160
-
161
-The following alerts are available:
162
-
163
-| Alert name | On metric | Description |
164
-|:------------|:----------|:------------|
165
-| [ interface_speed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | network interface ${label:device} current speed |
166
-
167
-
53
## Setup
54
55
@@ -290,3 +175,118 @@ A basic example that discards swap monitoring
175
</details>
176
177
178
+
179
+## Alerts
180
+
181
+
182
+The following alerts are available:
183
+
184
+| Alert name | On metric | Description |
185
+|:------------|:----------|:------------|
186
+| [ interface_speed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | network interface ${label:device} current speed |
187
+
188
+
189
+## Metrics
190
+
191
+Metrics grouped by *scope*.
192
+
193
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
194
+
195
+
196
+
197
+### Per macOS instance
198
+
199
+These metrics refer to hardware and network monitoring.
200
+
201
+
202
+This scope has no labels.
203
+
204
+Metrics:
205
+
206
+| Metric | Dimensions | Unit |
207
+|:------|:----------|:----|
208
+| system.cpu | user, nice, system, idle | percentage |
209
+| system.ram | active, wired, throttled, compressor, inactive, purgeable, speculative, free | MiB |
210
+| mem.swapio | io, out | KiB/s |
211
+| mem.pgfaults | memory, cow, pagein, pageout, compress, decompress, zero_fill, reactivate, purge | faults/s |
212
+| system.load | load1, load5, load15 | load |
213
+| mem.swap | free, used | MiB |
214
+| system.ipv4 | received, sent | kilobits/s |
215
+| ipv4.tcppackets | received, sent | packets/s |
216
+| ipv4.tcperrors | InErrs, InCsumErrors, RetransSegs | packets/s |
217
+| ipv4.tcphandshake | EstabResets, ActiveOpens, PassiveOpens, AttemptFails | events/s |
218
+| ipv4.tcpconnaborts | baddata, userclosed, nomemory, timeout | connections/s |
219
+| ipv4.tcpofo | inqueue | packets/s |
220
+| ipv4.tcpsyncookies | received, sent, failed | packets/s |
221
+| ipv4.ecnpkts | CEP, NoECTP | packets/s |
222
+| ipv4.udppackets | received, sent | packets/s |
223
+| ipv4.udperrors | RcvbufErrors, InErrors, NoPorts, InCsumErrors, IgnoredMulti | events/s |
224
+| ipv4.icmp | received, sent | packets/s |
225
+| ipv4.icmp_errors | InErrors, OutErrors, InCsumErrors | packets/s |
226
+| ipv4.icmpmsg | InEchoReps, OutEchoReps, InEchos, OutEchos | packets/s |
227
+| ipv4.packets | received, sent, forwarded, delivered | packets/s |
228
+| ipv4.fragsout | ok, failed, created | packets/s |
229
+| ipv4.fragsin | ok, failed, all | packets/s |
230
+| ipv4.errors | InDiscards, OutDiscards, InHdrErrors, OutNoRoutes, InAddrErrors, InUnknownProtos | packets/s |
231
+| ipv6.packets | received, sent, forwarded, delivers | packets/s |
232
+| ipv6.fragsout | ok, failed, all | packets/s |
233
+| ipv6.fragsin | ok, failed, timeout, all | packets/s |
234
+| ipv6.errors | InDiscards, OutDiscards, InHdrErrors, InAddrErrors, InTruncatedPkts, InNoRoutes, OutNoRoutes | packets/s |
235
+| ipv6.icmp | received, sent | messages/s |
236
+| ipv6.icmpredir | received, sent | redirects/s |
237
+| ipv6.icmperrors | InErrors, OutErrors, InCsumErrors, InDestUnreachs, InPktTooBigs, InTimeExcds, InParmProblems, OutDestUnreachs, OutTimeExcds, OutParmProblems | errors/s |
238
+| ipv6.icmpechos | InEchos, OutEchos, InEchoReplies, OutEchoReplies | messages/s |
239
+| ipv6.icmprouter | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
240
+| ipv6.icmpneighbor | InSolicits, OutSolicits, InAdvertisements, OutAdvertisements | messages/s |
241
+| ipv6.icmptypes | InType1, InType128, InType129, InType136, OutType1, OutType128, OutType129, OutType133, OutType135, OutType143 | messages/s |
242
+| system.uptime | uptime | seconds |
243
+| system.io | in, out | KiB/s |
244
+
245
+### Per disk
246
+
247
+
248
+
249
+This scope has no labels.
250
+
251
+Metrics:
252
+
253
+| Metric | Dimensions | Unit |
254
+|:------|:----------|:----|
255
+| disk.io | read, writes | KiB/s |
256
+| disk.ops | read, writes | operations/s |
257
+| disk.util | utilization | % of time working |
258
+| disk.iotime | reads, writes | milliseconds/s |
259
+| disk.await | reads, writes | milliseconds/operation |
260
+| disk.avgsz | reads, writes | KiB/operation |
261
+| disk.svctm | svctm | milliseconds/operation |
262
+
263
+### Per mount point
264
+
265
+
266
+
267
+This scope has no labels.
268
+
269
+Metrics:
270
+
271
+| Metric | Dimensions | Unit |
272
+|:------|:----------|:----|
273
+| disk.space | avail, used, reserved_for_root | GiB |
274
+| disk.inodes | avail, used, reserved_for_root | inodes |
275
+
276
+### Per network device
277
+
278
+
279
+
280
+This scope has no labels.
281
+
282
+Metrics:
283
+
284
+| Metric | Dimensions | Unit |
285
+|:------|:----------|:----|
286
+| net.net | received, sent | kilobits/s |
287
+| net.packets | received, sent, multicast_received, multicast_sent | packets/s |
288
+| net.errors | inbound, outbound | errors/s |
289
+| net.drops | inbound | drops/s |
290
+| net.events | frames, collisions, carrier | events/s |
291
+
292
+
src/collectors/network-viewer.plugin/integrations/network_connections.md
+32
-32
@@ -49,12 +49,43 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+There are no configuration options.
66
+
67
+
68
+
69
+#### via File
70
+
71
+There is no configuration file.
72
+
73
+##### Examples
74
+There are no configuration examples.
75
+
76
+
77
+
78
+## Alerts
79
+
80
+There are no alerts configured by default for this integration.
81
+
82
+
83
## Metrics
84
85
86
87
57
-## Functions
88
+## Live Data
89
90
This plugin exposes a real-time function for viewing active network connections.
91
@@ -94,34 +125,3 @@ This function has no parameters.
125
|:-------|:-----|:-----|:-----------|:------------|
126
127
97
-
98
-## Alerts
99
-
100
-There are no alerts configured by default for this integration.
101
-
102
-
103
-## Setup
104
-
105
-
106
-### Prerequisites
107
-
108
-No action required.
109
-
110
-### Configuration
111
-
112
-#### Options
113
-
114
-
115
-
116
-There are no configuration options.
117
-
118
-
119
-
120
-#### via File
121
-
122
-There is no configuration file.
123
-
124
-##### Examples
125
-There are no configuration examples.
126
-
127
-
src/collectors/nfacct.plugin/integrations/netfilter.md
+33
-33
@@ -44,39 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per Netfilter instance
56
-
57
-
58
-
59
-This scope has no labels.
60
-
61
-Metrics:
62
-
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| netfilter.netlink_new | new, ignore, invalid | connections/s |
66
-| netfilter.netlink_changes | insert, delete, delete_list | changes/s |
67
-| netfilter.netlink_search | searched, search_restart, found | searches/s |
68
-| netfilter.netlink_errors | icmp_error, insert_failed, drop, early_drop | events/s |
69
-| netfilter.netlink_expect | created, deleted, new | expectations/s |
70
-| netfilter.nfacct_packets | a dimension per nfacct object | packets/s |
71
-| netfilter.nfacct_bytes | a dimension per nfacct object | kilobytes/s |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-There are no alerts configured by default for this integration.
78
-
79
-
47
## Setup
48
49
@@ -135,3 +102,36 @@ sudo ./edit-config netdata.conf
102
There are no configuration examples.
103
104
105
+
106
+## Alerts
107
+
108
+There are no alerts configured by default for this integration.
109
+
110
+
111
+## Metrics
112
+
113
+Metrics grouped by *scope*.
114
+
115
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
116
+
117
+
118
+
119
+### Per Netfilter instance
120
+
121
+
122
+
123
+This scope has no labels.
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| netfilter.netlink_new | new, ignore, invalid | connections/s |
130
+| netfilter.netlink_changes | insert, delete, delete_list | changes/s |
131
+| netfilter.netlink_search | searched, search_restart, found | searches/s |
132
+| netfilter.netlink_errors | icmp_error, insert_failed, drop, early_drop | events/s |
133
+| netfilter.netlink_expect | created, deleted, new | expectations/s |
134
+| netfilter.nfacct_packets | a dimension per nfacct object | packets/s |
135
+| netfilter.nfacct_bytes | a dimension per nfacct object | kilobytes/s |
136
+
137
+
src/collectors/perf.plugin/integrations/cpu_performance.md
+43
-43
@@ -47,49 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per CPU performance instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| perf.cpu_cycles | cpu, ref_cpu | cycles/s |
69
-| perf.instructions | instructions | instructions/s |
70
-| perf.instructions_per_cycle | ipc | instructions/cycle |
71
-| perf.branch_instructions | instructions, misses | instructions/s |
72
-| perf.cache | references, misses | operations/s |
73
-| perf.bus_cycles | bus | cycles/s |
74
-| perf.stalled_cycles | frontend, backend | cycles/s |
75
-| perf.migrations | migrations | migrations |
76
-| perf.alignment_faults | faults | faults |
77
-| perf.emulation_faults | faults | faults |
78
-| perf.l1d_cache | read_access, read_misses, write_access, write_misses | events/s |
79
-| perf.l1d_cache_prefetch | prefetches | prefetches/s |
80
-| perf.l1i_cache | read_access, read_misses | events/s |
81
-| perf.ll_cache | read_access, read_misses, write_access, write_misses | events/s |
82
-| perf.dtlb_cache | read_access, read_misses, write_access, write_misses | events/s |
83
-| perf.itlb_cache | read_access, read_misses | events/s |
84
-| perf.pbu_cache | read_access | events/s |
85
-
86
-
87
-
88
-## Alerts
89
-
90
-There are no alerts configured by default for this integration.
91
-
92
-
50
## Setup
51
52
@@ -189,6 +146,49 @@ Monitor CPU cycles.
146
147
148
149
+## Alerts
150
+
151
+There are no alerts configured by default for this integration.
152
+
153
+
154
+## Metrics
155
+
156
+Metrics grouped by *scope*.
157
+
158
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
159
+
160
+
161
+
162
+### Per CPU performance instance
163
+
164
+These metrics refer to the entire monitored application.
165
+
166
+This scope has no labels.
167
+
168
+Metrics:
169
+
170
+| Metric | Dimensions | Unit |
171
+|:------|:----------|:----|
172
+| perf.cpu_cycles | cpu, ref_cpu | cycles/s |
173
+| perf.instructions | instructions | instructions/s |
174
+| perf.instructions_per_cycle | ipc | instructions/cycle |
175
+| perf.branch_instructions | instructions, misses | instructions/s |
176
+| perf.cache | references, misses | operations/s |
177
+| perf.bus_cycles | bus | cycles/s |
178
+| perf.stalled_cycles | frontend, backend | cycles/s |
179
+| perf.migrations | migrations | migrations |
180
+| perf.alignment_faults | faults | faults |
181
+| perf.emulation_faults | faults | faults |
182
+| perf.l1d_cache | read_access, read_misses, write_access, write_misses | events/s |
183
+| perf.l1d_cache_prefetch | prefetches | prefetches/s |
184
+| perf.l1i_cache | read_access, read_misses | events/s |
185
+| perf.ll_cache | read_access, read_misses, write_access, write_misses | events/s |
186
+| perf.dtlb_cache | read_access, read_misses, write_access, write_misses | events/s |
187
+| perf.itlb_cache | read_access, read_misses | events/s |
188
+| perf.pbu_cache | read_access | events/s |
189
+
190
+
191
+
192
## Troubleshooting
193
194
### Debug Mode
src/collectors/proc.plugin/integrations/amd_gpu.md
+31
-31
@@ -46,6 +46,37 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
+## Setup
50
+
51
+
52
+### Prerequisites
53
+
54
+No action required.
55
+
56
+### Configuration
57
+
58
+#### Options
59
+
60
+
61
+
62
+There are no configuration options.
63
+
64
+
65
+
66
+#### via File
67
+
68
+There is no configuration file.
69
+
70
+##### Examples
71
+There are no configuration examples.
72
+
73
+
74
+
75
+## Alerts
76
+
77
+There are no alerts configured by default for this integration.
78
+
79
+
80
## Metrics
81
82
Metrics grouped by *scope*.
@@ -80,34 +111,3 @@ Metrics:
111
| amdgpu.gpu_mem_gtt_usage | free, used | bytes |
112
113
83
-
84
-## Alerts
85
-
86
-There are no alerts configured by default for this integration.
87
-
88
-
89
-## Setup
90
-
91
-
92
-### Prerequisites
93
-
94
-No action required.
95
-
96
-### Configuration
97
-
98
-#### Options
99
-
100
-
101
-
102
-There are no configuration options.
103
-
104
-
105
-
106
-#### via File
107
-
108
-There is no configuration file.
109
-
110
-##### Examples
111
-There are no configuration examples.
112
-
113
-
src/collectors/proc.plugin/integrations/bcache.md
+46
-46
@@ -48,52 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per disk
60
-
61
-
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| device | TBD |
68
-| mount_point | TBD |
69
-| device_type | TBD |
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| disk.bcache_cache_alloc | ununsed, dirty, clean, metadata, undefined | percentage |
76
-| disk.bcache_hit_ratio | 5min, 1hour, 1day, ever | percentage |
77
-| disk.bcache_rates | congested, writeback | KiB/s |
78
-| disk.bcache_size | dirty | MiB |
79
-| disk.bcache_usage | avail | percentage |
80
-| disk.bcache_cache_read_races | races, errors | operations/s |
81
-| disk.bcache | hits, misses, collisions, readaheads | operations/s |
82
-| disk.bcache_bypass | hits, misses | operations/s |
83
-
84
-
85
-
86
-## Alerts
87
-
88
-
89
-The following alerts are available:
90
-
91
-| Alert name | On metric | Description |
92
-|:------------|:----------|:------------|
93
-| [ bcache_cache_dirty ](https://github.com/netdata/netdata/blob/master/src/health/health.d/bcache.conf) | disk.bcache_cache_alloc | percentage of cache space used for dirty data and metadata (this usually means your SSD cache is too small) |
94
-| [ bcache_cache_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/bcache.conf) | disk.bcache_cache_read_races | number of times data was read from the cache, the bucket was reused and invalidated in the last 10 minutes (when this occurs the data is reread from the backing device) |
95
-
96
-
51
## Setup
52
53
@@ -137,3 +91,49 @@ sudo ./edit-config netdata.conf
91
There are no configuration examples.
92
93
94
+
95
+## Alerts
96
+
97
+
98
+The following alerts are available:
99
+
100
+| Alert name | On metric | Description |
101
+|:------------|:----------|:------------|
102
+| [ bcache_cache_dirty ](https://github.com/netdata/netdata/blob/master/src/health/health.d/bcache.conf) | disk.bcache_cache_alloc | percentage of cache space used for dirty data and metadata (this usually means your SSD cache is too small) |
103
+| [ bcache_cache_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/bcache.conf) | disk.bcache_cache_read_races | number of times data was read from the cache, the bucket was reused and invalidated in the last 10 minutes (when this occurs the data is reread from the backing device) |
104
+
105
+
106
+## Metrics
107
+
108
+Metrics grouped by *scope*.
109
+
110
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
111
+
112
+
113
+
114
+### Per disk
115
+
116
+
117
+
118
+Labels:
119
+
120
+| Label | Description |
121
+|:-----------|:----------------|
122
+| device | TBD |
123
+| mount_point | TBD |
124
+| device_type | TBD |
125
+
126
+Metrics:
127
+
128
+| Metric | Dimensions | Unit |
129
+|:------|:----------|:----|
130
+| disk.bcache_cache_alloc | ununsed, dirty, clean, metadata, undefined | percentage |
131
+| disk.bcache_hit_ratio | 5min, 1hour, 1day, ever | percentage |
132
+| disk.bcache_rates | congested, writeback | KiB/s |
133
+| disk.bcache_size | dirty | MiB |
134
+| disk.bcache_usage | avail | percentage |
135
+| disk.bcache_cache_read_races | races, errors | operations/s |
136
+| disk.bcache | hits, misses, collisions, readaheads | operations/s |
137
+| disk.bcache_bypass | hits, misses | operations/s |
138
+
139
+
src/collectors/proc.plugin/integrations/btrfs.md
+44
-44
@@ -44,6 +44,50 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+
76
+The following alerts are available:
77
+
78
+| Alert name | On metric | Description |
79
+|:------------|:----------|:------------|
80
+| [ btrfs_allocated ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.disk | percentage of allocated BTRFS physical disk space |
81
+| [ btrfs_data ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.data | utilization of BTRFS data space |
82
+| [ btrfs_metadata ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.metadata | utilization of BTRFS metadata space |
83
+| [ btrfs_system ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.system | utilization of BTRFS system space |
84
+| [ btrfs_device_read_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS read errors |
85
+| [ btrfs_device_write_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS write errors |
86
+| [ btrfs_device_flush_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS flush errors |
87
+| [ btrfs_device_corruption_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS corruption errors |
88
+| [ btrfs_device_generation_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS generation errors |
89
+
90
+
91
## Metrics
92
93
Metrics grouped by *scope*.
@@ -94,47 +138,3 @@ Metrics:
138
| btrfs.device_errors | write_errs, read_errs, flush_errs, corruption_errs, generation_errs | errors |
139
140
97
-
98
-## Alerts
99
-
100
-
101
-The following alerts are available:
102
-
103
-| Alert name | On metric | Description |
104
-|:------------|:----------|:------------|
105
-| [ btrfs_allocated ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.disk | percentage of allocated BTRFS physical disk space |
106
-| [ btrfs_data ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.data | utilization of BTRFS data space |
107
-| [ btrfs_metadata ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.metadata | utilization of BTRFS metadata space |
108
-| [ btrfs_system ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.system | utilization of BTRFS system space |
109
-| [ btrfs_device_read_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS read errors |
110
-| [ btrfs_device_write_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS write errors |
111
-| [ btrfs_device_flush_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS flush errors |
112
-| [ btrfs_device_corruption_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS corruption errors |
113
-| [ btrfs_device_generation_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/btrfs.conf) | btrfs.device_errors | number of encountered BTRFS generation errors |
114
-
115
-
116
-## Setup
117
-
118
-
119
-### Prerequisites
120
-
121
-No action required.
122
-
123
-### Configuration
124
-
125
-#### Options
126
-
127
-
128
-
129
-There are no configuration options.
130
-
131
-
132
-
133
-#### via File
134
-
135
-There is no configuration file.
136
-
137
-##### Examples
138
-There are no configuration examples.
139
-
140
-
src/collectors/proc.plugin/integrations/conntrack.md
+27
-27
@@ -44,30 +44,29 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per Conntrack instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| netfilter.conntrack_sockets | connections | active connections |
66
-| netfilter.conntrack_new | new, ignore, invalid | connections/s |
67
-| netfilter.conntrack_changes | inserted, deleted, delete_list | changes/s |
68
-| netfilter.conntrack_expect | created, deleted, new | expectations/s |
69
-| netfilter.conntrack_search | searched, restarted, found | searches/s |
70
-| netfilter.conntrack_errors | icmp_error, error_failed, drop, early_drop | events/s |
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
71
72
@@ -81,28 +80,29 @@ The following alerts are available:
80
| [ netfilter_conntrack_full ](https://github.com/netdata/netdata/blob/master/src/health/health.d/netfilter.conf) | netfilter.conntrack_sockets | netfilter connection tracker table size utilization |
81
82
84
-## Setup
85
-
86
-
87
-### Prerequisites
88
-
89
-No action required.
83
+## Metrics
84
91
-### Configuration
85
+Metrics grouped by *scope*.
86
93
-#### Options
87
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
88
89
90
97
-There are no configuration options.
91
+### Per Conntrack instance
92
93
94
101
-#### via File
95
+This scope has no labels.
96
103
-There is no configuration file.
97
+Metrics:
98
105
-##### Examples
106
-There are no configuration examples.
99
+| Metric | Dimensions | Unit |
100
+|:------|:----------|:----|
101
+| netfilter.conntrack_sockets | connections | active connections |
102
+| netfilter.conntrack_new | new, ignore, invalid | connections/s |
103
+| netfilter.conntrack_changes | inserted, deleted, delete_list | changes/s |
104
+| netfilter.conntrack_expect | created, deleted, new | expectations/s |
105
+| netfilter.conntrack_search | searched, restarted, found | searches/s |
106
+| netfilter.conntrack_errors | icmp_error, error_failed, drop, early_drop | events/s |
107
108
src/collectors/proc.plugin/integrations/disk_statistics.md
+37
-37
@@ -48,6 +48,43 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
+## Setup
52
+
53
+
54
+### Prerequisites
55
+
56
+No action required.
57
+
58
+### Configuration
59
+
60
+#### Options
61
+
62
+
63
+
64
+There are no configuration options.
65
+
66
+
67
+
68
+#### via File
69
+
70
+There is no configuration file.
71
+
72
+##### Examples
73
+There are no configuration examples.
74
+
75
+
76
+
77
+## Alerts
78
+
79
+
80
+The following alerts are available:
81
+
82
+| Alert name | On metric | Description |
83
+|:------------|:----------|:------------|
84
+| [ 10min_disk_backlog ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.backlog | average backlog size of the ${label:device} disk over the last 10 minutes |
85
+| [ 10min_disk_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.util | average percentage of time ${label:device} disk was busy over the last 10 minutes |
86
+
87
+
88
## Metrics
89
90
Metrics grouped by *scope*.
@@ -103,40 +140,3 @@ Metrics:
140
| disk.svctm | svctm | milliseconds/operation |
141
142
106
-
107
-## Alerts
108
-
109
-
110
-The following alerts are available:
111
-
112
-| Alert name | On metric | Description |
113
-|:------------|:----------|:------------|
114
-| [ 10min_disk_backlog ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.backlog | average backlog size of the ${label:device} disk over the last 10 minutes |
115
-| [ 10min_disk_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/disks.conf) | disk.util | average percentage of time ${label:device} disk was busy over the last 10 minutes |
116
-
117
-
118
-## Setup
119
-
120
-
121
-### Prerequisites
122
-
123
-No action required.
124
-
125
-### Configuration
126
-
127
-#### Options
128
-
129
-
130
-
131
-There are no configuration options.
132
-
133
-
134
-
135
-#### via File
136
-
137
-There is no configuration file.
138
-
139
-##### Examples
140
-There are no configuration examples.
141
-
142
-
src/collectors/proc.plugin/integrations/entropy.md
+22
-22
@@ -77,25 +77,29 @@ The default configuration for this integration does not impose any limits on dat
77
78
The default configuration for this integration is not expected to impose a significant performance impact on the system.
79
80
-## Metrics
80
+## Setup
81
82
-Metrics grouped by *scope*.
82
84
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
+### Prerequisites
84
85
+No action required.
86
87
+### Configuration
88
88
-### Per Entropy instance
89
+#### Options
90
91
92
92
-This scope has no labels.
93
+There are no configuration options.
94
94
-Metrics:
95
96
-| Metric | Dimensions | Unit |
97
-|:------|:----------|:----|
98
-| system.entropy | entropy | entropy |
96
+
97
+#### via File
98
+
99
+There is no configuration file.
100
+
101
+##### Examples
102
+There are no configuration examples.
103
104
105
@@ -109,28 +113,24 @@ The following alerts are available:
113
| [ lowest_entropy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/entropy.conf) | system.entropy | minimum number of bits of entropy available for the kernel’s random number generator |
114
115
112
-## Setup
113
-
114
-
115
-### Prerequisites
116
-
117
-No action required.
116
+## Metrics
117
119
-### Configuration
118
+Metrics grouped by *scope*.
119
121
-#### Options
120
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
121
122
123
125
-There are no configuration options.
124
+### Per Entropy instance
125
126
127
129
-#### via File
128
+This scope has no labels.
129
131
-There is no configuration file.
130
+Metrics:
131
133
-##### Examples
134
-There are no configuration examples.
132
+| Metric | Dimensions | Unit |
133
+|:------|:----------|:----|
134
+| system.entropy | entropy | entropy |
135
136
src/collectors/proc.plugin/integrations/infiniband.md
+25
-25
@@ -44,59 +44,59 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per infiniband port
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| ib.bytes | Received, Sent | kilobits/s |
66
-| ib.packets | Received, Sent, Mcast_rcvd, Mcast_sent, Ucast_rcvd, Ucast_sent | packets/s |
67
-| ib.errors | Pkts_malformated, Pkts_rcvd_discarded, Pkts_sent_discarded, Tick_Wait_to_send, Pkts_missed_resource, Buffer_overrun, Link_Downed, Link_recovered, Link_integrity_err, Link_minor_errors, Pkts_rcvd_with_EBP, Pkts_rcvd_discarded_by_switch, Pkts_sent_discarded_by_switch | errors/s |
68
-| ib.hwerrors | Duplicated_packets, Pkt_Seq_Num_gap, Ack_timer_expired, Drop_missing_buffer, Drop_out_of_sequence, NAK_sequence_rcvd, CQE_err_Req, CQE_err_Resp, CQE_Flushed_err_Req, CQE_Flushed_err_Resp, Remote_access_err_Req, Remote_access_err_Resp, Remote_invalid_req, Local_length_err_Resp, RNR_NAK_Packets, CNP_Pkts_ignored, RoCE_ICRC_Errors | errors/s |
69
-| ib.hwpackets | RoCEv2_Congestion_sent, RoCEv2_Congestion_rcvd, IB_Congestion_handled, ATOMIC_req_rcvd, Connection_req_rcvd, Read_req_rcvd, Write_req_rcvd, RoCE_retrans_adaptive, RoCE_retrans_timeout, RoCE_slow_restart, RoCE_slow_restart_congestion, RoCE_slow_restart_count | packets/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
73
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
75
-There are no alerts configured by default for this integration.
71
72
78
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
81
-### Prerequisites
77
83
-No action required.
78
+## Metrics
79
85
-### Configuration
80
+Metrics grouped by *scope*.
81
87
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
91
-There are no configuration options.
86
+### Per infiniband port
87
88
89
95
-#### via File
90
+This scope has no labels.
91
97
-There is no configuration file.
92
+Metrics:
93
99
-##### Examples
100
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| ib.bytes | Received, Sent | kilobits/s |
97
+| ib.packets | Received, Sent, Mcast_rcvd, Mcast_sent, Ucast_rcvd, Ucast_sent | packets/s |
98
+| ib.errors | Pkts_malformated, Pkts_rcvd_discarded, Pkts_sent_discarded, Tick_Wait_to_send, Pkts_missed_resource, Buffer_overrun, Link_Downed, Link_recovered, Link_integrity_err, Link_minor_errors, Pkts_rcvd_with_EBP, Pkts_rcvd_discarded_by_switch, Pkts_sent_discarded_by_switch | errors/s |
99
+| ib.hwerrors | Duplicated_packets, Pkt_Seq_Num_gap, Ack_timer_expired, Drop_missing_buffer, Drop_out_of_sequence, NAK_sequence_rcvd, CQE_err_Req, CQE_err_Resp, CQE_Flushed_err_Req, CQE_Flushed_err_Resp, Remote_access_err_Req, Remote_access_err_Resp, Remote_invalid_req, Local_length_err_Resp, RNR_NAK_Packets, CNP_Pkts_ignored, RoCE_ICRC_Errors | errors/s |
100
+| ib.hwpackets | RoCEv2_Congestion_sent, RoCEv2_Congestion_rcvd, IB_Congestion_handled, ATOMIC_req_rcvd, Connection_req_rcvd, Read_req_rcvd, Write_req_rcvd, RoCE_retrans_adaptive, RoCE_retrans_timeout, RoCE_slow_restart, RoCE_slow_restart_congestion, RoCE_slow_restart_count | packets/s |
101
102
src/collectors/proc.plugin/integrations/inter_process_communication.md
+27
-27
@@ -58,30 +58,29 @@ The default configuration for this integration does not impose any limits on dat
58
59
The default configuration for this integration is not expected to impose a significant performance impact on the system.
60
61
-## Metrics
61
+## Setup
62
63
-Metrics grouped by *scope*.
63
65
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
64
+### Prerequisites
65
66
+No action required.
67
68
+### Configuration
69
69
-### Per Inter Process Communication instance
70
+#### Options
71
72
73
73
-This scope has no labels.
74
+There are no configuration options.
75
75
-Metrics:
76
77
-| Metric | Dimensions | Unit |
78
-|:------|:----------|:----|
79
-| system.ipc_semaphores | semaphores | semaphores |
80
-| system.ipc_semaphore_arrays | arrays | arrays |
81
-| system.message_queue_message | a dimension per queue | messages |
82
-| system.message_queue_bytes | a dimension per queue | bytes |
83
-| system.shared_memory_segments | segments | segments |
84
-| system.shared_memory_bytes | bytes | bytes |
77
+
78
+#### via File
79
+
80
+There is no configuration file.
81
+
82
+##### Examples
83
+There are no configuration examples.
84
85
86
@@ -96,28 +95,29 @@ The following alerts are available:
95
| [ semaphore_arrays_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipc.conf) | system.ipc_semaphore_arrays | IPC semaphore arrays utilization |
96
97
99
-## Setup
100
-
101
-
102
-### Prerequisites
103
-
104
-No action required.
98
+## Metrics
99
106
-### Configuration
100
+Metrics grouped by *scope*.
101
108
-#### Options
102
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
103
104
105
112
-There are no configuration options.
106
+### Per Inter Process Communication instance
107
108
109
116
-#### via File
110
+This scope has no labels.
111
118
-There is no configuration file.
112
+Metrics:
113
120
-##### Examples
121
-There are no configuration examples.
114
+| Metric | Dimensions | Unit |
115
+|:------|:----------|:----|
116
+| system.ipc_semaphores | semaphores | semaphores |
117
+| system.ipc_semaphore_arrays | arrays | arrays |
118
+| system.message_queue_message | a dimension per queue | messages |
119
+| system.message_queue_bytes | a dimension per queue | bytes |
120
+| system.shared_memory_segments | segments | segments |
121
+| system.shared_memory_bytes | bytes | bytes |
122
123
src/collectors/proc.plugin/integrations/interrupts.md
+30
-30
@@ -74,71 +74,71 @@ The default configuration for this integration does not impose any limits on dat
74
75
The default configuration for this integration is not expected to impose a significant performance impact on the system.
76
77
-## Metrics
77
+## Setup
78
79
-Metrics grouped by *scope*.
79
81
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
80
+### Prerequisites
81
82
+No action required.
83
84
+### Configuration
85
85
-### Per Interrupts instance
86
+#### Options
87
88
89
89
-This scope has no labels.
90
+There are no configuration options.
91
91
-Metrics:
92
93
-| Metric | Dimensions | Unit |
94
-|:------|:----------|:----|
95
-| system.interrupts | a dimension per device | interrupts/s |
93
97
-### Per cpu core
94
+#### via File
95
96
+There is no configuration file.
97
98
+##### Examples
99
+There are no configuration examples.
100
101
-Labels:
101
103
-| Label | Description |
104
-|:-----------|:----------------|
105
-| cpu | TBD |
102
107
-Metrics:
103
+## Alerts
104
109
-| Metric | Dimensions | Unit |
110
-|:------|:----------|:----|
111
-| cpu.interrupts | a dimension per device | interrupts/s |
105
+There are no alerts configured by default for this integration.
106
107
108
+## Metrics
109
115
-## Alerts
110
+Metrics grouped by *scope*.
111
117
-There are no alerts configured by default for this integration.
112
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
113
114
120
-## Setup
115
116
+### Per Interrupts instance
117
123
-### Prerequisites
118
125
-No action required.
119
127
-### Configuration
120
+This scope has no labels.
121
129
-#### Options
122
+Metrics:
123
124
+| Metric | Dimensions | Unit |
125
+|:------|:----------|:----|
126
+| system.interrupts | a dimension per device | interrupts/s |
127
128
+### Per cpu core
129
133
-There are no configuration options.
130
131
132
+Labels:
133
137
-#### via File
134
+| Label | Description |
135
+|:-----------|:----------------|
136
+| cpu | TBD |
137
139
-There is no configuration file.
138
+Metrics:
139
141
-##### Examples
142
-There are no configuration examples.
140
+| Metric | Dimensions | Unit |
141
+|:------|:----------|:----|
142
+| cpu.interrupts | a dimension per device | interrupts/s |
143
144
src/collectors/proc.plugin/integrations/ip_virtual_server.md
+23
-23
@@ -44,57 +44,57 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per IP Virtual Server instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| ipvs.sockets | connections | connections/s |
66
-| ipvs.packets | received, sent | packets/s |
67
-| ipvs.net | received, sent | kilobits/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
71
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
73
-There are no alerts configured by default for this integration.
71
72
76
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
79
-### Prerequisites
77
81
-No action required.
78
+## Metrics
79
83
-### Configuration
80
+Metrics grouped by *scope*.
81
85
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
89
-There are no configuration options.
86
+### Per IP Virtual Server instance
87
88
89
93
-#### via File
90
+This scope has no labels.
91
95
-There is no configuration file.
92
+Metrics:
93
97
-##### Examples
98
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| ipvs.sockets | connections | connections/s |
97
+| ipvs.packets | received, sent | packets/s |
98
+| ipvs.net | received, sent | kilobits/s |
99
100
src/collectors/proc.plugin/integrations/ipv6_socket_statistics.md
+25
-25
@@ -44,59 +44,59 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per IPv6 Socket Statistics instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| ipv6.sockstat6_tcp_sockets | inuse | sockets |
66
-| ipv6.sockstat6_udp_sockets | inuse | sockets |
67
-| ipv6.sockstat6_udplite_sockets | inuse | sockets |
68
-| ipv6.sockstat6_raw_sockets | inuse | sockets |
69
-| ipv6.sockstat6_frag_sockets | inuse | fragments |
63
64
+#### via File
65
66
+There is no configuration file.
67
73
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
75
-There are no alerts configured by default for this integration.
71
72
78
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
81
-### Prerequisites
77
83
-No action required.
78
+## Metrics
79
85
-### Configuration
80
+Metrics grouped by *scope*.
81
87
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
91
-There are no configuration options.
86
+### Per IPv6 Socket Statistics instance
87
88
89
95
-#### via File
90
+This scope has no labels.
91
97
-There is no configuration file.
92
+Metrics:
93
99
-##### Examples
100
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| ipv6.sockstat6_tcp_sockets | inuse | sockets |
97
+| ipv6.sockstat6_udp_sockets | inuse | sockets |
98
+| ipv6.sockstat6_udplite_sockets | inuse | sockets |
99
+| ipv6.sockstat6_raw_sockets | inuse | sockets |
100
+| ipv6.sockstat6_frag_sockets | inuse | fragments |
101
102
src/collectors/proc.plugin/integrations/kernel_same-page_merging.md
+23
-23
@@ -50,57 +50,57 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
53
+## Setup
54
55
-Metrics grouped by *scope*.
55
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
+### Prerequisites
57
58
+No action required.
59
60
+### Configuration
61
61
-### Per Kernel Same-Page Merging instance
62
+#### Options
63
64
65
65
-This scope has no labels.
66
+There are no configuration options.
67
67
-Metrics:
68
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| mem.ksm | shared, unshared, sharing, volatile | MiB |
72
-| mem.ksm_savings | savings, offered | MiB |
73
-| mem.ksm_ratios | savings | percentage |
69
70
+#### via File
71
72
+There is no configuration file.
73
77
-## Alerts
74
+##### Examples
75
+There are no configuration examples.
76
79
-There are no alerts configured by default for this integration.
77
78
82
-## Setup
79
+## Alerts
80
81
+There are no alerts configured by default for this integration.
82
85
-### Prerequisites
83
87
-No action required.
84
+## Metrics
85
89
-### Configuration
86
+Metrics grouped by *scope*.
87
91
-#### Options
88
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
89
90
91
95
-There are no configuration options.
92
+### Per Kernel Same-Page Merging instance
93
94
95
99
-#### via File
96
+This scope has no labels.
97
101
-There is no configuration file.
98
+Metrics:
99
103
-##### Examples
104
-There are no configuration examples.
100
+| Metric | Dimensions | Unit |
101
+|:------|:----------|:----|
102
+| mem.ksm | shared, unshared, sharing, volatile | MiB |
103
+| mem.ksm_savings | savings, offered | MiB |
104
+| mem.ksm_ratios | savings | percentage |
105
106
src/collectors/proc.plugin/integrations/md_raid.md
+38
-38
@@ -44,47 +44,29 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
47
+## Setup
48
49
55
-### Per MD RAID instance
56
-
50
+### Prerequisites
51
52
+No action required.
53
59
-This scope has no labels.
54
+### Configuration
55
61
-Metrics:
56
+#### Options
57
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| md.health | a dimension per md array | failed disks |
58
67
-### Per md array
59
60
+There are no configuration options.
61
62
71
-Labels:
63
73
-| Label | Description |
74
-|:-----------|:----------------|
75
-| device | TBD |
76
-| raid_level | TBD |
64
+#### via File
65
78
-Metrics:
66
+There is no configuration file.
67
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| md.disks | inuse, down | disks |
83
-| md.mismatch_cnt | count | unsynchronized blocks |
84
-| md.status | check, resync, recovery, reshape | percent |
85
-| md.expected_time_until_operation_finish | finish_in | seconds |
86
-| md.operation_speed | speed | KiB/s |
87
-| md.nonredundant | available | boolean |
68
+##### Examples
69
+There are no configuration examples.
70
71
72
@@ -101,28 +83,46 @@ The following alerts are available:
83
| [ mdstat_nonredundant_last_collected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mdstat.conf) | md.nonredundant | number of seconds since the last successful data collection |
84
85
104
-## Setup
86
+## Metrics
87
88
+Metrics grouped by *scope*.
89
107
-### Prerequisites
90
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
91
109
-No action required.
92
111
-### Configuration
93
113
-#### Options
94
+### Per MD RAID instance
95
96
97
117
-There are no configuration options.
98
+This scope has no labels.
99
100
+Metrics:
101
102
+| Metric | Dimensions | Unit |
103
+|:------|:----------|:----|
104
+| md.health | a dimension per md array | failed disks |
105
121
-#### via File
106
+### Per md array
107
123
-There is no configuration file.
108
125
-##### Examples
126
-There are no configuration examples.
109
+
110
+Labels:
111
+
112
+| Label | Description |
113
+|:-----------|:----------------|
114
+| device | TBD |
115
+| raid_level | TBD |
116
+
117
+Metrics:
118
+
119
+| Metric | Dimensions | Unit |
120
+|:------|:----------|:----|
121
+| md.disks | inuse, down | disks |
122
+| md.mismatch_cnt | count | unsynchronized blocks |
123
+| md.status | check, resync, recovery, reshape | percent |
124
+| md.expected_time_until_operation_finish | finish_in | seconds |
125
+| md.operation_speed | speed | KiB/s |
126
+| md.nonredundant | available | boolean |
127
128
src/collectors/proc.plugin/integrations/memory_modules_dimms.md
+39
-39
@@ -57,6 +57,45 @@ The default configuration for this integration does not impose any limits on dat
57
58
The default configuration for this integration is not expected to impose a significant performance impact on the system.
59
60
+## Setup
61
+
62
+
63
+### Prerequisites
64
+
65
+No action required.
66
+
67
+### Configuration
68
+
69
+#### Options
70
+
71
+
72
+
73
+There are no configuration options.
74
+
75
+
76
+
77
+#### via File
78
+
79
+There is no configuration file.
80
+
81
+##### Examples
82
+There are no configuration examples.
83
+
84
+
85
+
86
+## Alerts
87
+
88
+
89
+The following alerts are available:
90
+
91
+| Alert name | On metric | Description |
92
+|:------------|:----------|:------------|
93
+| [ ecc_memory_mc_noinfo_correctable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_errors | memory controller ${label:controller} ECC correctable errors (unknown DIMM slot) |
94
+| [ ecc_memory_mc_noinfo_uncorrectable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_errors | memory controller ${label:controller} ECC uncorrectable errors (unknown DIMM slot) |
95
+| [ ecc_memory_dimm_correctable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_dimm_errors | DIMM ${label:dimm} controller ${label:controller} (location ${label:dimm_location}) ECC correctable errors |
96
+| [ ecc_memory_dimm_uncorrectable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_dimm_errors | DIMM ${label:dimm} controller ${label:controller} (location ${label:dimm_location}) ECC uncorrectable errors |
97
+
98
+
99
## Metrics
100
101
Metrics grouped by *scope*.
@@ -108,42 +147,3 @@ Metrics:
147
| mem.edac_mc_errors | correctable, uncorrectable | errors |
148
149
111
-
112
-## Alerts
113
-
114
-
115
-The following alerts are available:
116
-
117
-| Alert name | On metric | Description |
118
-|:------------|:----------|:------------|
119
-| [ ecc_memory_mc_noinfo_correctable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_errors | memory controller ${label:controller} ECC correctable errors (unknown DIMM slot) |
120
-| [ ecc_memory_mc_noinfo_uncorrectable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_errors | memory controller ${label:controller} ECC uncorrectable errors (unknown DIMM slot) |
121
-| [ ecc_memory_dimm_correctable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_dimm_errors | DIMM ${label:dimm} controller ${label:controller} (location ${label:dimm_location}) ECC correctable errors |
122
-| [ ecc_memory_dimm_uncorrectable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.edac_mc_dimm_errors | DIMM ${label:dimm} controller ${label:controller} (location ${label:dimm_location}) ECC uncorrectable errors |
123
-
124
-
125
-## Setup
126
-
127
-
128
-### Prerequisites
129
-
130
-No action required.
131
-
132
-### Configuration
133
-
134
-#### Options
135
-
136
-
137
-
138
-There are no configuration options.
139
-
140
-
141
-
142
-#### via File
143
-
144
-There is no configuration file.
145
-
146
-##### Examples
147
-There are no configuration examples.
148
-
149
-
src/collectors/proc.plugin/integrations/memory_statistics.md
+36
-36
@@ -67,39 +67,29 @@ The default configuration for this integration does not impose any limits on dat
67
68
The default configuration for this integration is not expected to impose a significant performance impact on the system.
69
70
-## Metrics
70
+## Setup
71
72
-Metrics grouped by *scope*.
72
74
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
73
+### Prerequisites
74
75
+No action required.
76
77
+### Configuration
78
78
-### Per Memory Statistics instance
79
+#### Options
80
81
82
82
-This scope has no labels.
83
+There are no configuration options.
84
84
-Metrics:
85
86
-| Metric | Dimensions | Unit |
87
-|:------|:----------|:----|
88
-| mem.swapio | in, out | KiB/s |
89
-| system.pgpgio | in, out | KiB/s |
90
-| system.pgfaults | minor, major | faults/s |
91
-| mem.balloon | inflate, deflate, migrate | KiB/s |
92
-| mem.zswapio | in, out | KiB/s |
93
-| mem.ksm_cow | swapin, write | KiB/s |
94
-| mem.thp_faults | alloc, fallback, fallback_charge | events/s |
95
-| mem.thp_file | alloc, fallback, mapped, fallback_charge | events/s |
96
-| mem.thp_zero | alloc, failed | events/s |
97
-| mem.thp_collapse | alloc, failed | events/s |
98
-| mem.thp_split | split, failed, split_pmd, split_deferred | events/s |
99
-| mem.thp_swapout | swapout, fallback | events/s |
100
-| mem.thp_compact | success, fail, stall | events/s |
101
-| mem.oom_kill | kills | kills/s |
102
-| mem.numa | local, foreign, interleave, other, pte_updates, huge_pte_updates, hint_faults, hint_faults_local, pages_migrated | events/s |
86
+
87
+#### via File
88
+
89
+There is no configuration file.
90
+
91
+##### Examples
92
+There are no configuration examples.
93
94
95
@@ -114,28 +104,38 @@ The following alerts are available:
104
| [ oom_kill ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ram.conf) | mem.oom_kill | number of out of memory kills in the last 30 minutes |
105
106
117
-## Setup
118
-
119
-
120
-### Prerequisites
121
-
122
-No action required.
107
+## Metrics
108
124
-### Configuration
109
+Metrics grouped by *scope*.
110
126
-#### Options
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
113
114
130
-There are no configuration options.
115
+### Per Memory Statistics instance
116
117
118
134
-#### via File
119
+This scope has no labels.
120
136
-There is no configuration file.
121
+Metrics:
122
138
-##### Examples
139
-There are no configuration examples.
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| mem.swapio | in, out | KiB/s |
126
+| system.pgpgio | in, out | KiB/s |
127
+| system.pgfaults | minor, major | faults/s |
128
+| mem.balloon | inflate, deflate, migrate | KiB/s |
129
+| mem.zswapio | in, out | KiB/s |
130
+| mem.ksm_cow | swapin, write | KiB/s |
131
+| mem.thp_faults | alloc, fallback, fallback_charge | events/s |
132
+| mem.thp_file | alloc, fallback, mapped, fallback_charge | events/s |
133
+| mem.thp_zero | alloc, failed | events/s |
134
+| mem.thp_collapse | alloc, failed | events/s |
135
+| mem.thp_split | split, failed, split_pmd, split_deferred | events/s |
136
+| mem.thp_swapout | swapout, fallback | events/s |
137
+| mem.thp_compact | success, fail, stall | events/s |
138
+| mem.oom_kill | kills | kills/s |
139
+| mem.numa | local, foreign, interleave, other, pte_updates, huge_pte_updates, hint_faults, hint_faults_local, pages_migrated | events/s |
140
141
src/collectors/proc.plugin/integrations/memory_usage.md
+38
-38
@@ -60,41 +60,29 @@ The default configuration for this integration does not impose any limits on dat
60
61
The default configuration for this integration is not expected to impose a significant performance impact on the system.
62
63
-## Metrics
63
+## Setup
64
65
-Metrics grouped by *scope*.
65
67
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
66
+### Prerequisites
67
68
+No action required.
69
70
+### Configuration
71
71
-### Per Memory Usage instance
72
+#### Options
73
74
75
75
-This scope has no labels.
76
+There are no configuration options.
77
77
-Metrics:
78
79
-| Metric | Dimensions | Unit |
80
-|:------|:----------|:----|
81
-| system.ram | free, used, cached, buffers | MiB |
82
-| mem.available | avail | MiB |
83
-| mem.swap | free, used | MiB |
84
-| mem.swap_cached | cached | MiB |
85
-| mem.zswap | in-ram, on-disk | MiB |
86
-| mem.hwcorrupt | HardwareCorrupted | MiB |
87
-| mem.commited | Commited_AS | MiB |
88
-| mem.writeback | Dirty, Writeback, FuseWriteback, NfsWriteback, Bounce | MiB |
89
-| mem.kernel | Slab, KernelStack, PageTables, VmallocUsed, Percpu | MiB |
90
-| mem.slab | reclaimable, unreclaimable | MiB |
91
-| mem.hugepages | free, used, surplus, reserved | MiB |
92
-| mem.thp | anonymous, shmem | MiB |
93
-| mem.thp_details | ShmemPmdMapped, FileHugePages, FilePmdMapped | MiB |
94
-| mem.reclaiming | Active, Inactive, Active(anon), Inactive(anon), Active(file), Inactive(file), Unevictable, Mlocked | MiB |
95
-| mem.high_low | high_used, low_used, high_free, low_free | MiB |
96
-| mem.cma | used, free | MiB |
97
-| mem.directmaps | 4k, 2m, 4m, 1g | MiB |
79
+
80
+#### via File
81
+
82
+There is no configuration file.
83
+
84
+##### Examples
85
+There are no configuration examples.
86
87
88
@@ -111,28 +99,40 @@ The following alerts are available:
99
| [ 1hour_memory_hw_corrupted ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memory.conf) | mem.hwcorrupt | amount of memory corrupted due to a hardware failure |
100
101
114
-## Setup
115
-
116
-
117
-### Prerequisites
118
-
119
-No action required.
102
+## Metrics
103
121
-### Configuration
104
+Metrics grouped by *scope*.
105
123
-#### Options
106
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
107
108
109
127
-There are no configuration options.
110
+### Per Memory Usage instance
111
112
113
131
-#### via File
114
+This scope has no labels.
115
133
-There is no configuration file.
116
+Metrics:
117
135
-##### Examples
136
-There are no configuration examples.
118
+| Metric | Dimensions | Unit |
119
+|:------|:----------|:----|
120
+| system.ram | free, used, cached, buffers | MiB |
121
+| mem.available | avail | MiB |
122
+| mem.swap | free, used | MiB |
123
+| mem.swap_cached | cached | MiB |
124
+| mem.zswap | in-ram, on-disk | MiB |
125
+| mem.hwcorrupt | HardwareCorrupted | MiB |
126
+| mem.commited | Commited_AS | MiB |
127
+| mem.writeback | Dirty, Writeback, FuseWriteback, NfsWriteback, Bounce | MiB |
128
+| mem.kernel | Slab, KernelStack, PageTables, VmallocUsed, Percpu | MiB |
129
+| mem.slab | reclaimable, unreclaimable | MiB |
130
+| mem.hugepages | free, used, surplus, reserved | MiB |
131
+| mem.thp | anonymous, shmem | MiB |
132
+| mem.thp_details | ShmemPmdMapped, FileHugePages, FilePmdMapped | MiB |
133
+| mem.reclaiming | Active, Inactive, Active(anon), Inactive(anon), Active(file), Inactive(file), Unevictable, Mlocked | MiB |
134
+| mem.high_low | high_used, low_used, high_free, low_free | MiB |
135
+| mem.cma | used, free | MiB |
136
+| mem.directmaps | 4k, 2m, 4m, 1g | MiB |
137
138
src/collectors/proc.plugin/integrations/network_interfaces.md
+44
-44
@@ -44,53 +44,29 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
47
+## Setup
48
55
-### Per Network interfaces instance
49
50
+### Prerequisites
51
52
+No action required.
53
59
-This scope has no labels.
54
+### Configuration
55
61
-Metrics:
56
+#### Options
57
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| system.net | received, sent | kilobits/s |
58
67
-### Per network device
59
60
+There are no configuration options.
61
62
71
-Labels:
63
73
-| Label | Description |
74
-|:-----------|:----------------|
75
-| interface_type | TBD |
76
-| device | TBD |
64
+#### via File
65
78
-Metrics:
66
+There is no configuration file.
67
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| net.net | received, sent | kilobits/s |
83
-| net.speed | speed | kilobits/s |
84
-| net.duplex | full, half, unknown | state |
85
-| net.operstate | up, down, notpresent, lowerlayerdown, testing, dormant, unknown | state |
86
-| net.carrier | up, down | state |
87
-| net.mtu | mtu | octets |
88
-| net.packets | received, sent, multicast | packets/s |
89
-| net.errors | inbound, outbound | errors/s |
90
-| net.drops | inbound, outbound | drops/s |
91
-| net.fifo | receive, transmit | errors |
92
-| net.compressed | received, sent | packets/s |
93
-| net.events | frames, collisions, carrier | events/s |
68
+##### Examples
69
+There are no configuration examples.
70
71
72
@@ -113,28 +89,52 @@ The following alerts are available:
89
| [ 10min_fifo_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.fifo | number of FIFO errors for the network interface ${label:device} in the last 10 minutes |
90
91
116
-## Setup
92
+## Metrics
93
94
+Metrics grouped by *scope*.
95
119
-### Prerequisites
96
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
97
121
-No action required.
98
123
-### Configuration
99
125
-#### Options
100
+### Per Network interfaces instance
101
102
103
129
-There are no configuration options.
104
+This scope has no labels.
105
106
+Metrics:
107
108
+| Metric | Dimensions | Unit |
109
+|:------|:----------|:----|
110
+| system.net | received, sent | kilobits/s |
111
133
-#### via File
112
+### Per network device
113
135
-There is no configuration file.
114
137
-##### Examples
138
-There are no configuration examples.
115
+
116
+Labels:
117
+
118
+| Label | Description |
119
+|:-----------|:----------------|
120
+| interface_type | TBD |
121
+| device | TBD |
122
+
123
+Metrics:
124
+
125
+| Metric | Dimensions | Unit |
126
+|:------|:----------|:----|
127
+| net.net | received, sent | kilobits/s |
128
+| net.speed | speed | kilobits/s |
129
+| net.duplex | full, half, unknown | state |
130
+| net.operstate | up, down, notpresent, lowerlayerdown, testing, dormant, unknown | state |
131
+| net.carrier | up, down | state |
132
+| net.mtu | mtu | octets |
133
+| net.packets | received, sent, multicast | packets/s |
134
+| net.errors | inbound, outbound | errors/s |
135
+| net.drops | inbound, outbound | drops/s |
136
+| net.fifo | receive, transmit | errors |
137
+| net.compressed | received, sent | packets/s |
138
+| net.events | frames, collisions, carrier | events/s |
139
140
src/collectors/proc.plugin/integrations/network_statistics.md
+46
-46
@@ -44,6 +44,52 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+
76
+The following alerts are available:
77
+
78
+| Alert name | On metric | Description |
79
+|:------------|:----------|:------------|
80
+| [ 1m_tcp_syn_queue_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_syn_queue | average number of SYN requests was dropped due to the full TCP SYN queue over the last minute (SYN cookies were not enabled) |
81
+| [ 1m_tcp_syn_queue_cookies ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_syn_queue | average number of sent SYN cookies due to the full TCP SYN queue over the last minute |
82
+| [ 1m_tcp_accept_queue_overflows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_accept_queue | average number of overflows in the TCP accept queue over the last minute |
83
+| [ 1m_tcp_accept_queue_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_accept_queue | average number of dropped packets in the TCP accept queue over the last minute |
84
+| [ tcp_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_conn.conf) | ip.tcpsock | TCP connections utilization |
85
+| [ 1m_ip_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of sent TCP RESETS over the last minute |
86
+| [ 10s_ip_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of sent TCP RESETS over the last 10 seconds. This can indicate a port scan, or that a service running on this host has crashed. Netdata will not send a clear notification for this alarm. |
87
+| [ 1m_ip_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of received TCP RESETS over the last minute |
88
+| [ 10s_ip_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of received TCP RESETS over the last 10 seconds. This can be an indication that a service this host needs has crashed. Netdata will not send a clear notification for this alarm. |
89
+| [ 1m_ipv4_udp_receive_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP receive buffer errors over the last minute |
90
+| [ 1m_ipv4_udp_send_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP send buffer errors over the last minute |
91
+
92
+
93
## Metrics
94
95
Metrics grouped by *scope*.
@@ -115,49 +161,3 @@ Metrics:
161
| ipv6.fragsout | ok, failed, all | packets/s |
162
163
118
-
119
-## Alerts
120
-
121
-
122
-The following alerts are available:
123
-
124
-| Alert name | On metric | Description |
125
-|:------------|:----------|:------------|
126
-| [ 1m_tcp_syn_queue_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_syn_queue | average number of SYN requests was dropped due to the full TCP SYN queue over the last minute (SYN cookies were not enabled) |
127
-| [ 1m_tcp_syn_queue_cookies ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_syn_queue | average number of sent SYN cookies due to the full TCP SYN queue over the last minute |
128
-| [ 1m_tcp_accept_queue_overflows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_accept_queue | average number of overflows in the TCP accept queue over the last minute |
129
-| [ 1m_tcp_accept_queue_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_listen.conf) | ip.tcp_accept_queue | average number of dropped packets in the TCP accept queue over the last minute |
130
-| [ tcp_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_conn.conf) | ip.tcpsock | TCP connections utilization |
131
-| [ 1m_ip_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of sent TCP RESETS over the last minute |
132
-| [ 10s_ip_tcp_resets_sent ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of sent TCP RESETS over the last 10 seconds. This can indicate a port scan, or that a service running on this host has crashed. Netdata will not send a clear notification for this alarm. |
133
-| [ 1m_ip_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of received TCP RESETS over the last minute |
134
-| [ 10s_ip_tcp_resets_received ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_resets.conf) | ip.tcphandshake | average number of received TCP RESETS over the last 10 seconds. This can be an indication that a service this host needs has crashed. Netdata will not send a clear notification for this alarm. |
135
-| [ 1m_ipv4_udp_receive_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP receive buffer errors over the last minute |
136
-| [ 1m_ipv4_udp_send_buffer_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/udp_errors.conf) | ipv4.udperrors | average number of UDP send buffer errors over the last minute |
137
-
138
-
139
-## Setup
140
-
141
-
142
-### Prerequisites
143
-
144
-No action required.
145
-
146
-### Configuration
147
-
148
-#### Options
149
-
150
-
151
-
152
-There are no configuration options.
153
-
154
-
155
-
156
-#### via File
157
-
158
-There is no configuration file.
159
-
160
-##### Examples
161
-There are no configuration examples.
162
-
163
-
src/collectors/proc.plugin/integrations/nfs_client.md
+25
-25
@@ -44,59 +44,59 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per NFS Client instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| nfs.net | udp, tcp | operations/s |
66
-| nfs.rpc | calls, retransmits, auth_refresh | calls/s |
67
-| nfs.proc2 | a dimension per proc2 call | calls/s |
68
-| nfs.proc3 | a dimension per proc3 call | calls/s |
69
-| nfs.proc4 | a dimension per proc4 call | calls/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
73
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
75
-There are no alerts configured by default for this integration.
71
72
78
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
81
-### Prerequisites
77
83
-No action required.
78
+## Metrics
79
85
-### Configuration
80
+Metrics grouped by *scope*.
81
87
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
91
-There are no configuration options.
86
+### Per NFS Client instance
87
88
89
95
-#### via File
90
+This scope has no labels.
91
97
-There is no configuration file.
92
+Metrics:
93
99
-##### Examples
100
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| nfs.net | udp, tcp | operations/s |
97
+| nfs.rpc | calls, retransmits, auth_refresh | calls/s |
98
+| nfs.proc2 | a dimension per proc2 call | calls/s |
99
+| nfs.proc3 | a dimension per proc3 call | calls/s |
100
+| nfs.proc4 | a dimension per proc4 call | calls/s |
101
102
src/collectors/proc.plugin/integrations/nfs_server.md
+30
-30
@@ -44,64 +44,64 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per NFS Server instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| nfsd.readcache | hits, misses, nocache | reads/s |
66
-| nfsd.filehandles | stale | handles/s |
67
-| nfsd.io | read, write | kilobytes/s |
68
-| nfsd.threads | threads | threads |
69
-| nfsd.net | udp, tcp | packets/s |
70
-| nfsd.rpc | calls, bad_format, bad_auth | calls/s |
71
-| nfsd.proc2 | a dimension per proc2 call | calls/s |
72
-| nfsd.proc3 | a dimension per proc3 call | calls/s |
73
-| nfsd.proc4 | a dimension per proc4 call | calls/s |
74
-| nfsd.proc4ops | a dimension per proc4 operation | operations/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
78
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
80
-There are no alerts configured by default for this integration.
71
72
83
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
86
-### Prerequisites
77
88
-No action required.
78
+## Metrics
79
90
-### Configuration
80
+Metrics grouped by *scope*.
81
92
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
96
-There are no configuration options.
86
+### Per NFS Server instance
87
88
89
100
-#### via File
90
+This scope has no labels.
91
102
-There is no configuration file.
92
+Metrics:
93
104
-##### Examples
105
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| nfsd.readcache | hits, misses, nocache | reads/s |
97
+| nfsd.filehandles | stale | handles/s |
98
+| nfsd.io | read, write | kilobytes/s |
99
+| nfsd.threads | threads | threads |
100
+| nfsd.net | udp, tcp | packets/s |
101
+| nfsd.rpc | calls, bad_format, bad_auth | calls/s |
102
+| nfsd.proc2 | a dimension per proc2 call | calls/s |
103
+| nfsd.proc3 | a dimension per proc3 call | calls/s |
104
+| nfsd.proc4 | a dimension per proc4 call | calls/s |
105
+| nfsd.proc4ops | a dimension per proc4 operation | operations/s |
106
107
src/collectors/proc.plugin/integrations/non-uniform_memory_access.md
+24
-24
@@ -56,59 +56,59 @@ The default configuration for this integration does not impose any limits on dat
56
57
The default configuration for this integration is not expected to impose a significant performance impact on the system.
58
59
-## Metrics
59
+## Setup
60
61
-Metrics grouped by *scope*.
61
63
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
+### Prerequisites
63
64
+No action required.
65
66
+### Configuration
67
67
-### Per numa node
68
+#### Options
69
70
71
71
-Labels:
72
+There are no configuration options.
73
73
-| Label | Description |
74
-|:-----------|:----------------|
75
-| numa_node | TBD |
74
77
-Metrics:
75
79
-| Metric | Dimensions | Unit |
80
-|:------|:----------|:----|
81
-| mem.numa_nodes | hit, miss, local, foreign, interleave, other | events/s |
76
+#### via File
77
78
+There is no configuration file.
79
80
+##### Examples
81
+There are no configuration examples.
82
85
-## Alerts
83
87
-There are no alerts configured by default for this integration.
84
85
+## Alerts
86
90
-## Setup
87
+There are no alerts configured by default for this integration.
88
89
93
-### Prerequisites
90
+## Metrics
91
95
-No action required.
92
+Metrics grouped by *scope*.
93
97
-### Configuration
94
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
95
99
-#### Options
96
97
98
+### Per numa node
99
103
-There are no configuration options.
100
101
102
+Labels:
103
107
-#### via File
104
+| Label | Description |
105
+|:-----------|:----------------|
106
+| numa_node | TBD |
107
109
-There is no configuration file.
108
+Metrics:
109
111
-##### Examples
112
-There are no configuration examples.
110
+| Metric | Dimensions | Unit |
111
+|:------|:----------|:----|
112
+| mem.numa_nodes | hit, miss, local, foreign, interleave, other | events/s |
113
114
src/collectors/proc.plugin/integrations/page_types.md
+31
-31
@@ -44,6 +44,37 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+There are no alerts configured by default for this integration.
76
+
77
+
78
## Metrics
79
80
Metrics grouped by *scope*.
@@ -83,34 +114,3 @@ Metrics:
114
| mem.pagetype | a dimension per pagesize | B |
115
116
86
-
87
-## Alerts
88
-
89
-There are no alerts configured by default for this integration.
90
-
91
-
92
-## Setup
93
-
94
-
95
-### Prerequisites
96
-
97
-No action required.
98
-
99
-### Configuration
100
-
101
-#### Options
102
-
103
-
104
-
105
-There are no configuration options.
106
-
107
-
108
-
109
-#### via File
110
-
111
-There is no configuration file.
112
-
113
-##### Examples
114
-There are no configuration examples.
115
-
116
-
src/collectors/proc.plugin/integrations/power_supply.md
+28
-28
@@ -44,33 +44,29 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per power device
56
+#### Options
57
58
59
59
-Labels:
60
+There are no configuration options.
61
61
-| Label | Description |
62
-|:-----------|:----------------|
63
-| device | TBD |
62
65
-Metrics:
63
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| powersupply.capacity | capacity | percentage |
70
-| powersupply.power | power | W |
71
-| powersupply.charge | empty_design, empty, now, full, full_design | Ah |
72
-| powersupply.energy | empty_design, empty, now, full, full_design | Wh |
73
-| powersupply.voltage | min_design, min, now, max, max_design | V |
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
71
72
@@ -84,28 +80,32 @@ The following alerts are available:
80
| [ power_supply_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/power_supply_capacity.conf) | powersupply.capacity | percentage of remaining power supply capacity |
81
82
87
-## Setup
88
-
89
-
90
-### Prerequisites
83
+## Metrics
84
92
-No action required.
85
+Metrics grouped by *scope*.
86
94
-### Configuration
87
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
88
96
-#### Options
89
90
91
+### Per power device
92
100
-There are no configuration options.
93
94
95
+Labels:
96
104
-#### via File
97
+| Label | Description |
98
+|:-----------|:----------------|
99
+| device | TBD |
100
106
-There is no configuration file.
101
+Metrics:
102
108
-##### Examples
109
-There are no configuration examples.
103
+| Metric | Dimensions | Unit |
104
+|:------|:----------|:----|
105
+| powersupply.capacity | capacity | percentage |
106
+| powersupply.power | power | W |
107
+| powersupply.charge | empty_design, empty, now, full, full_design | Ah |
108
+| powersupply.energy | empty_design, empty, now, full, full_design | Wh |
109
+| powersupply.voltage | min_design, min, now, max, max_design | V |
110
111
src/collectors/proc.plugin/integrations/pressure_stall_information.md
+31
-31
@@ -67,6 +67,37 @@ The default configuration for this integration does not impose any limits on dat
67
68
The default configuration for this integration is not expected to impose a significant performance impact on the system.
69
70
+## Setup
71
+
72
+
73
+### Prerequisites
74
+
75
+No action required.
76
+
77
+### Configuration
78
+
79
+#### Options
80
+
81
+
82
+
83
+There are no configuration options.
84
+
85
+
86
+
87
+#### via File
88
+
89
+There is no configuration file.
90
+
91
+##### Examples
92
+There are no configuration examples.
93
+
94
+
95
+
96
+## Alerts
97
+
98
+There are no alerts configured by default for this integration.
99
+
100
+
101
## Metrics
102
103
Metrics grouped by *scope*.
@@ -99,34 +130,3 @@ Metrics:
130
| system.io_full_pressure_stall_time | time | ms |
131
132
102
-
103
-## Alerts
104
-
105
-There are no alerts configured by default for this integration.
106
-
107
-
108
-## Setup
109
-
110
-
111
-### Prerequisites
112
-
113
-No action required.
114
-
115
-### Configuration
116
-
117
-#### Options
118
-
119
-
120
-
121
-There are no configuration options.
122
-
123
-
124
-
125
-#### via File
126
-
127
-There is no configuration file.
128
-
129
-##### Examples
130
-There are no configuration examples.
131
-
132
-
src/collectors/proc.plugin/integrations/sctp_statistics.md
+25
-25
@@ -44,59 +44,59 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per SCTP Statistics instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| sctp.established | established | associations |
66
-| sctp.transitions | active, passive, aborted, shutdown | transitions/s |
67
-| sctp.packets | received, sent | packets/s |
68
-| sctp.packet_errors | invalid, checksum | packets/s |
69
-| sctp.fragmentation | reassembled, fragmented | packets/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
73
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
75
-There are no alerts configured by default for this integration.
71
72
78
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
81
-### Prerequisites
77
83
-No action required.
78
+## Metrics
79
85
-### Configuration
80
+Metrics grouped by *scope*.
81
87
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
91
-There are no configuration options.
86
+### Per SCTP Statistics instance
87
88
89
95
-#### via File
90
+This scope has no labels.
91
97
-There is no configuration file.
92
+Metrics:
93
99
-##### Examples
100
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| sctp.established | established | associations |
97
+| sctp.transitions | active, passive, aborted, shutdown | transitions/s |
98
+| sctp.packets | received, sent | packets/s |
99
+| sctp.packet_errors | invalid, checksum | packets/s |
100
+| sctp.fragmentation | reassembled, fragmented | packets/s |
101
102
src/collectors/proc.plugin/integrations/socket_statistics.md
+30
-30
@@ -44,33 +44,29 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per Socket statistics instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| ip.sockstat_sockets | used | sockets |
66
-| ipv4.sockstat_tcp_sockets | alloc, orphan, inuse, timewait | sockets |
67
-| ipv4.sockstat_tcp_mem | mem | KiB |
68
-| ipv4.sockstat_udp_sockets | inuse | sockets |
69
-| ipv4.sockstat_udp_mem | mem | sockets |
70
-| ipv4.sockstat_udplite_sockets | inuse | sockets |
71
-| ipv4.sockstat_raw_sockets | inuse | sockets |
72
-| ipv4.sockstat_frag_sockets | inuse | fragments |
73
-| ipv4.sockstat_frag_mem | mem | KiB |
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
71
72
@@ -85,28 +81,32 @@ The following alerts are available:
81
| [ tcp_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/tcp_mem.conf) | ipv4.sockstat_tcp_mem | TCP memory utilization |
82
83
88
-## Setup
89
-
90
-
91
-### Prerequisites
92
-
93
-No action required.
84
+## Metrics
85
95
-### Configuration
86
+Metrics grouped by *scope*.
87
97
-#### Options
88
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
89
90
91
101
-There are no configuration options.
92
+### Per Socket statistics instance
93
94
95
105
-#### via File
96
+This scope has no labels.
97
107
-There is no configuration file.
98
+Metrics:
99
109
-##### Examples
110
-There are no configuration examples.
100
+| Metric | Dimensions | Unit |
101
+|:------|:----------|:----|
102
+| ip.sockstat_sockets | used | sockets |
103
+| ipv4.sockstat_tcp_sockets | alloc, orphan, inuse, timewait | sockets |
104
+| ipv4.sockstat_tcp_mem | mem | KiB |
105
+| ipv4.sockstat_udp_sockets | inuse | sockets |
106
+| ipv4.sockstat_udp_mem | mem | sockets |
107
+| ipv4.sockstat_udplite_sockets | inuse | sockets |
108
+| ipv4.sockstat_raw_sockets | inuse | sockets |
109
+| ipv4.sockstat_frag_sockets | inuse | fragments |
110
+| ipv4.sockstat_frag_mem | mem | KiB |
111
112
src/collectors/proc.plugin/integrations/softirq_statistics.md
+30
-30
@@ -66,71 +66,71 @@ The default configuration for this integration does not impose any limits on dat
66
67
The default configuration for this integration is not expected to impose a significant performance impact on the system.
68
69
-## Metrics
69
+## Setup
70
71
-Metrics grouped by *scope*.
71
73
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
72
+### Prerequisites
73
74
+No action required.
75
76
+### Configuration
77
77
-### Per SoftIRQ statistics instance
78
+#### Options
79
80
81
81
-This scope has no labels.
82
+There are no configuration options.
83
83
-Metrics:
84
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| system.softirqs | a dimension per softirq | softirqs/s |
85
89
-### Per cpu core
86
+#### via File
87
88
+There is no configuration file.
89
90
+##### Examples
91
+There are no configuration examples.
92
93
-Labels:
93
95
-| Label | Description |
96
-|:-----------|:----------------|
97
-| cpu | TBD |
94
99
-Metrics:
95
+## Alerts
96
101
-| Metric | Dimensions | Unit |
102
-|:------|:----------|:----|
103
-| cpu.softirqs | a dimension per softirq | softirqs/s |
97
+There are no alerts configured by default for this integration.
98
99
100
+## Metrics
101
107
-## Alerts
102
+Metrics grouped by *scope*.
103
109
-There are no alerts configured by default for this integration.
104
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
105
106
112
-## Setup
107
108
+### Per SoftIRQ statistics instance
109
115
-### Prerequisites
110
117
-No action required.
111
119
-### Configuration
112
+This scope has no labels.
113
121
-#### Options
114
+Metrics:
115
116
+| Metric | Dimensions | Unit |
117
+|:------|:----------|:----|
118
+| system.softirqs | a dimension per softirq | softirqs/s |
119
120
+### Per cpu core
121
125
-There are no configuration options.
122
123
124
+Labels:
125
129
-#### via File
126
+| Label | Description |
127
+|:-----------|:----------------|
128
+| cpu | TBD |
129
131
-There is no configuration file.
130
+Metrics:
131
133
-##### Examples
134
-There are no configuration examples.
132
+| Metric | Dimensions | Unit |
133
+|:------|:----------|:----|
134
+| cpu.softirqs | a dimension per softirq | softirqs/s |
135
136
src/collectors/proc.plugin/integrations/softnet_statistics.md
+28
-28
@@ -66,37 +66,29 @@ The default configuration for this integration does not impose any limits on dat
66
67
The default configuration for this integration is not expected to impose a significant performance impact on the system.
68
69
-## Metrics
70
-
71
-Metrics grouped by *scope*.
72
-
73
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
74
-
69
+## Setup
70
71
77
-### Per Softnet Statistics instance
72
+### Prerequisites
73
74
+No action required.
75
76
+### Configuration
77
81
-This scope has no labels.
78
+#### Options
79
83
-Metrics:
80
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| system.softnet_stat | processed, dropped, squeezed, received_rps, flow_limit_count | events/s |
81
89
-### Per cpu core
82
+There are no configuration options.
83
84
85
93
-This scope has no labels.
86
+#### via File
87
95
-Metrics:
88
+There is no configuration file.
89
97
-| Metric | Dimensions | Unit |
98
-|:------|:----------|:----|
99
-| cpu.softnet_stat | processed, dropped, squeezed, received_rps, flow_limit_count | events/s |
90
+##### Examples
91
+There are no configuration examples.
92
93
94
@@ -111,28 +103,36 @@ The following alerts are available:
103
| [ 1min_netdev_budget_ran_outs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/softnet.conf) | system.softnet_stat | average number of times ksoftirq ran out of sysctl net.core.netdev_budget or net.core.netdev_budget_usecs with work remaining over the last minute (this can be a cause for dropped packets) |
104
105
114
-## Setup
106
+## Metrics
107
108
+Metrics grouped by *scope*.
109
117
-### Prerequisites
110
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
111
119
-No action required.
112
121
-### Configuration
113
123
-#### Options
114
+### Per Softnet Statistics instance
115
116
117
127
-There are no configuration options.
118
+This scope has no labels.
119
+
120
+Metrics:
121
+
122
+| Metric | Dimensions | Unit |
123
+|:------|:----------|:----|
124
+| system.softnet_stat | processed, dropped, squeezed, received_rps, flow_limit_count | events/s |
125
126
+### Per cpu core
127
128
131
-#### via File
129
133
-There is no configuration file.
130
+This scope has no labels.
131
135
-##### Examples
136
-There are no configuration examples.
132
+Metrics:
133
+
134
+| Metric | Dimensions | Unit |
135
+|:------|:----------|:----|
136
+| cpu.softnet_stat | processed, dropped, squeezed, received_rps, flow_limit_count | events/s |
137
138
src/collectors/proc.plugin/integrations/synproxy.md
+23
-23
@@ -44,57 +44,57 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per Synproxy instance
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| netfilter.synproxy_syn_received | received | packets/s |
66
-| netfilter.synproxy_conn_reopened | reopened | connections/s |
67
-| netfilter.synproxy_cookies | valid, invalid, retransmits | cookies/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
71
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
73
-There are no alerts configured by default for this integration.
71
72
76
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
79
-### Prerequisites
77
81
-No action required.
78
+## Metrics
79
83
-### Configuration
80
+Metrics grouped by *scope*.
81
85
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
89
-There are no configuration options.
86
+### Per Synproxy instance
87
88
89
93
-#### via File
90
+This scope has no labels.
91
95
-There is no configuration file.
92
+Metrics:
93
97
-##### Examples
98
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| netfilter.synproxy_syn_received | received | packets/s |
97
+| netfilter.synproxy_conn_reopened | reopened | connections/s |
98
+| netfilter.synproxy_cookies | valid, invalid, retransmits | cookies/s |
99
100
src/collectors/proc.plugin/integrations/system_load_average.md
+23
-23
@@ -67,26 +67,29 @@ The default configuration for this integration does not impose any limits on dat
67
68
The default configuration for this integration is not expected to impose a significant performance impact on the system.
69
70
-## Metrics
70
+## Setup
71
72
-Metrics grouped by *scope*.
72
74
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
73
+### Prerequisites
74
75
+No action required.
76
77
+### Configuration
78
78
-### Per System Load Average instance
79
+#### Options
80
81
82
82
-This scope has no labels.
83
+There are no configuration options.
84
84
-Metrics:
85
86
-| Metric | Dimensions | Unit |
87
-|:------|:----------|:----|
88
-| system.load | load1, load5, load15 | load |
89
-| system.active_processes | active | processes |
86
+
87
+#### via File
88
+
89
+There is no configuration file.
90
+
91
+##### Examples
92
+There are no configuration examples.
93
94
95
@@ -104,28 +107,25 @@ The following alerts are available:
107
| [ active_processes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/processes.conf) | system.active_processes | system process IDs (PID) space utilization |
108
109
107
-## Setup
108
-
109
-
110
-### Prerequisites
111
-
112
-No action required.
110
+## Metrics
111
114
-### Configuration
112
+Metrics grouped by *scope*.
113
116
-#### Options
114
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
115
116
117
120
-There are no configuration options.
118
+### Per System Load Average instance
119
120
121
124
-#### via File
122
+This scope has no labels.
123
126
-There is no configuration file.
124
+Metrics:
125
128
-##### Examples
129
-There are no configuration examples.
126
+| Metric | Dimensions | Unit |
127
+|:------|:----------|:----|
128
+| system.load | load1, load5, load15 | load |
129
+| system.active_processes | active | processes |
130
131
src/collectors/proc.plugin/integrations/system_statistics.md
+58
-58
@@ -68,64 +68,6 @@ The default configuration for this integration does not impose any limits on dat
68
The collector disables cpu frequency and idle state monitoring when there are more than 128 CPU cores available.
69
70
71
-## Metrics
72
-
73
-Metrics grouped by *scope*.
74
-
75
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
76
-
77
-
78
-
79
-### Per System statistics instance
80
-
81
-
82
-
83
-This scope has no labels.
84
-
85
-Metrics:
86
-
87
-| Metric | Dimensions | Unit |
88
-|:------|:----------|:----|
89
-| system.cpu | guest_nice, guest, steal, softirq, irq, user, system, nice, iowait, idle | percentage |
90
-| system.intr | interrupts | interrupts/s |
91
-| system.ctxt | switches | context switches/s |
92
-| system.forks | started | processes/s |
93
-| system.processes | running, blocked | processes |
94
-| cpu.core_throttling | a dimension per cpu core | events/s |
95
-| cpu.package_throttling | a dimension per package | events/s |
96
-| cpu.cpufreq | a dimension per cpu core | MHz |
97
-
98
-### Per cpu core
99
-
100
-Per-core CPU metrics. Disabled by default, can be enabled in the [configuration options](#configuration).
101
-
102
-Labels:
103
-
104
-| Label | Description |
105
-|:-----------|:----------------|
106
-| cpu | Identifier of the CPU core (e.g., core0, core1, core2). |
107
-
108
-Metrics:
109
-
110
-| Metric | Dimensions | Unit |
111
-|:------|:----------|:----|
112
-| cpu.cpu | guest_nice, guest, steal, softirq, irq, user, system, nice, iowait, idle | percentage |
113
-| cpuidle.cpu_cstate_residency_time | a dimension per c-state | percentage |
114
-
115
-
116
-
117
-## Alerts
118
-
119
-
120
-The following alerts are available:
121
-
122
-| Alert name | On metric | Description |
123
-|:------------|:----------|:------------|
124
-| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU utilization over the last 10 minutes (excluding iowait, nice and steal) |
125
-| [ 10min_cpu_iowait ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU iowait time over the last 10 minutes |
126
-| [ 20min_steal_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU steal time over the last 20 minutes |
127
-
128
-
71
## Setup
72
73
@@ -180,3 +122,61 @@ sudo ./edit-config netdata.conf
122
There are no configuration examples.
123
124
125
+
126
+## Alerts
127
+
128
+
129
+The following alerts are available:
130
+
131
+| Alert name | On metric | Description |
132
+|:------------|:----------|:------------|
133
+| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU utilization over the last 10 minutes (excluding iowait, nice and steal) |
134
+| [ 10min_cpu_iowait ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU iowait time over the last 10 minutes |
135
+| [ 20min_steal_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | average CPU steal time over the last 20 minutes |
136
+
137
+
138
+## Metrics
139
+
140
+Metrics grouped by *scope*.
141
+
142
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
143
+
144
+
145
+
146
+### Per System statistics instance
147
+
148
+
149
+
150
+This scope has no labels.
151
+
152
+Metrics:
153
+
154
+| Metric | Dimensions | Unit |
155
+|:------|:----------|:----|
156
+| system.cpu | guest_nice, guest, steal, softirq, irq, user, system, nice, iowait, idle | percentage |
157
+| system.intr | interrupts | interrupts/s |
158
+| system.ctxt | switches | context switches/s |
159
+| system.forks | started | processes/s |
160
+| system.processes | running, blocked | processes |
161
+| cpu.core_throttling | a dimension per cpu core | events/s |
162
+| cpu.package_throttling | a dimension per package | events/s |
163
+| cpu.cpufreq | a dimension per cpu core | MHz |
164
+
165
+### Per cpu core
166
+
167
+Per-core CPU metrics. Disabled by default, can be enabled in the [configuration options](#configuration).
168
+
169
+Labels:
170
+
171
+| Label | Description |
172
+|:-----------|:----------------|
173
+| cpu | Identifier of the CPU core (e.g., core0, core1, core2). |
174
+
175
+Metrics:
176
+
177
+| Metric | Dimensions | Unit |
178
+|:------|:----------|:----|
179
+| cpu.cpu | guest_nice, guest, steal, softirq, irq, user, system, nice, iowait, idle | percentage |
180
+| cpuidle.cpu_cstate_residency_time | a dimension per c-state | percentage |
181
+
182
+
src/collectors/proc.plugin/integrations/system_uptime.md
+21
-21
@@ -57,55 +57,55 @@ The default configuration for this integration does not impose any limits on dat
57
58
The default configuration for this integration is not expected to impose a significant performance impact on the system.
59
60
-## Metrics
60
+## Setup
61
62
-Metrics grouped by *scope*.
62
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
+### Prerequisites
64
65
+No action required.
66
67
+### Configuration
68
68
-### Per System Uptime instance
69
+#### Options
70
71
72
72
-This scope has no labels.
73
+There are no configuration options.
74
74
-Metrics:
75
76
-| Metric | Dimensions | Unit |
77
-|:------|:----------|:----|
78
-| system.uptime | uptime | seconds |
76
77
+#### via File
78
79
+There is no configuration file.
80
82
-## Alerts
81
+##### Examples
82
+There are no configuration examples.
83
84
-There are no alerts configured by default for this integration.
84
85
87
-## Setup
86
+## Alerts
87
88
+There are no alerts configured by default for this integration.
89
90
-### Prerequisites
90
92
-No action required.
91
+## Metrics
92
94
-### Configuration
93
+Metrics grouped by *scope*.
94
96
-#### Options
95
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
96
97
98
100
-There are no configuration options.
99
+### Per System Uptime instance
100
101
102
104
-#### via File
103
+This scope has no labels.
104
106
-There is no configuration file.
105
+Metrics:
106
108
-##### Examples
109
-There are no configuration examples.
107
+| Metric | Dimensions | Unit |
108
+|:------|:----------|:----|
109
+| system.uptime | uptime | seconds |
110
111
src/collectors/proc.plugin/integrations/wireless_network_interfaces.md
+26
-26
@@ -44,60 +44,60 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
47
+## Setup
48
49
-Metrics grouped by *scope*.
49
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
50
+### Prerequisites
51
52
+No action required.
53
54
+### Configuration
55
55
-### Per wireless device
56
+#### Options
57
58
59
59
-This scope has no labels.
60
+There are no configuration options.
61
61
-Metrics:
62
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| wireless.status | status | status |
66
-| wireless.link_quality | link_quality | value |
67
-| wireless.signal_level | signal_level | dBm |
68
-| wireless.noise_level | noise_level | dBm |
69
-| wireless.discarded_packets | nwid, crypt, frag, retry, misc | packets/s |
70
-| wireless.missed_beacons | missed_beacons | frames/s |
63
64
+#### via File
65
66
+There is no configuration file.
67
74
-## Alerts
68
+##### Examples
69
+There are no configuration examples.
70
76
-There are no alerts configured by default for this integration.
71
72
79
-## Setup
73
+## Alerts
74
75
+There are no alerts configured by default for this integration.
76
82
-### Prerequisites
77
84
-No action required.
78
+## Metrics
79
86
-### Configuration
80
+Metrics grouped by *scope*.
81
88
-#### Options
82
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
84
85
92
-There are no configuration options.
86
+### Per wireless device
87
88
89
96
-#### via File
90
+This scope has no labels.
91
98
-There is no configuration file.
92
+Metrics:
93
100
-##### Examples
101
-There are no configuration examples.
94
+| Metric | Dimensions | Unit |
95
+|:------|:----------|:----|
96
+| wireless.status | status | status |
97
+| wireless.link_quality | link_quality | value |
98
+| wireless.signal_level | signal_level | dBm |
99
+| wireless.noise_level | noise_level | dBm |
100
+| wireless.discarded_packets | nwid, crypt, frag, retry, misc | packets/s |
101
+| wireless.missed_beacons | missed_beacons | frames/s |
102
103
src/collectors/proc.plugin/integrations/zfs_adaptive_replacement_cache.md
+36
-36
@@ -44,6 +44,42 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+No action required.
53
+
54
+### Configuration
55
+
56
+#### Options
57
+
58
+
59
+
60
+There are no configuration options.
61
+
62
+
63
+
64
+#### via File
65
+
66
+There is no configuration file.
67
+
68
+##### Examples
69
+There are no configuration examples.
70
+
71
+
72
+
73
+## Alerts
74
+
75
+
76
+The following alerts are available:
77
+
78
+| Alert name | On metric | Description |
79
+|:------------|:----------|:------------|
80
+| [ zfs_memory_throttle ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfs.memory_ops | number of times ZFS had to limit the ARC growth in the last 10 minutes |
81
+
82
+
83
## Metrics
84
85
Metrics grouped by *scope*.
@@ -90,39 +126,3 @@ Metrics:
126
| zfs.hash_chains | current, max | chains |
127
128
93
-
94
-## Alerts
95
-
96
-
97
-The following alerts are available:
98
-
99
-| Alert name | On metric | Description |
100
-|:------------|:----------|:------------|
101
-| [ zfs_memory_throttle ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfs.memory_ops | number of times ZFS had to limit the ARC growth in the last 10 minutes |
102
-
103
-
104
-## Setup
105
-
106
-
107
-### Prerequisites
108
-
109
-No action required.
110
-
111
-### Configuration
112
-
113
-#### Options
114
-
115
-
116
-
117
-There are no configuration options.
118
-
119
-
120
-
121
-#### via File
122
-
123
-There is no configuration file.
124
-
125
-##### Examples
126
-There are no configuration examples.
127
-
128
-
src/collectors/proc.plugin/integrations/zram.md
+27
-27
@@ -48,62 +48,62 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
51
+## Setup
52
53
-Metrics grouped by *scope*.
53
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
54
+### Prerequisites
55
56
+No action required.
57
58
+### Configuration
59
59
-### Per zram device
60
+#### Options
61
62
63
63
-Labels:
64
+There are no configuration options.
65
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| device | TBD |
66
69
-Metrics:
67
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| mem.zram_usage | compressed, metadata | MiB |
74
-| mem.zram_savings | savings, original | MiB |
75
-| mem.zram_ratio | ratio | ratio |
76
-| mem.zram_efficiency | percent | percentage |
68
+#### via File
69
70
+There is no configuration file.
71
72
+##### Examples
73
+There are no configuration examples.
74
80
-## Alerts
75
82
-There are no alerts configured by default for this integration.
76
77
+## Alerts
78
85
-## Setup
79
+There are no alerts configured by default for this integration.
80
81
88
-### Prerequisites
82
+## Metrics
83
90
-No action required.
84
+Metrics grouped by *scope*.
85
92
-### Configuration
86
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
87
94
-#### Options
88
89
90
+### Per zram device
91
98
-There are no configuration options.
92
93
94
+Labels:
95
102
-#### via File
96
+| Label | Description |
97
+|:-----------|:----------------|
98
+| device | TBD |
99
104
-There is no configuration file.
100
+Metrics:
101
106
-##### Examples
107
-There are no configuration examples.
102
+| Metric | Dimensions | Unit |
103
+|:------|:----------|:----|
104
+| mem.zram_usage | compressed, metadata | MiB |
105
+| mem.zram_savings | savings, original | MiB |
106
+| mem.zram_ratio | ratio | ratio |
107
+| mem.zram_efficiency | percent | percentage |
108
109
src/collectors/python.d.plugin/am2320/integrations/am2320.md
+28
-28
@@ -44,34 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per AM2320 instance
56
-
57
-These metrics refer to the entire monitored application.
58
-
59
-This scope has no labels.
60
-
61
-Metrics:
62
-
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| am2320.temperature | temperature | celsius |
66
-| am2320.humidity | humidity | percentage |
67
-
68
-
69
-
70
-## Alerts
71
-
72
-There are no alerts configured by default for this integration.
73
-
74
-
47
## Setup
48
49
@@ -167,6 +139,34 @@ local_sensor:
139
```
140
141
142
+## Alerts
143
+
144
+There are no alerts configured by default for this integration.
145
+
146
+
147
+## Metrics
148
+
149
+Metrics grouped by *scope*.
150
+
151
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
152
+
153
+
154
+
155
+### Per AM2320 instance
156
+
157
+These metrics refer to the entire monitored application.
158
+
159
+This scope has no labels.
160
+
161
+Metrics:
162
+
163
+| Metric | Dimensions | Unit |
164
+|:------|:----------|:----|
165
+| am2320.temperature | temperature | celsius |
166
+| am2320.humidity | humidity | percentage |
167
+
168
+
169
+
170
## Troubleshooting
171
172
### Debug Mode
src/collectors/python.d.plugin/go_expvar/integrations/go_applications_expvar.md
+33
-33
@@ -44,39 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per Go applications (EXPVAR) instance
56
-
57
-These metrics refer to the entire monitored application.
58
-
59
-This scope has no labels.
60
-
61
-Metrics:
62
-
63
-| Metric | Dimensions | Unit |
64
-|:------|:----------|:----|
65
-| expvar.memstats.heap | alloc, inuse | KiB |
66
-| expvar.memstats.stack | inuse | KiB |
67
-| expvar.memstats.mspan | inuse | KiB |
68
-| expvar.memstats.mcache | inuse | KiB |
69
-| expvar.memstats.live_objects | live | objects |
70
-| expvar.memstats.sys | sys | KiB |
71
-| expvar.memstats.gc_pauses | avg | ns |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-There are no alerts configured by default for this integration.
78
-
79
-
47
## Setup
48
49
@@ -317,6 +284,39 @@ app1:
284
```
285
286
287
+## Alerts
288
+
289
+There are no alerts configured by default for this integration.
290
+
291
+
292
+## Metrics
293
+
294
+Metrics grouped by *scope*.
295
+
296
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
297
+
298
+
299
+
300
+### Per Go applications (EXPVAR) instance
301
+
302
+These metrics refer to the entire monitored application.
303
+
304
+This scope has no labels.
305
+
306
+Metrics:
307
+
308
+| Metric | Dimensions | Unit |
309
+|:------|:----------|:----|
310
+| expvar.memstats.heap | alloc, inuse | KiB |
311
+| expvar.memstats.stack | inuse | KiB |
312
+| expvar.memstats.mspan | inuse | KiB |
313
+| expvar.memstats.mcache | inuse | KiB |
314
+| expvar.memstats.live_objects | live | objects |
315
+| expvar.memstats.sys | sys | KiB |
316
+| expvar.memstats.gc_pauses | avg | ns |
317
+
318
+
319
+
320
## Troubleshooting
321
322
### Debug Mode
src/collectors/python.d.plugin/pandas/integrations/pandas.md
+30
-30
@@ -50,36 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-This collector is expecting one row in the final pandas DataFrame. It is that first row that will be taken
60
-as the most recent values for each dimension on each chart using (`df.to_dict(orient='records')[0]`).
61
-See [pd.to_dict()](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.to_dict.html)."
62
-
63
-
64
-### Per Pandas instance
65
-
66
-These metrics refer to the entire monitored application.
67
-
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-
76
-
77
-
78
-## Alerts
79
-
80
-There are no alerts configured by default for this integration.
81
-
82
-
53
## Setup
54
55
@@ -351,6 +321,36 @@ sql:
321
322
323
324
+## Alerts
325
+
326
+There are no alerts configured by default for this integration.
327
+
328
+
329
+## Metrics
330
+
331
+Metrics grouped by *scope*.
332
+
333
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
334
+
335
+This collector is expecting one row in the final pandas DataFrame. It is that first row that will be taken
336
+as the most recent values for each dimension on each chart using (`df.to_dict(orient='records')[0]`).
337
+See [pd.to_dict()](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.to_dict.html)."
338
+
339
+
340
+### Per Pandas instance
341
+
342
+These metrics refer to the entire monitored application.
343
+
344
+
345
+This scope has no labels.
346
+
347
+Metrics:
348
+
349
+| Metric | Dimensions | Unit |
350
+|:------|:----------|:----|
351
+
352
+
353
+
354
## Troubleshooting
355
356
### Debug Mode
src/collectors/slabinfo.plugin/integrations/linux_kernel_slab_allocator_statistics.md
+29
-29
@@ -50,35 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-SLAB cache utilization metrics for the whole system.
60
-
61
-### Per Linux kernel SLAB allocator statistics instance
62
-
63
-
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| mem.slabmemory | a dimension per cache | B |
72
-| mem.slabfilling | a dimension per cache | % |
73
-| mem.slabwaste | a dimension per cache | B |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
53
## Setup
54
55
@@ -135,3 +106,32 @@ sudo ./edit-config netdata.conf
106
There are no configuration examples.
107
108
109
+
110
+## Alerts
111
+
112
+There are no alerts configured by default for this integration.
113
+
114
+
115
+## Metrics
116
+
117
+Metrics grouped by *scope*.
118
+
119
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
120
+
121
+SLAB cache utilization metrics for the whole system.
122
+
123
+### Per Linux kernel SLAB allocator statistics instance
124
+
125
+
126
+
127
+This scope has no labels.
128
+
129
+Metrics:
130
+
131
+| Metric | Dimensions | Unit |
132
+|:------|:----------|:----|
133
+| mem.slabmemory | a dimension per cache | B |
134
+| mem.slabfilling | a dimension per cache | % |
135
+| mem.slabwaste | a dimension per cache | B |
136
+
137
+
src/collectors/tc.plugin/integrations/tc_qos_classes.md
+37
-37
@@ -46,43 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-Metrics grouped by *scope*.
52
-
53
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
54
-
55
-
56
-
57
-### Per network device direction
58
-
59
-Metrics related to QoS network device directions. Each direction (in/out) produces its own set of the following metrics.
60
-
61
-Labels:
62
-
63
-| Label | Description |
64
-|:-----------|:----------------|
65
-| device | The network interface. |
66
-| device_name | The network interface name |
67
-| group | The device family |
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| tc.qos | a dimension per class | kilobits/s |
74
-| tc.qos_packets | a dimension per class | packets/s |
75
-| tc.qos_dropped | a dimension per class | packets/s |
76
-| tc.qos_tokens | a dimension per class | tokens |
77
-| tc.qos_ctokens | a dimension per class | ctokens |
78
-
79
-
80
-
81
-## Alerts
82
-
83
-There are no alerts configured by default for this integration.
84
-
85
-
49
## Setup
50
51
@@ -174,3 +137,40 @@ You can read more about setting up the tc rules in rc.local in this [GitHub issu
137
138
```
139
140
+
141
+## Alerts
142
+
143
+There are no alerts configured by default for this integration.
144
+
145
+
146
+## Metrics
147
+
148
+Metrics grouped by *scope*.
149
+
150
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
151
+
152
+
153
+
154
+### Per network device direction
155
+
156
+Metrics related to QoS network device directions. Each direction (in/out) produces its own set of the following metrics.
157
+
158
+Labels:
159
+
160
+| Label | Description |
161
+|:-----------|:----------------|
162
+| device | The network interface. |
163
+| device_name | The network interface name |
164
+| group | The device family |
165
+
166
+Metrics:
167
+
168
+| Metric | Dimensions | Unit |
169
+|:------|:----------|:----|
170
+| tc.qos | a dimension per class | kilobits/s |
171
+| tc.qos_packets | a dimension per class | packets/s |
172
+| tc.qos_dropped | a dimension per class | packets/s |
173
+| tc.qos_tokens | a dimension per class | tokens |
174
+| tc.qos_ctokens | a dimension per class | ctokens |
175
+
176
+
src/collectors/timex.plugin/integrations/timex.md
+34
-34
@@ -43,40 +43,6 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
-## Metrics
47
-
48
-Metrics grouped by *scope*.
49
-
50
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
51
-
52
-
53
-
54
-### Per Timex instance
55
-
56
-These metrics refer to the entire monitored application.
57
-
58
-This scope has no labels.
59
-
60
-Metrics:
61
-
62
-| Metric | Dimensions | Unit |
63
-|:------|:----------|:----|
64
-| system.clock_sync_state | state | state |
65
-| system.clock_status | unsync, clockerr | status |
66
-| system.clock_sync_offset | offset | milliseconds |
67
-
68
-
69
-
70
-## Alerts
71
-
72
-
73
-The following alerts are available:
74
-
75
-| Alert name | On metric | Description |
76
-|:------------|:----------|:------------|
77
-| [ system_clock_sync_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/timex.conf) | system.clock_sync_state | when set to 0, the system kernel believes the system clock is not properly synchronized to a reliable server |
78
-
79
-
46
## Setup
47
48
@@ -146,3 +112,37 @@ A basic configuration example.
112
</details>
113
114
115
+
116
+## Alerts
117
+
118
+
119
+The following alerts are available:
120
+
121
+| Alert name | On metric | Description |
122
+|:------------|:----------|:------------|
123
+| [ system_clock_sync_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/timex.conf) | system.clock_sync_state | when set to 0, the system kernel believes the system clock is not properly synchronized to a reliable server |
124
+
125
+
126
+## Metrics
127
+
128
+Metrics grouped by *scope*.
129
+
130
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
131
+
132
+
133
+
134
+### Per Timex instance
135
+
136
+These metrics refer to the entire monitored application.
137
+
138
+This scope has no labels.
139
+
140
+Metrics:
141
+
142
+| Metric | Dimensions | Unit |
143
+|:------|:----------|:----|
144
+| system.clock_sync_state | state | state |
145
+| system.clock_status | unsync, clockerr | status |
146
+| system.clock_sync_offset | offset | milliseconds |
147
+
148
+
src/collectors/windows.plugin/integrations/active_directory.md
+40
-40
@@ -49,46 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Active Directory
61
-
62
-These metrics refer to Active Directory.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| ad.directory_operations | read, write, search | operations/s |
71
-| ad.name_cache_lookups | lookups | lookups/s |
72
-| ad.dra_replication_properties_updated | inbound | properties/s |
73
-| ad.dra_replication_properties_filtered | inbound | properties/s |
74
-| ad.dra_replication_intersite_compressed_traffic | inbound, outbound | bytes/s |
75
-| ad.dra_replication_intrasite_compressed_traffic | inbound, outbound | bytes/s |
76
-| ad.dra_replication_pending_syncs | pending | syncs |
77
-| ad.dra_replication_pending_syncs | pending | syncs |
78
-| ad.dra_replication_sync_requests | request | requests/s |
79
-| ad.name_cache_hits | hits | hits/s |
80
-| ad.ds_threads | thread | threads |
81
-| ad.ldap_last_bind_time | last_bind | seconds |
82
-| ad.ldap_searches | searches | searches/s |
83
-| ad.atq_average_request_latency | time | seconds |
84
-
85
-
86
-
87
-## Alerts
88
-
89
-There are no alerts configured by default for this integration.
90
-
91
-
52
## Setup
53
54
@@ -138,3 +98,43 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per Active Directory
116
+
117
+These metrics refer to Active Directory.
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| ad.directory_operations | read, write, search | operations/s |
126
+| ad.name_cache_lookups | lookups | lookups/s |
127
+| ad.dra_replication_properties_updated | inbound | properties/s |
128
+| ad.dra_replication_properties_filtered | inbound | properties/s |
129
+| ad.dra_replication_intersite_compressed_traffic | inbound, outbound | bytes/s |
130
+| ad.dra_replication_intrasite_compressed_traffic | inbound, outbound | bytes/s |
131
+| ad.dra_replication_pending_syncs | pending | syncs |
132
+| ad.dra_replication_pending_syncs | pending | syncs |
133
+| ad.dra_replication_sync_requests | request | requests/s |
134
+| ad.name_cache_hits | hits | hits/s |
135
+| ad.ds_threads | thread | threads |
136
+| ad.ldap_last_bind_time | last_bind | seconds |
137
+| ad.ldap_searches | searches | searches/s |
138
+| ad.atq_average_request_latency | time | seconds |
139
+
140
+
src/collectors/windows.plugin/integrations/active_directory_certificate_service.md
+46
-46
@@ -49,52 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Certificate Service Certificate
61
-
62
-These metrics refer to the Certificate instances defined on host.
63
-
64
-Labels:
65
-
66
-| Label | Description |
67
-|:-----------|:----------------|
68
-| cert | The certificate name. |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| adcs.cert_requests | requests | requests/s |
75
-| adcs.cert_request_processing_time | processing_times | seconds |
76
-| adcs.cert_retrievals | retrievals | retrievals/s |
77
-| adcs.cert_failed_requests | failed | requests/s |
78
-| adcs.cert_issued_requests | issued | requests/s |
79
-| adcs.cert_pending_requests | pending | requests/s |
80
-| adcs.cert_challenge_responses | challenge | responses/s |
81
-| adcs.cert_retrieval_processing_time | processing_time | seconds |
82
-| adcs.cert_request_cryptographic_signing_time | singing_time | seconds |
83
-| adcs.cert_request_policy_module_processing | processing_time | seconds |
84
-| adcs.cert_request_policy_module_processing | processing_time | seconds |
85
-| adcs.cert_challenge_response_processing_time | processing_time | seconds |
86
-| adcs.cert_signed_certificate_timestamp_lists | processing_time | lists/s |
87
-| adcs.cert_signed_certificate_timestamp_lists | lists | lists/s |
88
-| adcs.cert_signed_certificate_timestamp_list_processing_time | processing_time | seconds |
89
-| adcs.cert_retrieval_processing_time | processing_time | seconds |
90
-
91
-
92
-
93
-## Alerts
94
-
95
-There are no alerts configured by default for this integration.
96
-
97
-
52
## Setup
53
54
@@ -144,3 +98,49 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per Certificate Service Certificate
116
+
117
+These metrics refer to the Certificate instances defined on host.
118
+
119
+Labels:
120
+
121
+| Label | Description |
122
+|:-----------|:----------------|
123
+| cert | The certificate name. |
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| adcs.cert_requests | requests | requests/s |
130
+| adcs.cert_request_processing_time | processing_times | seconds |
131
+| adcs.cert_retrievals | retrievals | retrievals/s |
132
+| adcs.cert_failed_requests | failed | requests/s |
133
+| adcs.cert_issued_requests | issued | requests/s |
134
+| adcs.cert_pending_requests | pending | requests/s |
135
+| adcs.cert_challenge_responses | challenge | responses/s |
136
+| adcs.cert_retrieval_processing_time | processing_time | seconds |
137
+| adcs.cert_request_cryptographic_signing_time | singing_time | seconds |
138
+| adcs.cert_request_policy_module_processing | processing_time | seconds |
139
+| adcs.cert_request_policy_module_processing | processing_time | seconds |
140
+| adcs.cert_challenge_response_processing_time | processing_time | seconds |
141
+| adcs.cert_signed_certificate_timestamp_lists | processing_time | lists/s |
142
+| adcs.cert_signed_certificate_timestamp_lists | lists | lists/s |
143
+| adcs.cert_signed_certificate_timestamp_list_processing_time | processing_time | seconds |
144
+| adcs.cert_retrieval_processing_time | processing_time | seconds |
145
+
146
+
src/collectors/windows.plugin/integrations/active_directory_federation_service.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 10 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibADFS]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -100,58 +155,3 @@ Metrics:
155
| adfs.wstrust_token_requests_success | success | requests/s |
156
157
103
-
104
-## Alerts
105
-
106
-There are no alerts configured by default for this integration.
107
-
108
-
109
-## Setup
110
-
111
-
112
-### Prerequisites
113
-
114
-No action required.
115
-
116
-### Configuration
117
-
118
-#### Options
119
-
120
-
121
-
122
-
123
-
124
-| Option | Description | Default | Required |
125
-|:-----|:------------|:--------|:---------:|
126
-| update every | Data collection frequency. | 10 | no |
127
-
128
-
129
-
130
-
131
-#### via File
132
-
133
-The configuration file name for this integration is `netdata.conf`.
134
-Configuration for this specific integration is located in the `[plugin:windows:PerflibADFS]` section within that file.
135
-
136
-The file format is a modified INI syntax. The general structure is:
137
-
138
-```ini
139
-[section1]
140
- option1 = some value
141
- option2 = some other value
142
-
143
-[section2]
144
- option3 = some third value
145
-```
146
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
147
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
148
-
149
-```bash
150
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
-sudo ./edit-config netdata.conf
152
-```
153
-
154
-##### Examples
155
-There are no configuration examples.
156
-
157
-
src/collectors/windows.plugin/integrations/asp.net.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| PerflibASP | An option to enable or disable the data collection. | yes | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -115,58 +170,3 @@ Metrics:
170
| aspnet.form_authentication_failure | failure | auth |
171
172
118
-
119
-## Alerts
120
-
121
-There are no alerts configured by default for this integration.
122
-
123
-
124
-## Setup
125
-
126
-
127
-### Prerequisites
128
-
129
-No action required.
130
-
131
-### Configuration
132
-
133
-#### Options
134
-
135
-
136
-
137
-
138
-
139
-| Option | Description | Default | Required |
140
-|:-----|:------------|:--------|:---------:|
141
-| PerflibASP | An option to enable or disable the data collection. | yes | no |
142
-
143
-
144
-
145
-
146
-#### via File
147
-
148
-The configuration file name for this integration is `netdata.conf`.
149
-Configuration for this specific integration is located in the `[plugin:windows]` section within that file.
150
-
151
-The file format is a modified INI syntax. The general structure is:
152
-
153
-```ini
154
-[section1]
155
- option1 = some value
156
- option2 = some other value
157
-
158
-[section2]
159
- option3 = some third value
160
-```
161
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
162
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
163
-
164
-```bash
165
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
166
-sudo ./edit-config netdata.conf
167
-```
168
-
169
-##### Examples
170
-There are no configuration examples.
171
-
172
-
src/collectors/windows.plugin/integrations/hardware_information_collected_from_kernel_ring..md
+27
-27
@@ -49,33 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Hardware information collected from kernel ring. instance
61
-
62
-This metric show latest CPU temperature.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| cpu.temperature | a dimension per core | Celcius |
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
52
## Setup
53
54
@@ -125,3 +98,30 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per Hardware information collected from kernel ring. instance
116
+
117
+This metric show latest CPU temperature.
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| cpu.temperature | a dimension per core | Celcius |
126
+
127
+
src/collectors/windows.plugin/integrations/hyper-v.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 5 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibHyperV]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -169,58 +224,3 @@ Metrics:
224
| hyperv.vswitch_purged_mac_addresses | purged | mac addresses/s |
225
226
172
-
173
-## Alerts
174
-
175
-There are no alerts configured by default for this integration.
176
-
177
-
178
-## Setup
179
-
180
-
181
-### Prerequisites
182
-
183
-No action required.
184
-
185
-### Configuration
186
-
187
-#### Options
188
-
189
-
190
-
191
-
192
-
193
-| Option | Description | Default | Required |
194
-|:-----|:------------|:--------|:---------:|
195
-| update every | Data collection frequency. | 5 | no |
196
-
197
-
198
-
199
-
200
-#### via File
201
-
202
-The configuration file name for this integration is `netdata.conf`.
203
-Configuration for this specific integration is located in the `[plugin:windows:PerflibHyperV]` section within that file.
204
-
205
-The file format is a modified INI syntax. The general structure is:
206
-
207
-```ini
208
-[section1]
209
- option1 = some value
210
- option2 = some other value
211
-
212
-[section2]
213
- option3 = some third value
214
-```
215
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
216
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
217
-
218
-```bash
219
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
220
-sudo ./edit-config netdata.conf
221
-```
222
-
223
-##### Examples
224
-There are no configuration examples.
225
-
226
-
src/collectors/windows.plugin/integrations/iis.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 1 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibWebService]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -136,58 +191,3 @@ Metrics:
191
| iis.w3svc_w3wp_output_cache_flushed_total | output_cache_entries | flushes |
192
193
139
-
140
-## Alerts
141
-
142
-There are no alerts configured by default for this integration.
143
-
144
-
145
-## Setup
146
-
147
-
148
-### Prerequisites
149
-
150
-No action required.
151
-
152
-### Configuration
153
-
154
-#### Options
155
-
156
-
157
-
158
-
159
-
160
-| Option | Description | Default | Required |
161
-|:-----|:------------|:--------|:---------:|
162
-| update every | Data collection frequency. | 1 | no |
163
-
164
-
165
-
166
-
167
-#### via File
168
-
169
-The configuration file name for this integration is `netdata.conf`.
170
-Configuration for this specific integration is located in the `[plugin:windows:PerflibWebService]` section within that file.
171
-
172
-The file format is a modified INI syntax. The general structure is:
173
-
174
-```ini
175
-[section1]
176
- option1 = some value
177
- option2 = some other value
178
-
179
-[section2]
180
- option3 = some third value
181
-```
182
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
183
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
184
-
185
-```bash
186
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
187
-sudo ./edit-config netdata.conf
188
-```
189
-
190
-##### Examples
191
-There are no configuration examples.
192
-
193
-
src/collectors/windows.plugin/integrations/memory_statistics_win.md
+30
-30
@@ -49,36 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per System
61
-
62
-These metrics refer to the entire system.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| mem.swap_iops | read, write | operations/s |
71
-| mem.swap_pages_io | read, write | pages/s |
72
-| mem.system_pool_size | paged, non-paged | bytes |
73
-| mem.system_page_table_entries | free | pages |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
52
## Setup
53
54
@@ -128,3 +98,33 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per System
116
+
117
+These metrics refer to the entire system.
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| mem.swap_iops | read, write | operations/s |
126
+| mem.swap_pages_io | read, write | pages/s |
127
+| mem.system_pool_size | paged, non-paged | bytes |
128
+| mem.system_page_table_entries | free | pages |
129
+
130
+
src/collectors/windows.plugin/integrations/ms_exchange.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 10 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibExchange]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -100,58 +155,3 @@ Metrics:
155
| exchange.avail_service_requests | serviced | requests/s |
156
157
103
-
104
-## Alerts
105
-
106
-There are no alerts configured by default for this integration.
107
-
108
-
109
-## Setup
110
-
111
-
112
-### Prerequisites
113
-
114
-No action required.
115
-
116
-### Configuration
117
-
118
-#### Options
119
-
120
-
121
-
122
-
123
-
124
-| Option | Description | Default | Required |
125
-|:-----|:------------|:--------|:---------:|
126
-| update every | Data collection frequency. | 10 | no |
127
-
128
-
129
-
130
-
131
-#### via File
132
-
133
-The configuration file name for this integration is `netdata.conf`.
134
-Configuration for this specific integration is located in the `[plugin:windows:PerflibExchange]` section within that file.
135
-
136
-The file format is a modified INI syntax. The general structure is:
137
-
138
-```ini
139
-[section1]
140
- option1 = some value
141
- option2 = some other value
142
-
143
-[section2]
144
- option3 = some third value
145
-```
146
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
147
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
148
-
149
-```bash
150
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
-sudo ./edit-config netdata.conf
152
-```
153
-
154
-##### Examples
155
-There are no configuration examples.
156
-
157
-
src/collectors/windows.plugin/integrations/net_framework.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 1 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibNetFramework]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -104,58 +159,3 @@ Metrics:
159
| netframework.clrlocksandthreads_contentions | contentions | contentions/s |
160
161
107
-
108
-## Alerts
109
-
110
-There are no alerts configured by default for this integration.
111
-
112
-
113
-## Setup
114
-
115
-
116
-### Prerequisites
117
-
118
-No action required.
119
-
120
-### Configuration
121
-
122
-#### Options
123
-
124
-
125
-
126
-
127
-
128
-| Option | Description | Default | Required |
129
-|:-----|:------------|:--------|:---------:|
130
-| update every | Data collection frequency. | 1 | no |
131
-
132
-
133
-
134
-
135
-#### via File
136
-
137
-The configuration file name for this integration is `netdata.conf`.
138
-Configuration for this specific integration is located in the `[plugin:windows:PerflibNetFramework]` section within that file.
139
-
140
-The file format is a modified INI syntax. The general structure is:
141
-
142
-```ini
143
-[section1]
144
- option1 = some value
145
- option2 = some other value
146
-
147
-[section2]
148
- option3 = some third value
149
-```
150
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
151
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
152
-
153
-```bash
154
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
155
-sudo ./edit-config netdata.conf
156
-```
157
-
158
-##### Examples
159
-There are no configuration examples.
160
-
161
-
src/collectors/windows.plugin/integrations/network_subsystem.md
+64
-64
@@ -49,6 +49,70 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 1 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibNetwork]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+
105
+The following alerts are available:
106
+
107
+| Alert name | On metric | Description |
108
+|:------------|:----------|:------------|
109
+| [ inbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | Ratio of inbound dropped packets for the network interface ${label:device} over the last 10 minutes |
110
+| [ outbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | Ratio of outbound dropped packets for the network interface ${label:device} over the last 10 minutes |
111
+| [ 1m_received_traffic_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | Average inbound utilization for the network interface ${label:device} over the last minute |
112
+| [ 1m_sent_traffic_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | Average outbound utilization for the network interface ${label:device} over the last minute |
113
+| [ network_interface_output_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.queue_length | Output Queue Length on interface ${label:device} should be zero, otherwise there are delays and bottlenecks. |
114
+
115
+
116
## Metrics
117
118
Metrics grouped by *scope*.
@@ -110,67 +174,3 @@ Metrics:
174
| net.chimney_connections | connections | connections |
175
176
113
-
114
-## Alerts
115
-
116
-
117
-The following alerts are available:
118
-
119
-| Alert name | On metric | Description |
120
-|:------------|:----------|:------------|
121
-| [ inbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | Ratio of inbound dropped packets for the network interface ${label:device} over the last 10 minutes |
122
-| [ outbound_packets_dropped_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.drops | Ratio of outbound dropped packets for the network interface ${label:device} over the last 10 minutes |
123
-| [ 1m_received_traffic_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | Average inbound utilization for the network interface ${label:device} over the last minute |
124
-| [ 1m_sent_traffic_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.net | Average outbound utilization for the network interface ${label:device} over the last minute |
125
-| [ network_interface_output_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/net.conf) | net.queue_length | Output Queue Length on interface ${label:device} should be zero, otherwise there are delays and bottlenecks. |
126
-
127
-
128
-## Setup
129
-
130
-
131
-### Prerequisites
132
-
133
-No action required.
134
-
135
-### Configuration
136
-
137
-#### Options
138
-
139
-
140
-
141
-
142
-
143
-| Option | Description | Default | Required |
144
-|:-----|:------------|:--------|:---------:|
145
-| update every | Data collection frequency. | 1 | no |
146
-
147
-
148
-
149
-
150
-#### via File
151
-
152
-The configuration file name for this integration is `netdata.conf`.
153
-Configuration for this specific integration is located in the `[plugin:windows:PerflibNetwork]` section within that file.
154
-
155
-The file format is a modified INI syntax. The general structure is:
156
-
157
-```ini
158
-[section1]
159
- option1 = some value
160
- option2 = some other value
161
-
162
-[section2]
163
- option3 = some third value
164
-```
165
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
166
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
167
-
168
-```bash
169
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
170
-sudo ./edit-config netdata.conf
171
-```
172
-
173
-##### Examples
174
-There are no configuration examples.
175
-
176
-
src/collectors/windows.plugin/integrations/numa_architecture.md
+31
-31
@@ -49,37 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per NUMA
61
-
62
-These metrics refer to memory utilization on NUMA systems.
63
-
64
-Labels:
65
-
66
-| Label | Description |
67
-|:-----------|:----------------|
68
-| node | The identifier of the CPU node. |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| mem.numa_node_mem_usage | free, standby | bytes |
75
-
76
-
77
-
78
-## Alerts
79
-
80
-There are no alerts configured by default for this integration.
81
-
82
-
52
## Setup
53
54
@@ -129,3 +98,34 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per NUMA
116
+
117
+These metrics refer to memory utilization on NUMA systems.
118
+
119
+Labels:
120
+
121
+| Label | Description |
122
+|:-----------|:----------------|
123
+| node | The identifier of the CPU node. |
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| mem.numa_node_mem_usage | free, standby | bytes |
130
+
131
+
src/collectors/windows.plugin/integrations/physical_and_logical_disk_performance_metrics.md
+55
-55
@@ -49,6 +49,61 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
+## Setup
53
+
54
+
55
+### Prerequisites
56
+
57
+No action required.
58
+
59
+### Configuration
60
+
61
+#### Options
62
+
63
+
64
+
65
+
66
+
67
+| Option | Description | Default | Required |
68
+|:-----|:------------|:--------|:---------:|
69
+| update every | Data collection frequency. | 1 | no |
70
+
71
+
72
+
73
+
74
+#### via File
75
+
76
+The configuration file name for this integration is `netdata.conf`.
77
+Configuration for this specific integration is located in the `[plugin:windows:PerflibStorage]` section within that file.
78
+
79
+The file format is a modified INI syntax. The general structure is:
80
+
81
+```ini
82
+[section1]
83
+ option1 = some value
84
+ option2 = some other value
85
+
86
+[section2]
87
+ option3 = some third value
88
+```
89
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
90
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
91
+
92
+```bash
93
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
94
+sudo ./edit-config netdata.conf
95
+```
96
+
97
+##### Examples
98
+There are no configuration examples.
99
+
100
+
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
## Metrics
108
109
Metrics grouped by *scope*.
@@ -117,58 +172,3 @@ Metrics:
172
| disk.qops | operations | operations |
173
174
120
-
121
-## Alerts
122
-
123
-There are no alerts configured by default for this integration.
124
-
125
-
126
-## Setup
127
-
128
-
129
-### Prerequisites
130
-
131
-No action required.
132
-
133
-### Configuration
134
-
135
-#### Options
136
-
137
-
138
-
139
-
140
-
141
-| Option | Description | Default | Required |
142
-|:-----|:------------|:--------|:---------:|
143
-| update every | Data collection frequency. | 1 | no |
144
-
145
-
146
-
147
-
148
-#### via File
149
-
150
-The configuration file name for this integration is `netdata.conf`.
151
-Configuration for this specific integration is located in the `[plugin:windows:PerflibStorage]` section within that file.
152
-
153
-The file format is a modified INI syntax. The general structure is:
154
-
155
-```ini
156
-[section1]
157
- option1 = some value
158
- option2 = some other value
159
-
160
-[section2]
161
- option3 = some third value
162
-```
163
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
164
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
165
-
166
-```bash
167
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
168
-sudo ./edit-config netdata.conf
169
-```
170
-
171
-##### Examples
172
-There are no configuration examples.
173
-
174
-
src/collectors/windows.plugin/integrations/power_supply_win.md
+37
-37
@@ -49,43 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Power Supply
61
-
62
-These metrics refer to Power Supply device.
63
-
64
-Labels:
65
-
66
-| Label | Description |
67
-|:-----------|:----------------|
68
-| device | Device name delivered as a Windows path. |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| powersupply.capacity | capacity | percentage |
75
-| powersupply.voltage | now | V |
76
-
77
-
78
-
79
-## Alerts
80
-
81
-
82
-The following alerts are available:
83
-
84
-| Alert name | On metric | Description |
85
-|:------------|:----------|:------------|
86
-| [ power_supply_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/power_supply_capacity.conf) | powersupply.capacity | percentage of remaining power supply capacity |
87
-
88
-
52
## Setup
53
54
@@ -135,3 +98,40 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+
105
+The following alerts are available:
106
+
107
+| Alert name | On metric | Description |
108
+|:------------|:----------|:------------|
109
+| [ power_supply_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/power_supply_capacity.conf) | powersupply.capacity | percentage of remaining power supply capacity |
110
+
111
+
112
+## Metrics
113
+
114
+Metrics grouped by *scope*.
115
+
116
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
117
+
118
+
119
+
120
+### Per Power Supply
121
+
122
+These metrics refer to Power Supply device.
123
+
124
+Labels:
125
+
126
+| Label | Description |
127
+|:-----------|:----------------|
128
+| device | Device name delivered as a Windows path. |
129
+
130
+Metrics:
131
+
132
+| Metric | Dimensions | Unit |
133
+|:------|:----------|:----|
134
+| powersupply.capacity | capacity | percentage |
135
+| powersupply.voltage | now | V |
136
+
137
+
src/collectors/windows.plugin/integrations/processor.md
+48
-48
@@ -49,54 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per System
61
-
62
-These metrics refer to the entire system.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| system.cpu | interrupts, user, privileged, dpc | percentage |
71
-
72
-### Per CPU
73
-
74
-These metrics provide information about individual CPU cores.
75
-
76
-Labels:
77
-
78
-| Label | Description |
79
-|:-----------|:----------------|
80
-| cpu | The identifier of the CPU core. On Windows systems, CPU cores are labeled as 'cpu0', 'cpu1', etc. |
81
-
82
-Metrics:
83
-
84
-| Metric | Dimensions | Unit |
85
-|:------|:----------|:----|
86
-| cpu.cpu | interrupts, user, privileged, dpc | percentage |
87
-
88
-
89
-
90
-## Alerts
91
-
92
-
93
-The following alerts are available:
94
-
95
-| Alert name | On metric | Description |
96
-|:------------|:----------|:------------|
97
-| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | Average CPU utilization over the last 10 minutes |
98
-
99
-
52
## Setup
53
54
@@ -146,3 +98,51 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+
105
+The following alerts are available:
106
+
107
+| Alert name | On metric | Description |
108
+|:------------|:----------|:------------|
109
+| [ 10min_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cpu.conf) | system.cpu | Average CPU utilization over the last 10 minutes |
110
+
111
+
112
+## Metrics
113
+
114
+Metrics grouped by *scope*.
115
+
116
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
117
+
118
+
119
+
120
+### Per System
121
+
122
+These metrics refer to the entire system.
123
+
124
+This scope has no labels.
125
+
126
+Metrics:
127
+
128
+| Metric | Dimensions | Unit |
129
+|:------|:----------|:----|
130
+| system.cpu | interrupts, user, privileged, dpc | percentage |
131
+
132
+### Per CPU
133
+
134
+These metrics provide information about individual CPU cores.
135
+
136
+Labels:
137
+
138
+| Label | Description |
139
+|:-----------|:----------------|
140
+| cpu | The identifier of the CPU core. On Windows systems, CPU cores are labeled as 'cpu0', 'cpu1', etc. |
141
+
142
+Metrics:
143
+
144
+| Metric | Dimensions | Unit |
145
+|:------|:----------|:----|
146
+| cpu.cpu | interrupts, user, privileged, dpc | percentage |
147
+
148
+
src/collectors/windows.plugin/integrations/semaphore_statistics.md
+28
-28
@@ -53,34 +53,6 @@ The default configuration for this integration does not impose any limits on dat
53
54
The default configuration for this integration is not expected to impose a significant performance impact on the system.
55
56
-## Metrics
57
-
58
-Metrics grouped by *scope*.
59
-
60
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
61
-
62
-
63
-
64
-### Per System
65
-
66
-These metrics refer to the entire system.
67
-
68
-This scope has no labels.
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| system.ipc_semaphores | semaphores | semaphores |
75
-| system.ipc_mutexes | mutexes | mutexes |
76
-
77
-
78
-
79
-## Alerts
80
-
81
-There are no alerts configured by default for this integration.
82
-
83
-
56
## Setup
57
58
@@ -130,3 +102,31 @@ sudo ./edit-config netdata.conf
102
There are no configuration examples.
103
104
105
+
106
+## Alerts
107
+
108
+There are no alerts configured by default for this integration.
109
+
110
+
111
+## Metrics
112
+
113
+Metrics grouped by *scope*.
114
+
115
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
116
+
117
+
118
+
119
+### Per System
120
+
121
+These metrics refer to the entire system.
122
+
123
+This scope has no labels.
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| system.ipc_semaphores | semaphores | semaphores |
130
+| system.ipc_mutexes | mutexes | mutexes |
131
+
132
+
src/collectors/windows.plugin/integrations/sensors.md
+53
-53
@@ -49,59 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Sensor
61
-
62
-These metrics refer to Sensors.
63
-
64
-Labels:
65
-
66
-| Label | Description |
67
-|:-----------|:----------------|
68
-| name | Sensor friendly name. |
69
-| manufacturer | The sensor manufacturer. |
70
-| model | The sensor model. |
71
-
72
-Metrics:
73
-
74
-| Metric | Dimensions | Unit |
75
-|:------|:----------|:----|
76
-| system.hw.sensor.temperature.input | input | Cel |
77
-| system.hw.sensor.power.input | input | W |
78
-| system.hw.sensor.current.input | input | A |
79
-| system.hw.sensor.humidity.input | input | % |
80
-| system.hw.sensor.lux.input | input | lx |
81
-| system.hw.sensor.color.input | input | Cel |
82
-| system.hw.sensor.voltage.input | input | V |
83
-| system.hw.sensor.resistance.input | input | Ohms |
84
-| system.hw.sensor.capacitance.input | input | F |
85
-| system.hw.sensor.inductance.input | input | H |
86
-| system.hw.sensor.pressure.input | input | Pa |
87
-| system.hw.sensor.latitude.input | input | Degrees |
88
-| system.hw.sensor.longitude.input | input | Degrees |
89
-| system.hw.sensor.force.input | input | N |
90
-| system.hw.sensor.gauge_pressure.input | input | Pa |
91
-| system.hw.sensor.human_presence.input | input | presence |
92
-| system.hw.sensor.human_proximity.input | input | m |
93
-| system.hw.sensor.distance.input | inputX, inputY, inputZ | m |
94
-| system.hw.sensor.acceleration.input | inputX, inputY, inputZ | g |
95
-| system.hw.sensor.state.input | ready, not_available, no_data, initializing, access_denied, error | status |
96
-| system.hw.sensor.custom | inputN | nd |
97
-
98
-
99
-
100
-## Alerts
101
-
102
-There are no alerts configured by default for this integration.
103
-
104
-
52
## Setup
53
54
@@ -161,3 +108,56 @@ You can add custom sensor information by creating a dedicated sensor section.
108
109
```
110
111
+
112
+## Alerts
113
+
114
+There are no alerts configured by default for this integration.
115
+
116
+
117
+## Metrics
118
+
119
+Metrics grouped by *scope*.
120
+
121
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
122
+
123
+
124
+
125
+### Per Sensor
126
+
127
+These metrics refer to Sensors.
128
+
129
+Labels:
130
+
131
+| Label | Description |
132
+|:-----------|:----------------|
133
+| name | Sensor friendly name. |
134
+| manufacturer | The sensor manufacturer. |
135
+| model | The sensor model. |
136
+
137
+Metrics:
138
+
139
+| Metric | Dimensions | Unit |
140
+|:------|:----------|:----|
141
+| system.hw.sensor.temperature.input | input | Cel |
142
+| system.hw.sensor.power.input | input | W |
143
+| system.hw.sensor.current.input | input | A |
144
+| system.hw.sensor.humidity.input | input | % |
145
+| system.hw.sensor.lux.input | input | lx |
146
+| system.hw.sensor.color.input | input | Cel |
147
+| system.hw.sensor.voltage.input | input | V |
148
+| system.hw.sensor.resistance.input | input | Ohms |
149
+| system.hw.sensor.capacitance.input | input | F |
150
+| system.hw.sensor.inductance.input | input | H |
151
+| system.hw.sensor.pressure.input | input | Pa |
152
+| system.hw.sensor.latitude.input | input | Degrees |
153
+| system.hw.sensor.longitude.input | input | Degrees |
154
+| system.hw.sensor.force.input | input | N |
155
+| system.hw.sensor.gauge_pressure.input | input | Pa |
156
+| system.hw.sensor.human_presence.input | input | presence |
157
+| system.hw.sensor.human_proximity.input | input | m |
158
+| system.hw.sensor.distance.input | inputX, inputY, inputZ | m |
159
+| system.hw.sensor.acceleration.input | inputX, inputY, inputZ | g |
160
+| system.hw.sensor.state.input | ready, not_available, no_data, initializing, access_denied, error | status |
161
+| system.hw.sensor.custom | inputN | nd |
162
+
163
+
src/collectors/windows.plugin/integrations/system_statistics.md
+30
-30
@@ -49,36 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per System
61
-
62
-These metrics refer to the entire system.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| system.processes | running | processes |
71
-| system.threads | threads | threads |
72
-| system.ctxt | switches | context switches/s |
73
-| system.processor_queue_length | threads | threads |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
52
## Setup
53
54
@@ -128,3 +98,33 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per System
116
+
117
+These metrics refer to the entire system.
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| system.processes | running | processes |
126
+| system.threads | threads | threads |
127
+| system.ctxt | switches | context switches/s |
128
+| system.processor_queue_length | threads | threads |
129
+
130
+
src/collectors/windows.plugin/integrations/system_thermal_zone.md
+27
-27
@@ -49,33 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Thermal zone
61
-
62
-These metrics refer to a Thermal zone
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| system.thermalzone_temperature | temperature | celsius |
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
52
## Setup
53
54
@@ -125,3 +98,30 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per Thermal zone
116
+
117
+These metrics refer to a Thermal zone
118
+
119
+This scope has no labels.
120
+
121
+Metrics:
122
+
123
+| Metric | Dimensions | Unit |
124
+|:------|:----------|:----|
125
+| system.thermalzone_temperature | temperature | celsius |
126
+
127
+
src/collectors/windows.plugin/integrations/windows_services.md
+31
-31
@@ -49,37 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Windows Service
61
-
62
-These metrics refer to Windows Services.
63
-
64
-Labels:
65
-
66
-| Label | Description |
67
-|:-----------|:----------------|
68
-| service | The service name |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| windows.service_state | running, stopped, start_pending, stop_pending, continue_pending, pause_pending, paused, unknown | state |
75
-
76
-
77
-
78
-## Alerts
79
-
80
-There are no alerts configured by default for this integration.
81
-
82
-
52
## Setup
53
54
@@ -129,3 +98,34 @@ sudo ./edit-config netdata.conf
98
There are no configuration examples.
99
100
101
+
102
+## Alerts
103
+
104
+There are no alerts configured by default for this integration.
105
+
106
+
107
+## Metrics
108
+
109
+Metrics grouped by *scope*.
110
+
111
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
112
+
113
+
114
+
115
+### Per Windows Service
116
+
117
+These metrics refer to Windows Services.
118
+
119
+Labels:
120
+
121
+| Label | Description |
122
+|:-----------|:----------------|
123
+| service | The service name |
124
+
125
+Metrics:
126
+
127
+| Metric | Dimensions | Unit |
128
+|:------|:----------|:----|
129
+| windows.service_state | running, stopped, start_pending, stop_pending, continue_pending, pause_pending, paused, unknown | state |
130
+
131
+
src/collectors/xenstat.plugin/integrations/xen_xcp-ng.md
+67
-67
@@ -44,6 +44,73 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
+## Setup
48
+
49
+
50
+### Prerequisites
51
+
52
+#### Libraries
53
+
54
+1. Install `xen-dom0-libs-devel` and `yajl-devel` using the package manager of your system.
55
+
56
+ Note: On Cent-OS systems you will need `centos-release-xen` repository and the required package for xen is `xen-devel`
57
+
58
+2. Re-install Netdata from source. The installer will detect that the required libraries are now available and will also build xenstat.plugin.
59
+
60
+
61
+
62
+### Configuration
63
+
64
+#### Options
65
+
66
+
67
+
68
+<details open><summary>Config options</summary>
69
+
70
+
71
+
72
+| Option | Description | Default | Required |
73
+|:-----|:------------|:--------|:---------:|
74
+| update every | Data collection frequency. | 1 | no |
75
+
76
+
77
+</details>
78
+
79
+
80
+
81
+#### via File
82
+
83
+The configuration file name for this integration is `netdata.conf`.
84
+Configuration for this specific integration is located in the `[plugin:xenstat]` section within that file.
85
+
86
+The file format is a modified INI syntax. The general structure is:
87
+
88
+```ini
89
+[section1]
90
+ option1 = some value
91
+ option2 = some other value
92
+
93
+[section2]
94
+ option3 = some third value
95
+```
96
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
97
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
98
+
99
+```bash
100
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
101
+sudo ./edit-config netdata.conf
102
+```
103
+
104
+##### Examples
105
+There are no configuration examples.
106
+
107
+
108
+
109
+## Alerts
110
+
111
+There are no alerts configured by default for this integration.
112
+
113
+
114
## Metrics
115
116
Metrics grouped by *scope*.
@@ -112,70 +179,3 @@ Metrics:
179
| xendomain.drops_network | received, sent | drops/s |
180
181
115
-
116
-## Alerts
117
-
118
-There are no alerts configured by default for this integration.
119
-
120
-
121
-## Setup
122
-
123
-
124
-### Prerequisites
125
-
126
-#### Libraries
127
-
128
-1. Install `xen-dom0-libs-devel` and `yajl-devel` using the package manager of your system.
129
-
130
- Note: On Cent-OS systems you will need `centos-release-xen` repository and the required package for xen is `xen-devel`
131
-
132
-2. Re-install Netdata from source. The installer will detect that the required libraries are now available and will also build xenstat.plugin.
133
-
134
-
135
-
136
-### Configuration
137
-
138
-#### Options
139
-
140
-
141
-
142
-<details open><summary>Config options</summary>
143
-
144
-
145
-
146
-| Option | Description | Default | Required |
147
-|:-----|:------------|:--------|:---------:|
148
-| update every | Data collection frequency. | 1 | no |
149
-
150
-
151
-</details>
152
-
153
-
154
-
155
-#### via File
156
-
157
-The configuration file name for this integration is `netdata.conf`.
158
-Configuration for this specific integration is located in the `[plugin:xenstat]` section within that file.
159
-
160
-The file format is a modified INI syntax. The general structure is:
161
-
162
-```ini
163
-[section1]
164
- option1 = some value
165
- option2 = some other value
166
-
167
-[section2]
168
- option3 = some third value
169
-```
170
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
171
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
172
-
173
-```bash
174
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
175
-sudo ./edit-config netdata.conf
176
-```
177
-
178
-##### Examples
179
-There are no configuration examples.
180
-
181
-
src/crates/netdata-otel/otel-plugin/integrations/opentelemetry.md
+12
-12
@@ -74,18 +74,6 @@ The default configuration for this integration does not impose any limits on dat
74
75
The default configuration for this integration is not expected to impose a significant performance impact on the system.
76
77
-## Metrics
78
-
79
-Metrics are dynamically created based on the OpenTelemetry data received.
80
-The specific metrics depend on the OTLP sources sending data to the plugin.
81
-
82
-
83
-
84
-## Alerts
85
-
86
-There are no alerts configured by default for this integration.
87
-
88
-
77
## Setup
78
79
@@ -266,3 +254,15 @@ logs:
254
</details>
255
256
257
+
258
+## Alerts
259
+
260
+There are no alerts configured by default for this integration.
261
+
262
+
263
+## Metrics
264
+
265
+Metrics are dynamically created based on the OpenTelemetry data received.
266
+The specific metrics depend on the OTLP sources sending data to the plugin.
267
+
268
+
src/go/plugin/go.d/collector/activemq/integrations/activemq.md
+29
-29
@@ -53,35 +53,6 @@ The default configuration for this integration does not impose any limits on dat
53
54
The default configuration for this integration is not expected to impose a significant performance impact on the system.
55
56
-## Metrics
57
-
58
-Metrics grouped by *scope*.
59
-
60
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
61
-
62
-
63
-
64
-### Per ActiveMQ instance
65
-
66
-These metrics refer to the entire monitored application.
67
-
68
-This scope has no labels.
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| activemq.messages | enqueued, dequeued | messages/s |
75
-| activemq.unprocessed_messages | unprocessed | messages |
76
-| activemq.consumers | consumers | consumers |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-There are no alerts configured by default for this integration.
83
-
84
-
56
## Setup
57
58
@@ -254,6 +225,35 @@ jobs:
225
226
227
228
+## Alerts
229
+
230
+There are no alerts configured by default for this integration.
231
+
232
+
233
+## Metrics
234
+
235
+Metrics grouped by *scope*.
236
+
237
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
238
+
239
+
240
+
241
+### Per ActiveMQ instance
242
+
243
+These metrics refer to the entire monitored application.
244
+
245
+This scope has no labels.
246
+
247
+Metrics:
248
+
249
+| Metric | Dimensions | Unit |
250
+|:------|:----------|:----|
251
+| activemq.messages | enqueued, dequeued | messages/s |
252
+| activemq.unprocessed_messages | unprocessed | messages |
253
+| activemq.consumers | consumers | consumers |
254
+
255
+
256
+
257
## Troubleshooting
258
259
### Debug Mode
src/go/plugin/go.d/collector/adaptecraid/integrations/adaptec_raid.md
+60
-60
@@ -55,66 +55,6 @@ The default configuration for this integration does not impose any limits on dat
55
56
The default configuration for this integration is not expected to impose a significant performance impact on the system.
57
58
-## Metrics
59
-
60
-Metrics grouped by *scope*.
61
-
62
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
-
64
-
65
-
66
-### Per logical device
67
-
68
-These metrics refer to the Logical Device (LD).
69
-
70
-Labels:
71
-
72
-| Label | Description |
73
-|:-----------|:----------------|
74
-| ld_number | Logical device index number |
75
-| ld_name | Logical device name |
76
-| raid_level | RAID level |
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| adaptecraid.logical_device_status | ok, critical | status |
83
-
84
-### Per physical device
85
-
86
-These metrics refer to the Physical Device (PD).
87
-
88
-Labels:
89
-
90
-| Label | Description |
91
-|:-----------|:----------------|
92
-| pd_number | Physical device index number |
93
-| location | Physical device location (e.g. Connector 0, Device 1) |
94
-| vendor | Physical device vendor |
95
-| model | Physical device model |
96
-
97
-Metrics:
98
-
99
-| Metric | Dimensions | Unit |
100
-|:------|:----------|:----|
101
-| adaptecraid.physical_device_state | ok, critical | status |
102
-| adaptecraid.physical_device_smart_warnings | smart | warnings |
103
-| adaptecraid.physical_device_temperature | temperature | Celsius |
104
-
105
-
106
-
107
-## Alerts
108
-
109
-
110
-The following alerts are available:
111
-
112
-| Alert name | On metric | Description |
113
-|:------------|:----------|:------------|
114
-| [ adaptec_raid_ld_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/adaptec_raid.conf) | adaptecraid.logical_device_status | Adaptec RAID logical device (number ${label:ld_number} name ${label:ld_name}) health status is critical |
115
-| [ adaptec_raid_pd_health_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/adaptec_raid.conf) | adaptecraid.physical_device_state | Adaptec RAID physical device (number ${label:pd_number} location ${label:location}) health state is critical |
116
-
117
-
58
## Setup
59
60
@@ -209,6 +149,66 @@ jobs:
149
150
151
152
+## Alerts
153
+
154
+
155
+The following alerts are available:
156
+
157
+| Alert name | On metric | Description |
158
+|:------------|:----------|:------------|
159
+| [ adaptec_raid_ld_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/adaptec_raid.conf) | adaptecraid.logical_device_status | Adaptec RAID logical device (number ${label:ld_number} name ${label:ld_name}) health status is critical |
160
+| [ adaptec_raid_pd_health_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/adaptec_raid.conf) | adaptecraid.physical_device_state | Adaptec RAID physical device (number ${label:pd_number} location ${label:location}) health state is critical |
161
+
162
+
163
+## Metrics
164
+
165
+Metrics grouped by *scope*.
166
+
167
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
168
+
169
+
170
+
171
+### Per logical device
172
+
173
+These metrics refer to the Logical Device (LD).
174
+
175
+Labels:
176
+
177
+| Label | Description |
178
+|:-----------|:----------------|
179
+| ld_number | Logical device index number |
180
+| ld_name | Logical device name |
181
+| raid_level | RAID level |
182
+
183
+Metrics:
184
+
185
+| Metric | Dimensions | Unit |
186
+|:------|:----------|:----|
187
+| adaptecraid.logical_device_status | ok, critical | status |
188
+
189
+### Per physical device
190
+
191
+These metrics refer to the Physical Device (PD).
192
+
193
+Labels:
194
+
195
+| Label | Description |
196
+|:-----------|:----------------|
197
+| pd_number | Physical device index number |
198
+| location | Physical device location (e.g. Connector 0, Device 1) |
199
+| vendor | Physical device vendor |
200
+| model | Physical device model |
201
+
202
+Metrics:
203
+
204
+| Metric | Dimensions | Unit |
205
+|:------|:----------|:----|
206
+| adaptecraid.physical_device_state | ok, critical | status |
207
+| adaptecraid.physical_device_smart_warnings | smart | warnings |
208
+| adaptecraid.physical_device_temperature | temperature | Celsius |
209
+
210
+
211
+
212
## Troubleshooting
213
214
### Debug Mode
src/go/plugin/go.d/collector/ap/integrations/access_points.md
+37
-37
@@ -48,43 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per wireless device
60
-
61
-These metrics refer to the entire monitored application.
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| device | Wireless interface name |
68
-| ssid | SSID |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| ap.clients | clients | clients |
75
-| ap.net | received, sent | kilobits/s |
76
-| ap.packets | received, sent | packets/s |
77
-| ap.issues | retries, failures | issues/s |
78
-| ap.signal | average signal | dBm |
79
-| ap.bitrate | receive, transmit | Mbps |
80
-
81
-
82
-
83
-## Alerts
84
-
85
-There are no alerts configured by default for this integration.
86
-
87
-
51
## Setup
52
53
@@ -179,6 +142,43 @@ jobs:
142
```
143
144
145
+## Alerts
146
+
147
+There are no alerts configured by default for this integration.
148
+
149
+
150
+## Metrics
151
+
152
+Metrics grouped by *scope*.
153
+
154
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
155
+
156
+
157
+
158
+### Per wireless device
159
+
160
+These metrics refer to the entire monitored application.
161
+
162
+Labels:
163
+
164
+| Label | Description |
165
+|:-----------|:----------------|
166
+| device | Wireless interface name |
167
+| ssid | SSID |
168
+
169
+Metrics:
170
+
171
+| Metric | Dimensions | Unit |
172
+|:------|:----------|:----|
173
+| ap.clients | clients | clients |
174
+| ap.net | received, sent | kilobits/s |
175
+| ap.packets | received, sent | packets/s |
176
+| ap.issues | retries, failures | issues/s |
177
+| ap.signal | average signal | dBm |
178
+| ap.bitrate | receive, transmit | Mbps |
179
+
180
+
181
+
182
## Troubleshooting
183
184
### Debug Mode
src/go/plugin/go.d/collector/apache/integrations/apache.md
+37
-37
@@ -58,43 +58,6 @@ The default configuration for this integration does not impose any limits on dat
58
59
The default configuration for this integration is not expected to impose a significant performance impact on the system.
60
61
-## Metrics
62
-
63
-Metrics grouped by *scope*.
64
-
65
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
66
-
67
-All metrics available only if [ExtendedStatus](https://httpd.apache.org/docs/2.4/mod/core.html#extendedstatus) is on.
68
-
69
-
70
-### Per Apache instance
71
-
72
-These metrics refer to the entire monitored application.
73
-
74
-This scope has no labels.
75
-
76
-Metrics:
77
-
78
-| Metric | Dimensions | Unit | Basic | Extended |
79
-|:------|:----------|:----|:---:|:---:|
80
-| apache.connections | connections | connections | • | • |
81
-| apache.conns_async | keepalive, closing, writing | connections | • | • |
82
-| apache.workers | idle, busy | workers | • | • |
83
-| apache.scoreboard | waiting, starting, reading, sending, keepalive, dns_lookup, closing, logging, finishing, idle_cleanup, open | connections | • | • |
84
-| apache.requests | requests | requests/s | | • |
85
-| apache.net | sent | kilobit/s | | • |
86
-| apache.reqpersec | requests | requests/s | | • |
87
-| apache.bytespersec | served | KiB/s | | • |
88
-| apache.bytesperreq | size | KiB | | • |
89
-| apache.uptime | uptime | seconds | | • |
90
-
91
-
92
-
93
-## Alerts
94
-
95
-There are no alerts configured by default for this integration.
96
-
97
-
61
## Setup
62
63
@@ -259,6 +222,43 @@ jobs:
222
223
224
225
+## Alerts
226
+
227
+There are no alerts configured by default for this integration.
228
+
229
+
230
+## Metrics
231
+
232
+Metrics grouped by *scope*.
233
+
234
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
235
+
236
+All metrics available only if [ExtendedStatus](https://httpd.apache.org/docs/2.4/mod/core.html#extendedstatus) is on.
237
+
238
+
239
+### Per Apache instance
240
+
241
+These metrics refer to the entire monitored application.
242
+
243
+This scope has no labels.
244
+
245
+Metrics:
246
+
247
+| Metric | Dimensions | Unit | Basic | Extended |
248
+|:------|:----------|:----|:---:|:---:|
249
+| apache.connections | connections | connections | • | • |
250
+| apache.conns_async | keepalive, closing, writing | connections | • | • |
251
+| apache.workers | idle, busy | workers | • | • |
252
+| apache.scoreboard | waiting, starting, reading, sending, keepalive, dns_lookup, closing, logging, finishing, idle_cleanup, open | connections | • | • |
253
+| apache.requests | requests | requests/s | | • |
254
+| apache.net | sent | kilobit/s | | • |
255
+| apache.reqpersec | requests | requests/s | | • |
256
+| apache.bytespersec | served | KiB/s | | • |
257
+| apache.bytesperreq | size | KiB | | • |
258
+| apache.uptime | uptime | seconds | | • |
259
+
260
+
261
+
262
## Troubleshooting
263
264
### Debug Mode
src/go/plugin/go.d/collector/apache/integrations/httpd.md
+37
-37
@@ -58,43 +58,6 @@ The default configuration for this integration does not impose any limits on dat
58
59
The default configuration for this integration is not expected to impose a significant performance impact on the system.
60
61
-## Metrics
62
-
63
-Metrics grouped by *scope*.
64
-
65
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
66
-
67
-All metrics available only if [ExtendedStatus](https://httpd.apache.org/docs/2.4/mod/core.html#extendedstatus) is on.
68
-
69
-
70
-### Per Apache instance
71
-
72
-These metrics refer to the entire monitored application.
73
-
74
-This scope has no labels.
75
-
76
-Metrics:
77
-
78
-| Metric | Dimensions | Unit | Basic | Extended |
79
-|:------|:----------|:----|:---:|:---:|
80
-| apache.connections | connections | connections | • | • |
81
-| apache.conns_async | keepalive, closing, writing | connections | • | • |
82
-| apache.workers | idle, busy | workers | • | • |
83
-| apache.scoreboard | waiting, starting, reading, sending, keepalive, dns_lookup, closing, logging, finishing, idle_cleanup, open | connections | • | • |
84
-| apache.requests | requests | requests/s | | • |
85
-| apache.net | sent | kilobit/s | | • |
86
-| apache.reqpersec | requests | requests/s | | • |
87
-| apache.bytespersec | served | KiB/s | | • |
88
-| apache.bytesperreq | size | KiB | | • |
89
-| apache.uptime | uptime | seconds | | • |
90
-
91
-
92
-
93
-## Alerts
94
-
95
-There are no alerts configured by default for this integration.
96
-
97
-
61
## Setup
62
63
@@ -259,6 +222,43 @@ jobs:
222
223
224
225
+## Alerts
226
+
227
+There are no alerts configured by default for this integration.
228
+
229
+
230
+## Metrics
231
+
232
+Metrics grouped by *scope*.
233
+
234
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
235
+
236
+All metrics available only if [ExtendedStatus](https://httpd.apache.org/docs/2.4/mod/core.html#extendedstatus) is on.
237
+
238
+
239
+### Per Apache instance
240
+
241
+These metrics refer to the entire monitored application.
242
+
243
+This scope has no labels.
244
+
245
+Metrics:
246
+
247
+| Metric | Dimensions | Unit | Basic | Extended |
248
+|:------|:----------|:----|:---:|:---:|
249
+| apache.connections | connections | connections | • | • |
250
+| apache.conns_async | keepalive, closing, writing | connections | • | • |
251
+| apache.workers | idle, busy | workers | • | • |
252
+| apache.scoreboard | waiting, starting, reading, sending, keepalive, dns_lookup, closing, logging, finishing, idle_cleanup, open | connections | • | • |
253
+| apache.requests | requests | requests/s | | • |
254
+| apache.net | sent | kilobit/s | | • |
255
+| apache.reqpersec | requests | requests/s | | • |
256
+| apache.bytespersec | served | KiB/s | | • |
257
+| apache.bytesperreq | size | KiB | | • |
258
+| apache.uptime | uptime | seconds | | • |
259
+
260
+
261
+
262
## Troubleshooting
263
264
### Debug Mode
src/go/plugin/go.d/collector/apcupsd/integrations/apc_ups.md
+52
-52
@@ -49,58 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per ups
61
-
62
-These metrics refer to the UPS unit.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| apcupsd.ups_status | TRIM, BOOST, CAL, ONLINE, ONBATT, OVERLOAD, LOWBATT, REPLACEBATT, NOBATT, SLAVE, SLAVEDOWN, COMMLOST, SHUTTING_DOWN | status |
71
-| apcupsd.ups_selftest | NO, NG, WN, IP, OK, BT, UNK | status |
72
-| apcupsd.ups_battery_charge | charge | percent |
73
-| apcupsd.ups_battery_time_remaining | timeleft | seconds |
74
-| apcupsd.ups_battery_time_since_replacement | since_replacement | seconds |
75
-| apcupsd.ups_battery_voltage | voltage, nominal_voltage | Volts |
76
-| apcupsd.ups_load_capacity_utilization | load | percent |
77
-| apcupsd.ups_load | load | Watts |
78
-| apcupsd.ups_temperature | temperature | Celsius |
79
-| apcupsd.ups_input_voltage | voltage, min_voltage, max_voltage | Volts |
80
-| apcupsd.ups_input_frequency | frequency | Hz |
81
-| apcupsd.ups_output_voltage | voltage | Volts |
82
-
83
-
84
-
85
-## Alerts
86
-
87
-
88
-The following alerts are available:
89
-
90
-| Alert name | On metric | Description |
91
-|:------------|:----------|:------------|
92
-| [ apcupsd_ups_load_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_load_capacity_utilization | APC UPS average load over the last 10 minutes |
93
-| [ apcupsd_ups_battery_charge ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_battery_charge | APC UPS average battery charge over the last minute |
94
-| [ apcupsd_last_collected_secs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS number of seconds since the last successful data collection |
95
-| [ apcupsd_ups_selftest_warning ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_selftest | APC UPS self-test failed due to insufficient battery capacity or due to overload |
96
-| [ apcupsd_ups_status_onbatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS has switched to battery power because the input power has failed |
97
-| [ apcupsd_ups_status_overload ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS is overloaded and cannot supply enough power to the load |
98
-| [ apcupsd_ups_status_lowbatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS battery is low and needs to be recharged |
99
-| [ apcupsd_ups_status_replacebatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS battery has reached the end of its lifespan and needs to be replaced |
100
-| [ apcupsd_ups_status_nobatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS has no battery |
101
-| [ apcupsd_ups_status_commlost ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS communication link is lost |
102
-
103
-
52
## Setup
53
54
@@ -218,6 +166,58 @@ jobs:
166
167
168
169
+## Alerts
170
+
171
+
172
+The following alerts are available:
173
+
174
+| Alert name | On metric | Description |
175
+|:------------|:----------|:------------|
176
+| [ apcupsd_ups_load_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_load_capacity_utilization | APC UPS average load over the last 10 minutes |
177
+| [ apcupsd_ups_battery_charge ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_battery_charge | APC UPS average battery charge over the last minute |
178
+| [ apcupsd_last_collected_secs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS number of seconds since the last successful data collection |
179
+| [ apcupsd_ups_selftest_warning ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_selftest | APC UPS self-test failed due to insufficient battery capacity or due to overload |
180
+| [ apcupsd_ups_status_onbatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS has switched to battery power because the input power has failed |
181
+| [ apcupsd_ups_status_overload ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS is overloaded and cannot supply enough power to the load |
182
+| [ apcupsd_ups_status_lowbatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS battery is low and needs to be recharged |
183
+| [ apcupsd_ups_status_replacebatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS battery has reached the end of its lifespan and needs to be replaced |
184
+| [ apcupsd_ups_status_nobatt ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS has no battery |
185
+| [ apcupsd_ups_status_commlost ](https://github.com/netdata/netdata/blob/master/src/health/health.d/apcupsd.conf) | apcupsd.ups_status | APC UPS communication link is lost |
186
+
187
+
188
+## Metrics
189
+
190
+Metrics grouped by *scope*.
191
+
192
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
193
+
194
+
195
+
196
+### Per ups
197
+
198
+These metrics refer to the UPS unit.
199
+
200
+This scope has no labels.
201
+
202
+Metrics:
203
+
204
+| Metric | Dimensions | Unit |
205
+|:------|:----------|:----|
206
+| apcupsd.ups_status | TRIM, BOOST, CAL, ONLINE, ONBATT, OVERLOAD, LOWBATT, REPLACEBATT, NOBATT, SLAVE, SLAVEDOWN, COMMLOST, SHUTTING_DOWN | status |
207
+| apcupsd.ups_selftest | NO, NG, WN, IP, OK, BT, UNK | status |
208
+| apcupsd.ups_battery_charge | charge | percent |
209
+| apcupsd.ups_battery_time_remaining | timeleft | seconds |
210
+| apcupsd.ups_battery_time_since_replacement | since_replacement | seconds |
211
+| apcupsd.ups_battery_voltage | voltage, nominal_voltage | Volts |
212
+| apcupsd.ups_load_capacity_utilization | load | percent |
213
+| apcupsd.ups_load | load | Watts |
214
+| apcupsd.ups_temperature | temperature | Celsius |
215
+| apcupsd.ups_input_voltage | voltage, min_voltage, max_voltage | Volts |
216
+| apcupsd.ups_input_frequency | frequency | Hz |
217
+| apcupsd.ups_output_voltage | voltage | Volts |
218
+
219
+
220
+
221
## Troubleshooting
222
223
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_api_management.md
+60
-60
@@ -57,66 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.api_management.capacity | capacity | percentage |
88
-| azure_monitor.api_management.gateway_cpu | cpu | percentage |
89
-| azure_monitor.api_management.gateway_memory | memory | percentage |
90
-| azure_monitor.api_management.requests | requests | requests/s |
91
-| azure_monitor.api_management.request_duration | overall, backend | milliseconds |
92
-| azure_monitor.api_management.eventhub_events | total, successful, failed, dropped, rejected, throttled, timed_out | events/s |
93
-| azure_monitor.api_management.eventhub_bytes | sent | bytes/s |
94
-| azure_monitor.api_management.websocket_connections | connection_attempts | attempts/s |
95
-| azure_monitor.api_management.websocket_messages | messages | messages/s |
96
-| azure_monitor.api_management.network_connectivity | connectivity | status |
97
-
98
-
99
-
100
-## Alerts
101
-
102
-
103
-The following alerts are available:
104
-
105
-| Alert name | On metric | Description |
106
-|:------------|:----------|:------------|
107
-| [ am_api_management_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.capacity | APIM capacity on ${label:resource_name} |
108
-| [ am_api_management_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.gateway_cpu | APIM gateway CPU on ${label:resource_name} |
109
-| [ am_api_management_gateway_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.gateway_memory | APIM gateway memory on ${label:resource_name} |
110
-| [ am_api_management_request_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.request_duration | APIM request duration on ${label:resource_name} |
111
-| [ am_api_management_backend_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.request_duration | APIM backend duration on ${label:resource_name} |
112
-| [ am_api_management_network_connectivity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.network_connectivity | APIM network connectivity on ${label:resource_name} |
113
-| [ am_api_management_eventhub_failed_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub failed events on ${label:resource_name} |
114
-| [ am_api_management_eventhub_dropped_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub dropped events on ${label:resource_name} |
115
-| [ am_api_management_eventhub_rejected_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub rejected events on ${label:resource_name} |
116
-| [ am_api_management_eventhub_throttled_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub throttled events on ${label:resource_name} |
117
-| [ am_api_management_eventhub_timedout_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub timed out events on ${label:resource_name} |
118
-
119
-
60
## Setup
61
62
@@ -338,6 +278,66 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_api_management_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.capacity | APIM capacity on ${label:resource_name} |
289
+| [ am_api_management_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.gateway_cpu | APIM gateway CPU on ${label:resource_name} |
290
+| [ am_api_management_gateway_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.gateway_memory | APIM gateway memory on ${label:resource_name} |
291
+| [ am_api_management_request_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.request_duration | APIM request duration on ${label:resource_name} |
292
+| [ am_api_management_backend_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.request_duration | APIM backend duration on ${label:resource_name} |
293
+| [ am_api_management_network_connectivity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.network_connectivity | APIM network connectivity on ${label:resource_name} |
294
+| [ am_api_management_eventhub_failed_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub failed events on ${label:resource_name} |
295
+| [ am_api_management_eventhub_dropped_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub dropped events on ${label:resource_name} |
296
+| [ am_api_management_eventhub_rejected_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub rejected events on ${label:resource_name} |
297
+| [ am_api_management_eventhub_throttled_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub throttled events on ${label:resource_name} |
298
+| [ am_api_management_eventhub_timedout_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_api_management.conf) | azure_monitor.api_management.eventhub_events | APIM EventHub timed out events on ${label:resource_name} |
299
+
300
+
301
+## Metrics
302
+
303
+Metrics grouped by *scope*.
304
+
305
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
306
+
307
+
308
+
309
+### Per resource
310
+
311
+These metrics refer to each monitored Azure resource.
312
+
313
+Labels:
314
+
315
+| Label | Description |
316
+|:-----------|:----------------|
317
+| resource_name | The Azure resource name. |
318
+| resource_group | The Azure resource group. |
319
+| region | The Azure region where the resource is deployed. |
320
+| resource_type | The Azure resource type identifier. |
321
+| profile | The Azure Monitor profile id. |
322
+| resource_uid | The unique Azure resource identifier. |
323
+
324
+Metrics:
325
+
326
+| Metric | Dimensions | Unit |
327
+|:------|:----------|:----|
328
+| azure_monitor.api_management.capacity | capacity | percentage |
329
+| azure_monitor.api_management.gateway_cpu | cpu | percentage |
330
+| azure_monitor.api_management.gateway_memory | memory | percentage |
331
+| azure_monitor.api_management.requests | requests | requests/s |
332
+| azure_monitor.api_management.request_duration | overall, backend | milliseconds |
333
+| azure_monitor.api_management.eventhub_events | total, successful, failed, dropped, rejected, throttled, timed_out | events/s |
334
+| azure_monitor.api_management.eventhub_bytes | sent | bytes/s |
335
+| azure_monitor.api_management.websocket_connections | connection_attempts | attempts/s |
336
+| azure_monitor.api_management.websocket_messages | messages | messages/s |
337
+| azure_monitor.api_management.network_connectivity | connectivity | status |
338
+
339
+
340
+
341
## Troubleshooting
342
343
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_app_service.md
+73
-73
@@ -57,79 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.app_service.requests | requests | requests/s |
88
-| azure_monitor.app_service.response_time | average | seconds |
89
-| azure_monitor.app_service.http_status | 2xx, 3xx, 4xx, 5xx | responses/s |
90
-| azure_monitor.app_service.http_error_detail | 101_websocket, 401_unauthorized, 403_forbidden, 404_not_found, 406_not_acceptable | responses/s |
91
-| azure_monitor.app_service.cpu | average | percentage |
92
-| azure_monitor.app_service.cpu_time | total | seconds |
93
-| azure_monitor.app_service.memory_usage | average_working_set, working_set, private | bytes |
94
-| azure_monitor.app_service.health | average | percentage |
95
-| azure_monitor.app_service.network_traffic | received, sent | bytes/s |
96
-| azure_monitor.app_service.connections | average | connections |
97
-| azure_monitor.app_service.io_throughput | read, write, other | bytes/s |
98
-| azure_monitor.app_service.io_operations | read, write, other | operations/s |
99
-| azure_monitor.app_service.threads | average | threads |
100
-| azure_monitor.app_service.handles | average | handles |
101
-| azure_monitor.app_service.gc_collections | gen0, gen1, gen2 | collections/s |
102
-| azure_monitor.app_service.function_executions | total | executions/s |
103
-| azure_monitor.app_service.function_execution_units | total | MB-milliseconds/s |
104
-| azure_monitor.app_service.always_ready_function_executions | total | executions/s |
105
-| azure_monitor.app_service.always_ready_function_execution_units | total | MB-milliseconds/s |
106
-| azure_monitor.app_service.always_ready_units | total | units |
107
-| azure_monitor.app_service.on_demand_function_executions | total | executions/s |
108
-| azure_monitor.app_service.on_demand_function_execution_units | total | MB-milliseconds/s |
109
-| azure_monitor.app_service.request_queue | queued | requests |
110
-| azure_monitor.app_service.instances | running | instances |
111
-| azure_monitor.app_service.assemblies | loaded | assemblies |
112
-| azure_monitor.app_service.app_domains | loaded, unloaded | domains |
113
-
114
-
115
-
116
-## Alerts
117
-
118
-
119
-The following alerts are available:
120
-
121
-| Alert name | On metric | Description |
122
-|:------------|:----------|:------------|
123
-| [ am_app_service_health_check ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.health | App Service health on ${label:resource_name} |
124
-| [ am_app_service_http_5xx_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_status | App Service 5xx errors on ${label:resource_name} |
125
-| [ am_app_service_response_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.response_time | App Service response time on ${label:resource_name} |
126
-| [ am_app_service_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.cpu | App Service CPU on ${label:resource_name} |
127
-| [ am_app_service_request_queue ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.request_queue | App Service request queue on ${label:resource_name} |
128
-| [ am_app_service_http_4xx_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_status | App Service 4xx errors on ${label:resource_name} |
129
-| [ am_app_service_http_403_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_error_detail | App Service 403 forbidden on ${label:resource_name} |
130
-| [ am_app_service_http_401_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_error_detail | App Service 401 unauthorized on ${label:resource_name} |
131
-
132
-
60
## Setup
61
62
@@ -351,6 +278,79 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_app_service_health_check ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.health | App Service health on ${label:resource_name} |
289
+| [ am_app_service_http_5xx_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_status | App Service 5xx errors on ${label:resource_name} |
290
+| [ am_app_service_response_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.response_time | App Service response time on ${label:resource_name} |
291
+| [ am_app_service_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.cpu | App Service CPU on ${label:resource_name} |
292
+| [ am_app_service_request_queue ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.request_queue | App Service request queue on ${label:resource_name} |
293
+| [ am_app_service_http_4xx_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_status | App Service 4xx errors on ${label:resource_name} |
294
+| [ am_app_service_http_403_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_error_detail | App Service 403 forbidden on ${label:resource_name} |
295
+| [ am_app_service_http_401_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_app_service.conf) | azure_monitor.app_service.http_error_detail | App Service 401 unauthorized on ${label:resource_name} |
296
+
297
+
298
+## Metrics
299
+
300
+Metrics grouped by *scope*.
301
+
302
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
303
+
304
+
305
+
306
+### Per resource
307
+
308
+These metrics refer to each monitored Azure resource.
309
+
310
+Labels:
311
+
312
+| Label | Description |
313
+|:-----------|:----------------|
314
+| resource_name | The Azure resource name. |
315
+| resource_group | The Azure resource group. |
316
+| region | The Azure region where the resource is deployed. |
317
+| resource_type | The Azure resource type identifier. |
318
+| profile | The Azure Monitor profile id. |
319
+| resource_uid | The unique Azure resource identifier. |
320
+
321
+Metrics:
322
+
323
+| Metric | Dimensions | Unit |
324
+|:------|:----------|:----|
325
+| azure_monitor.app_service.requests | requests | requests/s |
326
+| azure_monitor.app_service.response_time | average | seconds |
327
+| azure_monitor.app_service.http_status | 2xx, 3xx, 4xx, 5xx | responses/s |
328
+| azure_monitor.app_service.http_error_detail | 101_websocket, 401_unauthorized, 403_forbidden, 404_not_found, 406_not_acceptable | responses/s |
329
+| azure_monitor.app_service.cpu | average | percentage |
330
+| azure_monitor.app_service.cpu_time | total | seconds |
331
+| azure_monitor.app_service.memory_usage | average_working_set, working_set, private | bytes |
332
+| azure_monitor.app_service.health | average | percentage |
333
+| azure_monitor.app_service.network_traffic | received, sent | bytes/s |
334
+| azure_monitor.app_service.connections | average | connections |
335
+| azure_monitor.app_service.io_throughput | read, write, other | bytes/s |
336
+| azure_monitor.app_service.io_operations | read, write, other | operations/s |
337
+| azure_monitor.app_service.threads | average | threads |
338
+| azure_monitor.app_service.handles | average | handles |
339
+| azure_monitor.app_service.gc_collections | gen0, gen1, gen2 | collections/s |
340
+| azure_monitor.app_service.function_executions | total | executions/s |
341
+| azure_monitor.app_service.function_execution_units | total | MB-milliseconds/s |
342
+| azure_monitor.app_service.always_ready_function_executions | total | executions/s |
343
+| azure_monitor.app_service.always_ready_function_execution_units | total | MB-milliseconds/s |
344
+| azure_monitor.app_service.always_ready_units | total | units |
345
+| azure_monitor.app_service.on_demand_function_executions | total | executions/s |
346
+| azure_monitor.app_service.on_demand_function_execution_units | total | MB-milliseconds/s |
347
+| azure_monitor.app_service.request_queue | queued | requests |
348
+| azure_monitor.app_service.instances | running | instances |
349
+| azure_monitor.app_service.assemblies | loaded | assemblies |
350
+| azure_monitor.app_service.app_domains | loaded, unloaded | domains |
351
+
352
+
353
+
354
## Troubleshooting
355
356
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_application_gateway.md
+66
-66
@@ -57,72 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.application_gateway.throughput | average | bytes/s |
88
-| azure_monitor.application_gateway.traffic_volume | received, sent | bytes/s |
89
-| azure_monitor.application_gateway.requests | total, failed | requests/s |
90
-| azure_monitor.application_gateway.response_status | gateway, backend | responses/s |
91
-| azure_monitor.application_gateway.backend_health | healthy, unhealthy | hosts |
92
-| azure_monitor.application_gateway.backend_request_load | per_healthy_host | requests |
93
-| azure_monitor.application_gateway.backend_latency | connect, first_byte, last_byte | milliseconds |
94
-| azure_monitor.application_gateway.client_latency | total_time, client_rtt | milliseconds |
95
-| azure_monitor.application_gateway.current_connections | current | connections |
96
-| azure_monitor.application_gateway.new_connections | average | connections/s |
97
-| azure_monitor.application_gateway.websocket_connections | active | connections |
98
-| azure_monitor.application_gateway.websocket_close_codes | total | connections/s |
99
-| azure_monitor.application_gateway.capacity | capacity, compute, billed, fixed_billed | units |
100
-| azure_monitor.application_gateway.cpu | average | percentage |
101
-| azure_monitor.application_gateway.tls_connections | total | connections/s |
102
-| azure_monitor.application_gateway.waf_requests | total, blocked, matched | requests/s |
103
-| azure_monitor.application_gateway.waf_rule_matches | managed, custom, bot | matches/s |
104
-| azure_monitor.application_gateway.waf_challenges | captcha, js_challenge | requests/s |
105
-| azure_monitor.application_gateway.waf_penalty_box | size | IPs |
106
-| azure_monitor.application_gateway.waf_penalty_box_hits | total | hits/s |
107
-
108
-
109
-
110
-## Alerts
111
-
112
-
113
-The following alerts are available:
114
-
115
-| Alert name | On metric | Description |
116
-|:------------|:----------|:------------|
117
-| [ am_appgw_failed_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.requests | App Gateway failed requests on ${label:resource_name} |
118
-| [ am_appgw_unhealthy_hosts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.backend_health | App Gateway unhealthy backends on ${label:resource_name} |
119
-| [ am_appgw_backend_connect_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.backend_latency | App Gateway backend connect time on ${label:resource_name} |
120
-| [ am_appgw_backend_first_byte ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.backend_latency | App Gateway backend TTFB on ${label:resource_name} |
121
-| [ am_appgw_total_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.client_latency | App Gateway total request time on ${label:resource_name} |
122
-| [ am_appgw_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.cpu | App Gateway CPU utilization on ${label:resource_name} |
123
-| [ am_appgw_waf_blocked_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.waf_requests | App Gateway WAF block ratio on ${label:resource_name} |
124
-
125
-
60
## Setup
61
62
@@ -344,6 +278,72 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_appgw_failed_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.requests | App Gateway failed requests on ${label:resource_name} |
289
+| [ am_appgw_unhealthy_hosts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.backend_health | App Gateway unhealthy backends on ${label:resource_name} |
290
+| [ am_appgw_backend_connect_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.backend_latency | App Gateway backend connect time on ${label:resource_name} |
291
+| [ am_appgw_backend_first_byte ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.backend_latency | App Gateway backend TTFB on ${label:resource_name} |
292
+| [ am_appgw_total_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.client_latency | App Gateway total request time on ${label:resource_name} |
293
+| [ am_appgw_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.cpu | App Gateway CPU utilization on ${label:resource_name} |
294
+| [ am_appgw_waf_blocked_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_gateway.conf) | azure_monitor.application_gateway.waf_requests | App Gateway WAF block ratio on ${label:resource_name} |
295
+
296
+
297
+## Metrics
298
+
299
+Metrics grouped by *scope*.
300
+
301
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
302
+
303
+
304
+
305
+### Per resource
306
+
307
+These metrics refer to each monitored Azure resource.
308
+
309
+Labels:
310
+
311
+| Label | Description |
312
+|:-----------|:----------------|
313
+| resource_name | The Azure resource name. |
314
+| resource_group | The Azure resource group. |
315
+| region | The Azure region where the resource is deployed. |
316
+| resource_type | The Azure resource type identifier. |
317
+| profile | The Azure Monitor profile id. |
318
+| resource_uid | The unique Azure resource identifier. |
319
+
320
+Metrics:
321
+
322
+| Metric | Dimensions | Unit |
323
+|:------|:----------|:----|
324
+| azure_monitor.application_gateway.throughput | average | bytes/s |
325
+| azure_monitor.application_gateway.traffic_volume | received, sent | bytes/s |
326
+| azure_monitor.application_gateway.requests | total, failed | requests/s |
327
+| azure_monitor.application_gateway.response_status | gateway, backend | responses/s |
328
+| azure_monitor.application_gateway.backend_health | healthy, unhealthy | hosts |
329
+| azure_monitor.application_gateway.backend_request_load | per_healthy_host | requests |
330
+| azure_monitor.application_gateway.backend_latency | connect, first_byte, last_byte | milliseconds |
331
+| azure_monitor.application_gateway.client_latency | total_time, client_rtt | milliseconds |
332
+| azure_monitor.application_gateway.current_connections | current | connections |
333
+| azure_monitor.application_gateway.new_connections | average | connections/s |
334
+| azure_monitor.application_gateway.websocket_connections | active | connections |
335
+| azure_monitor.application_gateway.websocket_close_codes | total | connections/s |
336
+| azure_monitor.application_gateway.capacity | capacity, compute, billed, fixed_billed | units |
337
+| azure_monitor.application_gateway.cpu | average | percentage |
338
+| azure_monitor.application_gateway.tls_connections | total | connections/s |
339
+| azure_monitor.application_gateway.waf_requests | total, blocked, matched | requests/s |
340
+| azure_monitor.application_gateway.waf_rule_matches | managed, custom, bot | matches/s |
341
+| azure_monitor.application_gateway.waf_challenges | captcha, js_challenge | requests/s |
342
+| azure_monitor.application_gateway.waf_penalty_box | size | IPs |
343
+| azure_monitor.application_gateway.waf_penalty_box_hits | total | hits/s |
344
+
345
+
346
+
347
## Troubleshooting
348
349
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_application_insights.md
+74
-74
@@ -57,80 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.application_insights.availability_percentage | average | percentage |
88
-| azure_monitor.application_insights.availability_tests | tests | tests/s |
89
-| azure_monitor.application_insights.availability_duration | average | milliseconds |
90
-| azure_monitor.application_insights.server_requests | total, failed | requests/s |
91
-| azure_monitor.application_insights.server_request_rate | average | requests/s |
92
-| azure_monitor.application_insights.server_response_time | average | milliseconds |
93
-| azure_monitor.application_insights.dependency_calls | total, failed | calls/s |
94
-| azure_monitor.application_insights.dependency_duration | average | milliseconds |
95
-| azure_monitor.application_insights.exceptions | total, browser, server | exceptions/s |
96
-| azure_monitor.application_insights.browser_page_load_time | total | milliseconds |
97
-| azure_monitor.application_insights.browser_timing_breakdown | network, send, receive, processing | milliseconds |
98
-| azure_monitor.application_insights.cpu_utilization | process, processor | percentage |
99
-| azure_monitor.application_insights.memory | available, private | bytes |
100
-| azure_monitor.application_insights.process_io_rate | average | bytes/s |
101
-| azure_monitor.application_insights.exception_rate | average | exceptions/s |
102
-| azure_monitor.application_insights.http_request_execution_time | average | milliseconds |
103
-| azure_monitor.application_insights.http_request_queue | queued | requests |
104
-| azure_monitor.application_insights.http_request_rate | average | requests/s |
105
-| azure_monitor.application_insights.page_views | views | views/s |
106
-| azure_monitor.application_insights.page_view_load_time | average | milliseconds |
107
-| azure_monitor.application_insights.traces | traces | traces/s |
108
-
109
-
110
-
111
-## Alerts
112
-
113
-
114
-The following alerts are available:
115
-
116
-| Alert name | On metric | Description |
117
-|:------------|:----------|:------------|
118
-| [ am_appinsights_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.availability_percentage | App Insights availability on ${label:resource_name} |
119
-| [ am_appinsights_availability_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.availability_duration | App Insights availability test duration on ${label:resource_name} |
120
-| [ am_appinsights_failed_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.server_requests | App Insights failed requests on ${label:resource_name} |
121
-| [ am_appinsights_response_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.server_response_time | App Insights server response time on ${label:resource_name} |
122
-| [ am_appinsights_failed_dependencies ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.dependency_calls | App Insights failed dependencies on ${label:resource_name} |
123
-| [ am_appinsights_dependency_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.dependency_duration | App Insights dependency duration on ${label:resource_name} |
124
-| [ am_appinsights_exception_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.exception_rate | App Insights exception rate on ${label:resource_name} |
125
-| [ am_appinsights_server_exceptions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.exceptions | App Insights server exceptions on ${label:resource_name} |
126
-| [ am_appinsights_browser_page_load_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.browser_page_load_time | App Insights browser page load time on ${label:resource_name} |
127
-| [ am_appinsights_process_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.cpu_utilization | App Insights process CPU on ${label:resource_name} |
128
-| [ am_appinsights_processor_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.cpu_utilization | App Insights processor CPU on ${label:resource_name} |
129
-| [ am_appinsights_http_execution_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.http_request_execution_time | App Insights HTTP execution time on ${label:resource_name} |
130
-| [ am_appinsights_http_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.http_request_queue | App Insights HTTP request queue on ${label:resource_name} |
131
-| [ am_appinsights_page_view_load_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.page_view_load_time | App Insights page view load time on ${label:resource_name} |
132
-
133
-
60
## Setup
61
62
@@ -352,6 +278,80 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_appinsights_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.availability_percentage | App Insights availability on ${label:resource_name} |
289
+| [ am_appinsights_availability_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.availability_duration | App Insights availability test duration on ${label:resource_name} |
290
+| [ am_appinsights_failed_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.server_requests | App Insights failed requests on ${label:resource_name} |
291
+| [ am_appinsights_response_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.server_response_time | App Insights server response time on ${label:resource_name} |
292
+| [ am_appinsights_failed_dependencies ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.dependency_calls | App Insights failed dependencies on ${label:resource_name} |
293
+| [ am_appinsights_dependency_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.dependency_duration | App Insights dependency duration on ${label:resource_name} |
294
+| [ am_appinsights_exception_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.exception_rate | App Insights exception rate on ${label:resource_name} |
295
+| [ am_appinsights_server_exceptions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.exceptions | App Insights server exceptions on ${label:resource_name} |
296
+| [ am_appinsights_browser_page_load_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.browser_page_load_time | App Insights browser page load time on ${label:resource_name} |
297
+| [ am_appinsights_process_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.cpu_utilization | App Insights process CPU on ${label:resource_name} |
298
+| [ am_appinsights_processor_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.cpu_utilization | App Insights processor CPU on ${label:resource_name} |
299
+| [ am_appinsights_http_execution_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.http_request_execution_time | App Insights HTTP execution time on ${label:resource_name} |
300
+| [ am_appinsights_http_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.http_request_queue | App Insights HTTP request queue on ${label:resource_name} |
301
+| [ am_appinsights_page_view_load_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_application_insights.conf) | azure_monitor.application_insights.page_view_load_time | App Insights page view load time on ${label:resource_name} |
302
+
303
+
304
+## Metrics
305
+
306
+Metrics grouped by *scope*.
307
+
308
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
309
+
310
+
311
+
312
+### Per resource
313
+
314
+These metrics refer to each monitored Azure resource.
315
+
316
+Labels:
317
+
318
+| Label | Description |
319
+|:-----------|:----------------|
320
+| resource_name | The Azure resource name. |
321
+| resource_group | The Azure resource group. |
322
+| region | The Azure region where the resource is deployed. |
323
+| resource_type | The Azure resource type identifier. |
324
+| profile | The Azure Monitor profile id. |
325
+| resource_uid | The unique Azure resource identifier. |
326
+
327
+Metrics:
328
+
329
+| Metric | Dimensions | Unit |
330
+|:------|:----------|:----|
331
+| azure_monitor.application_insights.availability_percentage | average | percentage |
332
+| azure_monitor.application_insights.availability_tests | tests | tests/s |
333
+| azure_monitor.application_insights.availability_duration | average | milliseconds |
334
+| azure_monitor.application_insights.server_requests | total, failed | requests/s |
335
+| azure_monitor.application_insights.server_request_rate | average | requests/s |
336
+| azure_monitor.application_insights.server_response_time | average | milliseconds |
337
+| azure_monitor.application_insights.dependency_calls | total, failed | calls/s |
338
+| azure_monitor.application_insights.dependency_duration | average | milliseconds |
339
+| azure_monitor.application_insights.exceptions | total, browser, server | exceptions/s |
340
+| azure_monitor.application_insights.browser_page_load_time | total | milliseconds |
341
+| azure_monitor.application_insights.browser_timing_breakdown | network, send, receive, processing | milliseconds |
342
+| azure_monitor.application_insights.cpu_utilization | process, processor | percentage |
343
+| azure_monitor.application_insights.memory | available, private | bytes |
344
+| azure_monitor.application_insights.process_io_rate | average | bytes/s |
345
+| azure_monitor.application_insights.exception_rate | average | exceptions/s |
346
+| azure_monitor.application_insights.http_request_execution_time | average | milliseconds |
347
+| azure_monitor.application_insights.http_request_queue | queued | requests |
348
+| azure_monitor.application_insights.http_request_rate | average | requests/s |
349
+| azure_monitor.application_insights.page_views | views | views/s |
350
+| azure_monitor.application_insights.page_view_load_time | average | milliseconds |
351
+| azure_monitor.application_insights.traces | traces | traces/s |
352
+
353
+
354
+
355
## Troubleshooting
356
357
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_cache_for_redis.md
+82
-82
@@ -57,88 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.redis_cache.cache_hits | hits, misses | operations/s |
88
-| azure_monitor.redis_cache.throughput | read, write | bytes/s |
89
-| azure_monitor.redis_cache.server_load | maximum | percentage |
90
-| azure_monitor.redis_cache.cpu | maximum | percentage |
91
-| azure_monitor.redis_cache.memory_usage | used, rss | bytes |
92
-| azure_monitor.redis_cache.memory_utilization | maximum | percentage |
93
-| azure_monitor.redis_cache.clients | maximum | clients |
94
-| azure_monitor.redis_cache.operations | maximum | operations/s |
95
-| azure_monitor.redis_cache.commands | total | commands/s |
96
-| azure_monitor.redis_cache.command_types | get, set | commands/s |
97
-| azure_monitor.redis_cache.latency | average | microseconds |
98
-| azure_monitor.redis_cache.key_events | evicted, expired | keys/s |
99
-| azure_monitor.redis_cache.total_keys | maximum | keys |
100
-| azure_monitor.redis_cache.errors | maximum | errors |
101
-| azure_monitor.redis_cache.miss_rate | miss_rate | percentage |
102
-| azure_monitor.redis_cache.latency_p99 | p99 | microseconds |
103
-| azure_monitor.redis_cache.connection_rate | created, closed | connections/s |
104
-| azure_monitor.redis_cache.aad_clients | maximum | clients |
105
-| azure_monitor.redis_cache.instance_cache_hits | hits, misses | operations/s |
106
-| azure_monitor.redis_cache.instance_throughput | read, write | bytes/s |
107
-| azure_monitor.redis_cache.instance_server_load | server_load, cpu | percentage |
108
-| azure_monitor.redis_cache.instance_memory_usage | used, rss | bytes |
109
-| azure_monitor.redis_cache.instance_memory_utilization | maximum | percentage |
110
-| azure_monitor.redis_cache.instance_clients | maximum | clients |
111
-| azure_monitor.redis_cache.instance_operations | maximum | operations/s |
112
-| azure_monitor.redis_cache.instance_commands | total, get, set | commands/s |
113
-| azure_monitor.redis_cache.instance_total_keys | maximum | keys |
114
-| azure_monitor.redis_cache.instance_key_events | evicted, expired | keys/s |
115
-| azure_monitor.redis_cache.geo_replication_lag | average | seconds |
116
-| azure_monitor.redis_cache.geo_replication_sync_offset | average | bytes |
117
-| azure_monitor.redis_cache.geo_replication_sync_events | started, finished | events/s |
118
-| azure_monitor.redis_cache.geo_replication_health | average | status |
119
-
120
-
121
-
122
-## Alerts
123
-
124
-
125
-The following alerts are available:
126
-
127
-| Alert name | On metric | Description |
128
-|:------------|:----------|:------------|
129
-| [ am_redis_cache_server_load ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.server_load | Redis server load on ${label:resource_name} |
130
-| [ am_redis_cache_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.cpu | Redis CPU on ${label:resource_name} |
131
-| [ am_redis_cache_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.memory_utilization | Redis memory utilization on ${label:resource_name} |
132
-| [ am_redis_cache_miss_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.miss_rate | Redis cache miss rate on ${label:resource_name} |
133
-| [ am_redis_cache_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.errors | Redis errors on ${label:resource_name} |
134
-| [ am_redis_cache_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.latency | Redis average latency on ${label:resource_name} |
135
-| [ am_redis_cache_latency_p99 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.latency_p99 | Redis P99 latency on ${label:resource_name} |
136
-| [ am_redis_cache_evicted_keys ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.key_events | Redis key evictions on ${label:resource_name} |
137
-| [ am_redis_cache_geo_replication_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.geo_replication_health | Redis geo-replication health on ${label:resource_name} |
138
-| [ am_redis_cache_geo_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.geo_replication_lag | Redis geo-replication lag on ${label:resource_name} |
139
-| [ am_redis_cache_geo_replication_sync_offset ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.geo_replication_sync_offset | Redis geo-replication sync offset on ${label:resource_name} |
140
-
141
-
60
## Setup
61
62
@@ -360,6 +278,88 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_redis_cache_server_load ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.server_load | Redis server load on ${label:resource_name} |
289
+| [ am_redis_cache_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.cpu | Redis CPU on ${label:resource_name} |
290
+| [ am_redis_cache_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.memory_utilization | Redis memory utilization on ${label:resource_name} |
291
+| [ am_redis_cache_miss_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.miss_rate | Redis cache miss rate on ${label:resource_name} |
292
+| [ am_redis_cache_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.errors | Redis errors on ${label:resource_name} |
293
+| [ am_redis_cache_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.latency | Redis average latency on ${label:resource_name} |
294
+| [ am_redis_cache_latency_p99 ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.latency_p99 | Redis P99 latency on ${label:resource_name} |
295
+| [ am_redis_cache_evicted_keys ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.key_events | Redis key evictions on ${label:resource_name} |
296
+| [ am_redis_cache_geo_replication_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.geo_replication_health | Redis geo-replication health on ${label:resource_name} |
297
+| [ am_redis_cache_geo_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.geo_replication_lag | Redis geo-replication lag on ${label:resource_name} |
298
+| [ am_redis_cache_geo_replication_sync_offset ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_redis_cache.conf) | azure_monitor.redis_cache.geo_replication_sync_offset | Redis geo-replication sync offset on ${label:resource_name} |
299
+
300
+
301
+## Metrics
302
+
303
+Metrics grouped by *scope*.
304
+
305
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
306
+
307
+
308
+
309
+### Per resource
310
+
311
+These metrics refer to each monitored Azure resource.
312
+
313
+Labels:
314
+
315
+| Label | Description |
316
+|:-----------|:----------------|
317
+| resource_name | The Azure resource name. |
318
+| resource_group | The Azure resource group. |
319
+| region | The Azure region where the resource is deployed. |
320
+| resource_type | The Azure resource type identifier. |
321
+| profile | The Azure Monitor profile id. |
322
+| resource_uid | The unique Azure resource identifier. |
323
+
324
+Metrics:
325
+
326
+| Metric | Dimensions | Unit |
327
+|:------|:----------|:----|
328
+| azure_monitor.redis_cache.cache_hits | hits, misses | operations/s |
329
+| azure_monitor.redis_cache.throughput | read, write | bytes/s |
330
+| azure_monitor.redis_cache.server_load | maximum | percentage |
331
+| azure_monitor.redis_cache.cpu | maximum | percentage |
332
+| azure_monitor.redis_cache.memory_usage | used, rss | bytes |
333
+| azure_monitor.redis_cache.memory_utilization | maximum | percentage |
334
+| azure_monitor.redis_cache.clients | maximum | clients |
335
+| azure_monitor.redis_cache.operations | maximum | operations/s |
336
+| azure_monitor.redis_cache.commands | total | commands/s |
337
+| azure_monitor.redis_cache.command_types | get, set | commands/s |
338
+| azure_monitor.redis_cache.latency | average | microseconds |
339
+| azure_monitor.redis_cache.key_events | evicted, expired | keys/s |
340
+| azure_monitor.redis_cache.total_keys | maximum | keys |
341
+| azure_monitor.redis_cache.errors | maximum | errors |
342
+| azure_monitor.redis_cache.miss_rate | miss_rate | percentage |
343
+| azure_monitor.redis_cache.latency_p99 | p99 | microseconds |
344
+| azure_monitor.redis_cache.connection_rate | created, closed | connections/s |
345
+| azure_monitor.redis_cache.aad_clients | maximum | clients |
346
+| azure_monitor.redis_cache.instance_cache_hits | hits, misses | operations/s |
347
+| azure_monitor.redis_cache.instance_throughput | read, write | bytes/s |
348
+| azure_monitor.redis_cache.instance_server_load | server_load, cpu | percentage |
349
+| azure_monitor.redis_cache.instance_memory_usage | used, rss | bytes |
350
+| azure_monitor.redis_cache.instance_memory_utilization | maximum | percentage |
351
+| azure_monitor.redis_cache.instance_clients | maximum | clients |
352
+| azure_monitor.redis_cache.instance_operations | maximum | operations/s |
353
+| azure_monitor.redis_cache.instance_commands | total, get, set | commands/s |
354
+| azure_monitor.redis_cache.instance_total_keys | maximum | keys |
355
+| azure_monitor.redis_cache.instance_key_events | evicted, expired | keys/s |
356
+| azure_monitor.redis_cache.geo_replication_lag | average | seconds |
357
+| azure_monitor.redis_cache.geo_replication_sync_offset | average | bytes |
358
+| azure_monitor.redis_cache.geo_replication_sync_events | started, finished | events/s |
359
+| azure_monitor.redis_cache.geo_replication_health | average | status |
360
+
361
+
362
+
363
## Troubleshooting
364
365
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_cognitive_services.md
+129
-129
@@ -57,135 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.cognitive_services.availability | availability | percentage |
88
-| azure_monitor.cognitive_services.calls | total, successful, blocked, token | calls/s |
89
-| azure_monitor.cognitive_services.errors | total, client, server | errors/s |
90
-| azure_monitor.cognitive_services.latency | average | milliseconds |
91
-| azure_monitor.cognitive_services.data_transfer | in, out | bytes/s |
92
-| azure_monitor.cognitive_services.rate_limit | rate_limit | requests/s |
93
-| azure_monitor.cognitive_services.openai_availability | availability | percentage |
94
-| azure_monitor.cognitive_services.openai_requests | requests | requests/s |
95
-| azure_monitor.cognitive_services.openai_latency | time_to_response, time_to_first_token, time_between_tokens, time_to_last_byte | milliseconds |
96
-| azure_monitor.cognitive_services.openai_generation_speed | tokens_per_second | tokens/s |
97
-| azure_monitor.cognitive_services.openai_token_usage | total, prompt, generated, active | tokens/s |
98
-| azure_monitor.cognitive_services.openai_audio_tokens | prompt, completion | tokens/s |
99
-| azure_monitor.cognitive_services.openai_cache_match_rate | cache_match_rate | percentage |
100
-| azure_monitor.cognitive_services.openai_provisioned_utilization | utilization | percentage |
101
-| azure_monitor.cognitive_services.openai_finetuning | training_hours | hours/s |
102
-| azure_monitor.cognitive_services.openai_realtime_usage | seconds_used | seconds/s |
103
-| azure_monitor.cognitive_services.model_availability | availability | percentage |
104
-| azure_monitor.cognitive_services.model_requests | requests | requests/s |
105
-| azure_monitor.cognitive_services.model_latency | time_to_response, time_to_first_token, time_between_tokens, time_to_last_byte | milliseconds |
106
-| azure_monitor.cognitive_services.model_generation_speed | tokens_per_second | tokens/s |
107
-| azure_monitor.cognitive_services.model_token_usage | total, input, output | tokens/s |
108
-| azure_monitor.cognitive_services.model_audio_tokens | input, output | tokens/s |
109
-| azure_monitor.cognitive_services.model_cache_tokens | cache_read, cache_write_1h, cache_write_5m | tokens/s |
110
-| azure_monitor.cognitive_services.model_provisioned_utilization | utilization | percentage |
111
-| azure_monitor.cognitive_services.model_pages | total, annotated | pages/s |
112
-| azure_monitor.cognitive_services.model_generated_images | generated | images/s |
113
-| azure_monitor.cognitive_services.content_safety_requests | total, harmful, blocked | requests/s |
114
-| azure_monitor.cognitive_services.content_safety_abusive_users | abusive_users | users/s |
115
-| azure_monitor.cognitive_services.content_safety_system_events | events | events |
116
-| azure_monitor.cognitive_services.content_safety_moderation | text, image | requests/s |
117
-| azure_monitor.cognitive_services.job_duration | average | milliseconds |
118
-| azure_monitor.cognitive_services.personalizer_actions | occurrences | occurrences/s |
119
-| azure_monitor.cognitive_services.personalizer_actions_per_event | average | actions |
120
-| azure_monitor.cognitive_services.personalizer_feature_occurrences | action, context, slot | occurrences/s |
121
-| azure_monitor.cognitive_services.personalizer_feature_cardinality | action, context, slot | features |
122
-| azure_monitor.cognitive_services.personalizer_features_per_event | action, context, slot | features |
123
-| azure_monitor.cognitive_services.personalizer_namespaces_per_event | action, context, slot | namespaces |
124
-| azure_monitor.cognitive_services.personalizer_rewards | average, slot | reward |
125
-| azure_monitor.cognitive_services.personalizer_estimator_rewards | online, baseline, baseline_random | reward |
126
-| azure_monitor.cognitive_services.personalizer_estimator_slot_rewards | online, baseline, baseline_random | reward |
127
-| azure_monitor.cognitive_services.personalizer_slots | average | slots |
128
-| azure_monitor.cognitive_services.personalizer_slot_occurrences | occurrences | occurrences/s |
129
-| azure_monitor.cognitive_services.personalizer_event_counts | online, baseline_random, user_baseline | events/s |
130
-| azure_monitor.cognitive_services.personalizer_estimated_rewards | online, baseline_random, user_baseline | reward/s |
131
-| azure_monitor.cognitive_services.speech_transcription | realtime, batch, batch_whisper, fast, fast_whisper | seconds/s |
132
-| azure_monitor.cognitive_services.speech_translation | translated | seconds/s |
133
-| azure_monitor.cognitive_services.speech_synthesis | synthesized | characters/s |
134
-| azure_monitor.cognitive_services.speech_video_synthesis | synthesized | seconds/s |
135
-| azure_monitor.cognitive_services.speech_avatar | hosting, training | seconds/s |
136
-| azure_monitor.cognitive_services.speech_speaker_recognition | transactions | transactions/s |
137
-| azure_monitor.cognitive_services.speech_speaker_profiles | profiles | profiles/s |
138
-| azure_monitor.cognitive_services.speech_model_hosting | hosting | hours/s |
139
-| azure_monitor.cognitive_services.speech_voice_live_tokens | audio_input, audio_output, cached_audio_input, text_input, text_output, cached_text_input | tokens/s |
140
-| azure_monitor.cognitive_services.speech_voice_model | hosting | hours/s |
141
-| azure_monitor.cognitive_services.speech_voice_training | training | minutes/s |
142
-| azure_monitor.cognitive_services.translator_text | standard, custom, trained | characters/s |
143
-| azure_monitor.cognitive_services.translator_document | standard, custom | characters/s |
144
-| azure_monitor.cognitive_services.translator_document_sync | standard, custom | characters/s |
145
-| azure_monitor.cognitive_services.translator_pro_app | seconds | seconds/s |
146
-| azure_monitor.cognitive_services.vision_transactions | computer_vision, custom_vision | transactions/s |
147
-| azure_monitor.cognitive_services.vision_training | training_time | seconds/s |
148
-| azure_monitor.cognitive_services.vision_images_stored | stored | images/s |
149
-| azure_monitor.cognitive_services.face_transactions | transactions | transactions/s |
150
-| azure_monitor.cognitive_services.face_images_trained | trained | images/s |
151
-| azure_monitor.cognitive_services.faces_stored | stored | faces/s |
152
-| azure_monitor.cognitive_services.luis_requests | speech, text | requests/s |
153
-| azure_monitor.cognitive_services.text_processing | text, health_text, question_answering | records/s |
154
-| azure_monitor.cognitive_services.processed_characters | characters | characters/s |
155
-| azure_monitor.cognitive_services.processed_images | images | images/s |
156
-| azure_monitor.cognitive_services.processed_pages | pages | pages/s |
157
-| azure_monitor.cognitive_services.carnegie_inference | inferences | inferences/s |
158
-| azure_monitor.cognitive_services.personalizer_events | total, learned, non_activated | events/s |
159
-| azure_monitor.cognitive_services.personalizer_reward_tracking | matched, observed | rewards/s |
160
-
161
-
162
-
163
-## Alerts
164
-
165
-
166
-The following alerts are available:
167
-
168
-| Alert name | On metric | Description |
169
-|:------------|:----------|:------------|
170
-| [ am_cognitive_services_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.availability | Cognitive Services availability on ${label:resource_name} |
171
-| [ am_cognitive_services_server_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.errors | Cognitive Services server errors on ${label:resource_name} |
172
-| [ am_cognitive_services_client_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.errors | Cognitive Services client errors on ${label:resource_name} |
173
-| [ am_cognitive_services_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.latency | Cognitive Services latency on ${label:resource_name} |
174
-| [ am_cognitive_services_rate_limit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.rate_limit | Cognitive Services rate limiting on ${label:resource_name} |
175
-| [ am_cognitive_services_blocked_calls ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.calls | Cognitive Services blocked calls on ${label:resource_name} |
176
-| [ am_cognitive_services_openai_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_availability | Azure OpenAI availability on ${label:resource_name} |
177
-| [ am_cognitive_services_openai_time_to_response ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_latency | Azure OpenAI time to response on ${label:resource_name} |
178
-| [ am_cognitive_services_openai_time_to_first_token ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_latency | Azure OpenAI time to first token on ${label:resource_name} |
179
-| [ am_cognitive_services_openai_provisioned_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_provisioned_utilization | Azure OpenAI provisioned utilization on ${label:resource_name} |
180
-| [ am_cognitive_services_model_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_availability | Model availability on ${label:resource_name} |
181
-| [ am_cognitive_services_model_time_to_response ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_latency | Model time to response on ${label:resource_name} |
182
-| [ am_cognitive_services_model_time_to_first_token ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_latency | Model time to first token on ${label:resource_name} |
183
-| [ am_cognitive_services_model_provisioned_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_provisioned_utilization | Model provisioned utilization on ${label:resource_name} |
184
-| [ am_cognitive_services_harmful_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.content_safety_requests | Harmful content requests on ${label:resource_name} |
185
-| [ am_cognitive_services_blocked_content_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.content_safety_requests | Blocked content requests on ${label:resource_name} |
186
-| [ am_cognitive_services_abusive_users ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.content_safety_abusive_users | Abusive users detected on ${label:resource_name} |
187
-
188
-
60
## Setup
61
62
@@ -407,6 +278,135 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_cognitive_services_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.availability | Cognitive Services availability on ${label:resource_name} |
289
+| [ am_cognitive_services_server_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.errors | Cognitive Services server errors on ${label:resource_name} |
290
+| [ am_cognitive_services_client_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.errors | Cognitive Services client errors on ${label:resource_name} |
291
+| [ am_cognitive_services_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.latency | Cognitive Services latency on ${label:resource_name} |
292
+| [ am_cognitive_services_rate_limit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.rate_limit | Cognitive Services rate limiting on ${label:resource_name} |
293
+| [ am_cognitive_services_blocked_calls ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.calls | Cognitive Services blocked calls on ${label:resource_name} |
294
+| [ am_cognitive_services_openai_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_availability | Azure OpenAI availability on ${label:resource_name} |
295
+| [ am_cognitive_services_openai_time_to_response ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_latency | Azure OpenAI time to response on ${label:resource_name} |
296
+| [ am_cognitive_services_openai_time_to_first_token ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_latency | Azure OpenAI time to first token on ${label:resource_name} |
297
+| [ am_cognitive_services_openai_provisioned_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.openai_provisioned_utilization | Azure OpenAI provisioned utilization on ${label:resource_name} |
298
+| [ am_cognitive_services_model_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_availability | Model availability on ${label:resource_name} |
299
+| [ am_cognitive_services_model_time_to_response ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_latency | Model time to response on ${label:resource_name} |
300
+| [ am_cognitive_services_model_time_to_first_token ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_latency | Model time to first token on ${label:resource_name} |
301
+| [ am_cognitive_services_model_provisioned_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.model_provisioned_utilization | Model provisioned utilization on ${label:resource_name} |
302
+| [ am_cognitive_services_harmful_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.content_safety_requests | Harmful content requests on ${label:resource_name} |
303
+| [ am_cognitive_services_blocked_content_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.content_safety_requests | Blocked content requests on ${label:resource_name} |
304
+| [ am_cognitive_services_abusive_users ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cognitive_services.conf) | azure_monitor.cognitive_services.content_safety_abusive_users | Abusive users detected on ${label:resource_name} |
305
+
306
+
307
+## Metrics
308
+
309
+Metrics grouped by *scope*.
310
+
311
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
312
+
313
+
314
+
315
+### Per resource
316
+
317
+These metrics refer to each monitored Azure resource.
318
+
319
+Labels:
320
+
321
+| Label | Description |
322
+|:-----------|:----------------|
323
+| resource_name | The Azure resource name. |
324
+| resource_group | The Azure resource group. |
325
+| region | The Azure region where the resource is deployed. |
326
+| resource_type | The Azure resource type identifier. |
327
+| profile | The Azure Monitor profile id. |
328
+| resource_uid | The unique Azure resource identifier. |
329
+
330
+Metrics:
331
+
332
+| Metric | Dimensions | Unit |
333
+|:------|:----------|:----|
334
+| azure_monitor.cognitive_services.availability | availability | percentage |
335
+| azure_monitor.cognitive_services.calls | total, successful, blocked, token | calls/s |
336
+| azure_monitor.cognitive_services.errors | total, client, server | errors/s |
337
+| azure_monitor.cognitive_services.latency | average | milliseconds |
338
+| azure_monitor.cognitive_services.data_transfer | in, out | bytes/s |
339
+| azure_monitor.cognitive_services.rate_limit | rate_limit | requests/s |
340
+| azure_monitor.cognitive_services.openai_availability | availability | percentage |
341
+| azure_monitor.cognitive_services.openai_requests | requests | requests/s |
342
+| azure_monitor.cognitive_services.openai_latency | time_to_response, time_to_first_token, time_between_tokens, time_to_last_byte | milliseconds |
343
+| azure_monitor.cognitive_services.openai_generation_speed | tokens_per_second | tokens/s |
344
+| azure_monitor.cognitive_services.openai_token_usage | total, prompt, generated, active | tokens/s |
345
+| azure_monitor.cognitive_services.openai_audio_tokens | prompt, completion | tokens/s |
346
+| azure_monitor.cognitive_services.openai_cache_match_rate | cache_match_rate | percentage |
347
+| azure_monitor.cognitive_services.openai_provisioned_utilization | utilization | percentage |
348
+| azure_monitor.cognitive_services.openai_finetuning | training_hours | hours/s |
349
+| azure_monitor.cognitive_services.openai_realtime_usage | seconds_used | seconds/s |
350
+| azure_monitor.cognitive_services.model_availability | availability | percentage |
351
+| azure_monitor.cognitive_services.model_requests | requests | requests/s |
352
+| azure_monitor.cognitive_services.model_latency | time_to_response, time_to_first_token, time_between_tokens, time_to_last_byte | milliseconds |
353
+| azure_monitor.cognitive_services.model_generation_speed | tokens_per_second | tokens/s |
354
+| azure_monitor.cognitive_services.model_token_usage | total, input, output | tokens/s |
355
+| azure_monitor.cognitive_services.model_audio_tokens | input, output | tokens/s |
356
+| azure_monitor.cognitive_services.model_cache_tokens | cache_read, cache_write_1h, cache_write_5m | tokens/s |
357
+| azure_monitor.cognitive_services.model_provisioned_utilization | utilization | percentage |
358
+| azure_monitor.cognitive_services.model_pages | total, annotated | pages/s |
359
+| azure_monitor.cognitive_services.model_generated_images | generated | images/s |
360
+| azure_monitor.cognitive_services.content_safety_requests | total, harmful, blocked | requests/s |
361
+| azure_monitor.cognitive_services.content_safety_abusive_users | abusive_users | users/s |
362
+| azure_monitor.cognitive_services.content_safety_system_events | events | events |
363
+| azure_monitor.cognitive_services.content_safety_moderation | text, image | requests/s |
364
+| azure_monitor.cognitive_services.job_duration | average | milliseconds |
365
+| azure_monitor.cognitive_services.personalizer_actions | occurrences | occurrences/s |
366
+| azure_monitor.cognitive_services.personalizer_actions_per_event | average | actions |
367
+| azure_monitor.cognitive_services.personalizer_feature_occurrences | action, context, slot | occurrences/s |
368
+| azure_monitor.cognitive_services.personalizer_feature_cardinality | action, context, slot | features |
369
+| azure_monitor.cognitive_services.personalizer_features_per_event | action, context, slot | features |
370
+| azure_monitor.cognitive_services.personalizer_namespaces_per_event | action, context, slot | namespaces |
371
+| azure_monitor.cognitive_services.personalizer_rewards | average, slot | reward |
372
+| azure_monitor.cognitive_services.personalizer_estimator_rewards | online, baseline, baseline_random | reward |
373
+| azure_monitor.cognitive_services.personalizer_estimator_slot_rewards | online, baseline, baseline_random | reward |
374
+| azure_monitor.cognitive_services.personalizer_slots | average | slots |
375
+| azure_monitor.cognitive_services.personalizer_slot_occurrences | occurrences | occurrences/s |
376
+| azure_monitor.cognitive_services.personalizer_event_counts | online, baseline_random, user_baseline | events/s |
377
+| azure_monitor.cognitive_services.personalizer_estimated_rewards | online, baseline_random, user_baseline | reward/s |
378
+| azure_monitor.cognitive_services.speech_transcription | realtime, batch, batch_whisper, fast, fast_whisper | seconds/s |
379
+| azure_monitor.cognitive_services.speech_translation | translated | seconds/s |
380
+| azure_monitor.cognitive_services.speech_synthesis | synthesized | characters/s |
381
+| azure_monitor.cognitive_services.speech_video_synthesis | synthesized | seconds/s |
382
+| azure_monitor.cognitive_services.speech_avatar | hosting, training | seconds/s |
383
+| azure_monitor.cognitive_services.speech_speaker_recognition | transactions | transactions/s |
384
+| azure_monitor.cognitive_services.speech_speaker_profiles | profiles | profiles/s |
385
+| azure_monitor.cognitive_services.speech_model_hosting | hosting | hours/s |
386
+| azure_monitor.cognitive_services.speech_voice_live_tokens | audio_input, audio_output, cached_audio_input, text_input, text_output, cached_text_input | tokens/s |
387
+| azure_monitor.cognitive_services.speech_voice_model | hosting | hours/s |
388
+| azure_monitor.cognitive_services.speech_voice_training | training | minutes/s |
389
+| azure_monitor.cognitive_services.translator_text | standard, custom, trained | characters/s |
390
+| azure_monitor.cognitive_services.translator_document | standard, custom | characters/s |
391
+| azure_monitor.cognitive_services.translator_document_sync | standard, custom | characters/s |
392
+| azure_monitor.cognitive_services.translator_pro_app | seconds | seconds/s |
393
+| azure_monitor.cognitive_services.vision_transactions | computer_vision, custom_vision | transactions/s |
394
+| azure_monitor.cognitive_services.vision_training | training_time | seconds/s |
395
+| azure_monitor.cognitive_services.vision_images_stored | stored | images/s |
396
+| azure_monitor.cognitive_services.face_transactions | transactions | transactions/s |
397
+| azure_monitor.cognitive_services.face_images_trained | trained | images/s |
398
+| azure_monitor.cognitive_services.faces_stored | stored | faces/s |
399
+| azure_monitor.cognitive_services.luis_requests | speech, text | requests/s |
400
+| azure_monitor.cognitive_services.text_processing | text, health_text, question_answering | records/s |
401
+| azure_monitor.cognitive_services.processed_characters | characters | characters/s |
402
+| azure_monitor.cognitive_services.processed_images | images | images/s |
403
+| azure_monitor.cognitive_services.processed_pages | pages | pages/s |
404
+| azure_monitor.cognitive_services.carnegie_inference | inferences | inferences/s |
405
+| azure_monitor.cognitive_services.personalizer_events | total, learned, non_activated | events/s |
406
+| azure_monitor.cognitive_services.personalizer_reward_tracking | matched, observed | rewards/s |
407
+
408
+
409
+
410
## Troubleshooting
411
412
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_container_apps.md
+72
-72
@@ -57,78 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.container_apps.cpu_usage | average, maximum | nanocores |
88
-| azure_monitor.container_apps.cpu_percentage | average, maximum | percentage |
89
-| azure_monitor.container_apps.memory_working_set | average, maximum | bytes |
90
-| azure_monitor.container_apps.memory_percentage | average, maximum | percentage |
91
-| azure_monitor.container_apps.replicas | average | replicas |
92
-| azure_monitor.container_apps.reserved_cores | per_revision, total | cores |
93
-| azure_monitor.container_apps.restart_count | restarts | restarts/s |
94
-| azure_monitor.container_apps.requests | requests | requests/s |
95
-| azure_monitor.container_apps.response_time | average | milliseconds |
96
-| azure_monitor.container_apps.network | received, sent | bytes/s |
97
-| azure_monitor.container_apps.resiliency_timeouts | connection, request | timeouts/s |
98
-| azure_monitor.container_apps.resiliency_retries | retries | retries/s |
99
-| azure_monitor.container_apps.resiliency_pending_connections | pending | requests/s |
100
-| azure_monitor.container_apps.resiliency_ejections | ejected, aborted | ejections/s |
101
-| azure_monitor.container_apps.gpu_utilization | average, maximum | percentage |
102
-| azure_monitor.container_apps.jvm_buffer_count | average | buffers |
103
-| azure_monitor.container_apps.jvm_buffer_memory | used, limit | bytes |
104
-| azure_monitor.container_apps.jvm_gc_count | collections | collections/s |
105
-| azure_monitor.container_apps.jvm_gc_duration | duration | milliseconds/s |
106
-| azure_monitor.container_apps.jvm_memory_pool | used, committed, limit | bytes |
107
-| azure_monitor.container_apps.jvm_memory_total | used, committed, limit | bytes |
108
-| azure_monitor.container_apps.jvm_thread_count | average | threads |
109
-
110
-
111
-
112
-## Alerts
113
-
114
-
115
-The following alerts are available:
116
-
117
-| Alert name | On metric | Description |
118
-|:------------|:----------|:------------|
119
-| [ am_container_apps_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.cpu_percentage | Container Apps CPU on ${label:resource_name} |
120
-| [ am_container_apps_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.memory_percentage | Container Apps memory on ${label:resource_name} |
121
-| [ am_container_apps_restarts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.restart_count | Container Apps restarts on ${label:resource_name} |
122
-| [ am_container_apps_response_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.response_time | Container Apps response time on ${label:resource_name} |
123
-| [ am_container_apps_resiliency_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_timeouts | Container Apps resiliency timeouts on ${label:resource_name} |
124
-| [ am_container_apps_resiliency_retries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_retries | Container Apps resiliency retries on ${label:resource_name} |
125
-| [ am_container_apps_pending_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_pending_connections | Container Apps pending connections on ${label:resource_name} |
126
-| [ am_container_apps_host_ejections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_ejections | Container Apps host ejections on ${label:resource_name} |
127
-| [ am_container_apps_replica_count ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.replicas | Container Apps replicas on ${label:resource_name} |
128
-| [ am_container_apps_gpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.gpu_utilization | Container Apps GPU on ${label:resource_name} |
129
-| [ am_container_apps_jvm_gc_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.jvm_gc_duration | Container Apps JVM GC duration on ${label:resource_name} |
130
-
131
-
60
## Setup
61
62
@@ -350,6 +278,78 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_container_apps_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.cpu_percentage | Container Apps CPU on ${label:resource_name} |
289
+| [ am_container_apps_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.memory_percentage | Container Apps memory on ${label:resource_name} |
290
+| [ am_container_apps_restarts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.restart_count | Container Apps restarts on ${label:resource_name} |
291
+| [ am_container_apps_response_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.response_time | Container Apps response time on ${label:resource_name} |
292
+| [ am_container_apps_resiliency_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_timeouts | Container Apps resiliency timeouts on ${label:resource_name} |
293
+| [ am_container_apps_resiliency_retries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_retries | Container Apps resiliency retries on ${label:resource_name} |
294
+| [ am_container_apps_pending_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_pending_connections | Container Apps pending connections on ${label:resource_name} |
295
+| [ am_container_apps_host_ejections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.resiliency_ejections | Container Apps host ejections on ${label:resource_name} |
296
+| [ am_container_apps_replica_count ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.replicas | Container Apps replicas on ${label:resource_name} |
297
+| [ am_container_apps_gpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.gpu_utilization | Container Apps GPU on ${label:resource_name} |
298
+| [ am_container_apps_jvm_gc_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_apps.conf) | azure_monitor.container_apps.jvm_gc_duration | Container Apps JVM GC duration on ${label:resource_name} |
299
+
300
+
301
+## Metrics
302
+
303
+Metrics grouped by *scope*.
304
+
305
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
306
+
307
+
308
+
309
+### Per resource
310
+
311
+These metrics refer to each monitored Azure resource.
312
+
313
+Labels:
314
+
315
+| Label | Description |
316
+|:-----------|:----------------|
317
+| resource_name | The Azure resource name. |
318
+| resource_group | The Azure resource group. |
319
+| region | The Azure region where the resource is deployed. |
320
+| resource_type | The Azure resource type identifier. |
321
+| profile | The Azure Monitor profile id. |
322
+| resource_uid | The unique Azure resource identifier. |
323
+
324
+Metrics:
325
+
326
+| Metric | Dimensions | Unit |
327
+|:------|:----------|:----|
328
+| azure_monitor.container_apps.cpu_usage | average, maximum | nanocores |
329
+| azure_monitor.container_apps.cpu_percentage | average, maximum | percentage |
330
+| azure_monitor.container_apps.memory_working_set | average, maximum | bytes |
331
+| azure_monitor.container_apps.memory_percentage | average, maximum | percentage |
332
+| azure_monitor.container_apps.replicas | average | replicas |
333
+| azure_monitor.container_apps.reserved_cores | per_revision, total | cores |
334
+| azure_monitor.container_apps.restart_count | restarts | restarts/s |
335
+| azure_monitor.container_apps.requests | requests | requests/s |
336
+| azure_monitor.container_apps.response_time | average | milliseconds |
337
+| azure_monitor.container_apps.network | received, sent | bytes/s |
338
+| azure_monitor.container_apps.resiliency_timeouts | connection, request | timeouts/s |
339
+| azure_monitor.container_apps.resiliency_retries | retries | retries/s |
340
+| azure_monitor.container_apps.resiliency_pending_connections | pending | requests/s |
341
+| azure_monitor.container_apps.resiliency_ejections | ejected, aborted | ejections/s |
342
+| azure_monitor.container_apps.gpu_utilization | average, maximum | percentage |
343
+| azure_monitor.container_apps.jvm_buffer_count | average | buffers |
344
+| azure_monitor.container_apps.jvm_buffer_memory | used, limit | bytes |
345
+| azure_monitor.container_apps.jvm_gc_count | collections | collections/s |
346
+| azure_monitor.container_apps.jvm_gc_duration | duration | milliseconds/s |
347
+| azure_monitor.container_apps.jvm_memory_pool | used, committed, limit | bytes |
348
+| azure_monitor.container_apps.jvm_memory_total | used, committed, limit | bytes |
349
+| azure_monitor.container_apps.jvm_thread_count | average | threads |
350
+
351
+
352
+
353
## Troubleshooting
354
355
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_container_instances.md
+46
-46
@@ -57,52 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.container_instances.cpu_usage | average, maximum | millicores |
88
-| azure_monitor.container_instances.memory_usage | average, maximum | bytes |
89
-| azure_monitor.container_instances.network | received, sent | bytes/s |
90
-
91
-
92
-
93
-## Alerts
94
-
95
-
96
-The following alerts are available:
97
-
98
-| Alert name | On metric | Description |
99
-|:------------|:----------|:------------|
100
-| [ am_container_instances_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.cpu_usage | Container CPU on ${label:resource_name} |
101
-| [ am_container_instances_memory_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.memory_usage | Container memory on ${label:resource_name} |
102
-| [ am_container_instances_network_rx ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.network | Container inbound traffic on ${label:resource_name} |
103
-| [ am_container_instances_network_tx ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.network | Container outbound traffic on ${label:resource_name} |
104
-
105
-
60
## Setup
61
62
@@ -324,6 +278,52 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_container_instances_cpu_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.cpu_usage | Container CPU on ${label:resource_name} |
289
+| [ am_container_instances_memory_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.memory_usage | Container memory on ${label:resource_name} |
290
+| [ am_container_instances_network_rx ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.network | Container inbound traffic on ${label:resource_name} |
291
+| [ am_container_instances_network_tx ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_instances.conf) | azure_monitor.container_instances.network | Container outbound traffic on ${label:resource_name} |
292
+
293
+
294
+## Metrics
295
+
296
+Metrics grouped by *scope*.
297
+
298
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
299
+
300
+
301
+
302
+### Per resource
303
+
304
+These metrics refer to each monitored Azure resource.
305
+
306
+Labels:
307
+
308
+| Label | Description |
309
+|:-----------|:----------------|
310
+| resource_name | The Azure resource name. |
311
+| resource_group | The Azure resource group. |
312
+| region | The Azure region where the resource is deployed. |
313
+| resource_type | The Azure resource type identifier. |
314
+| profile | The Azure Monitor profile id. |
315
+| resource_uid | The unique Azure resource identifier. |
316
+
317
+Metrics:
318
+
319
+| Metric | Dimensions | Unit |
320
+|:------|:----------|:----|
321
+| azure_monitor.container_instances.cpu_usage | average, maximum | millicores |
322
+| azure_monitor.container_instances.memory_usage | average, maximum | bytes |
323
+| azure_monitor.container_instances.network | received, sent | bytes/s |
324
+
325
+
326
+
327
## Troubleshooting
328
329
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_container_registry.md
+46
-46
@@ -57,52 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.container_registry.storage_used | used | bytes |
88
-| azure_monitor.container_registry.pull_count | successful, total | pulls/s |
89
-| azure_monitor.container_registry.push_count | successful, total | pushes/s |
90
-| azure_monitor.container_registry.agentpool_cpu_time | cpu_time | seconds/s |
91
-| azure_monitor.container_registry.run_duration | duration | milliseconds/s |
92
-
93
-
94
-
95
-## Alerts
96
-
97
-
98
-The following alerts are available:
99
-
100
-| Alert name | On metric | Description |
101
-|:------------|:----------|:------------|
102
-| [ am_container_registry_pull_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_registry.conf) | azure_monitor.container_registry.pull_count | ACR pull failures on ${label:resource_name} |
103
-| [ am_container_registry_push_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_registry.conf) | azure_monitor.container_registry.push_count | ACR push failures on ${label:resource_name} |
104
-
105
-
60
## Setup
61
62
@@ -324,6 +278,52 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_container_registry_pull_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_registry.conf) | azure_monitor.container_registry.pull_count | ACR pull failures on ${label:resource_name} |
289
+| [ am_container_registry_push_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_container_registry.conf) | azure_monitor.container_registry.push_count | ACR push failures on ${label:resource_name} |
290
+
291
+
292
+## Metrics
293
+
294
+Metrics grouped by *scope*.
295
+
296
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
297
+
298
+
299
+
300
+### Per resource
301
+
302
+These metrics refer to each monitored Azure resource.
303
+
304
+Labels:
305
+
306
+| Label | Description |
307
+|:-----------|:----------------|
308
+| resource_name | The Azure resource name. |
309
+| resource_group | The Azure resource group. |
310
+| region | The Azure region where the resource is deployed. |
311
+| resource_type | The Azure resource type identifier. |
312
+| profile | The Azure Monitor profile id. |
313
+| resource_uid | The unique Azure resource identifier. |
314
+
315
+Metrics:
316
+
317
+| Metric | Dimensions | Unit |
318
+|:------|:----------|:----|
319
+| azure_monitor.container_registry.storage_used | used | bytes |
320
+| azure_monitor.container_registry.pull_count | successful, total | pulls/s |
321
+| azure_monitor.container_registry.push_count | successful, total | pushes/s |
322
+| azure_monitor.container_registry.agentpool_cpu_time | cpu_time | seconds/s |
323
+| azure_monitor.container_registry.run_duration | duration | milliseconds/s |
324
+
325
+
326
+
327
## Troubleshooting
328
329
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_cosmos_db_account.md
+69
-69
@@ -57,75 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.cosmos_db.total_requests | count | requests/s |
88
-| azure_monitor.cosmos_db.request_units | total | RU/s |
89
-| azure_monitor.cosmos_db.normalized_ru_consumption | maximum | percentage |
90
-| azure_monitor.cosmos_db.server_side_latency | direct, gateway | milliseconds |
91
-| azure_monitor.cosmos_db.replication_latency | average | milliseconds |
92
-| azure_monitor.cosmos_db.storage | data, index, quota | bytes |
93
-| azure_monitor.cosmos_db.document_count | average | documents |
94
-| azure_monitor.cosmos_db.partition_size | maximum | bytes |
95
-| azure_monitor.cosmos_db.partition_count | maximum | partitions |
96
-| azure_monitor.cosmos_db.provisioned_throughput | provisioned, autoscale_max, autoscaled | RU/s |
97
-| azure_monitor.cosmos_db.partition_throughput | maximum | RU/s |
98
-| azure_monitor.cosmos_db.availability | average | percentage |
99
-| azure_monitor.cosmos_db.metadata_requests | count | requests/s |
100
-| azure_monitor.cosmos_db.api_requests | mongo, cassandra, gremlin | requests/s |
101
-| azure_monitor.cosmos_db.api_request_charges | mongo, cassandra, gremlin | RU/s |
102
-| azure_monitor.cosmos_db.cassandra_connections | total | connections/s |
103
-| azure_monitor.cosmos_db.dedicated_gateway_cpu | average | percentage |
104
-| azure_monitor.cosmos_db.dedicated_gateway_memory | average | bytes |
105
-| azure_monitor.cosmos_db.dedicated_gateway_requests | count | requests/s |
106
-| azure_monitor.cosmos_db.integrated_cache_hit_rate | item, query | percentage |
107
-
108
-
109
-
110
-## Alerts
111
-
112
-
113
-The following alerts are available:
114
-
115
-| Alert name | On metric | Description |
116
-|:------------|:----------|:------------|
117
-| [ am_cosmos_db_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.availability | Cosmos DB availability on ${label:resource_name} |
118
-| [ am_cosmos_db_normalized_ru_consumption ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.normalized_ru_consumption | Cosmos DB RU consumption on ${label:resource_name} |
119
-| [ am_cosmos_db_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.storage | Cosmos DB storage utilization on ${label:resource_name} |
120
-| [ am_cosmos_db_server_side_latency_direct ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.server_side_latency | Cosmos DB direct latency on ${label:resource_name} |
121
-| [ am_cosmos_db_server_side_latency_gateway ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.server_side_latency | Cosmos DB gateway latency on ${label:resource_name} |
122
-| [ am_cosmos_db_replication_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.replication_latency | Cosmos DB replication latency on ${label:resource_name} |
123
-| [ am_cosmos_db_dedicated_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.dedicated_gateway_cpu | Cosmos DB dedicated gateway CPU on ${label:resource_name} |
124
-| [ am_cosmos_db_integrated_cache_item_hit_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.integrated_cache_hit_rate | Cosmos DB cache item hit rate on ${label:resource_name} |
125
-| [ am_cosmos_db_integrated_cache_query_hit_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.integrated_cache_hit_rate | Cosmos DB cache query hit rate on ${label:resource_name} |
126
-| [ am_cosmos_db_cassandra_connection_closures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.cassandra_connections | Cosmos DB Cassandra connection closures on ${label:resource_name} |
127
-
128
-
60
## Setup
61
62
@@ -347,6 +278,75 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_cosmos_db_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.availability | Cosmos DB availability on ${label:resource_name} |
289
+| [ am_cosmos_db_normalized_ru_consumption ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.normalized_ru_consumption | Cosmos DB RU consumption on ${label:resource_name} |
290
+| [ am_cosmos_db_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.storage | Cosmos DB storage utilization on ${label:resource_name} |
291
+| [ am_cosmos_db_server_side_latency_direct ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.server_side_latency | Cosmos DB direct latency on ${label:resource_name} |
292
+| [ am_cosmos_db_server_side_latency_gateway ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.server_side_latency | Cosmos DB gateway latency on ${label:resource_name} |
293
+| [ am_cosmos_db_replication_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.replication_latency | Cosmos DB replication latency on ${label:resource_name} |
294
+| [ am_cosmos_db_dedicated_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.dedicated_gateway_cpu | Cosmos DB dedicated gateway CPU on ${label:resource_name} |
295
+| [ am_cosmos_db_integrated_cache_item_hit_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.integrated_cache_hit_rate | Cosmos DB cache item hit rate on ${label:resource_name} |
296
+| [ am_cosmos_db_integrated_cache_query_hit_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.integrated_cache_hit_rate | Cosmos DB cache query hit rate on ${label:resource_name} |
297
+| [ am_cosmos_db_cassandra_connection_closures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_cosmos_db.conf) | azure_monitor.cosmos_db.cassandra_connections | Cosmos DB Cassandra connection closures on ${label:resource_name} |
298
+
299
+
300
+## Metrics
301
+
302
+Metrics grouped by *scope*.
303
+
304
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
305
+
306
+
307
+
308
+### Per resource
309
+
310
+These metrics refer to each monitored Azure resource.
311
+
312
+Labels:
313
+
314
+| Label | Description |
315
+|:-----------|:----------------|
316
+| resource_name | The Azure resource name. |
317
+| resource_group | The Azure resource group. |
318
+| region | The Azure region where the resource is deployed. |
319
+| resource_type | The Azure resource type identifier. |
320
+| profile | The Azure Monitor profile id. |
321
+| resource_uid | The unique Azure resource identifier. |
322
+
323
+Metrics:
324
+
325
+| Metric | Dimensions | Unit |
326
+|:------|:----------|:----|
327
+| azure_monitor.cosmos_db.total_requests | count | requests/s |
328
+| azure_monitor.cosmos_db.request_units | total | RU/s |
329
+| azure_monitor.cosmos_db.normalized_ru_consumption | maximum | percentage |
330
+| azure_monitor.cosmos_db.server_side_latency | direct, gateway | milliseconds |
331
+| azure_monitor.cosmos_db.replication_latency | average | milliseconds |
332
+| azure_monitor.cosmos_db.storage | data, index, quota | bytes |
333
+| azure_monitor.cosmos_db.document_count | average | documents |
334
+| azure_monitor.cosmos_db.partition_size | maximum | bytes |
335
+| azure_monitor.cosmos_db.partition_count | maximum | partitions |
336
+| azure_monitor.cosmos_db.provisioned_throughput | provisioned, autoscale_max, autoscaled | RU/s |
337
+| azure_monitor.cosmos_db.partition_throughput | maximum | RU/s |
338
+| azure_monitor.cosmos_db.availability | average | percentage |
339
+| azure_monitor.cosmos_db.metadata_requests | count | requests/s |
340
+| azure_monitor.cosmos_db.api_requests | mongo, cassandra, gremlin | requests/s |
341
+| azure_monitor.cosmos_db.api_request_charges | mongo, cassandra, gremlin | RU/s |
342
+| azure_monitor.cosmos_db.cassandra_connections | total | connections/s |
343
+| azure_monitor.cosmos_db.dedicated_gateway_cpu | average | percentage |
344
+| azure_monitor.cosmos_db.dedicated_gateway_memory | average | bytes |
345
+| azure_monitor.cosmos_db.dedicated_gateway_requests | count | requests/s |
346
+| azure_monitor.cosmos_db.integrated_cache_hit_rate | item, query | percentage |
347
+
348
+
349
+
350
## Troubleshooting
351
352
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_data_explorer_cluster.md
+104
-104
@@ -57,110 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.data_explorer.cpu_utilization | average | percentage |
88
-| azure_monitor.data_explorer.utilization | ingestion, cache | percentage |
89
-| azure_monitor.data_explorer.keep_alive | average | count |
90
-| azure_monitor.data_explorer.instance_count | average, maximum, minimum | instances |
91
-| azure_monitor.data_explorer.extents | average | extents |
92
-| azure_monitor.data_explorer.throttled_commands | total | commands/s |
93
-| azure_monitor.data_explorer.follower_latency | average | milliseconds |
94
-| azure_monitor.data_explorer.query_duration | average | milliseconds |
95
-| azure_monitor.data_explorer.query_count | count | queries/s |
96
-| azure_monitor.data_explorer.concurrent_queries | average, maximum | queries |
97
-| azure_monitor.data_explorer.throttled_queries | total | queries/s |
98
-| azure_monitor.data_explorer.weak_consistency_latency | average | seconds |
99
-| azure_monitor.data_explorer.ingestion_result | total | sources/s |
100
-| azure_monitor.data_explorer.ingestion_volume | total | bytes/s |
101
-| azure_monitor.data_explorer.ingestion_latency | average | seconds |
102
-| azure_monitor.data_explorer.events | received, processed, dropped | events/s |
103
-| azure_monitor.data_explorer.blobs | received, processed, dropped | blobs/s |
104
-| azure_monitor.data_explorer.discovery_latency | average | seconds |
105
-| azure_monitor.data_explorer.stage_latency | average | seconds |
106
-| azure_monitor.data_explorer.ingestion_queue | length | messages |
107
-| azure_monitor.data_explorer.queue_oldest_message | age | seconds |
108
-| azure_monitor.data_explorer.received_data_size | total | bytes/s |
109
-| azure_monitor.data_explorer.batches_processed | total | batches/s |
110
-| azure_monitor.data_explorer.batch_blob_count | average | blobs |
111
-| azure_monitor.data_explorer.batch_size | average | bytes |
112
-| azure_monitor.data_explorer.batch_duration | average | seconds |
113
-| azure_monitor.data_explorer.export_utilization | maximum | percentage |
114
-| azure_monitor.data_explorer.continuous_export_records | total | records/s |
115
-| azure_monitor.data_explorer.continuous_export_result | count | results/s |
116
-| azure_monitor.data_explorer.continuous_export_pending | maximum | jobs |
117
-| azure_monitor.data_explorer.continuous_export_lateness | maximum | minutes |
118
-| azure_monitor.data_explorer.streaming_ingest_data_rate | average | bytes/s |
119
-| azure_monitor.data_explorer.streaming_ingest_duration | average | milliseconds |
120
-| azure_monitor.data_explorer.streaming_ingest_result | count | results/s |
121
-| azure_monitor.data_explorer.streaming_ingest_utilization | average | percentage |
122
-| azure_monitor.data_explorer.materialized_view_health | health | status |
123
-| azure_monitor.data_explorer.materialized_view_age | minutes | minutes |
124
-| azure_monitor.data_explorer.materialized_view_age_seconds | average | seconds |
125
-| azure_monitor.data_explorer.materialized_view_records_in_delta | average | records |
126
-| azure_monitor.data_explorer.materialized_view_extents_rebuild | average | extents |
127
-| azure_monitor.data_explorer.materialized_view_data_loss | maximum | status |
128
-| azure_monitor.data_explorer.materialized_view_result | average | status |
129
-| azure_monitor.data_explorer.partitioning_percentage | total, hot | percentage |
130
-| azure_monitor.data_explorer.partitioned_records | average | records |
131
-
132
-
133
-
134
-## Alerts
135
-
136
-
137
-The following alerts are available:
138
-
139
-| Alert name | On metric | Description |
140
-|:------------|:----------|:------------|
141
-| [ am_data_explorer_keep_alive ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.keep_alive | Data Explorer keep alive on ${label:resource_name} |
142
-| [ am_data_explorer_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.cpu_utilization | Data Explorer CPU on ${label:resource_name} |
143
-| [ am_data_explorer_ingestion_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.utilization | Data Explorer ingestion utilization on ${label:resource_name} |
144
-| [ am_data_explorer_cache_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.utilization | Data Explorer cache utilization on ${label:resource_name} |
145
-| [ am_data_explorer_throttled_commands ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.throttled_commands | Data Explorer throttled commands on ${label:resource_name} |
146
-| [ am_data_explorer_query_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.query_duration | Data Explorer query duration on ${label:resource_name} |
147
-| [ am_data_explorer_throttled_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.throttled_queries | Data Explorer throttled queries on ${label:resource_name} |
148
-| [ am_data_explorer_ingestion_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.ingestion_latency | Data Explorer ingestion latency on ${label:resource_name} |
149
-| [ am_data_explorer_events_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.events | Data Explorer events dropped on ${label:resource_name} |
150
-| [ am_data_explorer_blobs_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.blobs | Data Explorer blobs dropped on ${label:resource_name} |
151
-| [ am_data_explorer_ingestion_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.ingestion_queue | Data Explorer ingestion queue on ${label:resource_name} |
152
-| [ am_data_explorer_queue_oldest_message ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.queue_oldest_message | Data Explorer queue oldest message age on ${label:resource_name} |
153
-| [ am_data_explorer_export_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.export_utilization | Data Explorer export utilization on ${label:resource_name} |
154
-| [ am_data_explorer_continuous_export_pending ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.continuous_export_pending | Data Explorer continuous export pending on ${label:resource_name} |
155
-| [ am_data_explorer_continuous_export_lateness ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.continuous_export_lateness | Data Explorer continuous export lateness on ${label:resource_name} |
156
-| [ am_data_explorer_streaming_ingest_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.streaming_ingest_utilization | Data Explorer streaming ingest utilization on ${label:resource_name} |
157
-| [ am_data_explorer_streaming_ingest_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.streaming_ingest_duration | Data Explorer streaming ingest duration on ${label:resource_name} |
158
-| [ am_data_explorer_materialized_view_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.materialized_view_health | Data Explorer materialized view health on ${label:resource_name} |
159
-| [ am_data_explorer_materialized_view_age ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.materialized_view_age | Data Explorer materialized view age on ${label:resource_name} |
160
-| [ am_data_explorer_materialized_view_data_loss ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.materialized_view_data_loss | Data Explorer materialized view data loss on ${label:resource_name} |
161
-| [ am_data_explorer_follower_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.follower_latency | Data Explorer follower latency on ${label:resource_name} |
162
-
163
-
60
## Setup
61
62
@@ -382,6 +278,110 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_data_explorer_keep_alive ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.keep_alive | Data Explorer keep alive on ${label:resource_name} |
289
+| [ am_data_explorer_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.cpu_utilization | Data Explorer CPU on ${label:resource_name} |
290
+| [ am_data_explorer_ingestion_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.utilization | Data Explorer ingestion utilization on ${label:resource_name} |
291
+| [ am_data_explorer_cache_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.utilization | Data Explorer cache utilization on ${label:resource_name} |
292
+| [ am_data_explorer_throttled_commands ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.throttled_commands | Data Explorer throttled commands on ${label:resource_name} |
293
+| [ am_data_explorer_query_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.query_duration | Data Explorer query duration on ${label:resource_name} |
294
+| [ am_data_explorer_throttled_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.throttled_queries | Data Explorer throttled queries on ${label:resource_name} |
295
+| [ am_data_explorer_ingestion_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.ingestion_latency | Data Explorer ingestion latency on ${label:resource_name} |
296
+| [ am_data_explorer_events_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.events | Data Explorer events dropped on ${label:resource_name} |
297
+| [ am_data_explorer_blobs_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.blobs | Data Explorer blobs dropped on ${label:resource_name} |
298
+| [ am_data_explorer_ingestion_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.ingestion_queue | Data Explorer ingestion queue on ${label:resource_name} |
299
+| [ am_data_explorer_queue_oldest_message ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.queue_oldest_message | Data Explorer queue oldest message age on ${label:resource_name} |
300
+| [ am_data_explorer_export_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.export_utilization | Data Explorer export utilization on ${label:resource_name} |
301
+| [ am_data_explorer_continuous_export_pending ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.continuous_export_pending | Data Explorer continuous export pending on ${label:resource_name} |
302
+| [ am_data_explorer_continuous_export_lateness ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.continuous_export_lateness | Data Explorer continuous export lateness on ${label:resource_name} |
303
+| [ am_data_explorer_streaming_ingest_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.streaming_ingest_utilization | Data Explorer streaming ingest utilization on ${label:resource_name} |
304
+| [ am_data_explorer_streaming_ingest_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.streaming_ingest_duration | Data Explorer streaming ingest duration on ${label:resource_name} |
305
+| [ am_data_explorer_materialized_view_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.materialized_view_health | Data Explorer materialized view health on ${label:resource_name} |
306
+| [ am_data_explorer_materialized_view_age ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.materialized_view_age | Data Explorer materialized view age on ${label:resource_name} |
307
+| [ am_data_explorer_materialized_view_data_loss ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.materialized_view_data_loss | Data Explorer materialized view data loss on ${label:resource_name} |
308
+| [ am_data_explorer_follower_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_explorer.conf) | azure_monitor.data_explorer.follower_latency | Data Explorer follower latency on ${label:resource_name} |
309
+
310
+
311
+## Metrics
312
+
313
+Metrics grouped by *scope*.
314
+
315
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
316
+
317
+
318
+
319
+### Per resource
320
+
321
+These metrics refer to each monitored Azure resource.
322
+
323
+Labels:
324
+
325
+| Label | Description |
326
+|:-----------|:----------------|
327
+| resource_name | The Azure resource name. |
328
+| resource_group | The Azure resource group. |
329
+| region | The Azure region where the resource is deployed. |
330
+| resource_type | The Azure resource type identifier. |
331
+| profile | The Azure Monitor profile id. |
332
+| resource_uid | The unique Azure resource identifier. |
333
+
334
+Metrics:
335
+
336
+| Metric | Dimensions | Unit |
337
+|:------|:----------|:----|
338
+| azure_monitor.data_explorer.cpu_utilization | average | percentage |
339
+| azure_monitor.data_explorer.utilization | ingestion, cache | percentage |
340
+| azure_monitor.data_explorer.keep_alive | average | count |
341
+| azure_monitor.data_explorer.instance_count | average, maximum, minimum | instances |
342
+| azure_monitor.data_explorer.extents | average | extents |
343
+| azure_monitor.data_explorer.throttled_commands | total | commands/s |
344
+| azure_monitor.data_explorer.follower_latency | average | milliseconds |
345
+| azure_monitor.data_explorer.query_duration | average | milliseconds |
346
+| azure_monitor.data_explorer.query_count | count | queries/s |
347
+| azure_monitor.data_explorer.concurrent_queries | average, maximum | queries |
348
+| azure_monitor.data_explorer.throttled_queries | total | queries/s |
349
+| azure_monitor.data_explorer.weak_consistency_latency | average | seconds |
350
+| azure_monitor.data_explorer.ingestion_result | total | sources/s |
351
+| azure_monitor.data_explorer.ingestion_volume | total | bytes/s |
352
+| azure_monitor.data_explorer.ingestion_latency | average | seconds |
353
+| azure_monitor.data_explorer.events | received, processed, dropped | events/s |
354
+| azure_monitor.data_explorer.blobs | received, processed, dropped | blobs/s |
355
+| azure_monitor.data_explorer.discovery_latency | average | seconds |
356
+| azure_monitor.data_explorer.stage_latency | average | seconds |
357
+| azure_monitor.data_explorer.ingestion_queue | length | messages |
358
+| azure_monitor.data_explorer.queue_oldest_message | age | seconds |
359
+| azure_monitor.data_explorer.received_data_size | total | bytes/s |
360
+| azure_monitor.data_explorer.batches_processed | total | batches/s |
361
+| azure_monitor.data_explorer.batch_blob_count | average | blobs |
362
+| azure_monitor.data_explorer.batch_size | average | bytes |
363
+| azure_monitor.data_explorer.batch_duration | average | seconds |
364
+| azure_monitor.data_explorer.export_utilization | maximum | percentage |
365
+| azure_monitor.data_explorer.continuous_export_records | total | records/s |
366
+| azure_monitor.data_explorer.continuous_export_result | count | results/s |
367
+| azure_monitor.data_explorer.continuous_export_pending | maximum | jobs |
368
+| azure_monitor.data_explorer.continuous_export_lateness | maximum | minutes |
369
+| azure_monitor.data_explorer.streaming_ingest_data_rate | average | bytes/s |
370
+| azure_monitor.data_explorer.streaming_ingest_duration | average | milliseconds |
371
+| azure_monitor.data_explorer.streaming_ingest_result | count | results/s |
372
+| azure_monitor.data_explorer.streaming_ingest_utilization | average | percentage |
373
+| azure_monitor.data_explorer.materialized_view_health | health | status |
374
+| azure_monitor.data_explorer.materialized_view_age | minutes | minutes |
375
+| azure_monitor.data_explorer.materialized_view_age_seconds | average | seconds |
376
+| azure_monitor.data_explorer.materialized_view_records_in_delta | average | records |
377
+| azure_monitor.data_explorer.materialized_view_extents_rebuild | average | extents |
378
+| azure_monitor.data_explorer.materialized_view_data_loss | maximum | status |
379
+| azure_monitor.data_explorer.materialized_view_result | average | status |
380
+| azure_monitor.data_explorer.partitioning_percentage | total, hot | percentage |
381
+| azure_monitor.data_explorer.partitioned_records | average | records |
382
+
383
+
384
+
385
## Troubleshooting
386
387
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_data_factory.md
+113
-113
@@ -57,119 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.data_factory.pipeline_runs | succeeded, failed, cancelled | runs/s |
88
-| azure_monitor.data_factory.pipeline_elapsed_time | elapsed_time | runs/s |
89
-| azure_monitor.data_factory.activity_runs | succeeded, failed, cancelled | runs/s |
90
-| azure_monitor.data_factory.trigger_runs | succeeded, failed, cancelled | runs/s |
91
-| azure_monitor.data_factory.ssis_ir_starts | succeeded, failed, cancelled | runs/s |
92
-| azure_monitor.data_factory.ssis_ir_stops | succeeded, stuck | runs/s |
93
-| azure_monitor.data_factory.ssis_package_executions | succeeded, failed, cancelled | executions/s |
94
-| azure_monitor.data_factory.ir_cpu | average | percentage |
95
-| azure_monitor.data_factory.ir_memory | available | bytes |
96
-| azure_monitor.data_factory.ir_nodes | available | nodes |
97
-| azure_monitor.data_factory.ir_queue | queue_length | tasks |
98
-| azure_monitor.data_factory.ir_task_pickup_delay | average | seconds |
99
-| azure_monitor.data_factory.factory_size | current, max_allowed | GiB |
100
-| azure_monitor.data_factory.entity_count | current, max_allowed | entities |
101
-| azure_monitor.data_factory.mvnet_ir_copy_capacity | utilization, available | percentage |
102
-| azure_monitor.data_factory.mvnet_ir_copy_queue | waiting | tasks |
103
-| azure_monitor.data_factory.mvnet_ir_external_capacity | utilization, available | percentage |
104
-| azure_monitor.data_factory.mvnet_ir_external_queue | waiting | tasks |
105
-| azure_monitor.data_factory.mvnet_ir_pipeline_capacity | utilization, available | percentage |
106
-| azure_monitor.data_factory.mvnet_ir_pipeline_queue | waiting | tasks |
107
-| azure_monitor.data_factory.airflow_ir_cpu | percentage | percentage |
108
-| azure_monitor.data_factory.airflow_ir_cpu_usage | average | millicores |
109
-| azure_monitor.data_factory.airflow_ir_memory | percentage | percentage |
110
-| azure_monitor.data_factory.airflow_ir_memory_usage | average | bytes |
111
-| azure_monitor.data_factory.airflow_ir_nodes | average | nodes |
112
-| azure_monitor.data_factory.airflow_ir_dag_collection | average | milliseconds |
113
-| azure_monitor.data_factory.airflow_ir_dag_bag | total | dags/s |
114
-| azure_monitor.data_factory.airflow_ir_dag_errors | callback_exceptions, file_refresh, import | errors/s |
115
-| azure_monitor.data_factory.airflow_ir_dag_processing_duration | last_duration | milliseconds |
116
-| azure_monitor.data_factory.airflow_ir_dag_processing_lag | last_run_seconds_ago, processor_timeouts, total_parse_time | seconds |
117
-| azure_monitor.data_factory.airflow_ir_dag_processing_activity | manager_stalls, processes | events/s |
118
-| azure_monitor.data_factory.airflow_ir_dag_run_duration | success, failed | milliseconds |
119
-| azure_monitor.data_factory.airflow_ir_dag_run_scheduling | dependency_check, first_task_delay, schedule_delay | milliseconds |
120
-| azure_monitor.data_factory.airflow_ir_executor | open_slots, queued_tasks, running_tasks | slots/s |
121
-| azure_monitor.data_factory.airflow_ir_jobs | started, ended, heartbeat_failures | jobs/s |
122
-| azure_monitor.data_factory.airflow_ir_operators | successes, failures | operations/s |
123
-| azure_monitor.data_factory.airflow_ir_pool_slots | open, queued, running | slots/s |
124
-| azure_monitor.data_factory.airflow_ir_pool_starving | starving | tasks/s |
125
-| azure_monitor.data_factory.airflow_ir_scheduler_critical_section | duration | milliseconds |
126
-| azure_monitor.data_factory.airflow_ir_scheduler_activity | critical_section_busy, heartbeats, failed_sla_emails | events/s |
127
-| azure_monitor.data_factory.airflow_ir_scheduler_orphaned_tasks | adopted, cleared | tasks/s |
128
-| azure_monitor.data_factory.airflow_ir_scheduler_tasks | executable, running, starving, killed_externally | tasks/s |
129
-| azure_monitor.data_factory.airflow_ir_task_instances | started, succeeded, failed, finished, previously_succeeded, created_via_operator | instances/s |
130
-| azure_monitor.data_factory.airflow_ir_task_instance_duration | average | milliseconds |
131
-| azure_monitor.data_factory.airflow_ir_task_dag_changes | removed, restored | tasks/s |
132
-| azure_monitor.data_factory.airflow_ir_triggers | succeeded, failed, running | triggers/s |
133
-| azure_monitor.data_factory.airflow_ir_trigger_issues | blocked_main_thread, celery_timeout_errors | events/s |
134
-| azure_monitor.data_factory.airflow_ir_zombies | killed | tasks/s |
135
-
136
-
137
-
138
-## Alerts
139
-
140
-
141
-The following alerts are available:
142
-
143
-| Alert name | On metric | Description |
144
-|:------------|:----------|:------------|
145
-| [ am_data_factory_pipeline_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.pipeline_runs | Data Factory pipeline failures on ${label:resource_name} |
146
-| [ am_data_factory_pipeline_cancelled_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.pipeline_runs | Data Factory pipeline cancellations on ${label:resource_name} |
147
-| [ am_data_factory_activity_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.activity_runs | Data Factory activity failures on ${label:resource_name} |
148
-| [ am_data_factory_trigger_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.trigger_runs | Data Factory trigger failures on ${label:resource_name} |
149
-| [ am_data_factory_ssis_ir_start_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ssis_ir_starts | Data Factory SSIS IR start failures on ${label:resource_name} |
150
-| [ am_data_factory_ssis_ir_stop_stuck ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ssis_ir_stops | Data Factory SSIS IR stuck stops on ${label:resource_name} |
151
-| [ am_data_factory_ssis_package_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ssis_package_executions | Data Factory SSIS package failures on ${label:resource_name} |
152
-| [ am_data_factory_ir_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ir_cpu | Data Factory IR CPU on ${label:resource_name} |
153
-| [ am_data_factory_ir_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ir_queue | Data Factory IR queue depth on ${label:resource_name} |
154
-| [ am_data_factory_ir_task_pickup_delay ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ir_task_pickup_delay | Data Factory IR task pickup delay on ${label:resource_name} |
155
-| [ am_data_factory_size_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.factory_size | Data Factory size utilization on ${label:resource_name} |
156
-| [ am_data_factory_entity_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.entity_count | Data Factory entity count on ${label:resource_name} |
157
-| [ am_data_factory_mvnet_ir_copy_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.mvnet_ir_copy_capacity | Data Factory MVNet IR copy utilization on ${label:resource_name} |
158
-| [ am_data_factory_mvnet_ir_external_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.mvnet_ir_external_capacity | Data Factory MVNet IR external utilization on ${label:resource_name} |
159
-| [ am_data_factory_mvnet_ir_pipeline_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.mvnet_ir_pipeline_capacity | Data Factory MVNet IR pipeline utilization on ${label:resource_name} |
160
-| [ am_data_factory_airflow_ir_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_cpu | Data Factory Airflow IR CPU on ${label:resource_name} |
161
-| [ am_data_factory_airflow_ir_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_memory | Data Factory Airflow IR memory on ${label:resource_name} |
162
-| [ am_data_factory_airflow_ir_dag_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_dag_errors | Data Factory Airflow DAG errors on ${label:resource_name} |
163
-| [ am_data_factory_airflow_ir_operator_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_operators | Data Factory Airflow operator failures on ${label:resource_name} |
164
-| [ am_data_factory_airflow_ir_job_heartbeat_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_jobs | Data Factory Airflow job heartbeat failures on ${label:resource_name} |
165
-| [ am_data_factory_airflow_ir_pool_starving ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_pool_starving | Data Factory Airflow pool starvation on ${label:resource_name} |
166
-| [ am_data_factory_airflow_ir_tasks_killed_externally ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_scheduler_tasks | Data Factory Airflow tasks killed externally on ${label:resource_name} |
167
-| [ am_data_factory_airflow_ir_tasks_starving ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_scheduler_tasks | Data Factory Airflow scheduler starving tasks on ${label:resource_name} |
168
-| [ am_data_factory_airflow_ir_task_instance_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_task_instances | Data Factory Airflow task failures on ${label:resource_name} |
169
-| [ am_data_factory_airflow_ir_trigger_issues ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_trigger_issues | Data Factory Airflow trigger issues on ${label:resource_name} |
170
-| [ am_data_factory_airflow_ir_zombies ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_zombies | Data Factory Airflow zombie tasks on ${label:resource_name} |
171
-
172
-
60
## Setup
61
62
@@ -391,6 +278,119 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_data_factory_pipeline_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.pipeline_runs | Data Factory pipeline failures on ${label:resource_name} |
289
+| [ am_data_factory_pipeline_cancelled_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.pipeline_runs | Data Factory pipeline cancellations on ${label:resource_name} |
290
+| [ am_data_factory_activity_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.activity_runs | Data Factory activity failures on ${label:resource_name} |
291
+| [ am_data_factory_trigger_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.trigger_runs | Data Factory trigger failures on ${label:resource_name} |
292
+| [ am_data_factory_ssis_ir_start_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ssis_ir_starts | Data Factory SSIS IR start failures on ${label:resource_name} |
293
+| [ am_data_factory_ssis_ir_stop_stuck ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ssis_ir_stops | Data Factory SSIS IR stuck stops on ${label:resource_name} |
294
+| [ am_data_factory_ssis_package_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ssis_package_executions | Data Factory SSIS package failures on ${label:resource_name} |
295
+| [ am_data_factory_ir_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ir_cpu | Data Factory IR CPU on ${label:resource_name} |
296
+| [ am_data_factory_ir_queue_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ir_queue | Data Factory IR queue depth on ${label:resource_name} |
297
+| [ am_data_factory_ir_task_pickup_delay ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.ir_task_pickup_delay | Data Factory IR task pickup delay on ${label:resource_name} |
298
+| [ am_data_factory_size_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.factory_size | Data Factory size utilization on ${label:resource_name} |
299
+| [ am_data_factory_entity_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.entity_count | Data Factory entity count on ${label:resource_name} |
300
+| [ am_data_factory_mvnet_ir_copy_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.mvnet_ir_copy_capacity | Data Factory MVNet IR copy utilization on ${label:resource_name} |
301
+| [ am_data_factory_mvnet_ir_external_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.mvnet_ir_external_capacity | Data Factory MVNet IR external utilization on ${label:resource_name} |
302
+| [ am_data_factory_mvnet_ir_pipeline_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.mvnet_ir_pipeline_capacity | Data Factory MVNet IR pipeline utilization on ${label:resource_name} |
303
+| [ am_data_factory_airflow_ir_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_cpu | Data Factory Airflow IR CPU on ${label:resource_name} |
304
+| [ am_data_factory_airflow_ir_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_memory | Data Factory Airflow IR memory on ${label:resource_name} |
305
+| [ am_data_factory_airflow_ir_dag_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_dag_errors | Data Factory Airflow DAG errors on ${label:resource_name} |
306
+| [ am_data_factory_airflow_ir_operator_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_operators | Data Factory Airflow operator failures on ${label:resource_name} |
307
+| [ am_data_factory_airflow_ir_job_heartbeat_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_jobs | Data Factory Airflow job heartbeat failures on ${label:resource_name} |
308
+| [ am_data_factory_airflow_ir_pool_starving ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_pool_starving | Data Factory Airflow pool starvation on ${label:resource_name} |
309
+| [ am_data_factory_airflow_ir_tasks_killed_externally ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_scheduler_tasks | Data Factory Airflow tasks killed externally on ${label:resource_name} |
310
+| [ am_data_factory_airflow_ir_tasks_starving ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_scheduler_tasks | Data Factory Airflow scheduler starving tasks on ${label:resource_name} |
311
+| [ am_data_factory_airflow_ir_task_instance_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_task_instances | Data Factory Airflow task failures on ${label:resource_name} |
312
+| [ am_data_factory_airflow_ir_trigger_issues ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_trigger_issues | Data Factory Airflow trigger issues on ${label:resource_name} |
313
+| [ am_data_factory_airflow_ir_zombies ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_data_factory.conf) | azure_monitor.data_factory.airflow_ir_zombies | Data Factory Airflow zombie tasks on ${label:resource_name} |
314
+
315
+
316
+## Metrics
317
+
318
+Metrics grouped by *scope*.
319
+
320
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
321
+
322
+
323
+
324
+### Per resource
325
+
326
+These metrics refer to each monitored Azure resource.
327
+
328
+Labels:
329
+
330
+| Label | Description |
331
+|:-----------|:----------------|
332
+| resource_name | The Azure resource name. |
333
+| resource_group | The Azure resource group. |
334
+| region | The Azure region where the resource is deployed. |
335
+| resource_type | The Azure resource type identifier. |
336
+| profile | The Azure Monitor profile id. |
337
+| resource_uid | The unique Azure resource identifier. |
338
+
339
+Metrics:
340
+
341
+| Metric | Dimensions | Unit |
342
+|:------|:----------|:----|
343
+| azure_monitor.data_factory.pipeline_runs | succeeded, failed, cancelled | runs/s |
344
+| azure_monitor.data_factory.pipeline_elapsed_time | elapsed_time | runs/s |
345
+| azure_monitor.data_factory.activity_runs | succeeded, failed, cancelled | runs/s |
346
+| azure_monitor.data_factory.trigger_runs | succeeded, failed, cancelled | runs/s |
347
+| azure_monitor.data_factory.ssis_ir_starts | succeeded, failed, cancelled | runs/s |
348
+| azure_monitor.data_factory.ssis_ir_stops | succeeded, stuck | runs/s |
349
+| azure_monitor.data_factory.ssis_package_executions | succeeded, failed, cancelled | executions/s |
350
+| azure_monitor.data_factory.ir_cpu | average | percentage |
351
+| azure_monitor.data_factory.ir_memory | available | bytes |
352
+| azure_monitor.data_factory.ir_nodes | available | nodes |
353
+| azure_monitor.data_factory.ir_queue | queue_length | tasks |
354
+| azure_monitor.data_factory.ir_task_pickup_delay | average | seconds |
355
+| azure_monitor.data_factory.factory_size | current, max_allowed | GiB |
356
+| azure_monitor.data_factory.entity_count | current, max_allowed | entities |
357
+| azure_monitor.data_factory.mvnet_ir_copy_capacity | utilization, available | percentage |
358
+| azure_monitor.data_factory.mvnet_ir_copy_queue | waiting | tasks |
359
+| azure_monitor.data_factory.mvnet_ir_external_capacity | utilization, available | percentage |
360
+| azure_monitor.data_factory.mvnet_ir_external_queue | waiting | tasks |
361
+| azure_monitor.data_factory.mvnet_ir_pipeline_capacity | utilization, available | percentage |
362
+| azure_monitor.data_factory.mvnet_ir_pipeline_queue | waiting | tasks |
363
+| azure_monitor.data_factory.airflow_ir_cpu | percentage | percentage |
364
+| azure_monitor.data_factory.airflow_ir_cpu_usage | average | millicores |
365
+| azure_monitor.data_factory.airflow_ir_memory | percentage | percentage |
366
+| azure_monitor.data_factory.airflow_ir_memory_usage | average | bytes |
367
+| azure_monitor.data_factory.airflow_ir_nodes | average | nodes |
368
+| azure_monitor.data_factory.airflow_ir_dag_collection | average | milliseconds |
369
+| azure_monitor.data_factory.airflow_ir_dag_bag | total | dags/s |
370
+| azure_monitor.data_factory.airflow_ir_dag_errors | callback_exceptions, file_refresh, import | errors/s |
371
+| azure_monitor.data_factory.airflow_ir_dag_processing_duration | last_duration | milliseconds |
372
+| azure_monitor.data_factory.airflow_ir_dag_processing_lag | last_run_seconds_ago, processor_timeouts, total_parse_time | seconds |
373
+| azure_monitor.data_factory.airflow_ir_dag_processing_activity | manager_stalls, processes | events/s |
374
+| azure_monitor.data_factory.airflow_ir_dag_run_duration | success, failed | milliseconds |
375
+| azure_monitor.data_factory.airflow_ir_dag_run_scheduling | dependency_check, first_task_delay, schedule_delay | milliseconds |
376
+| azure_monitor.data_factory.airflow_ir_executor | open_slots, queued_tasks, running_tasks | slots/s |
377
+| azure_monitor.data_factory.airflow_ir_jobs | started, ended, heartbeat_failures | jobs/s |
378
+| azure_monitor.data_factory.airflow_ir_operators | successes, failures | operations/s |
379
+| azure_monitor.data_factory.airflow_ir_pool_slots | open, queued, running | slots/s |
380
+| azure_monitor.data_factory.airflow_ir_pool_starving | starving | tasks/s |
381
+| azure_monitor.data_factory.airflow_ir_scheduler_critical_section | duration | milliseconds |
382
+| azure_monitor.data_factory.airflow_ir_scheduler_activity | critical_section_busy, heartbeats, failed_sla_emails | events/s |
383
+| azure_monitor.data_factory.airflow_ir_scheduler_orphaned_tasks | adopted, cleared | tasks/s |
384
+| azure_monitor.data_factory.airflow_ir_scheduler_tasks | executable, running, starving, killed_externally | tasks/s |
385
+| azure_monitor.data_factory.airflow_ir_task_instances | started, succeeded, failed, finished, previously_succeeded, created_via_operator | instances/s |
386
+| azure_monitor.data_factory.airflow_ir_task_instance_duration | average | milliseconds |
387
+| azure_monitor.data_factory.airflow_ir_task_dag_changes | removed, restored | tasks/s |
388
+| azure_monitor.data_factory.airflow_ir_triggers | succeeded, failed, running | triggers/s |
389
+| azure_monitor.data_factory.airflow_ir_trigger_issues | blocked_main_thread, celery_timeout_errors | events/s |
390
+| azure_monitor.data_factory.airflow_ir_zombies | killed | tasks/s |
391
+
392
+
393
+
394
## Troubleshooting
395
396
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_event_grid_topic.md
+51
-51
@@ -57,57 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.event_grid.publish_rate | success, failed | events/s |
88
-| azure_monitor.event_grid.publish_latency | latency | milliseconds |
89
-| azure_monitor.event_grid.routing | matched, unmatched | events/s |
90
-| azure_monitor.event_grid.advanced_filter_evaluations | evaluations | evaluations/s |
91
-| azure_monitor.event_grid.delivery | delivered, failed, dropped, dead_lettered | events/s |
92
-| azure_monitor.event_grid.destination_processing_duration | average | milliseconds |
93
-
94
-
95
-
96
-## Alerts
97
-
98
-
99
-The following alerts are available:
100
-
101
-| Alert name | On metric | Description |
102
-|:------------|:----------|:------------|
103
-| [ am_event_grid_publish_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.publish_rate | Event Grid publish failures on ${label:resource_name} |
104
-| [ am_event_grid_delivery_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.delivery | Event Grid delivery failures on ${label:resource_name} |
105
-| [ am_event_grid_dropped_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.delivery | Event Grid dropped events on ${label:resource_name} |
106
-| [ am_event_grid_dead_lettered_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.delivery | Event Grid dead-lettered events on ${label:resource_name} |
107
-| [ am_event_grid_unmatched_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.routing | Event Grid unmatched events on ${label:resource_name} |
108
-| [ am_event_grid_destination_processing_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.destination_processing_duration | Event Grid destination processing duration on ${label:resource_name} |
109
-
110
-
60
## Setup
61
62
@@ -329,6 +278,57 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_event_grid_publish_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.publish_rate | Event Grid publish failures on ${label:resource_name} |
289
+| [ am_event_grid_delivery_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.delivery | Event Grid delivery failures on ${label:resource_name} |
290
+| [ am_event_grid_dropped_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.delivery | Event Grid dropped events on ${label:resource_name} |
291
+| [ am_event_grid_dead_lettered_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.delivery | Event Grid dead-lettered events on ${label:resource_name} |
292
+| [ am_event_grid_unmatched_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.routing | Event Grid unmatched events on ${label:resource_name} |
293
+| [ am_event_grid_destination_processing_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_grid.conf) | azure_monitor.event_grid.destination_processing_duration | Event Grid destination processing duration on ${label:resource_name} |
294
+
295
+
296
+## Metrics
297
+
298
+Metrics grouped by *scope*.
299
+
300
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
301
+
302
+
303
+
304
+### Per resource
305
+
306
+These metrics refer to each monitored Azure resource.
307
+
308
+Labels:
309
+
310
+| Label | Description |
311
+|:-----------|:----------------|
312
+| resource_name | The Azure resource name. |
313
+| resource_group | The Azure resource group. |
314
+| region | The Azure region where the resource is deployed. |
315
+| resource_type | The Azure resource type identifier. |
316
+| profile | The Azure Monitor profile id. |
317
+| resource_uid | The unique Azure resource identifier. |
318
+
319
+Metrics:
320
+
321
+| Metric | Dimensions | Unit |
322
+|:------|:----------|:----|
323
+| azure_monitor.event_grid.publish_rate | success, failed | events/s |
324
+| azure_monitor.event_grid.publish_latency | latency | milliseconds |
325
+| azure_monitor.event_grid.routing | matched, unmatched | events/s |
326
+| azure_monitor.event_grid.advanced_filter_evaluations | evaluations | evaluations/s |
327
+| azure_monitor.event_grid.delivery | delivered, failed, dropped, dead_lettered | events/s |
328
+| azure_monitor.event_grid.destination_processing_duration | average | milliseconds |
329
+
330
+
331
+
332
## Troubleshooting
333
334
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_event_hubs_namespace.md
+62
-62
@@ -57,68 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.event_hubs.message_flow | in, out | messages/s |
88
-| azure_monitor.event_hubs.data_throughput | in, out | bytes/s |
89
-| azure_monitor.event_hubs.requests | incoming, successful | requests/s |
90
-| azure_monitor.event_hubs.errors | server, user, throttled, quota_exceeded | errors/s |
91
-| azure_monitor.event_hubs.connections | active | connections |
92
-| azure_monitor.event_hubs.connection_events | opened, closed | connections |
93
-| azure_monitor.event_hubs.captured_messages | total | messages/s |
94
-| azure_monitor.event_hubs.captured_data | total | bytes/s |
95
-| azure_monitor.event_hubs.namespace_size | average | bytes |
96
-| azure_monitor.event_hubs.capture_backlog | backlog | messages |
97
-| azure_monitor.event_hubs.namespace_resources | cpu, memory | percentage |
98
-| azure_monitor.event_hubs.replication_lag | messages | messages |
99
-| azure_monitor.event_hubs.replication_lag_duration | duration | seconds |
100
-
101
-
102
-
103
-## Alerts
104
-
105
-
106
-The following alerts are available:
107
-
108
-| Alert name | On metric | Description |
109
-|:------------|:----------|:------------|
110
-| [ am_event_hubs_server_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs server errors on ${label:resource_name} |
111
-| [ am_event_hubs_throttled_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs throttled requests on ${label:resource_name} |
112
-| [ am_event_hubs_quota_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs quota exceeded on ${label:resource_name} |
113
-| [ am_event_hubs_user_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs user errors on ${label:resource_name} |
114
-| [ am_event_hubs_success_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.requests | Event Hubs request success rate on ${label:resource_name} |
115
-| [ am_event_hubs_namespace_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.namespace_resources | Event Hubs namespace CPU on ${label:resource_name} |
116
-| [ am_event_hubs_namespace_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.namespace_resources | Event Hubs namespace memory on ${label:resource_name} |
117
-| [ am_event_hubs_capture_backlog ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.capture_backlog | Event Hubs capture backlog on ${label:resource_name} |
118
-| [ am_event_hubs_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.replication_lag | Event Hubs replication lag on ${label:resource_name} |
119
-| [ am_event_hubs_replication_lag_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.replication_lag_duration | Event Hubs replication lag duration on ${label:resource_name} |
120
-
121
-
60
## Setup
61
62
@@ -340,6 +278,68 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_event_hubs_server_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs server errors on ${label:resource_name} |
289
+| [ am_event_hubs_throttled_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs throttled requests on ${label:resource_name} |
290
+| [ am_event_hubs_quota_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs quota exceeded on ${label:resource_name} |
291
+| [ am_event_hubs_user_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.errors | Event Hubs user errors on ${label:resource_name} |
292
+| [ am_event_hubs_success_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.requests | Event Hubs request success rate on ${label:resource_name} |
293
+| [ am_event_hubs_namespace_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.namespace_resources | Event Hubs namespace CPU on ${label:resource_name} |
294
+| [ am_event_hubs_namespace_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.namespace_resources | Event Hubs namespace memory on ${label:resource_name} |
295
+| [ am_event_hubs_capture_backlog ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.capture_backlog | Event Hubs capture backlog on ${label:resource_name} |
296
+| [ am_event_hubs_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.replication_lag | Event Hubs replication lag on ${label:resource_name} |
297
+| [ am_event_hubs_replication_lag_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_event_hubs.conf) | azure_monitor.event_hubs.replication_lag_duration | Event Hubs replication lag duration on ${label:resource_name} |
298
+
299
+
300
+## Metrics
301
+
302
+Metrics grouped by *scope*.
303
+
304
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
305
+
306
+
307
+
308
+### Per resource
309
+
310
+These metrics refer to each monitored Azure resource.
311
+
312
+Labels:
313
+
314
+| Label | Description |
315
+|:-----------|:----------------|
316
+| resource_name | The Azure resource name. |
317
+| resource_group | The Azure resource group. |
318
+| region | The Azure region where the resource is deployed. |
319
+| resource_type | The Azure resource type identifier. |
320
+| profile | The Azure Monitor profile id. |
321
+| resource_uid | The unique Azure resource identifier. |
322
+
323
+Metrics:
324
+
325
+| Metric | Dimensions | Unit |
326
+|:------|:----------|:----|
327
+| azure_monitor.event_hubs.message_flow | in, out | messages/s |
328
+| azure_monitor.event_hubs.data_throughput | in, out | bytes/s |
329
+| azure_monitor.event_hubs.requests | incoming, successful | requests/s |
330
+| azure_monitor.event_hubs.errors | server, user, throttled, quota_exceeded | errors/s |
331
+| azure_monitor.event_hubs.connections | active | connections |
332
+| azure_monitor.event_hubs.connection_events | opened, closed | connections |
333
+| azure_monitor.event_hubs.captured_messages | total | messages/s |
334
+| azure_monitor.event_hubs.captured_data | total | bytes/s |
335
+| azure_monitor.event_hubs.namespace_size | average | bytes |
336
+| azure_monitor.event_hubs.capture_backlog | backlog | messages |
337
+| azure_monitor.event_hubs.namespace_resources | cpu, memory | percentage |
338
+| azure_monitor.event_hubs.replication_lag | messages | messages |
339
+| azure_monitor.event_hubs.replication_lag_duration | duration | seconds |
340
+
341
+
342
+
343
## Troubleshooting
344
345
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_expressroute_circuit.md
+52
-52
@@ -57,58 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.express_route_circuit.arp_availability | average | percentage |
88
-| azure_monitor.express_route_circuit.bgp_availability | average | percentage |
89
-| azure_monitor.express_route_circuit.throughput | in, out | bits/s |
90
-| azure_monitor.express_route_circuit.bandwidth_utilization | ingress, egress | percentage |
91
-| azure_monitor.express_route_circuit.qos_dropped_bits | in, out | bits/s |
92
-| azure_monitor.express_route_circuit.fastpath_routes | maximum | routes |
93
-| azure_monitor.express_route_circuit.global_reach_throughput | in, out | bits/s |
94
-
95
-
96
-
97
-## Alerts
98
-
99
-
100
-The following alerts are available:
101
-
102
-| Alert name | On metric | Description |
103
-|:------------|:----------|:------------|
104
-| [ am_express_route_circuit_arp_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.arp_availability | ExpressRoute ARP availability on ${label:resource_name} |
105
-| [ am_express_route_circuit_bgp_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.bgp_availability | ExpressRoute BGP availability on ${label:resource_name} |
106
-| [ am_express_route_circuit_ingress_bandwidth_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.bandwidth_utilization | ExpressRoute ingress bandwidth on ${label:resource_name} |
107
-| [ am_express_route_circuit_egress_bandwidth_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.bandwidth_utilization | ExpressRoute egress bandwidth on ${label:resource_name} |
108
-| [ am_express_route_circuit_qos_drop_in ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.qos_dropped_bits | ExpressRoute QoS ingress drops on ${label:resource_name} |
109
-| [ am_express_route_circuit_qos_drop_out ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.qos_dropped_bits | ExpressRoute QoS egress drops on ${label:resource_name} |
110
-
111
-
60
## Setup
61
62
@@ -330,6 +278,58 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_express_route_circuit_arp_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.arp_availability | ExpressRoute ARP availability on ${label:resource_name} |
289
+| [ am_express_route_circuit_bgp_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.bgp_availability | ExpressRoute BGP availability on ${label:resource_name} |
290
+| [ am_express_route_circuit_ingress_bandwidth_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.bandwidth_utilization | ExpressRoute ingress bandwidth on ${label:resource_name} |
291
+| [ am_express_route_circuit_egress_bandwidth_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.bandwidth_utilization | ExpressRoute egress bandwidth on ${label:resource_name} |
292
+| [ am_express_route_circuit_qos_drop_in ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.qos_dropped_bits | ExpressRoute QoS ingress drops on ${label:resource_name} |
293
+| [ am_express_route_circuit_qos_drop_out ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_circuit.conf) | azure_monitor.express_route_circuit.qos_dropped_bits | ExpressRoute QoS egress drops on ${label:resource_name} |
294
+
295
+
296
+## Metrics
297
+
298
+Metrics grouped by *scope*.
299
+
300
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
301
+
302
+
303
+
304
+### Per resource
305
+
306
+These metrics refer to each monitored Azure resource.
307
+
308
+Labels:
309
+
310
+| Label | Description |
311
+|:-----------|:----------------|
312
+| resource_name | The Azure resource name. |
313
+| resource_group | The Azure resource group. |
314
+| region | The Azure region where the resource is deployed. |
315
+| resource_type | The Azure resource type identifier. |
316
+| profile | The Azure Monitor profile id. |
317
+| resource_uid | The unique Azure resource identifier. |
318
+
319
+Metrics:
320
+
321
+| Metric | Dimensions | Unit |
322
+|:------|:----------|:----|
323
+| azure_monitor.express_route_circuit.arp_availability | average | percentage |
324
+| azure_monitor.express_route_circuit.bgp_availability | average | percentage |
325
+| azure_monitor.express_route_circuit.throughput | in, out | bits/s |
326
+| azure_monitor.express_route_circuit.bandwidth_utilization | ingress, egress | percentage |
327
+| azure_monitor.express_route_circuit.qos_dropped_bits | in, out | bits/s |
328
+| azure_monitor.express_route_circuit.fastpath_routes | maximum | routes |
329
+| azure_monitor.express_route_circuit.global_reach_throughput | in, out | bits/s |
330
+
331
+
332
+
333
## Troubleshooting
334
335
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_expressroute_gateway.md
+54
-54
@@ -57,60 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.express_route_gateway.connection_throughput | in, out | bits/s |
88
-| azure_monitor.express_route_gateway.gateway_throughput | average | bits/s |
89
-| azure_monitor.express_route_gateway.cpu_utilization | average | percentage |
90
-| azure_monitor.express_route_gateway.packets | average | packets/s |
91
-| azure_monitor.express_route_gateway.active_flows | average | flows |
92
-| azure_monitor.express_route_gateway.routes_advertised | maximum | routes |
93
-| azure_monitor.express_route_gateway.routes_learned | maximum | routes |
94
-| azure_monitor.express_route_gateway.route_changes | total | changes/s |
95
-| azure_monitor.express_route_gateway.max_flows_creation_rate | maximum | flows/s |
96
-| azure_monitor.express_route_gateway.vm_count | maximum | VMs |
97
-
98
-
99
-
100
-## Alerts
101
-
102
-
103
-The following alerts are available:
104
-
105
-| Alert name | On metric | Description |
106
-|:------------|:----------|:------------|
107
-| [ am_express_route_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.cpu_utilization | ExpressRoute GW CPU on ${label:resource_name} |
108
-| [ am_express_route_gateway_active_flows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.active_flows | ExpressRoute GW active flows on ${label:resource_name} |
109
-| [ am_express_route_gateway_route_changes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.route_changes | ExpressRoute GW route churn on ${label:resource_name} |
110
-| [ am_express_route_gateway_routes_advertised ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.routes_advertised | ExpressRoute GW routes advertised on ${label:resource_name} |
111
-| [ am_express_route_gateway_routes_learned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.routes_learned | ExpressRoute GW routes learned on ${label:resource_name} |
112
-
113
-
60
## Setup
61
62
@@ -332,6 +278,60 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_express_route_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.cpu_utilization | ExpressRoute GW CPU on ${label:resource_name} |
289
+| [ am_express_route_gateway_active_flows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.active_flows | ExpressRoute GW active flows on ${label:resource_name} |
290
+| [ am_express_route_gateway_route_changes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.route_changes | ExpressRoute GW route churn on ${label:resource_name} |
291
+| [ am_express_route_gateway_routes_advertised ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.routes_advertised | ExpressRoute GW routes advertised on ${label:resource_name} |
292
+| [ am_express_route_gateway_routes_learned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_express_route_gateway.conf) | azure_monitor.express_route_gateway.routes_learned | ExpressRoute GW routes learned on ${label:resource_name} |
293
+
294
+
295
+## Metrics
296
+
297
+Metrics grouped by *scope*.
298
+
299
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
300
+
301
+
302
+
303
+### Per resource
304
+
305
+These metrics refer to each monitored Azure resource.
306
+
307
+Labels:
308
+
309
+| Label | Description |
310
+|:-----------|:----------------|
311
+| resource_name | The Azure resource name. |
312
+| resource_group | The Azure resource group. |
313
+| region | The Azure region where the resource is deployed. |
314
+| resource_type | The Azure resource type identifier. |
315
+| profile | The Azure Monitor profile id. |
316
+| resource_uid | The unique Azure resource identifier. |
317
+
318
+Metrics:
319
+
320
+| Metric | Dimensions | Unit |
321
+|:------|:----------|:----|
322
+| azure_monitor.express_route_gateway.connection_throughput | in, out | bits/s |
323
+| azure_monitor.express_route_gateway.gateway_throughput | average | bits/s |
324
+| azure_monitor.express_route_gateway.cpu_utilization | average | percentage |
325
+| azure_monitor.express_route_gateway.packets | average | packets/s |
326
+| azure_monitor.express_route_gateway.active_flows | average | flows |
327
+| azure_monitor.express_route_gateway.routes_advertised | maximum | routes |
328
+| azure_monitor.express_route_gateway.routes_learned | maximum | routes |
329
+| azure_monitor.express_route_gateway.route_changes | total | changes/s |
330
+| azure_monitor.express_route_gateway.max_flows_creation_rate | maximum | flows/s |
331
+| azure_monitor.express_route_gateway.vm_count | maximum | VMs |
332
+
333
+
334
+
335
## Troubleshooting
336
337
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_firewall.md
+49
-49
@@ -57,55 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.firewall.health | average | percentage |
88
-| azure_monitor.firewall.latency | average | milliseconds |
89
-| azure_monitor.firewall.throughput | average | bits/s |
90
-| azure_monitor.firewall.data_processed | total | bytes/s |
91
-| azure_monitor.firewall.rule_hits | application, network | hits/s |
92
-| azure_monitor.firewall.snat_port_utilization | average | percentage |
93
-| azure_monitor.firewall.capacity | average | units |
94
-
95
-
96
-
97
-## Alerts
98
-
99
-
100
-The following alerts are available:
101
-
102
-| Alert name | On metric | Description |
103
-|:------------|:----------|:------------|
104
-| [ am_firewall_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_firewall.conf) | azure_monitor.firewall.health | Firewall health on ${label:resource_name} |
105
-| [ am_firewall_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_firewall.conf) | azure_monitor.firewall.latency | Firewall latency on ${label:resource_name} |
106
-| [ am_firewall_snat_port_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_firewall.conf) | azure_monitor.firewall.snat_port_utilization | Firewall SNAT port utilization on ${label:resource_name} |
107
-
108
-
60
## Setup
61
62
@@ -327,6 +278,55 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_firewall_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_firewall.conf) | azure_monitor.firewall.health | Firewall health on ${label:resource_name} |
289
+| [ am_firewall_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_firewall.conf) | azure_monitor.firewall.latency | Firewall latency on ${label:resource_name} |
290
+| [ am_firewall_snat_port_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_firewall.conf) | azure_monitor.firewall.snat_port_utilization | Firewall SNAT port utilization on ${label:resource_name} |
291
+
292
+
293
+## Metrics
294
+
295
+Metrics grouped by *scope*.
296
+
297
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
298
+
299
+
300
+
301
+### Per resource
302
+
303
+These metrics refer to each monitored Azure resource.
304
+
305
+Labels:
306
+
307
+| Label | Description |
308
+|:-----------|:----------------|
309
+| resource_name | The Azure resource name. |
310
+| resource_group | The Azure resource group. |
311
+| region | The Azure region where the resource is deployed. |
312
+| resource_type | The Azure resource type identifier. |
313
+| profile | The Azure Monitor profile id. |
314
+| resource_uid | The unique Azure resource identifier. |
315
+
316
+Metrics:
317
+
318
+| Metric | Dimensions | Unit |
319
+|:------|:----------|:----|
320
+| azure_monitor.firewall.health | average | percentage |
321
+| azure_monitor.firewall.latency | average | milliseconds |
322
+| azure_monitor.firewall.throughput | average | bits/s |
323
+| azure_monitor.firewall.data_processed | total | bytes/s |
324
+| azure_monitor.firewall.rule_hits | application, network | hits/s |
325
+| azure_monitor.firewall.snat_port_utilization | average | percentage |
326
+| azure_monitor.firewall.capacity | average | units |
327
+
328
+
329
+
330
## Troubleshooting
331
332
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_front_door.md
+58
-58
@@ -57,64 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.front_door.latency | total, origin | milliseconds |
88
-| azure_monitor.front_door.origin_health | health | percentage |
89
-| azure_monitor.front_door.byte_hit_ratio | hit_ratio | percentage |
90
-| azure_monitor.front_door.error_rate | 4xx, 5xx | percentage |
91
-| azure_monitor.front_door.requests | client, origin | requests/s |
92
-| azure_monitor.front_door.data_transfer | request, response | bytes/s |
93
-| azure_monitor.front_door.origin_shield_requests | to_shield, to_origin, rate_limited | requests/s |
94
-| azure_monitor.front_door.origin_shield_data_transfer | request | bytes/s |
95
-| azure_monitor.front_door.waf_requests | total | requests/s |
96
-| azure_monitor.front_door.waf_challenges | captcha, js_challenge | requests/s |
97
-| azure_monitor.front_door.websocket_connections | requested, active | connections/s |
98
-| azure_monitor.front_door.websocket_duration | average | milliseconds |
99
-
100
-
101
-
102
-## Alerts
103
-
104
-
105
-The following alerts are available:
106
-
107
-| Alert name | On metric | Description |
108
-|:------------|:----------|:------------|
109
-| [ am_front_door_origin_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.origin_health | Front Door origin health on ${label:resource_name} |
110
-| [ am_front_door_total_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.latency | Front Door total latency on ${label:resource_name} |
111
-| [ am_front_door_origin_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.latency | Front Door origin latency on ${label:resource_name} |
112
-| [ am_front_door_5xx_error_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.error_rate | Front Door 5xx error rate on ${label:resource_name} |
113
-| [ am_front_door_4xx_error_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.error_rate | Front Door 4xx error rate on ${label:resource_name} |
114
-| [ am_front_door_byte_hit_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.byte_hit_ratio | Front Door cache hit ratio on ${label:resource_name} |
115
-| [ am_front_door_waf_rate_limited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.origin_shield_requests | Front Door origin shield rate limiting on ${label:resource_name} |
116
-
117
-
60
## Setup
61
62
@@ -336,6 +278,64 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_front_door_origin_health ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.origin_health | Front Door origin health on ${label:resource_name} |
289
+| [ am_front_door_total_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.latency | Front Door total latency on ${label:resource_name} |
290
+| [ am_front_door_origin_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.latency | Front Door origin latency on ${label:resource_name} |
291
+| [ am_front_door_5xx_error_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.error_rate | Front Door 5xx error rate on ${label:resource_name} |
292
+| [ am_front_door_4xx_error_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.error_rate | Front Door 4xx error rate on ${label:resource_name} |
293
+| [ am_front_door_byte_hit_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.byte_hit_ratio | Front Door cache hit ratio on ${label:resource_name} |
294
+| [ am_front_door_waf_rate_limited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_front_door.conf) | azure_monitor.front_door.origin_shield_requests | Front Door origin shield rate limiting on ${label:resource_name} |
295
+
296
+
297
+## Metrics
298
+
299
+Metrics grouped by *scope*.
300
+
301
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
302
+
303
+
304
+
305
+### Per resource
306
+
307
+These metrics refer to each monitored Azure resource.
308
+
309
+Labels:
310
+
311
+| Label | Description |
312
+|:-----------|:----------------|
313
+| resource_name | The Azure resource name. |
314
+| resource_group | The Azure resource group. |
315
+| region | The Azure region where the resource is deployed. |
316
+| resource_type | The Azure resource type identifier. |
317
+| profile | The Azure Monitor profile id. |
318
+| resource_uid | The unique Azure resource identifier. |
319
+
320
+Metrics:
321
+
322
+| Metric | Dimensions | Unit |
323
+|:------|:----------|:----|
324
+| azure_monitor.front_door.latency | total, origin | milliseconds |
325
+| azure_monitor.front_door.origin_health | health | percentage |
326
+| azure_monitor.front_door.byte_hit_ratio | hit_ratio | percentage |
327
+| azure_monitor.front_door.error_rate | 4xx, 5xx | percentage |
328
+| azure_monitor.front_door.requests | client, origin | requests/s |
329
+| azure_monitor.front_door.data_transfer | request, response | bytes/s |
330
+| azure_monitor.front_door.origin_shield_requests | to_shield, to_origin, rate_limited | requests/s |
331
+| azure_monitor.front_door.origin_shield_data_transfer | request | bytes/s |
332
+| azure_monitor.front_door.waf_requests | total | requests/s |
333
+| azure_monitor.front_door.waf_challenges | captcha, js_challenge | requests/s |
334
+| azure_monitor.front_door.websocket_connections | requested, active | connections/s |
335
+| azure_monitor.front_door.websocket_duration | average | milliseconds |
336
+
337
+
338
+
339
## Troubleshooting
340
341
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_functions.md
+61
-61
@@ -57,67 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.app_service.requests | requests | requests/s |
88
-| azure_monitor.app_service.response_time | average | seconds |
89
-| azure_monitor.app_service.http_status | 2xx, 3xx, 4xx, 5xx | responses/s |
90
-| azure_monitor.app_service.http_error_detail | 101_websocket, 401_unauthorized, 403_forbidden, 404_not_found, 406_not_acceptable | responses/s |
91
-| azure_monitor.app_service.cpu | average | percentage |
92
-| azure_monitor.app_service.cpu_time | total | seconds |
93
-| azure_monitor.app_service.memory_usage | average_working_set, working_set, private | bytes |
94
-| azure_monitor.app_service.health | average | percentage |
95
-| azure_monitor.app_service.network_traffic | received, sent | bytes/s |
96
-| azure_monitor.app_service.connections | average | connections |
97
-| azure_monitor.app_service.io_throughput | read, write, other | bytes/s |
98
-| azure_monitor.app_service.io_operations | read, write, other | operations/s |
99
-| azure_monitor.app_service.threads | average | threads |
100
-| azure_monitor.app_service.handles | average | handles |
101
-| azure_monitor.app_service.gc_collections | gen0, gen1, gen2 | collections/s |
102
-| azure_monitor.app_service.function_executions | total | executions/s |
103
-| azure_monitor.app_service.function_execution_units | total | MB-milliseconds/s |
104
-| azure_monitor.app_service.always_ready_function_executions | total | executions/s |
105
-| azure_monitor.app_service.always_ready_function_execution_units | total | MB-milliseconds/s |
106
-| azure_monitor.app_service.always_ready_units | total | units |
107
-| azure_monitor.app_service.on_demand_function_executions | total | executions/s |
108
-| azure_monitor.app_service.on_demand_function_execution_units | total | MB-milliseconds/s |
109
-| azure_monitor.app_service.request_queue | queued | requests |
110
-| azure_monitor.app_service.instances | running | instances |
111
-| azure_monitor.app_service.assemblies | loaded | assemblies |
112
-| azure_monitor.app_service.app_domains | loaded, unloaded | domains |
113
-
114
-
115
-
116
-## Alerts
117
-
118
-There are no alerts configured by default for this integration.
119
-
120
-
60
## Setup
61
62
@@ -339,6 +278,67 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+Metrics grouped by *scope*.
289
+
290
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
291
+
292
+
293
+
294
+### Per resource
295
+
296
+These metrics refer to each monitored Azure resource.
297
+
298
+Labels:
299
+
300
+| Label | Description |
301
+|:-----------|:----------------|
302
+| resource_name | The Azure resource name. |
303
+| resource_group | The Azure resource group. |
304
+| region | The Azure region where the resource is deployed. |
305
+| resource_type | The Azure resource type identifier. |
306
+| profile | The Azure Monitor profile id. |
307
+| resource_uid | The unique Azure resource identifier. |
308
+
309
+Metrics:
310
+
311
+| Metric | Dimensions | Unit |
312
+|:------|:----------|:----|
313
+| azure_monitor.app_service.requests | requests | requests/s |
314
+| azure_monitor.app_service.response_time | average | seconds |
315
+| azure_monitor.app_service.http_status | 2xx, 3xx, 4xx, 5xx | responses/s |
316
+| azure_monitor.app_service.http_error_detail | 101_websocket, 401_unauthorized, 403_forbidden, 404_not_found, 406_not_acceptable | responses/s |
317
+| azure_monitor.app_service.cpu | average | percentage |
318
+| azure_monitor.app_service.cpu_time | total | seconds |
319
+| azure_monitor.app_service.memory_usage | average_working_set, working_set, private | bytes |
320
+| azure_monitor.app_service.health | average | percentage |
321
+| azure_monitor.app_service.network_traffic | received, sent | bytes/s |
322
+| azure_monitor.app_service.connections | average | connections |
323
+| azure_monitor.app_service.io_throughput | read, write, other | bytes/s |
324
+| azure_monitor.app_service.io_operations | read, write, other | operations/s |
325
+| azure_monitor.app_service.threads | average | threads |
326
+| azure_monitor.app_service.handles | average | handles |
327
+| azure_monitor.app_service.gc_collections | gen0, gen1, gen2 | collections/s |
328
+| azure_monitor.app_service.function_executions | total | executions/s |
329
+| azure_monitor.app_service.function_execution_units | total | MB-milliseconds/s |
330
+| azure_monitor.app_service.always_ready_function_executions | total | executions/s |
331
+| azure_monitor.app_service.always_ready_function_execution_units | total | MB-milliseconds/s |
332
+| azure_monitor.app_service.always_ready_units | total | units |
333
+| azure_monitor.app_service.on_demand_function_executions | total | executions/s |
334
+| azure_monitor.app_service.on_demand_function_execution_units | total | MB-milliseconds/s |
335
+| azure_monitor.app_service.request_queue | queued | requests |
336
+| azure_monitor.app_service.instances | running | instances |
337
+| azure_monitor.app_service.assemblies | loaded | assemblies |
338
+| azure_monitor.app_service.app_domains | loaded, unloaded | domains |
339
+
340
+
341
+
342
## Troubleshooting
343
344
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_iot_hub.md
+95
-95
@@ -57,101 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.iot_hub.c2d_commands | completed, abandoned, rejected | messages/s |
88
-| azure_monitor.iot_hub.c2d_messages_expired | expired | messages/s |
89
-| azure_monitor.iot_hub.c2d_methods | successful, failed | invocations/s |
90
-| azure_monitor.iot_hub.c2d_methods_request_size | average | bytes |
91
-| azure_monitor.iot_hub.c2d_methods_response_size | average | bytes |
92
-| azure_monitor.iot_hub.c2d_twin_reads | successful, failed | operations/s |
93
-| azure_monitor.iot_hub.c2d_twin_read_size | average | bytes |
94
-| azure_monitor.iot_hub.c2d_twin_updates | successful, failed | operations/s |
95
-| azure_monitor.iot_hub.c2d_twin_update_size | average | bytes |
96
-| azure_monitor.iot_hub.d2c_telemetry | attempted, sent | messages/s |
97
-| azure_monitor.iot_hub.d2c_telemetry_throttle | throttled | errors/s |
98
-| azure_monitor.iot_hub.d2c_twin_reads | successful, failed | operations/s |
99
-| azure_monitor.iot_hub.d2c_twin_read_size | average | bytes |
100
-| azure_monitor.iot_hub.d2c_twin_updates | successful, failed | operations/s |
101
-| azure_monitor.iot_hub.d2c_twin_update_size | average | bytes |
102
-| azure_monitor.iot_hub.routing_deliveries | delivered, dropped, orphaned, invalid, fallback | messages/s |
103
-| azure_monitor.iot_hub.routing_delivery_by_endpoint | builtin_events, event_hubs, service_bus_queues, service_bus_topics, storage | messages/s |
104
-| azure_monitor.iot_hub.routing_storage_blobs | blobs | blobs/s |
105
-| azure_monitor.iot_hub.routing_storage_data | bytes | bytes/s |
106
-| azure_monitor.iot_hub.routing_latency | builtin_events, event_hubs, service_bus_queues, service_bus_topics, storage | milliseconds |
107
-| azure_monitor.iot_hub.routing_deliveries_preview | deliveries | deliveries/s |
108
-| azure_monitor.iot_hub.routing_delivery_latency_preview | average | milliseconds |
109
-| azure_monitor.iot_hub.routing_data_size_preview | bytes | bytes/s |
110
-| azure_monitor.iot_hub.connections | successful | connections/s |
111
-| azure_monitor.iot_hub.connected_devices | connected | devices |
112
-| azure_monitor.iot_hub.total_devices | total | devices |
113
-| azure_monitor.iot_hub.daily_message_quota | used | messages |
114
-| azure_monitor.iot_hub.data_usage | data_usage, data_usage_v2 | bytes/s |
115
-| azure_monitor.iot_hub.configurations | operations | operations/s |
116
-| azure_monitor.iot_hub.event_grid_deliveries | deliveries | deliveries/s |
117
-| azure_monitor.iot_hub.event_grid_latency | average | milliseconds |
118
-| azure_monitor.iot_hub.jobs_status | completed, failed | operations/s |
119
-| azure_monitor.iot_hub.jobs_cancel | successful, failed | operations/s |
120
-| azure_monitor.iot_hub.jobs_create_method | successful, failed | operations/s |
121
-| azure_monitor.iot_hub.jobs_create_twin_update | successful, failed | operations/s |
122
-| azure_monitor.iot_hub.jobs_list | successful, failed | operations/s |
123
-| azure_monitor.iot_hub.jobs_query | successful, failed | operations/s |
124
-| azure_monitor.iot_hub.twin_queries | successful, failed | queries/s |
125
-| azure_monitor.iot_hub.twin_queries_result_size | average | bytes |
126
-
127
-
128
-
129
-## Alerts
130
-
131
-
132
-The following alerts are available:
133
-
134
-| Alert name | On metric | Description |
135
-|:------------|:----------|:------------|
136
-| [ am_iot_hub_d2c_telemetry_throttle ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.d2c_telemetry_throttle | IoT Hub telemetry throttling on ${label:resource_name} |
137
-| [ am_iot_hub_c2d_messages_expired ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_messages_expired | IoT Hub C2D messages expiring on ${label:resource_name} |
138
-| [ am_iot_hub_c2d_methods_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_methods | IoT Hub direct method failures on ${label:resource_name} |
139
-| [ am_iot_hub_c2d_twin_read_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_twin_reads | IoT Hub backend twin read failures on ${label:resource_name} |
140
-| [ am_iot_hub_c2d_twin_update_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_twin_updates | IoT Hub backend twin update failures on ${label:resource_name} |
141
-| [ am_iot_hub_d2c_twin_read_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.d2c_twin_reads | IoT Hub device twin read failures on ${label:resource_name} |
142
-| [ am_iot_hub_d2c_twin_update_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.d2c_twin_updates | IoT Hub device twin update failures on ${label:resource_name} |
143
-| [ am_iot_hub_routing_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_deliveries | IoT Hub routing dropped messages on ${label:resource_name} |
144
-| [ am_iot_hub_routing_orphaned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_deliveries | IoT Hub routing orphaned messages on ${label:resource_name} |
145
-| [ am_iot_hub_routing_invalid ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_deliveries | IoT Hub routing invalid messages on ${label:resource_name} |
146
-| [ am_iot_hub_routing_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_latency | IoT Hub routing latency on ${label:resource_name} |
147
-| [ am_iot_hub_event_grid_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.event_grid_latency | IoT Hub Event Grid latency on ${label:resource_name} |
148
-| [ am_iot_hub_jobs_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.jobs_status | IoT Hub job failures on ${label:resource_name} |
149
-| [ am_iot_hub_twin_query_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.twin_queries | IoT Hub twin query failures on ${label:resource_name} |
150
-| [ am_iot_hub_c2d_commands_abandoned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_commands | IoT Hub C2D commands abandoned on ${label:resource_name} |
151
-| [ am_iot_hub_c2d_commands_rejected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_commands | IoT Hub C2D commands rejected on ${label:resource_name} |
152
-| [ am_iot_hub_routing_delivery_latency_preview ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_delivery_latency_preview | IoT Hub routing delivery latency on ${label:resource_name} |
153
-
154
-
60
## Setup
61
62
@@ -373,6 +278,101 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_iot_hub_d2c_telemetry_throttle ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.d2c_telemetry_throttle | IoT Hub telemetry throttling on ${label:resource_name} |
289
+| [ am_iot_hub_c2d_messages_expired ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_messages_expired | IoT Hub C2D messages expiring on ${label:resource_name} |
290
+| [ am_iot_hub_c2d_methods_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_methods | IoT Hub direct method failures on ${label:resource_name} |
291
+| [ am_iot_hub_c2d_twin_read_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_twin_reads | IoT Hub backend twin read failures on ${label:resource_name} |
292
+| [ am_iot_hub_c2d_twin_update_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_twin_updates | IoT Hub backend twin update failures on ${label:resource_name} |
293
+| [ am_iot_hub_d2c_twin_read_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.d2c_twin_reads | IoT Hub device twin read failures on ${label:resource_name} |
294
+| [ am_iot_hub_d2c_twin_update_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.d2c_twin_updates | IoT Hub device twin update failures on ${label:resource_name} |
295
+| [ am_iot_hub_routing_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_deliveries | IoT Hub routing dropped messages on ${label:resource_name} |
296
+| [ am_iot_hub_routing_orphaned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_deliveries | IoT Hub routing orphaned messages on ${label:resource_name} |
297
+| [ am_iot_hub_routing_invalid ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_deliveries | IoT Hub routing invalid messages on ${label:resource_name} |
298
+| [ am_iot_hub_routing_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_latency | IoT Hub routing latency on ${label:resource_name} |
299
+| [ am_iot_hub_event_grid_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.event_grid_latency | IoT Hub Event Grid latency on ${label:resource_name} |
300
+| [ am_iot_hub_jobs_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.jobs_status | IoT Hub job failures on ${label:resource_name} |
301
+| [ am_iot_hub_twin_query_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.twin_queries | IoT Hub twin query failures on ${label:resource_name} |
302
+| [ am_iot_hub_c2d_commands_abandoned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_commands | IoT Hub C2D commands abandoned on ${label:resource_name} |
303
+| [ am_iot_hub_c2d_commands_rejected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.c2d_commands | IoT Hub C2D commands rejected on ${label:resource_name} |
304
+| [ am_iot_hub_routing_delivery_latency_preview ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_iot_hub.conf) | azure_monitor.iot_hub.routing_delivery_latency_preview | IoT Hub routing delivery latency on ${label:resource_name} |
305
+
306
+
307
+## Metrics
308
+
309
+Metrics grouped by *scope*.
310
+
311
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
312
+
313
+
314
+
315
+### Per resource
316
+
317
+These metrics refer to each monitored Azure resource.
318
+
319
+Labels:
320
+
321
+| Label | Description |
322
+|:-----------|:----------------|
323
+| resource_name | The Azure resource name. |
324
+| resource_group | The Azure resource group. |
325
+| region | The Azure region where the resource is deployed. |
326
+| resource_type | The Azure resource type identifier. |
327
+| profile | The Azure Monitor profile id. |
328
+| resource_uid | The unique Azure resource identifier. |
329
+
330
+Metrics:
331
+
332
+| Metric | Dimensions | Unit |
333
+|:------|:----------|:----|
334
+| azure_monitor.iot_hub.c2d_commands | completed, abandoned, rejected | messages/s |
335
+| azure_monitor.iot_hub.c2d_messages_expired | expired | messages/s |
336
+| azure_monitor.iot_hub.c2d_methods | successful, failed | invocations/s |
337
+| azure_monitor.iot_hub.c2d_methods_request_size | average | bytes |
338
+| azure_monitor.iot_hub.c2d_methods_response_size | average | bytes |
339
+| azure_monitor.iot_hub.c2d_twin_reads | successful, failed | operations/s |
340
+| azure_monitor.iot_hub.c2d_twin_read_size | average | bytes |
341
+| azure_monitor.iot_hub.c2d_twin_updates | successful, failed | operations/s |
342
+| azure_monitor.iot_hub.c2d_twin_update_size | average | bytes |
343
+| azure_monitor.iot_hub.d2c_telemetry | attempted, sent | messages/s |
344
+| azure_monitor.iot_hub.d2c_telemetry_throttle | throttled | errors/s |
345
+| azure_monitor.iot_hub.d2c_twin_reads | successful, failed | operations/s |
346
+| azure_monitor.iot_hub.d2c_twin_read_size | average | bytes |
347
+| azure_monitor.iot_hub.d2c_twin_updates | successful, failed | operations/s |
348
+| azure_monitor.iot_hub.d2c_twin_update_size | average | bytes |
349
+| azure_monitor.iot_hub.routing_deliveries | delivered, dropped, orphaned, invalid, fallback | messages/s |
350
+| azure_monitor.iot_hub.routing_delivery_by_endpoint | builtin_events, event_hubs, service_bus_queues, service_bus_topics, storage | messages/s |
351
+| azure_monitor.iot_hub.routing_storage_blobs | blobs | blobs/s |
352
+| azure_monitor.iot_hub.routing_storage_data | bytes | bytes/s |
353
+| azure_monitor.iot_hub.routing_latency | builtin_events, event_hubs, service_bus_queues, service_bus_topics, storage | milliseconds |
354
+| azure_monitor.iot_hub.routing_deliveries_preview | deliveries | deliveries/s |
355
+| azure_monitor.iot_hub.routing_delivery_latency_preview | average | milliseconds |
356
+| azure_monitor.iot_hub.routing_data_size_preview | bytes | bytes/s |
357
+| azure_monitor.iot_hub.connections | successful | connections/s |
358
+| azure_monitor.iot_hub.connected_devices | connected | devices |
359
+| azure_monitor.iot_hub.total_devices | total | devices |
360
+| azure_monitor.iot_hub.daily_message_quota | used | messages |
361
+| azure_monitor.iot_hub.data_usage | data_usage, data_usage_v2 | bytes/s |
362
+| azure_monitor.iot_hub.configurations | operations | operations/s |
363
+| azure_monitor.iot_hub.event_grid_deliveries | deliveries | deliveries/s |
364
+| azure_monitor.iot_hub.event_grid_latency | average | milliseconds |
365
+| azure_monitor.iot_hub.jobs_status | completed, failed | operations/s |
366
+| azure_monitor.iot_hub.jobs_cancel | successful, failed | operations/s |
367
+| azure_monitor.iot_hub.jobs_create_method | successful, failed | operations/s |
368
+| azure_monitor.iot_hub.jobs_create_twin_update | successful, failed | operations/s |
369
+| azure_monitor.iot_hub.jobs_list | successful, failed | operations/s |
370
+| azure_monitor.iot_hub.jobs_query | successful, failed | operations/s |
371
+| azure_monitor.iot_hub.twin_queries | successful, failed | queries/s |
372
+| azure_monitor.iot_hub.twin_queries_result_size | average | bytes |
373
+
374
+
375
+
376
## Troubleshooting
377
378
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_key_vault.md
+46
-46
@@ -57,52 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.key_vault.availability | average | percentage |
88
-| azure_monitor.key_vault.api_latency | average | milliseconds |
89
-| azure_monitor.key_vault.saturation | average | percentage |
90
-| azure_monitor.key_vault.api_activity | hits, results | operations/s |
91
-
92
-
93
-
94
-## Alerts
95
-
96
-
97
-The following alerts are available:
98
-
99
-| Alert name | On metric | Description |
100
-|:------------|:----------|:------------|
101
-| [ am_key_vault_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf) | azure_monitor.key_vault.availability | Key Vault availability on ${label:resource_name} |
102
-| [ am_key_vault_api_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf) | azure_monitor.key_vault.api_latency | Key Vault API latency on ${label:resource_name} |
103
-| [ am_key_vault_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf) | azure_monitor.key_vault.saturation | Key Vault saturation on ${label:resource_name} |
104
-
105
-
60
## Setup
61
62
@@ -324,6 +278,52 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_key_vault_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf) | azure_monitor.key_vault.availability | Key Vault availability on ${label:resource_name} |
289
+| [ am_key_vault_api_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf) | azure_monitor.key_vault.api_latency | Key Vault API latency on ${label:resource_name} |
290
+| [ am_key_vault_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_key_vault.conf) | azure_monitor.key_vault.saturation | Key Vault saturation on ${label:resource_name} |
291
+
292
+
293
+## Metrics
294
+
295
+Metrics grouped by *scope*.
296
+
297
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
298
+
299
+
300
+
301
+### Per resource
302
+
303
+These metrics refer to each monitored Azure resource.
304
+
305
+Labels:
306
+
307
+| Label | Description |
308
+|:-----------|:----------------|
309
+| resource_name | The Azure resource name. |
310
+| resource_group | The Azure resource group. |
311
+| region | The Azure region where the resource is deployed. |
312
+| resource_type | The Azure resource type identifier. |
313
+| profile | The Azure Monitor profile id. |
314
+| resource_uid | The unique Azure resource identifier. |
315
+
316
+Metrics:
317
+
318
+| Metric | Dimensions | Unit |
319
+|:------|:----------|:----|
320
+| azure_monitor.key_vault.availability | average | percentage |
321
+| azure_monitor.key_vault.api_latency | average | milliseconds |
322
+| azure_monitor.key_vault.saturation | average | percentage |
323
+| azure_monitor.key_vault.api_activity | hits, results | operations/s |
324
+
325
+
326
+
327
## Troubleshooting
328
329
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_kubernetes_service_cluster.md
+74
-74
@@ -57,80 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.aks.apiserver_cpu | average, maximum | percentage |
88
-| azure_monitor.aks.apiserver_memory | average, maximum | percentage |
89
-| azure_monitor.aks.apiserver_inflight_requests | average | requests |
90
-| azure_monitor.aks.etcd_cpu | average, maximum | percentage |
91
-| azure_monitor.aks.etcd_memory | average, maximum | percentage |
92
-| azure_monitor.aks.etcd_database | average, maximum | percentage |
93
-| azure_monitor.aks.pod_status_phase | average | pods |
94
-| azure_monitor.aks.pod_status_ready | average | pods |
95
-| azure_monitor.aks.allocatable_cpu | average | cores |
96
-| azure_monitor.aks.allocatable_memory | average | bytes |
97
-| azure_monitor.aks.node_conditions | average | nodes |
98
-| azure_monitor.aks.autoscaler_health | safe_to_autoscale, cooldown | state |
99
-| azure_monitor.aks.autoscaler_unschedulable_pods | average | pods |
100
-| azure_monitor.aks.autoscaler_unneeded_nodes | average | nodes |
101
-| azure_monitor.aks.node_cpu_millicores | average, maximum | millicores |
102
-| azure_monitor.aks.node_cpu_percentage | average, maximum | percentage |
103
-| azure_monitor.aks.node_memory_working_set | average, maximum | bytes |
104
-| azure_monitor.aks.node_memory_working_set_percentage | average, maximum | percentage |
105
-| azure_monitor.aks.node_memory_rss | average, maximum | bytes |
106
-| azure_monitor.aks.node_memory_rss_percentage | average, maximum | percentage |
107
-| azure_monitor.aks.node_disk_usage | average, maximum | bytes |
108
-| azure_monitor.aks.node_disk_percentage | average, maximum | percentage |
109
-| azure_monitor.aks.node_network | in, out | bytes |
110
-
111
-
112
-
113
-## Alerts
114
-
115
-
116
-The following alerts are available:
117
-
118
-| Alert name | On metric | Description |
119
-|:------------|:----------|:------------|
120
-| [ am_aks_apiserver_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.apiserver_cpu | AKS API server CPU on ${label:resource_name} |
121
-| [ am_aks_apiserver_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.apiserver_memory | AKS API server memory on ${label:resource_name} |
122
-| [ am_aks_apiserver_inflight_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.apiserver_inflight_requests | AKS API server inflight requests on ${label:resource_name} |
123
-| [ am_aks_etcd_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.etcd_cpu | AKS etcd CPU on ${label:resource_name} |
124
-| [ am_aks_etcd_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.etcd_memory | AKS etcd memory on ${label:resource_name} |
125
-| [ am_aks_etcd_database ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.etcd_database | AKS etcd database usage on ${label:resource_name} |
126
-| [ am_aks_autoscaler_safe_to_autoscale ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.autoscaler_health | AKS autoscaler unsafe on ${label:resource_name} |
127
-| [ am_aks_autoscaler_unschedulable_pods ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.autoscaler_unschedulable_pods | AKS unschedulable pods on ${label:resource_name} |
128
-| [ am_aks_node_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_cpu_percentage | AKS node CPU on ${label:resource_name} |
129
-| [ am_aks_node_memory_working_set ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_memory_working_set_percentage | AKS node memory working set on ${label:resource_name} |
130
-| [ am_aks_node_memory_rss ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_memory_rss_percentage | AKS node memory RSS on ${label:resource_name} |
131
-| [ am_aks_node_disk ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_disk_percentage | AKS node disk usage on ${label:resource_name} |
132
-
133
-
60
## Setup
61
62
@@ -352,6 +278,80 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_aks_apiserver_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.apiserver_cpu | AKS API server CPU on ${label:resource_name} |
289
+| [ am_aks_apiserver_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.apiserver_memory | AKS API server memory on ${label:resource_name} |
290
+| [ am_aks_apiserver_inflight_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.apiserver_inflight_requests | AKS API server inflight requests on ${label:resource_name} |
291
+| [ am_aks_etcd_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.etcd_cpu | AKS etcd CPU on ${label:resource_name} |
292
+| [ am_aks_etcd_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.etcd_memory | AKS etcd memory on ${label:resource_name} |
293
+| [ am_aks_etcd_database ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.etcd_database | AKS etcd database usage on ${label:resource_name} |
294
+| [ am_aks_autoscaler_safe_to_autoscale ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.autoscaler_health | AKS autoscaler unsafe on ${label:resource_name} |
295
+| [ am_aks_autoscaler_unschedulable_pods ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.autoscaler_unschedulable_pods | AKS unschedulable pods on ${label:resource_name} |
296
+| [ am_aks_node_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_cpu_percentage | AKS node CPU on ${label:resource_name} |
297
+| [ am_aks_node_memory_working_set ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_memory_working_set_percentage | AKS node memory working set on ${label:resource_name} |
298
+| [ am_aks_node_memory_rss ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_memory_rss_percentage | AKS node memory RSS on ${label:resource_name} |
299
+| [ am_aks_node_disk ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_aks.conf) | azure_monitor.aks.node_disk_percentage | AKS node disk usage on ${label:resource_name} |
300
+
301
+
302
+## Metrics
303
+
304
+Metrics grouped by *scope*.
305
+
306
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
307
+
308
+
309
+
310
+### Per resource
311
+
312
+These metrics refer to each monitored Azure resource.
313
+
314
+Labels:
315
+
316
+| Label | Description |
317
+|:-----------|:----------------|
318
+| resource_name | The Azure resource name. |
319
+| resource_group | The Azure resource group. |
320
+| region | The Azure region where the resource is deployed. |
321
+| resource_type | The Azure resource type identifier. |
322
+| profile | The Azure Monitor profile id. |
323
+| resource_uid | The unique Azure resource identifier. |
324
+
325
+Metrics:
326
+
327
+| Metric | Dimensions | Unit |
328
+|:------|:----------|:----|
329
+| azure_monitor.aks.apiserver_cpu | average, maximum | percentage |
330
+| azure_monitor.aks.apiserver_memory | average, maximum | percentage |
331
+| azure_monitor.aks.apiserver_inflight_requests | average | requests |
332
+| azure_monitor.aks.etcd_cpu | average, maximum | percentage |
333
+| azure_monitor.aks.etcd_memory | average, maximum | percentage |
334
+| azure_monitor.aks.etcd_database | average, maximum | percentage |
335
+| azure_monitor.aks.pod_status_phase | average | pods |
336
+| azure_monitor.aks.pod_status_ready | average | pods |
337
+| azure_monitor.aks.allocatable_cpu | average | cores |
338
+| azure_monitor.aks.allocatable_memory | average | bytes |
339
+| azure_monitor.aks.node_conditions | average | nodes |
340
+| azure_monitor.aks.autoscaler_health | safe_to_autoscale, cooldown | state |
341
+| azure_monitor.aks.autoscaler_unschedulable_pods | average | pods |
342
+| azure_monitor.aks.autoscaler_unneeded_nodes | average | nodes |
343
+| azure_monitor.aks.node_cpu_millicores | average, maximum | millicores |
344
+| azure_monitor.aks.node_cpu_percentage | average, maximum | percentage |
345
+| azure_monitor.aks.node_memory_working_set | average, maximum | bytes |
346
+| azure_monitor.aks.node_memory_working_set_percentage | average, maximum | percentage |
347
+| azure_monitor.aks.node_memory_rss | average, maximum | bytes |
348
+| azure_monitor.aks.node_memory_rss_percentage | average, maximum | percentage |
349
+| azure_monitor.aks.node_disk_usage | average, maximum | bytes |
350
+| azure_monitor.aks.node_disk_percentage | average, maximum | percentage |
351
+| azure_monitor.aks.node_network | in, out | bytes |
352
+
353
+
354
+
355
## Troubleshooting
356
357
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_load_balancer.md
+51
-51
@@ -57,57 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.load_balancers.vip_availability | average | percentage |
88
-| azure_monitor.load_balancers.dip_availability | average | percentage |
89
-| azure_monitor.load_balancers.global_backend_availability | average | percentage |
90
-| azure_monitor.load_balancers.byte_throughput | total | bytes/s |
91
-| azure_monitor.load_balancers.packet_throughput | total | packets/s |
92
-| azure_monitor.load_balancers.syn_count | total | packets/s |
93
-| azure_monitor.load_balancers.snat_connections | total | connections/s |
94
-| azure_monitor.load_balancers.snat_ports | allocated, used | ports |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-
101
-The following alerts are available:
102
-
103
-| Alert name | On metric | Description |
104
-|:------------|:----------|:------------|
105
-| [ am_load_balancers_vip_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.vip_availability | LB data path availability on ${label:resource_name} |
106
-| [ am_load_balancers_dip_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.dip_availability | LB health probe status on ${label:resource_name} |
107
-| [ am_load_balancers_global_backend_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.global_backend_availability | LB global backend availability on ${label:resource_name} |
108
-| [ am_load_balancers_snat_port_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.snat_ports | LB SNAT port utilization on ${label:resource_name} |
109
-
110
-
60
## Setup
61
62
@@ -329,6 +278,57 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_load_balancers_vip_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.vip_availability | LB data path availability on ${label:resource_name} |
289
+| [ am_load_balancers_dip_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.dip_availability | LB health probe status on ${label:resource_name} |
290
+| [ am_load_balancers_global_backend_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.global_backend_availability | LB global backend availability on ${label:resource_name} |
291
+| [ am_load_balancers_snat_port_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_load_balancers.conf) | azure_monitor.load_balancers.snat_ports | LB SNAT port utilization on ${label:resource_name} |
292
+
293
+
294
+## Metrics
295
+
296
+Metrics grouped by *scope*.
297
+
298
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
299
+
300
+
301
+
302
+### Per resource
303
+
304
+These metrics refer to each monitored Azure resource.
305
+
306
+Labels:
307
+
308
+| Label | Description |
309
+|:-----------|:----------------|
310
+| resource_name | The Azure resource name. |
311
+| resource_group | The Azure resource group. |
312
+| region | The Azure region where the resource is deployed. |
313
+| resource_type | The Azure resource type identifier. |
314
+| profile | The Azure Monitor profile id. |
315
+| resource_uid | The unique Azure resource identifier. |
316
+
317
+Metrics:
318
+
319
+| Metric | Dimensions | Unit |
320
+|:------|:----------|:----|
321
+| azure_monitor.load_balancers.vip_availability | average | percentage |
322
+| azure_monitor.load_balancers.dip_availability | average | percentage |
323
+| azure_monitor.load_balancers.global_backend_availability | average | percentage |
324
+| azure_monitor.load_balancers.byte_throughput | total | bytes/s |
325
+| azure_monitor.load_balancers.packet_throughput | total | packets/s |
326
+| azure_monitor.load_balancers.syn_count | total | packets/s |
327
+| azure_monitor.load_balancers.snat_connections | total | connections/s |
328
+| azure_monitor.load_balancers.snat_ports | allocated, used | ports |
329
+
330
+
331
+
332
## Troubleshooting
333
334
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_log_analytics_workspace.md
+90
-90
@@ -57,96 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.log_analytics.query_availability | availability | percentage |
88
-| azure_monitor.log_analytics.ingestion_latency | average, maximum, minimum | seconds |
89
-| azure_monitor.log_analytics.ingestion_volume | records | records/s |
90
-| azure_monitor.log_analytics.queries | total, failed | queries/s |
91
-| azure_monitor.log_analytics.export_data | exported | bytes/s |
92
-| azure_monitor.log_analytics.export_records | exported | records/s |
93
-| azure_monitor.log_analytics.export_failures | failed | exports/s |
94
-| azure_monitor.log_analytics.legacy_cpu_utilization | processor, privileged, user, idle | percentage |
95
-| azure_monitor.log_analytics.legacy_cpu_detailed | dpc, interrupt, io_wait, nice | percentage |
96
-| azure_monitor.log_analytics.legacy_cpu_pct | privileged, user | percentage |
97
-| azure_monitor.log_analytics.legacy_memory_utilization | available, used, committed | percentage |
98
-| azure_monitor.log_analytics.legacy_memory_available | available_mbytes, available_mbytes_memory | megabytes |
99
-| azure_monitor.log_analytics.legacy_memory_used_kbytes | used | kilobytes |
100
-| azure_monitor.log_analytics.legacy_memory_used_mbytes | used | megabytes |
101
-| azure_monitor.log_analytics.legacy_memory_free | physical, virtual, shared | megabytes |
102
-| azure_monitor.log_analytics.legacy_swap_utilization | available, used | percentage |
103
-| azure_monitor.log_analytics.legacy_swap_size | available, used | megabytes |
104
-| azure_monitor.log_analytics.legacy_disk_space_utilization | free, used | percentage |
105
-| azure_monitor.log_analytics.legacy_disk_inodes | free, used | percentage |
106
-| azure_monitor.log_analytics.legacy_disk_free | free | megabytes |
107
-| azure_monitor.log_analytics.legacy_disk_io_throughput | read, write, logical, physical | bytes/s |
108
-| azure_monitor.log_analytics.legacy_disk_io_operations | reads, writes, transfers | operations/s |
109
-| azure_monitor.log_analytics.legacy_disk_io_latency | read, write, transfer | seconds |
110
-| azure_monitor.log_analytics.legacy_disk_queue | queue_length | operations |
111
-| azure_monitor.log_analytics.legacy_paging | reads, writes, total | pages/s |
112
-| azure_monitor.log_analytics.legacy_paging_files | free, stored | megabytes |
113
-| azure_monitor.log_analytics.legacy_network_throughput_win | received, sent, total | bytes/s |
114
-| azure_monitor.log_analytics.legacy_network_traffic | total, received, transmitted | bytes |
115
-| azure_monitor.log_analytics.legacy_network_packets | received, transmitted | packets |
116
-| azure_monitor.log_analytics.legacy_network_errors | rx, tx, collisions | errors |
117
-| azure_monitor.log_analytics.legacy_system | processes | processes |
118
-| azure_monitor.log_analytics.legacy_processor_queue | queue_length | threads |
119
-| azure_monitor.log_analytics.legacy_uptime | uptime | seconds |
120
-| azure_monitor.log_analytics.legacy_users | users | users |
121
-| azure_monitor.log_analytics.legacy_events | events | events/s |
122
-| azure_monitor.log_analytics.legacy_heartbeat | heartbeats | heartbeats/s |
123
-| azure_monitor.log_analytics.legacy_updates | updates | updates |
124
-
125
-
126
-
127
-## Alerts
128
-
129
-
130
-The following alerts are available:
131
-
132
-| Alert name | On metric | Description |
133
-|:------------|:----------|:------------|
134
-| [ am_log_analytics_query_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.query_availability | Log Analytics query availability on ${label:resource_name} |
135
-| [ am_log_analytics_ingestion_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.ingestion_latency | Log Analytics ingestion latency on ${label:resource_name} |
136
-| [ am_log_analytics_query_failure_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.queries | Log Analytics query failures on ${label:resource_name} |
137
-| [ am_log_analytics_export_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.export_failures | Log Analytics export failures on ${label:resource_name} |
138
-| [ am_log_analytics_legacy_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_cpu_utilization | Legacy agent CPU on ${label:resource_name} |
139
-| [ am_log_analytics_legacy_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_memory_utilization | Legacy agent memory on ${label:resource_name} |
140
-| [ am_log_analytics_legacy_swap ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_swap_utilization | Legacy agent swap usage on ${label:resource_name} |
141
-| [ am_log_analytics_legacy_disk_space ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_space_utilization | Legacy agent disk space on ${label:resource_name} |
142
-| [ am_log_analytics_legacy_disk_inodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_inodes | Legacy agent inode usage on ${label:resource_name} |
143
-| [ am_log_analytics_legacy_disk_read_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_io_latency | Legacy agent disk read latency on ${label:resource_name} |
144
-| [ am_log_analytics_legacy_disk_write_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_io_latency | Legacy agent disk write latency on ${label:resource_name} |
145
-| [ am_log_analytics_legacy_disk_queue ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_queue | Legacy agent disk queue on ${label:resource_name} |
146
-| [ am_log_analytics_legacy_network_rx_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_network_errors | Legacy agent network RX errors on ${label:resource_name} |
147
-| [ am_log_analytics_legacy_network_tx_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_network_errors | Legacy agent network TX errors on ${label:resource_name} |
148
-
149
-
60
## Setup
61
62
@@ -368,6 +278,96 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_log_analytics_query_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.query_availability | Log Analytics query availability on ${label:resource_name} |
289
+| [ am_log_analytics_ingestion_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.ingestion_latency | Log Analytics ingestion latency on ${label:resource_name} |
290
+| [ am_log_analytics_query_failure_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.queries | Log Analytics query failures on ${label:resource_name} |
291
+| [ am_log_analytics_export_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.export_failures | Log Analytics export failures on ${label:resource_name} |
292
+| [ am_log_analytics_legacy_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_cpu_utilization | Legacy agent CPU on ${label:resource_name} |
293
+| [ am_log_analytics_legacy_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_memory_utilization | Legacy agent memory on ${label:resource_name} |
294
+| [ am_log_analytics_legacy_swap ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_swap_utilization | Legacy agent swap usage on ${label:resource_name} |
295
+| [ am_log_analytics_legacy_disk_space ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_space_utilization | Legacy agent disk space on ${label:resource_name} |
296
+| [ am_log_analytics_legacy_disk_inodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_inodes | Legacy agent inode usage on ${label:resource_name} |
297
+| [ am_log_analytics_legacy_disk_read_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_io_latency | Legacy agent disk read latency on ${label:resource_name} |
298
+| [ am_log_analytics_legacy_disk_write_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_io_latency | Legacy agent disk write latency on ${label:resource_name} |
299
+| [ am_log_analytics_legacy_disk_queue ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_disk_queue | Legacy agent disk queue on ${label:resource_name} |
300
+| [ am_log_analytics_legacy_network_rx_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_network_errors | Legacy agent network RX errors on ${label:resource_name} |
301
+| [ am_log_analytics_legacy_network_tx_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_log_analytics.conf) | azure_monitor.log_analytics.legacy_network_errors | Legacy agent network TX errors on ${label:resource_name} |
302
+
303
+
304
+## Metrics
305
+
306
+Metrics grouped by *scope*.
307
+
308
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
309
+
310
+
311
+
312
+### Per resource
313
+
314
+These metrics refer to each monitored Azure resource.
315
+
316
+Labels:
317
+
318
+| Label | Description |
319
+|:-----------|:----------------|
320
+| resource_name | The Azure resource name. |
321
+| resource_group | The Azure resource group. |
322
+| region | The Azure region where the resource is deployed. |
323
+| resource_type | The Azure resource type identifier. |
324
+| profile | The Azure Monitor profile id. |
325
+| resource_uid | The unique Azure resource identifier. |
326
+
327
+Metrics:
328
+
329
+| Metric | Dimensions | Unit |
330
+|:------|:----------|:----|
331
+| azure_monitor.log_analytics.query_availability | availability | percentage |
332
+| azure_monitor.log_analytics.ingestion_latency | average, maximum, minimum | seconds |
333
+| azure_monitor.log_analytics.ingestion_volume | records | records/s |
334
+| azure_monitor.log_analytics.queries | total, failed | queries/s |
335
+| azure_monitor.log_analytics.export_data | exported | bytes/s |
336
+| azure_monitor.log_analytics.export_records | exported | records/s |
337
+| azure_monitor.log_analytics.export_failures | failed | exports/s |
338
+| azure_monitor.log_analytics.legacy_cpu_utilization | processor, privileged, user, idle | percentage |
339
+| azure_monitor.log_analytics.legacy_cpu_detailed | dpc, interrupt, io_wait, nice | percentage |
340
+| azure_monitor.log_analytics.legacy_cpu_pct | privileged, user | percentage |
341
+| azure_monitor.log_analytics.legacy_memory_utilization | available, used, committed | percentage |
342
+| azure_monitor.log_analytics.legacy_memory_available | available_mbytes, available_mbytes_memory | megabytes |
343
+| azure_monitor.log_analytics.legacy_memory_used_kbytes | used | kilobytes |
344
+| azure_monitor.log_analytics.legacy_memory_used_mbytes | used | megabytes |
345
+| azure_monitor.log_analytics.legacy_memory_free | physical, virtual, shared | megabytes |
346
+| azure_monitor.log_analytics.legacy_swap_utilization | available, used | percentage |
347
+| azure_monitor.log_analytics.legacy_swap_size | available, used | megabytes |
348
+| azure_monitor.log_analytics.legacy_disk_space_utilization | free, used | percentage |
349
+| azure_monitor.log_analytics.legacy_disk_inodes | free, used | percentage |
350
+| azure_monitor.log_analytics.legacy_disk_free | free | megabytes |
351
+| azure_monitor.log_analytics.legacy_disk_io_throughput | read, write, logical, physical | bytes/s |
352
+| azure_monitor.log_analytics.legacy_disk_io_operations | reads, writes, transfers | operations/s |
353
+| azure_monitor.log_analytics.legacy_disk_io_latency | read, write, transfer | seconds |
354
+| azure_monitor.log_analytics.legacy_disk_queue | queue_length | operations |
355
+| azure_monitor.log_analytics.legacy_paging | reads, writes, total | pages/s |
356
+| azure_monitor.log_analytics.legacy_paging_files | free, stored | megabytes |
357
+| azure_monitor.log_analytics.legacy_network_throughput_win | received, sent, total | bytes/s |
358
+| azure_monitor.log_analytics.legacy_network_traffic | total, received, transmitted | bytes |
359
+| azure_monitor.log_analytics.legacy_network_packets | received, transmitted | packets |
360
+| azure_monitor.log_analytics.legacy_network_errors | rx, tx, collisions | errors |
361
+| azure_monitor.log_analytics.legacy_system | processes | processes |
362
+| azure_monitor.log_analytics.legacy_processor_queue | queue_length | threads |
363
+| azure_monitor.log_analytics.legacy_uptime | uptime | seconds |
364
+| azure_monitor.log_analytics.legacy_users | users | users |
365
+| azure_monitor.log_analytics.legacy_events | events | events/s |
366
+| azure_monitor.log_analytics.legacy_heartbeat | heartbeats | heartbeats/s |
367
+| azure_monitor.log_analytics.legacy_updates | updates | updates |
368
+
369
+
370
+
371
## Troubleshooting
372
373
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_logic_apps_workflow.md
+64
-64
@@ -57,70 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.logic_apps.run_lifecycle | started, completed, succeeded, failed, cancelled | runs/s |
88
-| azure_monitor.logic_apps.run_latency | all, success | seconds |
89
-| azure_monitor.logic_apps.run_failure_rate | failure_rate | percentage |
90
-| azure_monitor.logic_apps.run_throttling | during_run, at_start | events/s |
91
-| azure_monitor.logic_apps.action_lifecycle | started, completed, succeeded, failed, skipped | actions/s |
92
-| azure_monitor.logic_apps.action_latency | all, success | seconds |
93
-| azure_monitor.logic_apps.action_throttling | total | events/s |
94
-| azure_monitor.logic_apps.trigger_lifecycle | started, completed, succeeded, fired, failed, skipped | triggers/s |
95
-| azure_monitor.logic_apps.trigger_latency | all, fire, success | seconds |
96
-| azure_monitor.logic_apps.trigger_throttling | total | events/s |
97
-| azure_monitor.logic_apps.billable_executions | total, actions, triggers | executions/s |
98
-| azure_monitor.logic_apps.billing_by_type | native, standard_connector, storage | operations/s |
99
-| azure_monitor.logic_apps.agent | loop_executions, completion_overflow, prompt_overflow | events/s |
100
-
101
-
102
-
103
-## Alerts
104
-
105
-
106
-The following alerts are available:
107
-
108
-| Alert name | On metric | Description |
109
-|:------------|:----------|:------------|
110
-| [ am_logic_apps_run_failure_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_failure_rate | Logic Apps run failure rate on ${label:resource_name} |
111
-| [ am_logic_apps_runs_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_lifecycle | Logic Apps failed runs on ${label:resource_name} |
112
-| [ am_logic_apps_run_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_latency | Logic Apps run latency on ${label:resource_name} |
113
-| [ am_logic_apps_run_throttled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_throttling | Logic Apps run throttling on ${label:resource_name} |
114
-| [ am_logic_apps_actions_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.action_lifecycle | Logic Apps failed actions on ${label:resource_name} |
115
-| [ am_logic_apps_action_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.action_latency | Logic Apps action latency on ${label:resource_name} |
116
-| [ am_logic_apps_action_throttled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.action_throttling | Logic Apps action throttling on ${label:resource_name} |
117
-| [ am_logic_apps_triggers_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.trigger_lifecycle | Logic Apps failed triggers on ${label:resource_name} |
118
-| [ am_logic_apps_trigger_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.trigger_latency | Logic Apps trigger latency on ${label:resource_name} |
119
-| [ am_logic_apps_trigger_throttled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.trigger_throttling | Logic Apps trigger throttling on ${label:resource_name} |
120
-| [ am_logic_apps_completion_token_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.agent | Logic Apps completion token overflow on ${label:resource_name} |
121
-| [ am_logic_apps_prompt_token_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.agent | Logic Apps prompt token overflow on ${label:resource_name} |
122
-
123
-
60
## Setup
61
62
@@ -342,6 +278,70 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_logic_apps_run_failure_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_failure_rate | Logic Apps run failure rate on ${label:resource_name} |
289
+| [ am_logic_apps_runs_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_lifecycle | Logic Apps failed runs on ${label:resource_name} |
290
+| [ am_logic_apps_run_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_latency | Logic Apps run latency on ${label:resource_name} |
291
+| [ am_logic_apps_run_throttled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.run_throttling | Logic Apps run throttling on ${label:resource_name} |
292
+| [ am_logic_apps_actions_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.action_lifecycle | Logic Apps failed actions on ${label:resource_name} |
293
+| [ am_logic_apps_action_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.action_latency | Logic Apps action latency on ${label:resource_name} |
294
+| [ am_logic_apps_action_throttled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.action_throttling | Logic Apps action throttling on ${label:resource_name} |
295
+| [ am_logic_apps_triggers_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.trigger_lifecycle | Logic Apps failed triggers on ${label:resource_name} |
296
+| [ am_logic_apps_trigger_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.trigger_latency | Logic Apps trigger latency on ${label:resource_name} |
297
+| [ am_logic_apps_trigger_throttled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.trigger_throttling | Logic Apps trigger throttling on ${label:resource_name} |
298
+| [ am_logic_apps_completion_token_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.agent | Logic Apps completion token overflow on ${label:resource_name} |
299
+| [ am_logic_apps_prompt_token_overflow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_logic_apps.conf) | azure_monitor.logic_apps.agent | Logic Apps prompt token overflow on ${label:resource_name} |
300
+
301
+
302
+## Metrics
303
+
304
+Metrics grouped by *scope*.
305
+
306
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
307
+
308
+
309
+
310
+### Per resource
311
+
312
+These metrics refer to each monitored Azure resource.
313
+
314
+Labels:
315
+
316
+| Label | Description |
317
+|:-----------|:----------------|
318
+| resource_name | The Azure resource name. |
319
+| resource_group | The Azure resource group. |
320
+| region | The Azure region where the resource is deployed. |
321
+| resource_type | The Azure resource type identifier. |
322
+| profile | The Azure Monitor profile id. |
323
+| resource_uid | The unique Azure resource identifier. |
324
+
325
+Metrics:
326
+
327
+| Metric | Dimensions | Unit |
328
+|:------|:----------|:----|
329
+| azure_monitor.logic_apps.run_lifecycle | started, completed, succeeded, failed, cancelled | runs/s |
330
+| azure_monitor.logic_apps.run_latency | all, success | seconds |
331
+| azure_monitor.logic_apps.run_failure_rate | failure_rate | percentage |
332
+| azure_monitor.logic_apps.run_throttling | during_run, at_start | events/s |
333
+| azure_monitor.logic_apps.action_lifecycle | started, completed, succeeded, failed, skipped | actions/s |
334
+| azure_monitor.logic_apps.action_latency | all, success | seconds |
335
+| azure_monitor.logic_apps.action_throttling | total | events/s |
336
+| azure_monitor.logic_apps.trigger_lifecycle | started, completed, succeeded, fired, failed, skipped | triggers/s |
337
+| azure_monitor.logic_apps.trigger_latency | all, fire, success | seconds |
338
+| azure_monitor.logic_apps.trigger_throttling | total | events/s |
339
+| azure_monitor.logic_apps.billable_executions | total, actions, triggers | executions/s |
340
+| azure_monitor.logic_apps.billing_by_type | native, standard_connector, storage | operations/s |
341
+| azure_monitor.logic_apps.agent | loop_executions, completion_overflow, prompt_overflow | events/s |
342
+
343
+
344
+
345
## Troubleshooting
346
347
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_machine_learning_workspace.md
+84
-84
@@ -57,90 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.machine_learning.agent_events | agent_events, thread_events | events/s |
88
-| azure_monitor.machine_learning.agent_messages | messages | messages/s |
89
-| azure_monitor.machine_learning.agent_runs | runs | runs/s |
90
-| azure_monitor.machine_learning.agent_tokens | tokens | tokens/s |
91
-| azure_monitor.machine_learning.agent_tool_calls | tool_calls | calls/s |
92
-| azure_monitor.machine_learning.agent_indexed_files | indexed_files | files/s |
93
-| azure_monitor.machine_learning.model_deployments | started, succeeded, failed | deployments/s |
94
-| azure_monitor.machine_learning.model_registrations | succeeded, failed | registrations/s |
95
-| azure_monitor.machine_learning.cluster_cores | active, idle, leaving, preempted, unusable | cores |
96
-| azure_monitor.machine_learning.total_cores | total | cores |
97
-| azure_monitor.machine_learning.cluster_nodes | active, idle, leaving, preempted, unusable | nodes |
98
-| azure_monitor.machine_learning.total_nodes | total | nodes |
99
-| azure_monitor.machine_learning.quota_utilization | utilization | percentage |
100
-| azure_monitor.machine_learning.cpu_utilization | cluster_cpu, node_cpu | percentage |
101
-| azure_monitor.machine_learning.cpu_millicores | used, capacity | millicores |
102
-| azure_monitor.machine_learning.cpu_memory_utilization | utilization | percentage |
103
-| azure_monitor.machine_learning.cpu_memory_megabytes | used, capacity | megabytes |
104
-| azure_monitor.machine_learning.gpu_utilization | cluster_gpu, node_gpu | percentage |
105
-| azure_monitor.machine_learning.gpu_milligpus | used, capacity | milliGPUs |
106
-| azure_monitor.machine_learning.gpu_memory_utilization | cluster_gpu_memory, node_gpu_memory | percentage |
107
-| azure_monitor.machine_learning.gpu_memory_megabytes | used, capacity | megabytes |
108
-| azure_monitor.machine_learning.gpu_energy | energy | joules/s |
109
-| azure_monitor.machine_learning.disk_usage | used, available | megabytes |
110
-| azure_monitor.machine_learning.disk_io | read, write | megabytes/s |
111
-| azure_monitor.machine_learning.network_traffic | in, out | megabytes/s |
112
-| azure_monitor.machine_learning.infiniband_traffic | receive, transmit | megabytes/s |
113
-| azure_monitor.machine_learning.storage_api_calls | success, failure | calls/s |
114
-| azure_monitor.machine_learning.run_lifecycle | not_started, starting, preparing, provisioning, queued, started | runs/s |
115
-| azure_monitor.machine_learning.run_completion | completed, failed, finalizing, cancelled, cancel_requested, not_responding | runs/s |
116
-| azure_monitor.machine_learning.run_issues | errors, warnings | events/s |
117
-
118
-
119
-
120
-## Alerts
121
-
122
-
123
-The following alerts are available:
124
-
125
-| Alert name | On metric | Description |
126
-|:------------|:----------|:------------|
127
-| [ am_ml_quota_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.quota_utilization | ML quota utilization on ${label:resource_name} |
128
-| [ am_ml_unusable_cores ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cluster_cores | ML unusable cores on ${label:resource_name} |
129
-| [ am_ml_preempted_cores ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cluster_cores | ML preempted cores on ${label:resource_name} |
130
-| [ am_ml_unusable_nodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cluster_nodes | ML unusable nodes on ${label:resource_name} |
131
-| [ am_ml_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cpu_utilization | ML CPU utilization on ${label:resource_name} |
132
-| [ am_ml_cpu_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cpu_memory_utilization | ML CPU memory utilization on ${label:resource_name} |
133
-| [ am_ml_gpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.gpu_utilization | ML GPU utilization on ${label:resource_name} |
134
-| [ am_ml_gpu_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.gpu_memory_utilization | ML GPU memory utilization on ${label:resource_name} |
135
-| [ am_ml_disk_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.disk_usage | ML disk utilization on ${label:resource_name} |
136
-| [ am_ml_model_deploy_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.model_deployments | ML model deployment failures on ${label:resource_name} |
137
-| [ am_ml_model_register_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.model_registrations | ML model registration failures on ${label:resource_name} |
138
-| [ am_ml_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.run_completion | ML failed runs on ${label:resource_name} |
139
-| [ am_ml_not_responding_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.run_completion | ML not-responding runs on ${label:resource_name} |
140
-| [ am_ml_run_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.run_issues | ML run errors on ${label:resource_name} |
141
-| [ am_ml_storage_api_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.storage_api_calls | ML storage API failure rate on ${label:resource_name} |
142
-
143
-
60
## Setup
61
62
@@ -362,6 +278,90 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_ml_quota_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.quota_utilization | ML quota utilization on ${label:resource_name} |
289
+| [ am_ml_unusable_cores ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cluster_cores | ML unusable cores on ${label:resource_name} |
290
+| [ am_ml_preempted_cores ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cluster_cores | ML preempted cores on ${label:resource_name} |
291
+| [ am_ml_unusable_nodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cluster_nodes | ML unusable nodes on ${label:resource_name} |
292
+| [ am_ml_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cpu_utilization | ML CPU utilization on ${label:resource_name} |
293
+| [ am_ml_cpu_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.cpu_memory_utilization | ML CPU memory utilization on ${label:resource_name} |
294
+| [ am_ml_gpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.gpu_utilization | ML GPU utilization on ${label:resource_name} |
295
+| [ am_ml_gpu_memory_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.gpu_memory_utilization | ML GPU memory utilization on ${label:resource_name} |
296
+| [ am_ml_disk_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.disk_usage | ML disk utilization on ${label:resource_name} |
297
+| [ am_ml_model_deploy_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.model_deployments | ML model deployment failures on ${label:resource_name} |
298
+| [ am_ml_model_register_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.model_registrations | ML model registration failures on ${label:resource_name} |
299
+| [ am_ml_failed_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.run_completion | ML failed runs on ${label:resource_name} |
300
+| [ am_ml_not_responding_runs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.run_completion | ML not-responding runs on ${label:resource_name} |
301
+| [ am_ml_run_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.run_issues | ML run errors on ${label:resource_name} |
302
+| [ am_ml_storage_api_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_machine_learning.conf) | azure_monitor.machine_learning.storage_api_calls | ML storage API failure rate on ${label:resource_name} |
303
+
304
+
305
+## Metrics
306
+
307
+Metrics grouped by *scope*.
308
+
309
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
310
+
311
+
312
+
313
+### Per resource
314
+
315
+These metrics refer to each monitored Azure resource.
316
+
317
+Labels:
318
+
319
+| Label | Description |
320
+|:-----------|:----------------|
321
+| resource_name | The Azure resource name. |
322
+| resource_group | The Azure resource group. |
323
+| region | The Azure region where the resource is deployed. |
324
+| resource_type | The Azure resource type identifier. |
325
+| profile | The Azure Monitor profile id. |
326
+| resource_uid | The unique Azure resource identifier. |
327
+
328
+Metrics:
329
+
330
+| Metric | Dimensions | Unit |
331
+|:------|:----------|:----|
332
+| azure_monitor.machine_learning.agent_events | agent_events, thread_events | events/s |
333
+| azure_monitor.machine_learning.agent_messages | messages | messages/s |
334
+| azure_monitor.machine_learning.agent_runs | runs | runs/s |
335
+| azure_monitor.machine_learning.agent_tokens | tokens | tokens/s |
336
+| azure_monitor.machine_learning.agent_tool_calls | tool_calls | calls/s |
337
+| azure_monitor.machine_learning.agent_indexed_files | indexed_files | files/s |
338
+| azure_monitor.machine_learning.model_deployments | started, succeeded, failed | deployments/s |
339
+| azure_monitor.machine_learning.model_registrations | succeeded, failed | registrations/s |
340
+| azure_monitor.machine_learning.cluster_cores | active, idle, leaving, preempted, unusable | cores |
341
+| azure_monitor.machine_learning.total_cores | total | cores |
342
+| azure_monitor.machine_learning.cluster_nodes | active, idle, leaving, preempted, unusable | nodes |
343
+| azure_monitor.machine_learning.total_nodes | total | nodes |
344
+| azure_monitor.machine_learning.quota_utilization | utilization | percentage |
345
+| azure_monitor.machine_learning.cpu_utilization | cluster_cpu, node_cpu | percentage |
346
+| azure_monitor.machine_learning.cpu_millicores | used, capacity | millicores |
347
+| azure_monitor.machine_learning.cpu_memory_utilization | utilization | percentage |
348
+| azure_monitor.machine_learning.cpu_memory_megabytes | used, capacity | megabytes |
349
+| azure_monitor.machine_learning.gpu_utilization | cluster_gpu, node_gpu | percentage |
350
+| azure_monitor.machine_learning.gpu_milligpus | used, capacity | milliGPUs |
351
+| azure_monitor.machine_learning.gpu_memory_utilization | cluster_gpu_memory, node_gpu_memory | percentage |
352
+| azure_monitor.machine_learning.gpu_memory_megabytes | used, capacity | megabytes |
353
+| azure_monitor.machine_learning.gpu_energy | energy | joules/s |
354
+| azure_monitor.machine_learning.disk_usage | used, available | megabytes |
355
+| azure_monitor.machine_learning.disk_io | read, write | megabytes/s |
356
+| azure_monitor.machine_learning.network_traffic | in, out | megabytes/s |
357
+| azure_monitor.machine_learning.infiniband_traffic | receive, transmit | megabytes/s |
358
+| azure_monitor.machine_learning.storage_api_calls | success, failure | calls/s |
359
+| azure_monitor.machine_learning.run_lifecycle | not_started, starting, preparing, provisioning, queued, started | runs/s |
360
+| azure_monitor.machine_learning.run_completion | completed, failed, finalizing, cancelled, cancel_requested, not_responding | runs/s |
361
+| azure_monitor.machine_learning.run_issues | errors, warnings | events/s |
362
+
363
+
364
+
365
## Troubleshooting
366
367
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_monitor.md
+15
-15
@@ -59,21 +59,6 @@ The collector uses bounded request concurrency and batches resources and metrics
59
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
60
61
62
-## Metrics
63
-
64
-Metrics depend on which Azure Monitor profiles are enabled. Each profile corresponds to an Azure
65
-service type and defines the specific metrics collected. With the default `profiles: [auto]` setting,
66
-profiles are automatically enabled for resource types found in your subscription.
67
-
68
-See the service-specific integrations below for detailed metrics lists.
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
62
## Setup
63
64
@@ -295,6 +280,21 @@ jobs:
280
281
282
283
+## Alerts
284
+
285
+There are no alerts configured by default for this integration.
286
+
287
+
288
+## Metrics
289
+
290
+Metrics depend on which Azure Monitor profiles are enabled. Each profile corresponds to an Azure
291
+service type and defines the specific metrics collected. With the default `profiles: [auto]` setting,
292
+profiles are automatically enabled for resource types found in your subscription.
293
+
294
+See the service-specific integrations below for detailed metrics lists.
295
+
296
+
297
+
298
## Troubleshooting
299
300
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_mysql_flexible_server.md
+91
-91
@@ -57,97 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.mysql_flexible.cpu | average | percentage |
88
-| azure_monitor.mysql_flexible.memory | average | percentage |
89
-| azure_monitor.mysql_flexible.io_utilization | average | percentage |
90
-| azure_monitor.mysql_flexible.cpu_credits | consumed, remaining | credits |
91
-| azure_monitor.mysql_flexible.ha_status | io, sql | status |
92
-| azure_monitor.mysql_flexible.replica_status | io, sql | status |
93
-| azure_monitor.mysql_flexible.uptime | uptime | seconds |
94
-| azure_monitor.mysql_flexible.replication_lag | replica, ha | seconds |
95
-| azure_monitor.mysql_flexible.innodb_row_lock_time | average | milliseconds |
96
-| azure_monitor.mysql_flexible.innodb_row_lock_waits | total | waits/s |
97
-| azure_monitor.mysql_flexible.aborted_connections | total | connections/s |
98
-| azure_monitor.mysql_flexible.active_connections | average | connections |
99
-| azure_monitor.mysql_flexible.total_connections | total | connections/s |
100
-| azure_monitor.mysql_flexible.active_transactions | average | transactions |
101
-| azure_monitor.mysql_flexible.threads_running | maximum | threads |
102
-| azure_monitor.mysql_flexible.queries | total, slow | queries/s |
103
-| azure_monitor.mysql_flexible.dml_statements | select, insert, update, delete | statements/s |
104
-| azure_monitor.mysql_flexible.ddl_statements | create_table, alter_table, drop_table, create_db, drop_db | statements/s |
105
-| azure_monitor.mysql_flexible.lock_deadlocks | total | deadlocks/s |
106
-| azure_monitor.mysql_flexible.lock_timeouts | total | timeouts/s |
107
-| azure_monitor.mysql_flexible.innodb_buffer_pool_pages | data, dirty, free, flushed | pages |
108
-| azure_monitor.mysql_flexible.innodb_buffer_pool_io | read_requests, disk_reads | requests/s |
109
-| azure_monitor.mysql_flexible.innodb_data_writes | total | writes/s |
110
-| azure_monitor.mysql_flexible.sort_merge_passes | total | passes/s |
111
-| azure_monitor.mysql_flexible.network | in, out | bytes/s |
112
-| azure_monitor.mysql_flexible.storage_io | total | operations/s |
113
-| azure_monitor.mysql_flexible.storage | used, limit | bytes |
114
-| azure_monitor.mysql_flexible.storage_utilization | average | percentage |
115
-| azure_monitor.mysql_flexible.storage_breakdown | data, ibdata1, binlog, others | bytes |
116
-| azure_monitor.mysql_flexible.backup_storage | used | bytes |
117
-| azure_monitor.mysql_flexible.serverlog_storage | used, limit | bytes |
118
-| azure_monitor.mysql_flexible.serverlog_storage_utilization | average | percentage |
119
-| azure_monitor.mysql_flexible.history_list_length | maximum | entries |
120
-
121
-
122
-
123
-## Alerts
124
-
125
-
126
-The following alerts are available:
127
-
128
-| Alert name | On metric | Description |
129
-|:------------|:----------|:------------|
130
-| [ am_mysql_flexible_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.cpu | MySQL Flexible CPU on ${label:resource_name} |
131
-| [ am_mysql_flexible_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.memory | MySQL Flexible memory on ${label:resource_name} |
132
-| [ am_mysql_flexible_io_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.io_utilization | MySQL Flexible I/O utilization on ${label:resource_name} |
133
-| [ am_mysql_flexible_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.storage_utilization | MySQL Flexible storage on ${label:resource_name} |
134
-| [ am_mysql_flexible_serverlog_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.serverlog_storage_utilization | MySQL Flexible server log storage on ${label:resource_name} |
135
-| [ am_mysql_flexible_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.cpu_credits | MySQL Flexible CPU credits low on ${label:resource_name} |
136
-| [ am_mysql_flexible_ha_io_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.ha_status | MySQL Flexible HA IO thread down on ${label:resource_name} |
137
-| [ am_mysql_flexible_ha_sql_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.ha_status | MySQL Flexible HA SQL thread down on ${label:resource_name} |
138
-| [ am_mysql_flexible_replica_io_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replica_status | MySQL Flexible replica IO thread down on ${label:resource_name} |
139
-| [ am_mysql_flexible_replica_sql_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replica_status | MySQL Flexible replica SQL thread down on ${label:resource_name} |
140
-| [ am_mysql_flexible_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replication_lag | MySQL Flexible replica lag on ${label:resource_name} |
141
-| [ am_mysql_flexible_ha_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replication_lag | MySQL Flexible HA replication lag on ${label:resource_name} |
142
-| [ am_mysql_flexible_innodb_row_lock_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.innodb_row_lock_time | MySQL Flexible row lock wait time on ${label:resource_name} |
143
-| [ am_mysql_flexible_lock_deadlocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.lock_deadlocks | MySQL Flexible deadlocks on ${label:resource_name} |
144
-| [ am_mysql_flexible_lock_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.lock_timeouts | MySQL Flexible lock timeouts on ${label:resource_name} |
145
-| [ am_mysql_flexible_aborted_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.aborted_connections | MySQL Flexible aborted connections on ${label:resource_name} |
146
-| [ am_mysql_flexible_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.queries | MySQL Flexible slow queries on ${label:resource_name} |
147
-| [ am_mysql_flexible_innodb_row_lock_waits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.innodb_row_lock_waits | MySQL Flexible row lock waits on ${label:resource_name} |
148
-| [ am_mysql_flexible_history_list_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.history_list_length | MySQL Flexible history list length on ${label:resource_name} |
149
-
150
-
60
## Setup
61
62
@@ -369,6 +278,97 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_mysql_flexible_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.cpu | MySQL Flexible CPU on ${label:resource_name} |
289
+| [ am_mysql_flexible_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.memory | MySQL Flexible memory on ${label:resource_name} |
290
+| [ am_mysql_flexible_io_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.io_utilization | MySQL Flexible I/O utilization on ${label:resource_name} |
291
+| [ am_mysql_flexible_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.storage_utilization | MySQL Flexible storage on ${label:resource_name} |
292
+| [ am_mysql_flexible_serverlog_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.serverlog_storage_utilization | MySQL Flexible server log storage on ${label:resource_name} |
293
+| [ am_mysql_flexible_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.cpu_credits | MySQL Flexible CPU credits low on ${label:resource_name} |
294
+| [ am_mysql_flexible_ha_io_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.ha_status | MySQL Flexible HA IO thread down on ${label:resource_name} |
295
+| [ am_mysql_flexible_ha_sql_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.ha_status | MySQL Flexible HA SQL thread down on ${label:resource_name} |
296
+| [ am_mysql_flexible_replica_io_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replica_status | MySQL Flexible replica IO thread down on ${label:resource_name} |
297
+| [ am_mysql_flexible_replica_sql_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replica_status | MySQL Flexible replica SQL thread down on ${label:resource_name} |
298
+| [ am_mysql_flexible_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replication_lag | MySQL Flexible replica lag on ${label:resource_name} |
299
+| [ am_mysql_flexible_ha_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.replication_lag | MySQL Flexible HA replication lag on ${label:resource_name} |
300
+| [ am_mysql_flexible_innodb_row_lock_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.innodb_row_lock_time | MySQL Flexible row lock wait time on ${label:resource_name} |
301
+| [ am_mysql_flexible_lock_deadlocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.lock_deadlocks | MySQL Flexible deadlocks on ${label:resource_name} |
302
+| [ am_mysql_flexible_lock_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.lock_timeouts | MySQL Flexible lock timeouts on ${label:resource_name} |
303
+| [ am_mysql_flexible_aborted_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.aborted_connections | MySQL Flexible aborted connections on ${label:resource_name} |
304
+| [ am_mysql_flexible_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.queries | MySQL Flexible slow queries on ${label:resource_name} |
305
+| [ am_mysql_flexible_innodb_row_lock_waits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.innodb_row_lock_waits | MySQL Flexible row lock waits on ${label:resource_name} |
306
+| [ am_mysql_flexible_history_list_length ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_mysql_flexible.conf) | azure_monitor.mysql_flexible.history_list_length | MySQL Flexible history list length on ${label:resource_name} |
307
+
308
+
309
+## Metrics
310
+
311
+Metrics grouped by *scope*.
312
+
313
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
314
+
315
+
316
+
317
+### Per resource
318
+
319
+These metrics refer to each monitored Azure resource.
320
+
321
+Labels:
322
+
323
+| Label | Description |
324
+|:-----------|:----------------|
325
+| resource_name | The Azure resource name. |
326
+| resource_group | The Azure resource group. |
327
+| region | The Azure region where the resource is deployed. |
328
+| resource_type | The Azure resource type identifier. |
329
+| profile | The Azure Monitor profile id. |
330
+| resource_uid | The unique Azure resource identifier. |
331
+
332
+Metrics:
333
+
334
+| Metric | Dimensions | Unit |
335
+|:------|:----------|:----|
336
+| azure_monitor.mysql_flexible.cpu | average | percentage |
337
+| azure_monitor.mysql_flexible.memory | average | percentage |
338
+| azure_monitor.mysql_flexible.io_utilization | average | percentage |
339
+| azure_monitor.mysql_flexible.cpu_credits | consumed, remaining | credits |
340
+| azure_monitor.mysql_flexible.ha_status | io, sql | status |
341
+| azure_monitor.mysql_flexible.replica_status | io, sql | status |
342
+| azure_monitor.mysql_flexible.uptime | uptime | seconds |
343
+| azure_monitor.mysql_flexible.replication_lag | replica, ha | seconds |
344
+| azure_monitor.mysql_flexible.innodb_row_lock_time | average | milliseconds |
345
+| azure_monitor.mysql_flexible.innodb_row_lock_waits | total | waits/s |
346
+| azure_monitor.mysql_flexible.aborted_connections | total | connections/s |
347
+| azure_monitor.mysql_flexible.active_connections | average | connections |
348
+| azure_monitor.mysql_flexible.total_connections | total | connections/s |
349
+| azure_monitor.mysql_flexible.active_transactions | average | transactions |
350
+| azure_monitor.mysql_flexible.threads_running | maximum | threads |
351
+| azure_monitor.mysql_flexible.queries | total, slow | queries/s |
352
+| azure_monitor.mysql_flexible.dml_statements | select, insert, update, delete | statements/s |
353
+| azure_monitor.mysql_flexible.ddl_statements | create_table, alter_table, drop_table, create_db, drop_db | statements/s |
354
+| azure_monitor.mysql_flexible.lock_deadlocks | total | deadlocks/s |
355
+| azure_monitor.mysql_flexible.lock_timeouts | total | timeouts/s |
356
+| azure_monitor.mysql_flexible.innodb_buffer_pool_pages | data, dirty, free, flushed | pages |
357
+| azure_monitor.mysql_flexible.innodb_buffer_pool_io | read_requests, disk_reads | requests/s |
358
+| azure_monitor.mysql_flexible.innodb_data_writes | total | writes/s |
359
+| azure_monitor.mysql_flexible.sort_merge_passes | total | passes/s |
360
+| azure_monitor.mysql_flexible.network | in, out | bytes/s |
361
+| azure_monitor.mysql_flexible.storage_io | total | operations/s |
362
+| azure_monitor.mysql_flexible.storage | used, limit | bytes |
363
+| azure_monitor.mysql_flexible.storage_utilization | average | percentage |
364
+| azure_monitor.mysql_flexible.storage_breakdown | data, ibdata1, binlog, others | bytes |
365
+| azure_monitor.mysql_flexible.backup_storage | used | bytes |
366
+| azure_monitor.mysql_flexible.serverlog_storage | used, limit | bytes |
367
+| azure_monitor.mysql_flexible.serverlog_storage_utilization | average | percentage |
368
+| azure_monitor.mysql_flexible.history_list_length | maximum | entries |
369
+
370
+
371
+
372
## Troubleshooting
373
374
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_nat_gateway.md
+49
-49
@@ -57,55 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.nat_gateway.datapath_availability | average | percentage |
88
-| azure_monitor.nat_gateway.byte_throughput | total | bytes/s |
89
-| azure_monitor.nat_gateway.packet_throughput | total | packets/s |
90
-| azure_monitor.nat_gateway.dropped_packets | total | packets/s |
91
-| azure_monitor.nat_gateway.snat_connections | total | connections/s |
92
-| azure_monitor.nat_gateway.total_connections | total | connections/s |
93
-
94
-
95
-
96
-## Alerts
97
-
98
-
99
-The following alerts are available:
100
-
101
-| Alert name | On metric | Description |
102
-|:------------|:----------|:------------|
103
-| [ am_nat_gateway_datapath_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.datapath_availability | NAT Gateway availability on ${label:resource_name} |
104
-| [ am_nat_gateway_dropped_packets ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.dropped_packets | NAT Gateway packet drops on ${label:resource_name} |
105
-| [ am_nat_gateway_snat_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.snat_connections | NAT Gateway SNAT connections on ${label:resource_name} |
106
-| [ am_nat_gateway_total_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.total_connections | NAT Gateway total connections on ${label:resource_name} |
107
-
108
-
60
## Setup
61
62
@@ -327,6 +278,55 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_nat_gateway_datapath_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.datapath_availability | NAT Gateway availability on ${label:resource_name} |
289
+| [ am_nat_gateway_dropped_packets ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.dropped_packets | NAT Gateway packet drops on ${label:resource_name} |
290
+| [ am_nat_gateway_snat_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.snat_connections | NAT Gateway SNAT connections on ${label:resource_name} |
291
+| [ am_nat_gateway_total_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_nat_gateway.conf) | azure_monitor.nat_gateway.total_connections | NAT Gateway total connections on ${label:resource_name} |
292
+
293
+
294
+## Metrics
295
+
296
+Metrics grouped by *scope*.
297
+
298
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
299
+
300
+
301
+
302
+### Per resource
303
+
304
+These metrics refer to each monitored Azure resource.
305
+
306
+Labels:
307
+
308
+| Label | Description |
309
+|:-----------|:----------------|
310
+| resource_name | The Azure resource name. |
311
+| resource_group | The Azure resource group. |
312
+| region | The Azure region where the resource is deployed. |
313
+| resource_type | The Azure resource type identifier. |
314
+| profile | The Azure Monitor profile id. |
315
+| resource_uid | The unique Azure resource identifier. |
316
+
317
+Metrics:
318
+
319
+| Metric | Dimensions | Unit |
320
+|:------|:----------|:----|
321
+| azure_monitor.nat_gateway.datapath_availability | average | percentage |
322
+| azure_monitor.nat_gateway.byte_throughput | total | bytes/s |
323
+| azure_monitor.nat_gateway.packet_throughput | total | packets/s |
324
+| azure_monitor.nat_gateway.dropped_packets | total | packets/s |
325
+| azure_monitor.nat_gateway.snat_connections | total | connections/s |
326
+| azure_monitor.nat_gateway.total_connections | total | connections/s |
327
+
328
+
329
+
330
## Troubleshooting
331
332
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_postgresql_flexible_server.md
+101
-101
@@ -57,107 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.postgres_flexible.cpu | average | percentage |
88
-| azure_monitor.postgres_flexible.memory | average | percentage |
89
-| azure_monitor.postgres_flexible.availability | maximum | state |
90
-| azure_monitor.postgres_flexible.iops | total, read, write | operations/s |
91
-| azure_monitor.postgres_flexible.disk_throughput | read, write | bytes/s |
92
-| azure_monitor.postgres_flexible.disk_saturation | bandwidth, iops | percentage |
93
-| azure_monitor.postgres_flexible.disk_queue_depth | average | operations |
94
-| azure_monitor.postgres_flexible.buffer_cache | hits, reads | blocks/s |
95
-| azure_monitor.postgres_flexible.active_connections | average | connections |
96
-| azure_monitor.postgres_flexible.connection_rate | succeeded, failed | connections/s |
97
-| azure_monitor.postgres_flexible.transactions | committed, rolled_back | transactions/s |
98
-| azure_monitor.postgres_flexible.transaction_rate | total, xact_total | transactions/s |
99
-| azure_monitor.postgres_flexible.deadlocks | total | deadlocks/s |
100
-| azure_monitor.postgres_flexible.tuple_reads | returned, fetched | tuples/s |
101
-| azure_monitor.postgres_flexible.tuple_writes | inserted, updated, deleted | tuples/s |
102
-| azure_monitor.postgres_flexible.temp_files | total | files/s |
103
-| azure_monitor.postgres_flexible.temp_bytes | total | bytes/s |
104
-| azure_monitor.postgres_flexible.long_running | query, transaction | seconds |
105
-| azure_monitor.postgres_flexible.xid_usage | max_used, oldest_xmin | transactions |
106
-| azure_monitor.postgres_flexible.xmin_age | maximum | transactions |
107
-| azure_monitor.postgres_flexible.network | in, out | bytes/s |
108
-| azure_monitor.postgres_flexible.storage | used, free | bytes |
109
-| azure_monitor.postgres_flexible.storage_utilization | average | percentage |
110
-| azure_monitor.postgres_flexible.wal_storage | used | bytes |
111
-| azure_monitor.postgres_flexible.database_size | average | bytes |
112
-| azure_monitor.postgres_flexible.backup_storage | used | bytes |
113
-| azure_monitor.postgres_flexible.replication_lag_time | average | seconds |
114
-| azure_monitor.postgres_flexible.replication_lag_bytes | physical, logical | bytes |
115
-| azure_monitor.postgres_flexible.sessions_by_state | maximum | sessions |
116
-| azure_monitor.postgres_flexible.sessions_by_wait_event_type | maximum | sessions |
117
-| azure_monitor.postgres_flexible.autovacuum_operations | vacuum, autovacuum, analyze, autoanalyze | operations |
118
-| azure_monitor.postgres_flexible.autovacuum_table_coverage | vacuumed, autovacuumed, analyzed, autoanalyzed, total | tables |
119
-| azure_monitor.postgres_flexible.tuple_liveness | live, dead, modified_since_analyze | tuples |
120
-| azure_monitor.postgres_flexible.bloat | maximum | percentage |
121
-| azure_monitor.postgres_flexible.backend_count | maximum | connections |
122
-| azure_monitor.postgres_flexible.pgbouncer_client_connections | active, waiting | connections |
123
-| azure_monitor.postgres_flexible.pgbouncer_server_connections | active, idle | connections |
124
-| azure_monitor.postgres_flexible.pgbouncer_pool_count | pools | pools |
125
-| azure_monitor.postgres_flexible.pgbouncer_pooled_connections | pooled_connections | connections |
126
-| azure_monitor.postgres_flexible.cpu_credits | consumed, remaining | credits |
127
-| azure_monitor.postgres_flexible.postmaster_cpu | average | percentage |
128
-| azure_monitor.postgres_flexible.max_connections | maximum | connections |
129
-| azure_monitor.postgres_flexible.tcp_connection_backlog | maximum | connections |
130
-
131
-
132
-
133
-## Alerts
134
-
135
-
136
-The following alerts are available:
137
-
138
-| Alert name | On metric | Description |
139
-|:------------|:----------|:------------|
140
-| [ am_postgres_flexible_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.availability | PostgreSQL Flexible Server down on ${label:resource_name} |
141
-| [ am_postgres_flexible_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.cpu | PostgreSQL Flexible CPU on ${label:resource_name} |
142
-| [ am_postgres_flexible_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.memory | PostgreSQL Flexible memory on ${label:resource_name} |
143
-| [ am_postgres_flexible_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.storage_utilization | PostgreSQL Flexible storage on ${label:resource_name} |
144
-| [ am_postgres_flexible_disk_bandwidth_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.disk_saturation | PostgreSQL Flexible disk bandwidth saturation on ${label:resource_name} |
145
-| [ am_postgres_flexible_disk_iops_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.disk_saturation | PostgreSQL Flexible disk IOPS saturation on ${label:resource_name} |
146
-| [ am_postgres_flexible_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.disk_queue_depth | PostgreSQL Flexible disk queue depth on ${label:resource_name} |
147
-| [ am_postgres_flexible_failed_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.connection_rate | PostgreSQL Flexible failed connections on ${label:resource_name} |
148
-| [ am_postgres_flexible_tcp_connection_backlog ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.tcp_connection_backlog | PostgreSQL Flexible TCP connection backlog on ${label:resource_name} |
149
-| [ am_postgres_flexible_deadlocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.deadlocks | PostgreSQL Flexible deadlocks on ${label:resource_name} |
150
-| [ am_postgres_flexible_rollback_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.transactions | PostgreSQL Flexible rollback ratio on ${label:resource_name} |
151
-| [ am_postgres_flexible_longest_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.long_running | PostgreSQL Flexible long running query on ${label:resource_name} |
152
-| [ am_postgres_flexible_longest_transaction ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.long_running | PostgreSQL Flexible long running transaction on ${label:resource_name} |
153
-| [ am_postgres_flexible_xid_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.xid_usage | PostgreSQL Flexible transaction ID usage on ${label:resource_name} |
154
-| [ am_postgres_flexible_xmin_age ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.xmin_age | PostgreSQL Flexible backend xmin age on ${label:resource_name} |
155
-| [ am_postgres_flexible_bloat ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.bloat | PostgreSQL Flexible table bloat on ${label:resource_name} |
156
-| [ am_postgres_flexible_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.replication_lag_time | PostgreSQL Flexible replication lag on ${label:resource_name} |
157
-| [ am_postgres_flexible_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.cpu_credits | PostgreSQL Flexible CPU credits low on ${label:resource_name} |
158
-| [ am_postgres_flexible_temp_bytes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.temp_bytes | PostgreSQL Flexible temp file I/O on ${label:resource_name} |
159
-
160
-
60
## Setup
61
62
@@ -379,6 +278,107 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_postgres_flexible_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.availability | PostgreSQL Flexible Server down on ${label:resource_name} |
289
+| [ am_postgres_flexible_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.cpu | PostgreSQL Flexible CPU on ${label:resource_name} |
290
+| [ am_postgres_flexible_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.memory | PostgreSQL Flexible memory on ${label:resource_name} |
291
+| [ am_postgres_flexible_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.storage_utilization | PostgreSQL Flexible storage on ${label:resource_name} |
292
+| [ am_postgres_flexible_disk_bandwidth_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.disk_saturation | PostgreSQL Flexible disk bandwidth saturation on ${label:resource_name} |
293
+| [ am_postgres_flexible_disk_iops_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.disk_saturation | PostgreSQL Flexible disk IOPS saturation on ${label:resource_name} |
294
+| [ am_postgres_flexible_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.disk_queue_depth | PostgreSQL Flexible disk queue depth on ${label:resource_name} |
295
+| [ am_postgres_flexible_failed_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.connection_rate | PostgreSQL Flexible failed connections on ${label:resource_name} |
296
+| [ am_postgres_flexible_tcp_connection_backlog ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.tcp_connection_backlog | PostgreSQL Flexible TCP connection backlog on ${label:resource_name} |
297
+| [ am_postgres_flexible_deadlocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.deadlocks | PostgreSQL Flexible deadlocks on ${label:resource_name} |
298
+| [ am_postgres_flexible_rollback_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.transactions | PostgreSQL Flexible rollback ratio on ${label:resource_name} |
299
+| [ am_postgres_flexible_longest_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.long_running | PostgreSQL Flexible long running query on ${label:resource_name} |
300
+| [ am_postgres_flexible_longest_transaction ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.long_running | PostgreSQL Flexible long running transaction on ${label:resource_name} |
301
+| [ am_postgres_flexible_xid_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.xid_usage | PostgreSQL Flexible transaction ID usage on ${label:resource_name} |
302
+| [ am_postgres_flexible_xmin_age ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.xmin_age | PostgreSQL Flexible backend xmin age on ${label:resource_name} |
303
+| [ am_postgres_flexible_bloat ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.bloat | PostgreSQL Flexible table bloat on ${label:resource_name} |
304
+| [ am_postgres_flexible_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.replication_lag_time | PostgreSQL Flexible replication lag on ${label:resource_name} |
305
+| [ am_postgres_flexible_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.cpu_credits | PostgreSQL Flexible CPU credits low on ${label:resource_name} |
306
+| [ am_postgres_flexible_temp_bytes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_postgres_flexible.conf) | azure_monitor.postgres_flexible.temp_bytes | PostgreSQL Flexible temp file I/O on ${label:resource_name} |
307
+
308
+
309
+## Metrics
310
+
311
+Metrics grouped by *scope*.
312
+
313
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
314
+
315
+
316
+
317
+### Per resource
318
+
319
+These metrics refer to each monitored Azure resource.
320
+
321
+Labels:
322
+
323
+| Label | Description |
324
+|:-----------|:----------------|
325
+| resource_name | The Azure resource name. |
326
+| resource_group | The Azure resource group. |
327
+| region | The Azure region where the resource is deployed. |
328
+| resource_type | The Azure resource type identifier. |
329
+| profile | The Azure Monitor profile id. |
330
+| resource_uid | The unique Azure resource identifier. |
331
+
332
+Metrics:
333
+
334
+| Metric | Dimensions | Unit |
335
+|:------|:----------|:----|
336
+| azure_monitor.postgres_flexible.cpu | average | percentage |
337
+| azure_monitor.postgres_flexible.memory | average | percentage |
338
+| azure_monitor.postgres_flexible.availability | maximum | state |
339
+| azure_monitor.postgres_flexible.iops | total, read, write | operations/s |
340
+| azure_monitor.postgres_flexible.disk_throughput | read, write | bytes/s |
341
+| azure_monitor.postgres_flexible.disk_saturation | bandwidth, iops | percentage |
342
+| azure_monitor.postgres_flexible.disk_queue_depth | average | operations |
343
+| azure_monitor.postgres_flexible.buffer_cache | hits, reads | blocks/s |
344
+| azure_monitor.postgres_flexible.active_connections | average | connections |
345
+| azure_monitor.postgres_flexible.connection_rate | succeeded, failed | connections/s |
346
+| azure_monitor.postgres_flexible.transactions | committed, rolled_back | transactions/s |
347
+| azure_monitor.postgres_flexible.transaction_rate | total, xact_total | transactions/s |
348
+| azure_monitor.postgres_flexible.deadlocks | total | deadlocks/s |
349
+| azure_monitor.postgres_flexible.tuple_reads | returned, fetched | tuples/s |
350
+| azure_monitor.postgres_flexible.tuple_writes | inserted, updated, deleted | tuples/s |
351
+| azure_monitor.postgres_flexible.temp_files | total | files/s |
352
+| azure_monitor.postgres_flexible.temp_bytes | total | bytes/s |
353
+| azure_monitor.postgres_flexible.long_running | query, transaction | seconds |
354
+| azure_monitor.postgres_flexible.xid_usage | max_used, oldest_xmin | transactions |
355
+| azure_monitor.postgres_flexible.xmin_age | maximum | transactions |
356
+| azure_monitor.postgres_flexible.network | in, out | bytes/s |
357
+| azure_monitor.postgres_flexible.storage | used, free | bytes |
358
+| azure_monitor.postgres_flexible.storage_utilization | average | percentage |
359
+| azure_monitor.postgres_flexible.wal_storage | used | bytes |
360
+| azure_monitor.postgres_flexible.database_size | average | bytes |
361
+| azure_monitor.postgres_flexible.backup_storage | used | bytes |
362
+| azure_monitor.postgres_flexible.replication_lag_time | average | seconds |
363
+| azure_monitor.postgres_flexible.replication_lag_bytes | physical, logical | bytes |
364
+| azure_monitor.postgres_flexible.sessions_by_state | maximum | sessions |
365
+| azure_monitor.postgres_flexible.sessions_by_wait_event_type | maximum | sessions |
366
+| azure_monitor.postgres_flexible.autovacuum_operations | vacuum, autovacuum, analyze, autoanalyze | operations |
367
+| azure_monitor.postgres_flexible.autovacuum_table_coverage | vacuumed, autovacuumed, analyzed, autoanalyzed, total | tables |
368
+| azure_monitor.postgres_flexible.tuple_liveness | live, dead, modified_since_analyze | tuples |
369
+| azure_monitor.postgres_flexible.bloat | maximum | percentage |
370
+| azure_monitor.postgres_flexible.backend_count | maximum | connections |
371
+| azure_monitor.postgres_flexible.pgbouncer_client_connections | active, waiting | connections |
372
+| azure_monitor.postgres_flexible.pgbouncer_server_connections | active, idle | connections |
373
+| azure_monitor.postgres_flexible.pgbouncer_pool_count | pools | pools |
374
+| azure_monitor.postgres_flexible.pgbouncer_pooled_connections | pooled_connections | connections |
375
+| azure_monitor.postgres_flexible.cpu_credits | consumed, remaining | credits |
376
+| azure_monitor.postgres_flexible.postmaster_cpu | average | percentage |
377
+| azure_monitor.postgres_flexible.max_connections | maximum | connections |
378
+| azure_monitor.postgres_flexible.tcp_connection_backlog | maximum | connections |
379
+
380
+
381
+
382
## Troubleshooting
383
384
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_service_bus_namespace.md
+67
-67
@@ -57,73 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.service_bus.message_flow | in, out | messages/s |
88
-| azure_monitor.service_bus.message_operations | completed, abandoned | messages/s |
89
-| azure_monitor.service_bus.queue_depth | active | messages |
90
-| azure_monitor.service_bus.problem_messages | dead_lettered, scheduled | messages |
91
-| azure_monitor.service_bus.requests | incoming, successful | requests/s |
92
-| azure_monitor.service_bus.errors | server, user, throttled | errors/s |
93
-| azure_monitor.service_bus.connections | active | connections |
94
-| azure_monitor.service_bus.connection_events | opened, closed | connections |
95
-| azure_monitor.service_bus.namespace_size | average | bytes |
96
-| azure_monitor.service_bus.data_throughput | in, out | bytes/s |
97
-| azure_monitor.service_bus.total_messages | total | messages |
98
-| azure_monitor.service_bus.namespace_resources | cpu, memory | percentage |
99
-| azure_monitor.service_bus.send_latency | average | milliseconds |
100
-| azure_monitor.service_bus.replication_lag | messages | messages |
101
-| azure_monitor.service_bus.replication_lag_duration | duration | seconds |
102
-| azure_monitor.service_bus.checkpoint_operations | pending | operations |
103
-
104
-
105
-
106
-## Alerts
107
-
108
-
109
-The following alerts are available:
110
-
111
-| Alert name | On metric | Description |
112
-|:------------|:----------|:------------|
113
-| [ am_service_bus_server_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.errors | Service Bus server errors on ${label:resource_name} |
114
-| [ am_service_bus_throttled_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.errors | Service Bus throttled requests on ${label:resource_name} |
115
-| [ am_service_bus_user_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.errors | Service Bus user errors on ${label:resource_name} |
116
-| [ am_service_bus_namespace_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.namespace_resources | Service Bus namespace CPU on ${label:resource_name} |
117
-| [ am_service_bus_namespace_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.namespace_resources | Service Bus namespace memory on ${label:resource_name} |
118
-| [ am_service_bus_send_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.send_latency | Service Bus send latency on ${label:resource_name} |
119
-| [ am_service_bus_dead_lettered_messages ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.problem_messages | Service Bus dead-lettered messages on ${label:resource_name} |
120
-| [ am_service_bus_active_messages ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.queue_depth | Service Bus queue depth on ${label:resource_name} |
121
-| [ am_service_bus_request_success_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.requests | Service Bus request success rate on ${label:resource_name} |
122
-| [ am_service_bus_abandoned_messages ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.message_operations | Service Bus abandoned messages on ${label:resource_name} |
123
-| [ am_service_bus_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.replication_lag | Service Bus replication lag on ${label:resource_name} |
124
-| [ am_service_bus_replication_lag_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.replication_lag_duration | Service Bus replication lag duration on ${label:resource_name} |
125
-
126
-
60
## Setup
61
62
@@ -345,6 +278,73 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_service_bus_server_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.errors | Service Bus server errors on ${label:resource_name} |
289
+| [ am_service_bus_throttled_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.errors | Service Bus throttled requests on ${label:resource_name} |
290
+| [ am_service_bus_user_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.errors | Service Bus user errors on ${label:resource_name} |
291
+| [ am_service_bus_namespace_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.namespace_resources | Service Bus namespace CPU on ${label:resource_name} |
292
+| [ am_service_bus_namespace_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.namespace_resources | Service Bus namespace memory on ${label:resource_name} |
293
+| [ am_service_bus_send_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.send_latency | Service Bus send latency on ${label:resource_name} |
294
+| [ am_service_bus_dead_lettered_messages ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.problem_messages | Service Bus dead-lettered messages on ${label:resource_name} |
295
+| [ am_service_bus_active_messages ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.queue_depth | Service Bus queue depth on ${label:resource_name} |
296
+| [ am_service_bus_request_success_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.requests | Service Bus request success rate on ${label:resource_name} |
297
+| [ am_service_bus_abandoned_messages ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.message_operations | Service Bus abandoned messages on ${label:resource_name} |
298
+| [ am_service_bus_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.replication_lag | Service Bus replication lag on ${label:resource_name} |
299
+| [ am_service_bus_replication_lag_duration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_service_bus.conf) | azure_monitor.service_bus.replication_lag_duration | Service Bus replication lag duration on ${label:resource_name} |
300
+
301
+
302
+## Metrics
303
+
304
+Metrics grouped by *scope*.
305
+
306
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
307
+
308
+
309
+
310
+### Per resource
311
+
312
+These metrics refer to each monitored Azure resource.
313
+
314
+Labels:
315
+
316
+| Label | Description |
317
+|:-----------|:----------------|
318
+| resource_name | The Azure resource name. |
319
+| resource_group | The Azure resource group. |
320
+| region | The Azure region where the resource is deployed. |
321
+| resource_type | The Azure resource type identifier. |
322
+| profile | The Azure Monitor profile id. |
323
+| resource_uid | The unique Azure resource identifier. |
324
+
325
+Metrics:
326
+
327
+| Metric | Dimensions | Unit |
328
+|:------|:----------|:----|
329
+| azure_monitor.service_bus.message_flow | in, out | messages/s |
330
+| azure_monitor.service_bus.message_operations | completed, abandoned | messages/s |
331
+| azure_monitor.service_bus.queue_depth | active | messages |
332
+| azure_monitor.service_bus.problem_messages | dead_lettered, scheduled | messages |
333
+| azure_monitor.service_bus.requests | incoming, successful | requests/s |
334
+| azure_monitor.service_bus.errors | server, user, throttled | errors/s |
335
+| azure_monitor.service_bus.connections | active | connections |
336
+| azure_monitor.service_bus.connection_events | opened, closed | connections |
337
+| azure_monitor.service_bus.namespace_size | average | bytes |
338
+| azure_monitor.service_bus.data_throughput | in, out | bytes/s |
339
+| azure_monitor.service_bus.total_messages | total | messages |
340
+| azure_monitor.service_bus.namespace_resources | cpu, memory | percentage |
341
+| azure_monitor.service_bus.send_latency | average | milliseconds |
342
+| azure_monitor.service_bus.replication_lag | messages | messages |
343
+| azure_monitor.service_bus.replication_lag_duration | duration | seconds |
344
+| azure_monitor.service_bus.checkpoint_operations | pending | operations |
345
+
346
+
347
+
348
## Troubleshooting
349
350
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_sql_database.md
+80
-80
@@ -57,86 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.sql_database.cpu | average, maximum | percentage |
88
-| azure_monitor.sql_database.instance_cpu | average | percentage |
89
-| azure_monitor.sql_database.instance_memory | average | percentage |
90
-| azure_monitor.sql_database.dtu_consumption | average | percentage |
91
-| azure_monitor.sql_database.io_utilization | data_read, log_write | percentage |
92
-| azure_monitor.sql_database.resource_utilization | workers, sessions | percentage |
93
-| azure_monitor.sql_database.availability | average | percentage |
94
-| azure_monitor.sql_database.connections | successful, failed_system, failed_user, firewall_blocked | connections/s |
95
-| azure_monitor.sql_database.deadlocks | total | deadlocks/s |
96
-| azure_monitor.sql_database.storage | used, allocated | bytes |
97
-| azure_monitor.sql_database.storage_utilization | average | percentage |
98
-| azure_monitor.sql_database.tempdb_size | data, log | KiB |
99
-| azure_monitor.sql_database.tempdb_log_utilization | average | percentage |
100
-| azure_monitor.sql_database.vcore_usage | used, limit | vCores |
101
-| azure_monitor.sql_database.dtu_usage | used, limit | DTU |
102
-| azure_monitor.sql_database.sessions_count | average | sessions |
103
-| azure_monitor.sql_database.replication_lag | average | seconds |
104
-| azure_monitor.sql_database.xtp_storage | average | percentage |
105
-| azure_monitor.sql_database.serverless_utilization | cpu, memory | percentage |
106
-| azure_monitor.sql_database.serverless_billing | total, ha_replicas | vCore-seconds/s |
107
-| azure_monitor.sql_database.free_tier_usage | consumed, remaining | vCore-seconds |
108
-| azure_monitor.sql_database.ledger_digest | success, failed | events/s |
109
-
110
-
111
-
112
-## Alerts
113
-
114
-
115
-The following alerts are available:
116
-
117
-| Alert name | On metric | Description |
118
-|:------------|:----------|:------------|
119
-| [ am_sql_database_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.availability | SQL Database availability on ${label:resource_name} |
120
-| [ am_sql_database_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.cpu | SQL Database CPU on ${label:resource_name} |
121
-| [ am_sql_database_instance_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.instance_cpu | SQL Database instance CPU on ${label:resource_name} |
122
-| [ am_sql_database_instance_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.instance_memory | SQL Database instance memory on ${label:resource_name} |
123
-| [ am_sql_database_dtu_consumption ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.dtu_consumption | SQL Database DTU consumption on ${label:resource_name} |
124
-| [ am_sql_database_data_io ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.io_utilization | SQL Database data I/O on ${label:resource_name} |
125
-| [ am_sql_database_log_write ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.io_utilization | SQL Database log write I/O on ${label:resource_name} |
126
-| [ am_sql_database_workers ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.resource_utilization | SQL Database worker utilization on ${label:resource_name} |
127
-| [ am_sql_database_sessions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.resource_utilization | SQL Database session utilization on ${label:resource_name} |
128
-| [ am_sql_database_connection_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.connections | SQL Database system connection failures on ${label:resource_name} |
129
-| [ am_sql_database_firewall_blocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.connections | SQL Database firewall blocks on ${label:resource_name} |
130
-| [ am_sql_database_deadlocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.deadlocks | SQL Database deadlocks on ${label:resource_name} |
131
-| [ am_sql_database_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.storage_utilization | SQL Database storage utilization on ${label:resource_name} |
132
-| [ am_sql_database_xtp_storage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.xtp_storage | SQL Database In-Memory OLTP storage on ${label:resource_name} |
133
-| [ am_sql_database_tempdb_log_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.tempdb_log_utilization | SQL Database tempdb log utilization on ${label:resource_name} |
134
-| [ am_sql_database_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.replication_lag | SQL Database replication lag on ${label:resource_name} |
135
-| [ am_sql_database_serverless_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.serverless_utilization | SQL Database serverless CPU on ${label:resource_name} |
136
-| [ am_sql_database_serverless_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.serverless_utilization | SQL Database serverless memory on ${label:resource_name} |
137
-| [ am_sql_database_ledger_digest_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.ledger_digest | SQL Database ledger digest failures on ${label:resource_name} |
138
-
139
-
60
## Setup
61
62
@@ -358,6 +278,86 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_sql_database_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.availability | SQL Database availability on ${label:resource_name} |
289
+| [ am_sql_database_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.cpu | SQL Database CPU on ${label:resource_name} |
290
+| [ am_sql_database_instance_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.instance_cpu | SQL Database instance CPU on ${label:resource_name} |
291
+| [ am_sql_database_instance_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.instance_memory | SQL Database instance memory on ${label:resource_name} |
292
+| [ am_sql_database_dtu_consumption ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.dtu_consumption | SQL Database DTU consumption on ${label:resource_name} |
293
+| [ am_sql_database_data_io ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.io_utilization | SQL Database data I/O on ${label:resource_name} |
294
+| [ am_sql_database_log_write ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.io_utilization | SQL Database log write I/O on ${label:resource_name} |
295
+| [ am_sql_database_workers ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.resource_utilization | SQL Database worker utilization on ${label:resource_name} |
296
+| [ am_sql_database_sessions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.resource_utilization | SQL Database session utilization on ${label:resource_name} |
297
+| [ am_sql_database_connection_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.connections | SQL Database system connection failures on ${label:resource_name} |
298
+| [ am_sql_database_firewall_blocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.connections | SQL Database firewall blocks on ${label:resource_name} |
299
+| [ am_sql_database_deadlocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.deadlocks | SQL Database deadlocks on ${label:resource_name} |
300
+| [ am_sql_database_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.storage_utilization | SQL Database storage utilization on ${label:resource_name} |
301
+| [ am_sql_database_xtp_storage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.xtp_storage | SQL Database In-Memory OLTP storage on ${label:resource_name} |
302
+| [ am_sql_database_tempdb_log_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.tempdb_log_utilization | SQL Database tempdb log utilization on ${label:resource_name} |
303
+| [ am_sql_database_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.replication_lag | SQL Database replication lag on ${label:resource_name} |
304
+| [ am_sql_database_serverless_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.serverless_utilization | SQL Database serverless CPU on ${label:resource_name} |
305
+| [ am_sql_database_serverless_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.serverless_utilization | SQL Database serverless memory on ${label:resource_name} |
306
+| [ am_sql_database_ledger_digest_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_database.conf) | azure_monitor.sql_database.ledger_digest | SQL Database ledger digest failures on ${label:resource_name} |
307
+
308
+
309
+## Metrics
310
+
311
+Metrics grouped by *scope*.
312
+
313
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
314
+
315
+
316
+
317
+### Per resource
318
+
319
+These metrics refer to each monitored Azure resource.
320
+
321
+Labels:
322
+
323
+| Label | Description |
324
+|:-----------|:----------------|
325
+| resource_name | The Azure resource name. |
326
+| resource_group | The Azure resource group. |
327
+| region | The Azure region where the resource is deployed. |
328
+| resource_type | The Azure resource type identifier. |
329
+| profile | The Azure Monitor profile id. |
330
+| resource_uid | The unique Azure resource identifier. |
331
+
332
+Metrics:
333
+
334
+| Metric | Dimensions | Unit |
335
+|:------|:----------|:----|
336
+| azure_monitor.sql_database.cpu | average, maximum | percentage |
337
+| azure_monitor.sql_database.instance_cpu | average | percentage |
338
+| azure_monitor.sql_database.instance_memory | average | percentage |
339
+| azure_monitor.sql_database.dtu_consumption | average | percentage |
340
+| azure_monitor.sql_database.io_utilization | data_read, log_write | percentage |
341
+| azure_monitor.sql_database.resource_utilization | workers, sessions | percentage |
342
+| azure_monitor.sql_database.availability | average | percentage |
343
+| azure_monitor.sql_database.connections | successful, failed_system, failed_user, firewall_blocked | connections/s |
344
+| azure_monitor.sql_database.deadlocks | total | deadlocks/s |
345
+| azure_monitor.sql_database.storage | used, allocated | bytes |
346
+| azure_monitor.sql_database.storage_utilization | average | percentage |
347
+| azure_monitor.sql_database.tempdb_size | data, log | KiB |
348
+| azure_monitor.sql_database.tempdb_log_utilization | average | percentage |
349
+| azure_monitor.sql_database.vcore_usage | used, limit | vCores |
350
+| azure_monitor.sql_database.dtu_usage | used, limit | DTU |
351
+| azure_monitor.sql_database.sessions_count | average | sessions |
352
+| azure_monitor.sql_database.replication_lag | average | seconds |
353
+| azure_monitor.sql_database.xtp_storage | average | percentage |
354
+| azure_monitor.sql_database.serverless_utilization | cpu, memory | percentage |
355
+| azure_monitor.sql_database.serverless_billing | total, ha_replicas | vCore-seconds/s |
356
+| azure_monitor.sql_database.free_tier_usage | consumed, remaining | vCore-seconds |
357
+| azure_monitor.sql_database.ledger_digest | success, failed | events/s |
358
+
359
+
360
+
361
## Troubleshooting
362
363
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_sql_elastic_pool.md
+69
-69
@@ -57,75 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.sql_elastic_pool.cpu | average, maximum | percentage |
88
-| azure_monitor.sql_elastic_pool.instance_cpu | average | percentage |
89
-| azure_monitor.sql_elastic_pool.instance_memory | average | percentage |
90
-| azure_monitor.sql_elastic_pool.dtu_consumption | average | percentage |
91
-| azure_monitor.sql_elastic_pool.io_utilization | data_read, log_write | percentage |
92
-| azure_monitor.sql_elastic_pool.resource_utilization | workers, sessions | percentage |
93
-| azure_monitor.sql_elastic_pool.sessions_count | average | sessions |
94
-| azure_monitor.sql_elastic_pool.storage | used, allocated, limit | bytes |
95
-| azure_monitor.sql_elastic_pool.storage_utilization | used, allocated | percentage |
96
-| azure_monitor.sql_elastic_pool.xtp_storage | average | percentage |
97
-| azure_monitor.sql_elastic_pool.tempdb_size | data, log | KiB |
98
-| azure_monitor.sql_elastic_pool.tempdb_log_utilization | average | percentage |
99
-| azure_monitor.sql_elastic_pool.vcore_usage | used, limit | vCores |
100
-| azure_monitor.sql_elastic_pool.edtu_usage | used, limit | eDTU |
101
-| azure_monitor.sql_elastic_pool.serverless_utilization | cpu, memory | percentage |
102
-| azure_monitor.sql_elastic_pool.serverless_billing | total | vCore-seconds/s |
103
-
104
-
105
-
106
-## Alerts
107
-
108
-
109
-The following alerts are available:
110
-
111
-| Alert name | On metric | Description |
112
-|:------------|:----------|:------------|
113
-| [ am_sql_elastic_pool_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.cpu | SQL Elastic Pool CPU on ${label:resource_name} |
114
-| [ am_sql_elastic_pool_instance_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.instance_cpu | SQL Elastic Pool instance CPU on ${label:resource_name} |
115
-| [ am_sql_elastic_pool_instance_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.instance_memory | SQL Elastic Pool instance memory on ${label:resource_name} |
116
-| [ am_sql_elastic_pool_dtu_consumption ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.dtu_consumption | SQL Elastic Pool DTU consumption on ${label:resource_name} |
117
-| [ am_sql_elastic_pool_data_io ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.io_utilization | SQL Elastic Pool data I/O on ${label:resource_name} |
118
-| [ am_sql_elastic_pool_log_write ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.io_utilization | SQL Elastic Pool log write on ${label:resource_name} |
119
-| [ am_sql_elastic_pool_workers ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.resource_utilization | SQL Elastic Pool workers on ${label:resource_name} |
120
-| [ am_sql_elastic_pool_sessions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.resource_utilization | SQL Elastic Pool sessions on ${label:resource_name} |
121
-| [ am_sql_elastic_pool_storage_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.storage_utilization | SQL Elastic Pool storage used on ${label:resource_name} |
122
-| [ am_sql_elastic_pool_storage_allocated ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.storage_utilization | SQL Elastic Pool storage allocated on ${label:resource_name} |
123
-| [ am_sql_elastic_pool_xtp_storage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.xtp_storage | SQL Elastic Pool In-Memory OLTP storage on ${label:resource_name} |
124
-| [ am_sql_elastic_pool_tempdb_log ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.tempdb_log_utilization | SQL Elastic Pool tempdb log on ${label:resource_name} |
125
-| [ am_sql_elastic_pool_serverless_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.serverless_utilization | SQL Elastic Pool serverless CPU on ${label:resource_name} |
126
-| [ am_sql_elastic_pool_serverless_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.serverless_utilization | SQL Elastic Pool serverless memory on ${label:resource_name} |
127
-
128
-
60
## Setup
61
62
@@ -347,6 +278,75 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_sql_elastic_pool_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.cpu | SQL Elastic Pool CPU on ${label:resource_name} |
289
+| [ am_sql_elastic_pool_instance_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.instance_cpu | SQL Elastic Pool instance CPU on ${label:resource_name} |
290
+| [ am_sql_elastic_pool_instance_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.instance_memory | SQL Elastic Pool instance memory on ${label:resource_name} |
291
+| [ am_sql_elastic_pool_dtu_consumption ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.dtu_consumption | SQL Elastic Pool DTU consumption on ${label:resource_name} |
292
+| [ am_sql_elastic_pool_data_io ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.io_utilization | SQL Elastic Pool data I/O on ${label:resource_name} |
293
+| [ am_sql_elastic_pool_log_write ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.io_utilization | SQL Elastic Pool log write on ${label:resource_name} |
294
+| [ am_sql_elastic_pool_workers ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.resource_utilization | SQL Elastic Pool workers on ${label:resource_name} |
295
+| [ am_sql_elastic_pool_sessions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.resource_utilization | SQL Elastic Pool sessions on ${label:resource_name} |
296
+| [ am_sql_elastic_pool_storage_used ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.storage_utilization | SQL Elastic Pool storage used on ${label:resource_name} |
297
+| [ am_sql_elastic_pool_storage_allocated ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.storage_utilization | SQL Elastic Pool storage allocated on ${label:resource_name} |
298
+| [ am_sql_elastic_pool_xtp_storage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.xtp_storage | SQL Elastic Pool In-Memory OLTP storage on ${label:resource_name} |
299
+| [ am_sql_elastic_pool_tempdb_log ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.tempdb_log_utilization | SQL Elastic Pool tempdb log on ${label:resource_name} |
300
+| [ am_sql_elastic_pool_serverless_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.serverless_utilization | SQL Elastic Pool serverless CPU on ${label:resource_name} |
301
+| [ am_sql_elastic_pool_serverless_memory ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_elastic_pool.conf) | azure_monitor.sql_elastic_pool.serverless_utilization | SQL Elastic Pool serverless memory on ${label:resource_name} |
302
+
303
+
304
+## Metrics
305
+
306
+Metrics grouped by *scope*.
307
+
308
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
309
+
310
+
311
+
312
+### Per resource
313
+
314
+These metrics refer to each monitored Azure resource.
315
+
316
+Labels:
317
+
318
+| Label | Description |
319
+|:-----------|:----------------|
320
+| resource_name | The Azure resource name. |
321
+| resource_group | The Azure resource group. |
322
+| region | The Azure region where the resource is deployed. |
323
+| resource_type | The Azure resource type identifier. |
324
+| profile | The Azure Monitor profile id. |
325
+| resource_uid | The unique Azure resource identifier. |
326
+
327
+Metrics:
328
+
329
+| Metric | Dimensions | Unit |
330
+|:------|:----------|:----|
331
+| azure_monitor.sql_elastic_pool.cpu | average, maximum | percentage |
332
+| azure_monitor.sql_elastic_pool.instance_cpu | average | percentage |
333
+| azure_monitor.sql_elastic_pool.instance_memory | average | percentage |
334
+| azure_monitor.sql_elastic_pool.dtu_consumption | average | percentage |
335
+| azure_monitor.sql_elastic_pool.io_utilization | data_read, log_write | percentage |
336
+| azure_monitor.sql_elastic_pool.resource_utilization | workers, sessions | percentage |
337
+| azure_monitor.sql_elastic_pool.sessions_count | average | sessions |
338
+| azure_monitor.sql_elastic_pool.storage | used, allocated, limit | bytes |
339
+| azure_monitor.sql_elastic_pool.storage_utilization | used, allocated | percentage |
340
+| azure_monitor.sql_elastic_pool.xtp_storage | average | percentage |
341
+| azure_monitor.sql_elastic_pool.tempdb_size | data, log | KiB |
342
+| azure_monitor.sql_elastic_pool.tempdb_log_utilization | average | percentage |
343
+| azure_monitor.sql_elastic_pool.vcore_usage | used, limit | vCores |
344
+| azure_monitor.sql_elastic_pool.edtu_usage | used, limit | eDTU |
345
+| azure_monitor.sql_elastic_pool.serverless_utilization | cpu, memory | percentage |
346
+| azure_monitor.sql_elastic_pool.serverless_billing | total | vCore-seconds/s |
347
+
348
+
349
+
350
## Troubleshooting
351
352
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_sql_managed_instance.md
+47
-47
@@ -57,53 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.sql_managed_instance.cpu | average, maximum | percentage |
88
-| azure_monitor.sql_managed_instance.io_throughput | read, written | bytes/s |
89
-| azure_monitor.sql_managed_instance.io_requests | average | requests/s |
90
-| azure_monitor.sql_managed_instance.storage | reserved, used | MiB |
91
-| azure_monitor.sql_managed_instance.virtual_core_count | average | cores |
92
-
93
-
94
-
95
-## Alerts
96
-
97
-
98
-The following alerts are available:
99
-
100
-| Alert name | On metric | Description |
101
-|:------------|:----------|:------------|
102
-| [ am_sql_managed_instance_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf) | azure_monitor.sql_managed_instance.cpu | SQL MI CPU utilization on ${label:resource_name} |
103
-| [ am_sql_managed_instance_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf) | azure_monitor.sql_managed_instance.storage | SQL MI storage utilization on ${label:resource_name} |
104
-| [ am_sql_managed_instance_io_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf) | azure_monitor.sql_managed_instance.io_requests | SQL MI I/O requests on ${label:resource_name} |
105
-
106
-
60
## Setup
61
62
@@ -325,6 +278,53 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_sql_managed_instance_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf) | azure_monitor.sql_managed_instance.cpu | SQL MI CPU utilization on ${label:resource_name} |
289
+| [ am_sql_managed_instance_storage_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf) | azure_monitor.sql_managed_instance.storage | SQL MI storage utilization on ${label:resource_name} |
290
+| [ am_sql_managed_instance_io_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_sql_managed_instance.conf) | azure_monitor.sql_managed_instance.io_requests | SQL MI I/O requests on ${label:resource_name} |
291
+
292
+
293
+## Metrics
294
+
295
+Metrics grouped by *scope*.
296
+
297
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
298
+
299
+
300
+
301
+### Per resource
302
+
303
+These metrics refer to each monitored Azure resource.
304
+
305
+Labels:
306
+
307
+| Label | Description |
308
+|:-----------|:----------------|
309
+| resource_name | The Azure resource name. |
310
+| resource_group | The Azure resource group. |
311
+| region | The Azure region where the resource is deployed. |
312
+| resource_type | The Azure resource type identifier. |
313
+| profile | The Azure Monitor profile id. |
314
+| resource_uid | The unique Azure resource identifier. |
315
+
316
+Metrics:
317
+
318
+| Metric | Dimensions | Unit |
319
+|:------|:----------|:----|
320
+| azure_monitor.sql_managed_instance.cpu | average, maximum | percentage |
321
+| azure_monitor.sql_managed_instance.io_throughput | read, written | bytes/s |
322
+| azure_monitor.sql_managed_instance.io_requests | average | requests/s |
323
+| azure_monitor.sql_managed_instance.storage | reserved, used | MiB |
324
+| azure_monitor.sql_managed_instance.virtual_core_count | average | cores |
325
+
326
+
327
+
328
## Troubleshooting
329
330
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_storage_account.md
+50
-50
@@ -57,56 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.storage_accounts.availability | average | percentage |
88
-| azure_monitor.storage_accounts.transactions | total | transactions/s |
89
-| azure_monitor.storage_accounts.throughput | ingress, egress | bytes/s |
90
-| azure_monitor.storage_accounts.e2e_latency | average, maximum | milliseconds |
91
-| azure_monitor.storage_accounts.server_latency | average, maximum | milliseconds |
92
-| azure_monitor.storage_accounts.used_capacity | average | bytes |
93
-
94
-
95
-
96
-## Alerts
97
-
98
-
99
-The following alerts are available:
100
-
101
-| Alert name | On metric | Description |
102
-|:------------|:----------|:------------|
103
-| [ am_storage_accounts_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.availability | Storage availability on ${label:resource_name} |
104
-| [ am_storage_accounts_e2e_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.e2e_latency | Storage E2E latency on ${label:resource_name} |
105
-| [ am_storage_accounts_e2e_latency_peak ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.e2e_latency | Storage E2E latency peak on ${label:resource_name} |
106
-| [ am_storage_accounts_server_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.server_latency | Storage server latency on ${label:resource_name} |
107
-| [ am_storage_accounts_server_latency_peak ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.server_latency | Storage server latency peak on ${label:resource_name} |
108
-
109
-
60
## Setup
61
62
@@ -328,6 +278,56 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_storage_accounts_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.availability | Storage availability on ${label:resource_name} |
289
+| [ am_storage_accounts_e2e_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.e2e_latency | Storage E2E latency on ${label:resource_name} |
290
+| [ am_storage_accounts_e2e_latency_peak ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.e2e_latency | Storage E2E latency peak on ${label:resource_name} |
291
+| [ am_storage_accounts_server_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.server_latency | Storage server latency on ${label:resource_name} |
292
+| [ am_storage_accounts_server_latency_peak ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_storage_accounts.conf) | azure_monitor.storage_accounts.server_latency | Storage server latency peak on ${label:resource_name} |
293
+
294
+
295
+## Metrics
296
+
297
+Metrics grouped by *scope*.
298
+
299
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
300
+
301
+
302
+
303
+### Per resource
304
+
305
+These metrics refer to each monitored Azure resource.
306
+
307
+Labels:
308
+
309
+| Label | Description |
310
+|:-----------|:----------------|
311
+| resource_name | The Azure resource name. |
312
+| resource_group | The Azure resource group. |
313
+| region | The Azure region where the resource is deployed. |
314
+| resource_type | The Azure resource type identifier. |
315
+| profile | The Azure Monitor profile id. |
316
+| resource_uid | The unique Azure resource identifier. |
317
+
318
+Metrics:
319
+
320
+| Metric | Dimensions | Unit |
321
+|:------|:----------|:----|
322
+| azure_monitor.storage_accounts.availability | average | percentage |
323
+| azure_monitor.storage_accounts.transactions | total | transactions/s |
324
+| azure_monitor.storage_accounts.throughput | ingress, egress | bytes/s |
325
+| azure_monitor.storage_accounts.e2e_latency | average, maximum | milliseconds |
326
+| azure_monitor.storage_accounts.server_latency | average, maximum | milliseconds |
327
+| azure_monitor.storage_accounts.used_capacity | average | bytes |
328
+
329
+
330
+
331
## Troubleshooting
332
333
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_stream_analytics_job.md
+59
-59
@@ -57,65 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.stream_analytics.event_flow | in, out | events/s |
88
-| azure_monitor.stream_analytics.input_data_throughput | received | bytes/s |
89
-| azure_monitor.stream_analytics.input_sources_received | received | sources/s |
90
-| azure_monitor.stream_analytics.event_timing | late, early, out_of_order | events/s |
91
-| azure_monitor.stream_analytics.backlogged_events | backlogged | events |
92
-| azure_monitor.stream_analytics.watermark_delay | delay | seconds |
93
-| azure_monitor.stream_analytics.errors | runtime, data_conversion, deserialization | errors/s |
94
-| azure_monitor.stream_analytics.function_requests | total, failed | requests/s |
95
-| azure_monitor.stream_analytics.function_events | input | events/s |
96
-| azure_monitor.stream_analytics.resource_utilization | cpu, su_memory | percentage |
97
-
98
-
99
-
100
-## Alerts
101
-
102
-
103
-The following alerts are available:
104
-
105
-| Alert name | On metric | Description |
106
-|:------------|:----------|:------------|
107
-| [ am_stream_analytics_su_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.resource_utilization | Stream Analytics SU utilization on ${label:resource_name} |
108
-| [ am_stream_analytics_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.resource_utilization | Stream Analytics CPU on ${label:resource_name} |
109
-| [ am_stream_analytics_watermark_delay ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.watermark_delay | Stream Analytics watermark delay on ${label:resource_name} |
110
-| [ am_stream_analytics_runtime_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.errors | Stream Analytics runtime errors on ${label:resource_name} |
111
-| [ am_stream_analytics_data_conversion_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.errors | Stream Analytics conversion errors on ${label:resource_name} |
112
-| [ am_stream_analytics_deserialization_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.errors | Stream Analytics deserialization errors on ${label:resource_name} |
113
-| [ am_stream_analytics_out_of_order_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.event_timing | Stream Analytics out-of-order events on ${label:resource_name} |
114
-| [ am_stream_analytics_late_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.event_timing | Stream Analytics late events on ${label:resource_name} |
115
-| [ am_stream_analytics_backlogged_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.backlogged_events | Stream Analytics backlog on ${label:resource_name} |
116
-| [ am_stream_analytics_function_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.function_requests | Stream Analytics ML function failures on ${label:resource_name} |
117
-
118
-
60
## Setup
61
62
@@ -337,6 +278,65 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_stream_analytics_su_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.resource_utilization | Stream Analytics SU utilization on ${label:resource_name} |
289
+| [ am_stream_analytics_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.resource_utilization | Stream Analytics CPU on ${label:resource_name} |
290
+| [ am_stream_analytics_watermark_delay ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.watermark_delay | Stream Analytics watermark delay on ${label:resource_name} |
291
+| [ am_stream_analytics_runtime_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.errors | Stream Analytics runtime errors on ${label:resource_name} |
292
+| [ am_stream_analytics_data_conversion_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.errors | Stream Analytics conversion errors on ${label:resource_name} |
293
+| [ am_stream_analytics_deserialization_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.errors | Stream Analytics deserialization errors on ${label:resource_name} |
294
+| [ am_stream_analytics_out_of_order_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.event_timing | Stream Analytics out-of-order events on ${label:resource_name} |
295
+| [ am_stream_analytics_late_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.event_timing | Stream Analytics late events on ${label:resource_name} |
296
+| [ am_stream_analytics_backlogged_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.backlogged_events | Stream Analytics backlog on ${label:resource_name} |
297
+| [ am_stream_analytics_function_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_stream_analytics.conf) | azure_monitor.stream_analytics.function_requests | Stream Analytics ML function failures on ${label:resource_name} |
298
+
299
+
300
+## Metrics
301
+
302
+Metrics grouped by *scope*.
303
+
304
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
305
+
306
+
307
+
308
+### Per resource
309
+
310
+These metrics refer to each monitored Azure resource.
311
+
312
+Labels:
313
+
314
+| Label | Description |
315
+|:-----------|:----------------|
316
+| resource_name | The Azure resource name. |
317
+| resource_group | The Azure resource group. |
318
+| region | The Azure region where the resource is deployed. |
319
+| resource_type | The Azure resource type identifier. |
320
+| profile | The Azure Monitor profile id. |
321
+| resource_uid | The unique Azure resource identifier. |
322
+
323
+Metrics:
324
+
325
+| Metric | Dimensions | Unit |
326
+|:------|:----------|:----|
327
+| azure_monitor.stream_analytics.event_flow | in, out | events/s |
328
+| azure_monitor.stream_analytics.input_data_throughput | received | bytes/s |
329
+| azure_monitor.stream_analytics.input_sources_received | received | sources/s |
330
+| azure_monitor.stream_analytics.event_timing | late, early, out_of_order | events/s |
331
+| azure_monitor.stream_analytics.backlogged_events | backlogged | events |
332
+| azure_monitor.stream_analytics.watermark_delay | delay | seconds |
333
+| azure_monitor.stream_analytics.errors | runtime, data_conversion, deserialization | errors/s |
334
+| azure_monitor.stream_analytics.function_requests | total, failed | requests/s |
335
+| azure_monitor.stream_analytics.function_events | input | events/s |
336
+| azure_monitor.stream_analytics.resource_utilization | cpu, su_memory | percentage |
337
+
338
+
339
+
340
## Troubleshooting
341
342
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_synapse_analytics_workspace.md
+65
-65
@@ -57,71 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.synapse.builtin_sql_pool_data_processed | processed | bytes/s |
88
-| azure_monitor.synapse.builtin_sql_pool_login_attempts | login_attempts | attempts/s |
89
-| azure_monitor.synapse.builtin_sql_pool_requests | requests | requests/s |
90
-| azure_monitor.synapse.activity_runs | ended | runs/s |
91
-| azure_monitor.synapse.pipeline_runs | ended | runs/s |
92
-| azure_monitor.synapse.trigger_runs | ended | runs/s |
93
-| azure_monitor.synapse.link_connection_events | events | events/s |
94
-| azure_monitor.synapse.link_table_events | events | events/s |
95
-| azure_monitor.synapse.link_processed_rows | changed_rows | rows/s |
96
-| azure_monitor.synapse.link_data_volume | processed | bytes/s |
97
-| azure_monitor.synapse.link_processing_latency | average | seconds |
98
-| azure_monitor.synapse.streaming_event_flow | in, out | events/s |
99
-| azure_monitor.synapse.streaming_input_throughput | received | bytes/s |
100
-| azure_monitor.synapse.streaming_input_sources | received | sources/s |
101
-| azure_monitor.synapse.streaming_event_timing | late, early, out_of_order, backlogged | events/s |
102
-| azure_monitor.synapse.streaming_watermark_delay | delay | seconds |
103
-| azure_monitor.synapse.streaming_errors | runtime, data_conversion, deserialization | errors/s |
104
-| azure_monitor.synapse.streaming_resource_utilization | utilization | percentage |
105
-
106
-
107
-
108
-## Alerts
109
-
110
-
111
-The following alerts are available:
112
-
113
-| Alert name | On metric | Description |
114
-|:------------|:----------|:------------|
115
-| [ am_synapse_streaming_resource_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_resource_utilization | Synapse streaming SU utilization on ${label:resource_name} |
116
-| [ am_synapse_streaming_runtime_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_errors | Synapse streaming runtime errors on ${label:resource_name} |
117
-| [ am_synapse_streaming_data_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_errors | Synapse streaming data errors on ${label:resource_name} |
118
-| [ am_synapse_streaming_watermark_delay ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_watermark_delay | Synapse streaming watermark delay on ${label:resource_name} |
119
-| [ am_synapse_streaming_late_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_event_timing | Synapse streaming late events on ${label:resource_name} |
120
-| [ am_synapse_streaming_out_of_order_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_event_timing | Synapse streaming out-of-order events on ${label:resource_name} |
121
-| [ am_synapse_streaming_backlogged_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_event_timing | Synapse streaming backlogged events on ${label:resource_name} |
122
-| [ am_synapse_link_processing_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.link_processing_latency | Synapse Link processing latency on ${label:resource_name} |
123
-
124
-
60
## Setup
61
62
@@ -343,6 +278,71 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_synapse_streaming_resource_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_resource_utilization | Synapse streaming SU utilization on ${label:resource_name} |
289
+| [ am_synapse_streaming_runtime_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_errors | Synapse streaming runtime errors on ${label:resource_name} |
290
+| [ am_synapse_streaming_data_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_errors | Synapse streaming data errors on ${label:resource_name} |
291
+| [ am_synapse_streaming_watermark_delay ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_watermark_delay | Synapse streaming watermark delay on ${label:resource_name} |
292
+| [ am_synapse_streaming_late_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_event_timing | Synapse streaming late events on ${label:resource_name} |
293
+| [ am_synapse_streaming_out_of_order_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_event_timing | Synapse streaming out-of-order events on ${label:resource_name} |
294
+| [ am_synapse_streaming_backlogged_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.streaming_event_timing | Synapse streaming backlogged events on ${label:resource_name} |
295
+| [ am_synapse_link_processing_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_synapse.conf) | azure_monitor.synapse.link_processing_latency | Synapse Link processing latency on ${label:resource_name} |
296
+
297
+
298
+## Metrics
299
+
300
+Metrics grouped by *scope*.
301
+
302
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
303
+
304
+
305
+
306
+### Per resource
307
+
308
+These metrics refer to each monitored Azure resource.
309
+
310
+Labels:
311
+
312
+| Label | Description |
313
+|:-----------|:----------------|
314
+| resource_name | The Azure resource name. |
315
+| resource_group | The Azure resource group. |
316
+| region | The Azure region where the resource is deployed. |
317
+| resource_type | The Azure resource type identifier. |
318
+| profile | The Azure Monitor profile id. |
319
+| resource_uid | The unique Azure resource identifier. |
320
+
321
+Metrics:
322
+
323
+| Metric | Dimensions | Unit |
324
+|:------|:----------|:----|
325
+| azure_monitor.synapse.builtin_sql_pool_data_processed | processed | bytes/s |
326
+| azure_monitor.synapse.builtin_sql_pool_login_attempts | login_attempts | attempts/s |
327
+| azure_monitor.synapse.builtin_sql_pool_requests | requests | requests/s |
328
+| azure_monitor.synapse.activity_runs | ended | runs/s |
329
+| azure_monitor.synapse.pipeline_runs | ended | runs/s |
330
+| azure_monitor.synapse.trigger_runs | ended | runs/s |
331
+| azure_monitor.synapse.link_connection_events | events | events/s |
332
+| azure_monitor.synapse.link_table_events | events | events/s |
333
+| azure_monitor.synapse.link_processed_rows | changed_rows | rows/s |
334
+| azure_monitor.synapse.link_data_volume | processed | bytes/s |
335
+| azure_monitor.synapse.link_processing_latency | average | seconds |
336
+| azure_monitor.synapse.streaming_event_flow | in, out | events/s |
337
+| azure_monitor.synapse.streaming_input_throughput | received | bytes/s |
338
+| azure_monitor.synapse.streaming_input_sources | received | sources/s |
339
+| azure_monitor.synapse.streaming_event_timing | late, early, out_of_order, backlogged | events/s |
340
+| azure_monitor.synapse.streaming_watermark_delay | delay | seconds |
341
+| azure_monitor.synapse.streaming_errors | runtime, data_conversion, deserialization | errors/s |
342
+| azure_monitor.synapse.streaming_resource_utilization | utilization | percentage |
343
+
344
+
345
+
346
## Troubleshooting
347
348
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_virtual_machine.md
+99
-99
@@ -57,105 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.virtual_machines.cpu | average | percentage |
88
-| azure_monitor.virtual_machines.cpu_credits | consumed, remaining | credits |
89
-| azure_monitor.virtual_machines.memory | available | bytes |
90
-| azure_monitor.virtual_machines.memory_percentage | available | percentage |
91
-| azure_monitor.virtual_machines.availability | average | state |
92
-| azure_monitor.virtual_machines.network_traffic | in, out | bytes/s |
93
-| azure_monitor.virtual_machines.network_flows | in, out | flows |
94
-| azure_monitor.virtual_machines.network_flow_creation_rate | in, out | flows/s |
95
-| azure_monitor.virtual_machines.disk_throughput | read, write | bytes/s |
96
-| azure_monitor.virtual_machines.disk_iops | read, write | operations/s |
97
-| azure_monitor.virtual_machines.os_disk_throughput | read, write | bytes/s |
98
-| azure_monitor.virtual_machines.os_disk_iops | read, write | operations/s |
99
-| azure_monitor.virtual_machines.os_disk_latency | average | milliseconds |
100
-| azure_monitor.virtual_machines.os_disk_queue_depth | average | operations |
101
-| azure_monitor.virtual_machines.os_disk_throttling | bandwidth, iops | percentage |
102
-| azure_monitor.virtual_machines.os_disk_burst_capacity | max_burst, target | bytes/s |
103
-| azure_monitor.virtual_machines.os_disk_burst_iops_capacity | max_burst, target | iops |
104
-| azure_monitor.virtual_machines.os_disk_burst_credits | bandwidth, io | percentage |
105
-| azure_monitor.virtual_machines.data_disk_throughput | read, write | bytes/s |
106
-| azure_monitor.virtual_machines.data_disk_iops | read, write | operations/s |
107
-| azure_monitor.virtual_machines.data_disk_latency | average | milliseconds |
108
-| azure_monitor.virtual_machines.data_disk_queue_depth | average | operations |
109
-| azure_monitor.virtual_machines.data_disk_throttling | bandwidth, iops | percentage |
110
-| azure_monitor.virtual_machines.data_disk_burst_capacity | max_burst, target | bytes/s |
111
-| azure_monitor.virtual_machines.data_disk_burst_iops_capacity | max_burst, target | iops |
112
-| azure_monitor.virtual_machines.data_disk_burst_credits | bandwidth, io | percentage |
113
-| azure_monitor.virtual_machines.temp_disk_throughput | read, write | bytes/s |
114
-| azure_monitor.virtual_machines.temp_disk_iops | read, write | operations/s |
115
-| azure_monitor.virtual_machines.temp_disk_latency | average | milliseconds |
116
-| azure_monitor.virtual_machines.temp_disk_queue_depth | average | operations |
117
-| azure_monitor.virtual_machines.premium_data_disk_cache | hit, miss | percentage |
118
-| azure_monitor.virtual_machines.premium_os_disk_cache | hit, miss | percentage |
119
-| azure_monitor.virtual_machines.vm_cached_throttling | bandwidth, iops | percentage |
120
-| azure_monitor.virtual_machines.vm_uncached_throttling | bandwidth, iops | percentage |
121
-| azure_monitor.virtual_machines.vm_cached_burst_credits | bandwidth, io | percentage |
122
-| azure_monitor.virtual_machines.vm_uncached_burst_credits | bandwidth, io | percentage |
123
-
124
-
125
-
126
-## Alerts
127
-
128
-
129
-The following alerts are available:
130
-
131
-| Alert name | On metric | Description |
132
-|:------------|:----------|:------------|
133
-| [ am_vm_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.cpu | VM CPU on ${label:resource_name} |
134
-| [ am_vm_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.cpu_credits | VM CPU credits low on ${label:resource_name} |
135
-| [ am_vm_memory_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.memory_percentage | VM available memory on ${label:resource_name} |
136
-| [ am_vm_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.availability | VM unavailable ${label:resource_name} |
137
-| [ am_vm_os_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_latency | VM OS disk latency on ${label:resource_name} |
138
-| [ am_vm_os_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_queue_depth | VM OS disk queue depth on ${label:resource_name} |
139
-| [ am_vm_os_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_throttling | VM OS disk bandwidth throttling on ${label:resource_name} |
140
-| [ am_vm_os_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_throttling | VM OS disk IOPS throttling on ${label:resource_name} |
141
-| [ am_vm_os_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_burst_credits | VM OS disk burst bandwidth credits on ${label:resource_name} |
142
-| [ am_vm_os_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_burst_credits | VM OS disk burst IO credits on ${label:resource_name} |
143
-| [ am_vm_data_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_latency | VM data disk latency on ${label:resource_name} |
144
-| [ am_vm_data_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_queue_depth | VM data disk queue depth on ${label:resource_name} |
145
-| [ am_vm_data_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_throttling | VM data disk bandwidth throttling on ${label:resource_name} |
146
-| [ am_vm_data_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_throttling | VM data disk IOPS throttling on ${label:resource_name} |
147
-| [ am_vm_data_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_burst_credits | VM data disk burst bandwidth credits on ${label:resource_name} |
148
-| [ am_vm_data_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_burst_credits | VM data disk burst IO credits on ${label:resource_name} |
149
-| [ am_vm_cached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_throttling | VM cached bandwidth throttling on ${label:resource_name} |
150
-| [ am_vm_cached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_throttling | VM cached IOPS throttling on ${label:resource_name} |
151
-| [ am_vm_uncached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_throttling | VM uncached bandwidth throttling on ${label:resource_name} |
152
-| [ am_vm_uncached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_throttling | VM uncached IOPS throttling on ${label:resource_name} |
153
-| [ am_vm_cached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_burst_credits | VM cached burst bandwidth credits on ${label:resource_name} |
154
-| [ am_vm_cached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_burst_credits | VM cached burst IO credits on ${label:resource_name} |
155
-| [ am_vm_uncached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_burst_credits | VM uncached burst bandwidth credits on ${label:resource_name} |
156
-| [ am_vm_uncached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_burst_credits | VM uncached burst IO credits on ${label:resource_name} |
157
-
158
-
60
## Setup
61
62
@@ -377,6 +278,105 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_vm_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.cpu | VM CPU on ${label:resource_name} |
289
+| [ am_vm_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.cpu_credits | VM CPU credits low on ${label:resource_name} |
290
+| [ am_vm_memory_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.memory_percentage | VM available memory on ${label:resource_name} |
291
+| [ am_vm_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.availability | VM unavailable ${label:resource_name} |
292
+| [ am_vm_os_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_latency | VM OS disk latency on ${label:resource_name} |
293
+| [ am_vm_os_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_queue_depth | VM OS disk queue depth on ${label:resource_name} |
294
+| [ am_vm_os_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_throttling | VM OS disk bandwidth throttling on ${label:resource_name} |
295
+| [ am_vm_os_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_throttling | VM OS disk IOPS throttling on ${label:resource_name} |
296
+| [ am_vm_os_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_burst_credits | VM OS disk burst bandwidth credits on ${label:resource_name} |
297
+| [ am_vm_os_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.os_disk_burst_credits | VM OS disk burst IO credits on ${label:resource_name} |
298
+| [ am_vm_data_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_latency | VM data disk latency on ${label:resource_name} |
299
+| [ am_vm_data_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_queue_depth | VM data disk queue depth on ${label:resource_name} |
300
+| [ am_vm_data_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_throttling | VM data disk bandwidth throttling on ${label:resource_name} |
301
+| [ am_vm_data_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_throttling | VM data disk IOPS throttling on ${label:resource_name} |
302
+| [ am_vm_data_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_burst_credits | VM data disk burst bandwidth credits on ${label:resource_name} |
303
+| [ am_vm_data_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.data_disk_burst_credits | VM data disk burst IO credits on ${label:resource_name} |
304
+| [ am_vm_cached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_throttling | VM cached bandwidth throttling on ${label:resource_name} |
305
+| [ am_vm_cached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_throttling | VM cached IOPS throttling on ${label:resource_name} |
306
+| [ am_vm_uncached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_throttling | VM uncached bandwidth throttling on ${label:resource_name} |
307
+| [ am_vm_uncached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_throttling | VM uncached IOPS throttling on ${label:resource_name} |
308
+| [ am_vm_cached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_burst_credits | VM cached burst bandwidth credits on ${label:resource_name} |
309
+| [ am_vm_cached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_cached_burst_credits | VM cached burst IO credits on ${label:resource_name} |
310
+| [ am_vm_uncached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_burst_credits | VM uncached burst bandwidth credits on ${label:resource_name} |
311
+| [ am_vm_uncached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_virtual_machines.conf) | azure_monitor.virtual_machines.vm_uncached_burst_credits | VM uncached burst IO credits on ${label:resource_name} |
312
+
313
+
314
+## Metrics
315
+
316
+Metrics grouped by *scope*.
317
+
318
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
319
+
320
+
321
+
322
+### Per resource
323
+
324
+These metrics refer to each monitored Azure resource.
325
+
326
+Labels:
327
+
328
+| Label | Description |
329
+|:-----------|:----------------|
330
+| resource_name | The Azure resource name. |
331
+| resource_group | The Azure resource group. |
332
+| region | The Azure region where the resource is deployed. |
333
+| resource_type | The Azure resource type identifier. |
334
+| profile | The Azure Monitor profile id. |
335
+| resource_uid | The unique Azure resource identifier. |
336
+
337
+Metrics:
338
+
339
+| Metric | Dimensions | Unit |
340
+|:------|:----------|:----|
341
+| azure_monitor.virtual_machines.cpu | average | percentage |
342
+| azure_monitor.virtual_machines.cpu_credits | consumed, remaining | credits |
343
+| azure_monitor.virtual_machines.memory | available | bytes |
344
+| azure_monitor.virtual_machines.memory_percentage | available | percentage |
345
+| azure_monitor.virtual_machines.availability | average | state |
346
+| azure_monitor.virtual_machines.network_traffic | in, out | bytes/s |
347
+| azure_monitor.virtual_machines.network_flows | in, out | flows |
348
+| azure_monitor.virtual_machines.network_flow_creation_rate | in, out | flows/s |
349
+| azure_monitor.virtual_machines.disk_throughput | read, write | bytes/s |
350
+| azure_monitor.virtual_machines.disk_iops | read, write | operations/s |
351
+| azure_monitor.virtual_machines.os_disk_throughput | read, write | bytes/s |
352
+| azure_monitor.virtual_machines.os_disk_iops | read, write | operations/s |
353
+| azure_monitor.virtual_machines.os_disk_latency | average | milliseconds |
354
+| azure_monitor.virtual_machines.os_disk_queue_depth | average | operations |
355
+| azure_monitor.virtual_machines.os_disk_throttling | bandwidth, iops | percentage |
356
+| azure_monitor.virtual_machines.os_disk_burst_capacity | max_burst, target | bytes/s |
357
+| azure_monitor.virtual_machines.os_disk_burst_iops_capacity | max_burst, target | iops |
358
+| azure_monitor.virtual_machines.os_disk_burst_credits | bandwidth, io | percentage |
359
+| azure_monitor.virtual_machines.data_disk_throughput | read, write | bytes/s |
360
+| azure_monitor.virtual_machines.data_disk_iops | read, write | operations/s |
361
+| azure_monitor.virtual_machines.data_disk_latency | average | milliseconds |
362
+| azure_monitor.virtual_machines.data_disk_queue_depth | average | operations |
363
+| azure_monitor.virtual_machines.data_disk_throttling | bandwidth, iops | percentage |
364
+| azure_monitor.virtual_machines.data_disk_burst_capacity | max_burst, target | bytes/s |
365
+| azure_monitor.virtual_machines.data_disk_burst_iops_capacity | max_burst, target | iops |
366
+| azure_monitor.virtual_machines.data_disk_burst_credits | bandwidth, io | percentage |
367
+| azure_monitor.virtual_machines.temp_disk_throughput | read, write | bytes/s |
368
+| azure_monitor.virtual_machines.temp_disk_iops | read, write | operations/s |
369
+| azure_monitor.virtual_machines.temp_disk_latency | average | milliseconds |
370
+| azure_monitor.virtual_machines.temp_disk_queue_depth | average | operations |
371
+| azure_monitor.virtual_machines.premium_data_disk_cache | hit, miss | percentage |
372
+| azure_monitor.virtual_machines.premium_os_disk_cache | hit, miss | percentage |
373
+| azure_monitor.virtual_machines.vm_cached_throttling | bandwidth, iops | percentage |
374
+| azure_monitor.virtual_machines.vm_uncached_throttling | bandwidth, iops | percentage |
375
+| azure_monitor.virtual_machines.vm_cached_burst_credits | bandwidth, io | percentage |
376
+| azure_monitor.virtual_machines.vm_uncached_burst_credits | bandwidth, io | percentage |
377
+
378
+
379
+
380
## Troubleshooting
381
382
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_virtual_machine_scale_set.md
+101
-101
@@ -57,107 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.vmss.cpu | average | percentage |
88
-| azure_monitor.vmss.cpu_credits | consumed, remaining | credits |
89
-| azure_monitor.vmss.memory | available | bytes |
90
-| azure_monitor.vmss.memory_percentage | available | percentage |
91
-| azure_monitor.vmss.availability | average | state |
92
-| azure_monitor.vmss.network_traffic | in, out | bytes/s |
93
-| azure_monitor.vmss.network_flows | in, out | flows |
94
-| azure_monitor.vmss.network_flow_creation_rate | in, out | flows/s |
95
-| azure_monitor.vmss.disk_throughput | read, write | bytes/s |
96
-| azure_monitor.vmss.disk_iops | read, write | operations/s |
97
-| azure_monitor.vmss.os_disk_throughput | read, write | bytes/s |
98
-| azure_monitor.vmss.os_disk_iops | read, write | operations/s |
99
-| azure_monitor.vmss.os_disk_latency | average | milliseconds |
100
-| azure_monitor.vmss.os_disk_queue_depth | average | operations |
101
-| azure_monitor.vmss.os_disk_throttling | bandwidth, iops | percentage |
102
-| azure_monitor.vmss.os_disk_burst_capacity | max_burst, target | bytes/s |
103
-| azure_monitor.vmss.os_disk_burst_iops_capacity | max_burst, target | iops |
104
-| azure_monitor.vmss.os_disk_burst_credits | bandwidth, io | percentage |
105
-| azure_monitor.vmss.data_disk_throughput | read, write | bytes/s |
106
-| azure_monitor.vmss.data_disk_iops | read, write | operations/s |
107
-| azure_monitor.vmss.data_disk_latency | average | milliseconds |
108
-| azure_monitor.vmss.data_disk_queue_depth | average | operations |
109
-| azure_monitor.vmss.data_disk_throttling | bandwidth, iops | percentage |
110
-| azure_monitor.vmss.data_disk_burst_capacity | max_burst, target | bytes/s |
111
-| azure_monitor.vmss.data_disk_burst_iops_capacity | max_burst, target | iops |
112
-| azure_monitor.vmss.data_disk_burst_credits | bandwidth, io | percentage |
113
-| azure_monitor.vmss.temp_disk_throughput | read, write | bytes/s |
114
-| azure_monitor.vmss.temp_disk_iops | read, write | operations/s |
115
-| azure_monitor.vmss.temp_disk_latency | average | milliseconds |
116
-| azure_monitor.vmss.temp_disk_queue_depth | average | operations |
117
-| azure_monitor.vmss.premium_data_disk_cache | hit, miss | percentage |
118
-| azure_monitor.vmss.premium_os_disk_cache | hit, miss | percentage |
119
-| azure_monitor.vmss.vm_cached_throttling | bandwidth, iops | percentage |
120
-| azure_monitor.vmss.vm_uncached_throttling | bandwidth, iops | percentage |
121
-| azure_monitor.vmss.vm_cached_burst_credits | bandwidth, io | percentage |
122
-| azure_monitor.vmss.vm_uncached_burst_credits | bandwidth, io | percentage |
123
-
124
-
125
-
126
-## Alerts
127
-
128
-
129
-The following alerts are available:
130
-
131
-| Alert name | On metric | Description |
132
-|:------------|:----------|:------------|
133
-| [ am_vmss_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.cpu | VMSS CPU utilization on ${label:resource_name} |
134
-| [ am_vmss_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.cpu_credits | VMSS CPU credits low on ${label:resource_name} |
135
-| [ am_vmss_memory_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.memory_percentage | VMSS available memory low on ${label:resource_name} |
136
-| [ am_vmss_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.availability | VMSS availability degraded on ${label:resource_name} |
137
-| [ am_vmss_os_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_latency | VMSS OS disk latency on ${label:resource_name} |
138
-| [ am_vmss_os_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_queue_depth | VMSS OS disk queue depth on ${label:resource_name} |
139
-| [ am_vmss_os_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_throttling | VMSS OS disk bandwidth consumed on ${label:resource_name} |
140
-| [ am_vmss_os_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_throttling | VMSS OS disk IOPS consumed on ${label:resource_name} |
141
-| [ am_vmss_os_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_burst_credits | VMSS OS disk burst BPS credits depleting on ${label:resource_name} |
142
-| [ am_vmss_os_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_burst_credits | VMSS OS disk burst IO credits depleting on ${label:resource_name} |
143
-| [ am_vmss_data_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_latency | VMSS data disk latency on ${label:resource_name} |
144
-| [ am_vmss_data_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_queue_depth | VMSS data disk queue depth on ${label:resource_name} |
145
-| [ am_vmss_data_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_throttling | VMSS data disk bandwidth consumed on ${label:resource_name} |
146
-| [ am_vmss_data_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_throttling | VMSS data disk IOPS consumed on ${label:resource_name} |
147
-| [ am_vmss_data_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_burst_credits | VMSS data disk burst BPS credits depleting on ${label:resource_name} |
148
-| [ am_vmss_data_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_burst_credits | VMSS data disk burst IO credits depleting on ${label:resource_name} |
149
-| [ am_vmss_temp_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.temp_disk_latency | VMSS temp disk latency on ${label:resource_name} |
150
-| [ am_vmss_temp_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.temp_disk_queue_depth | VMSS temp disk queue depth on ${label:resource_name} |
151
-| [ am_vmss_vm_cached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_throttling | VMSS cached bandwidth consumed on ${label:resource_name} |
152
-| [ am_vmss_vm_cached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_throttling | VMSS cached IOPS consumed on ${label:resource_name} |
153
-| [ am_vmss_vm_uncached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_throttling | VMSS uncached bandwidth consumed on ${label:resource_name} |
154
-| [ am_vmss_vm_uncached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_throttling | VMSS uncached IOPS consumed on ${label:resource_name} |
155
-| [ am_vmss_vm_cached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_burst_credits | VMSS cached burst BPS credits depleting on ${label:resource_name} |
156
-| [ am_vmss_vm_cached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_burst_credits | VMSS cached burst IO credits depleting on ${label:resource_name} |
157
-| [ am_vmss_vm_uncached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_burst_credits | VMSS uncached burst BPS credits depleting on ${label:resource_name} |
158
-| [ am_vmss_vm_uncached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_burst_credits | VMSS uncached burst IO credits depleting on ${label:resource_name} |
159
-
160
-
60
## Setup
61
62
@@ -379,6 +278,107 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_vmss_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.cpu | VMSS CPU utilization on ${label:resource_name} |
289
+| [ am_vmss_cpu_credits_remaining ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.cpu_credits | VMSS CPU credits low on ${label:resource_name} |
290
+| [ am_vmss_memory_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.memory_percentage | VMSS available memory low on ${label:resource_name} |
291
+| [ am_vmss_availability ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.availability | VMSS availability degraded on ${label:resource_name} |
292
+| [ am_vmss_os_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_latency | VMSS OS disk latency on ${label:resource_name} |
293
+| [ am_vmss_os_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_queue_depth | VMSS OS disk queue depth on ${label:resource_name} |
294
+| [ am_vmss_os_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_throttling | VMSS OS disk bandwidth consumed on ${label:resource_name} |
295
+| [ am_vmss_os_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_throttling | VMSS OS disk IOPS consumed on ${label:resource_name} |
296
+| [ am_vmss_os_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_burst_credits | VMSS OS disk burst BPS credits depleting on ${label:resource_name} |
297
+| [ am_vmss_os_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.os_disk_burst_credits | VMSS OS disk burst IO credits depleting on ${label:resource_name} |
298
+| [ am_vmss_data_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_latency | VMSS data disk latency on ${label:resource_name} |
299
+| [ am_vmss_data_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_queue_depth | VMSS data disk queue depth on ${label:resource_name} |
300
+| [ am_vmss_data_disk_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_throttling | VMSS data disk bandwidth consumed on ${label:resource_name} |
301
+| [ am_vmss_data_disk_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_throttling | VMSS data disk IOPS consumed on ${label:resource_name} |
302
+| [ am_vmss_data_disk_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_burst_credits | VMSS data disk burst BPS credits depleting on ${label:resource_name} |
303
+| [ am_vmss_data_disk_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.data_disk_burst_credits | VMSS data disk burst IO credits depleting on ${label:resource_name} |
304
+| [ am_vmss_temp_disk_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.temp_disk_latency | VMSS temp disk latency on ${label:resource_name} |
305
+| [ am_vmss_temp_disk_queue_depth ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.temp_disk_queue_depth | VMSS temp disk queue depth on ${label:resource_name} |
306
+| [ am_vmss_vm_cached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_throttling | VMSS cached bandwidth consumed on ${label:resource_name} |
307
+| [ am_vmss_vm_cached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_throttling | VMSS cached IOPS consumed on ${label:resource_name} |
308
+| [ am_vmss_vm_uncached_bandwidth_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_throttling | VMSS uncached bandwidth consumed on ${label:resource_name} |
309
+| [ am_vmss_vm_uncached_iops_throttling ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_throttling | VMSS uncached IOPS consumed on ${label:resource_name} |
310
+| [ am_vmss_vm_cached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_burst_credits | VMSS cached burst BPS credits depleting on ${label:resource_name} |
311
+| [ am_vmss_vm_cached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_cached_burst_credits | VMSS cached burst IO credits depleting on ${label:resource_name} |
312
+| [ am_vmss_vm_uncached_burst_bps_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_burst_credits | VMSS uncached burst BPS credits depleting on ${label:resource_name} |
313
+| [ am_vmss_vm_uncached_burst_io_credits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vmss.conf) | azure_monitor.vmss.vm_uncached_burst_credits | VMSS uncached burst IO credits depleting on ${label:resource_name} |
314
+
315
+
316
+## Metrics
317
+
318
+Metrics grouped by *scope*.
319
+
320
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
321
+
322
+
323
+
324
+### Per resource
325
+
326
+These metrics refer to each monitored Azure resource.
327
+
328
+Labels:
329
+
330
+| Label | Description |
331
+|:-----------|:----------------|
332
+| resource_name | The Azure resource name. |
333
+| resource_group | The Azure resource group. |
334
+| region | The Azure region where the resource is deployed. |
335
+| resource_type | The Azure resource type identifier. |
336
+| profile | The Azure Monitor profile id. |
337
+| resource_uid | The unique Azure resource identifier. |
338
+
339
+Metrics:
340
+
341
+| Metric | Dimensions | Unit |
342
+|:------|:----------|:----|
343
+| azure_monitor.vmss.cpu | average | percentage |
344
+| azure_monitor.vmss.cpu_credits | consumed, remaining | credits |
345
+| azure_monitor.vmss.memory | available | bytes |
346
+| azure_monitor.vmss.memory_percentage | available | percentage |
347
+| azure_monitor.vmss.availability | average | state |
348
+| azure_monitor.vmss.network_traffic | in, out | bytes/s |
349
+| azure_monitor.vmss.network_flows | in, out | flows |
350
+| azure_monitor.vmss.network_flow_creation_rate | in, out | flows/s |
351
+| azure_monitor.vmss.disk_throughput | read, write | bytes/s |
352
+| azure_monitor.vmss.disk_iops | read, write | operations/s |
353
+| azure_monitor.vmss.os_disk_throughput | read, write | bytes/s |
354
+| azure_monitor.vmss.os_disk_iops | read, write | operations/s |
355
+| azure_monitor.vmss.os_disk_latency | average | milliseconds |
356
+| azure_monitor.vmss.os_disk_queue_depth | average | operations |
357
+| azure_monitor.vmss.os_disk_throttling | bandwidth, iops | percentage |
358
+| azure_monitor.vmss.os_disk_burst_capacity | max_burst, target | bytes/s |
359
+| azure_monitor.vmss.os_disk_burst_iops_capacity | max_burst, target | iops |
360
+| azure_monitor.vmss.os_disk_burst_credits | bandwidth, io | percentage |
361
+| azure_monitor.vmss.data_disk_throughput | read, write | bytes/s |
362
+| azure_monitor.vmss.data_disk_iops | read, write | operations/s |
363
+| azure_monitor.vmss.data_disk_latency | average | milliseconds |
364
+| azure_monitor.vmss.data_disk_queue_depth | average | operations |
365
+| azure_monitor.vmss.data_disk_throttling | bandwidth, iops | percentage |
366
+| azure_monitor.vmss.data_disk_burst_capacity | max_burst, target | bytes/s |
367
+| azure_monitor.vmss.data_disk_burst_iops_capacity | max_burst, target | iops |
368
+| azure_monitor.vmss.data_disk_burst_credits | bandwidth, io | percentage |
369
+| azure_monitor.vmss.temp_disk_throughput | read, write | bytes/s |
370
+| azure_monitor.vmss.temp_disk_iops | read, write | operations/s |
371
+| azure_monitor.vmss.temp_disk_latency | average | milliseconds |
372
+| azure_monitor.vmss.temp_disk_queue_depth | average | operations |
373
+| azure_monitor.vmss.premium_data_disk_cache | hit, miss | percentage |
374
+| azure_monitor.vmss.premium_os_disk_cache | hit, miss | percentage |
375
+| azure_monitor.vmss.vm_cached_throttling | bandwidth, iops | percentage |
376
+| azure_monitor.vmss.vm_uncached_throttling | bandwidth, iops | percentage |
377
+| azure_monitor.vmss.vm_cached_burst_credits | bandwidth, io | percentage |
378
+| azure_monitor.vmss.vm_uncached_burst_credits | bandwidth, io | percentage |
379
+
380
+
381
+
382
## Troubleshooting
383
384
### Debug Mode
src/go/plugin/go.d/collector/azure_monitor/integrations/azure_vpn_gateway.md
+92
-92
@@ -57,98 +57,6 @@ The collector uses bounded request concurrency and batches resources and metrics
57
Default limits: 4 concurrent queries, 50 resources per batch, 20 metrics per query.
58
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per resource
69
-
70
-These metrics refer to each monitored Azure resource.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| resource_name | The Azure resource name. |
77
-| resource_group | The Azure resource group. |
78
-| region | The Azure region where the resource is deployed. |
79
-| resource_type | The Azure resource type identifier. |
80
-| profile | The Azure Monitor profile id. |
81
-| resource_uid | The unique Azure resource identifier. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| azure_monitor.vpn_gateway.s2s_bandwidth | average | bytes/s |
88
-| azure_monitor.vpn_gateway.p2s_bandwidth | average | bytes/s |
89
-| azure_monitor.vpn_gateway.p2s_connections | total | connections |
90
-| azure_monitor.vpn_gateway.gateway_flows | inbound, outbound | flows |
91
-| azure_monitor.vpn_gateway.tunnel_bandwidth | average | bytes/s |
92
-| azure_monitor.vpn_gateway.tunnel_bytes | egress, ingress | bytes/s |
93
-| azure_monitor.vpn_gateway.tunnel_packets | egress, ingress | packets/s |
94
-| azure_monitor.vpn_gateway.tunnel_peak_pps | peak | packets/s |
95
-| azure_monitor.vpn_gateway.tunnel_total_flows | total | flows/s |
96
-| azure_monitor.vpn_gateway.tunnel_nat_allocations | total | allocations/s |
97
-| azure_monitor.vpn_gateway.tunnel_nated_bytes | nated, reverse_nated | bytes/s |
98
-| azure_monitor.vpn_gateway.tunnel_nated_packets | nated, reverse_nated | packets/s |
99
-| azure_monitor.vpn_gateway.tunnel_nat_flows | total | flows/s |
100
-| azure_monitor.vpn_gateway.tunnel_packet_drops | egress, ingress | packets/s |
101
-| azure_monitor.vpn_gateway.tunnel_ts_mismatch_drops | egress, ingress | packets/s |
102
-| azure_monitor.vpn_gateway.tunnel_nat_packet_drops | total | packets/s |
103
-| azure_monitor.vpn_gateway.ipsec_sa | mmsa, qmsa | associations |
104
-| azure_monitor.vpn_gateway.bgp_peer_status | average | status |
105
-| azure_monitor.vpn_gateway.bgp_routes | advertised, learned | routes/s |
106
-| azure_monitor.vpn_gateway.route_counts | user_vpn, vnet_prefix | routes |
107
-| azure_monitor.vpn_gateway.er_gateway_bandwidth | average | bits/s |
108
-| azure_monitor.vpn_gateway.er_gateway_cpu | average | percentage |
109
-| azure_monitor.vpn_gateway.er_gateway_packets | average | packets/s |
110
-| azure_monitor.vpn_gateway.er_gateway_active_flows | average | flows |
111
-| azure_monitor.vpn_gateway.er_gateway_routes_advertised | maximum | routes |
112
-| azure_monitor.vpn_gateway.er_gateway_routes_learned | maximum | routes |
113
-| azure_monitor.vpn_gateway.er_gateway_route_changes | total | changes/s |
114
-| azure_monitor.vpn_gateway.er_gateway_max_flows_rate | maximum | flows/s |
115
-| azure_monitor.vpn_gateway.er_gateway_vm_count | maximum | VMs |
116
-| azure_monitor.vpn_gateway.scalable_er_bandwidth | average | bits/s |
117
-| azure_monitor.vpn_gateway.scalable_er_cpu | average | percentage |
118
-| azure_monitor.vpn_gateway.scalable_er_packets | average | packets/s |
119
-| azure_monitor.vpn_gateway.scalable_er_active_flows | average | flows |
120
-| azure_monitor.vpn_gateway.scalable_er_routes_advertised | maximum | routes |
121
-| azure_monitor.vpn_gateway.scalable_er_routes_learned | maximum | routes |
122
-| azure_monitor.vpn_gateway.scalable_er_route_changes | total | changes/s |
123
-| azure_monitor.vpn_gateway.scalable_er_max_flows_rate | maximum | flows/s |
124
-| azure_monitor.vpn_gateway.scalable_er_vm_count | maximum | VMs |
125
-| azure_monitor.vpn_gateway.scalable_er_scale_units | maximum | units |
126
-
127
-
128
-
129
-## Alerts
130
-
131
-
132
-The following alerts are available:
133
-
134
-| Alert name | On metric | Description |
135
-|:------------|:----------|:------------|
136
-| [ am_vpn_gateway_tunnel_packet_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.tunnel_packet_drops | VPN Gateway tunnel packet drops on ${label:resource_name} |
137
-| [ am_vpn_gateway_tunnel_ts_mismatch_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.tunnel_ts_mismatch_drops | VPN Gateway TS mismatch drops on ${label:resource_name} |
138
-| [ am_vpn_gateway_tunnel_nat_packet_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.tunnel_nat_packet_drops | VPN Gateway NAT packet drops on ${label:resource_name} |
139
-| [ am_vpn_gateway_bgp_peer_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.bgp_peer_status | VPN Gateway BGP peer down on ${label:resource_name} |
140
-| [ am_vpn_gateway_er_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_cpu | VPN GW ExpressRoute CPU on ${label:resource_name} |
141
-| [ am_vpn_gateway_er_gateway_active_flows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_active_flows | VPN GW ExpressRoute active flows on ${label:resource_name} |
142
-| [ am_vpn_gateway_er_gateway_route_changes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_route_changes | VPN GW ExpressRoute route churn on ${label:resource_name} |
143
-| [ am_vpn_gateway_er_gateway_routes_advertised ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_routes_advertised | VPN GW ExpressRoute routes advertised on ${label:resource_name} |
144
-| [ am_vpn_gateway_er_gateway_routes_learned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_routes_learned | VPN GW ExpressRoute routes learned on ${label:resource_name} |
145
-| [ am_vpn_gateway_scalable_er_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_cpu | VPN GW Scalable ER CPU on ${label:resource_name} |
146
-| [ am_vpn_gateway_scalable_er_active_flows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_active_flows | VPN GW Scalable ER active flows on ${label:resource_name} |
147
-| [ am_vpn_gateway_scalable_er_route_changes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_route_changes | VPN GW Scalable ER route churn on ${label:resource_name} |
148
-| [ am_vpn_gateway_scalable_er_routes_advertised ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_routes_advertised | VPN GW Scalable ER routes advertised on ${label:resource_name} |
149
-| [ am_vpn_gateway_scalable_er_routes_learned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_routes_learned | VPN GW Scalable ER routes learned on ${label:resource_name} |
150
-
151
-
60
## Setup
61
62
@@ -370,6 +278,98 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+
284
+The following alerts are available:
285
+
286
+| Alert name | On metric | Description |
287
+|:------------|:----------|:------------|
288
+| [ am_vpn_gateway_tunnel_packet_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.tunnel_packet_drops | VPN Gateway tunnel packet drops on ${label:resource_name} |
289
+| [ am_vpn_gateway_tunnel_ts_mismatch_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.tunnel_ts_mismatch_drops | VPN Gateway TS mismatch drops on ${label:resource_name} |
290
+| [ am_vpn_gateway_tunnel_nat_packet_drops ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.tunnel_nat_packet_drops | VPN Gateway NAT packet drops on ${label:resource_name} |
291
+| [ am_vpn_gateway_bgp_peer_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.bgp_peer_status | VPN Gateway BGP peer down on ${label:resource_name} |
292
+| [ am_vpn_gateway_er_gateway_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_cpu | VPN GW ExpressRoute CPU on ${label:resource_name} |
293
+| [ am_vpn_gateway_er_gateway_active_flows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_active_flows | VPN GW ExpressRoute active flows on ${label:resource_name} |
294
+| [ am_vpn_gateway_er_gateway_route_changes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_route_changes | VPN GW ExpressRoute route churn on ${label:resource_name} |
295
+| [ am_vpn_gateway_er_gateway_routes_advertised ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_routes_advertised | VPN GW ExpressRoute routes advertised on ${label:resource_name} |
296
+| [ am_vpn_gateway_er_gateway_routes_learned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.er_gateway_routes_learned | VPN GW ExpressRoute routes learned on ${label:resource_name} |
297
+| [ am_vpn_gateway_scalable_er_cpu ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_cpu | VPN GW Scalable ER CPU on ${label:resource_name} |
298
+| [ am_vpn_gateway_scalable_er_active_flows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_active_flows | VPN GW Scalable ER active flows on ${label:resource_name} |
299
+| [ am_vpn_gateway_scalable_er_route_changes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_route_changes | VPN GW Scalable ER route churn on ${label:resource_name} |
300
+| [ am_vpn_gateway_scalable_er_routes_advertised ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_routes_advertised | VPN GW Scalable ER routes advertised on ${label:resource_name} |
301
+| [ am_vpn_gateway_scalable_er_routes_learned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/azure_monitor_vpn_gateway.conf) | azure_monitor.vpn_gateway.scalable_er_routes_learned | VPN GW Scalable ER routes learned on ${label:resource_name} |
302
+
303
+
304
+## Metrics
305
+
306
+Metrics grouped by *scope*.
307
+
308
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
309
+
310
+
311
+
312
+### Per resource
313
+
314
+These metrics refer to each monitored Azure resource.
315
+
316
+Labels:
317
+
318
+| Label | Description |
319
+|:-----------|:----------------|
320
+| resource_name | The Azure resource name. |
321
+| resource_group | The Azure resource group. |
322
+| region | The Azure region where the resource is deployed. |
323
+| resource_type | The Azure resource type identifier. |
324
+| profile | The Azure Monitor profile id. |
325
+| resource_uid | The unique Azure resource identifier. |
326
+
327
+Metrics:
328
+
329
+| Metric | Dimensions | Unit |
330
+|:------|:----------|:----|
331
+| azure_monitor.vpn_gateway.s2s_bandwidth | average | bytes/s |
332
+| azure_monitor.vpn_gateway.p2s_bandwidth | average | bytes/s |
333
+| azure_monitor.vpn_gateway.p2s_connections | total | connections |
334
+| azure_monitor.vpn_gateway.gateway_flows | inbound, outbound | flows |
335
+| azure_monitor.vpn_gateway.tunnel_bandwidth | average | bytes/s |
336
+| azure_monitor.vpn_gateway.tunnel_bytes | egress, ingress | bytes/s |
337
+| azure_monitor.vpn_gateway.tunnel_packets | egress, ingress | packets/s |
338
+| azure_monitor.vpn_gateway.tunnel_peak_pps | peak | packets/s |
339
+| azure_monitor.vpn_gateway.tunnel_total_flows | total | flows/s |
340
+| azure_monitor.vpn_gateway.tunnel_nat_allocations | total | allocations/s |
341
+| azure_monitor.vpn_gateway.tunnel_nated_bytes | nated, reverse_nated | bytes/s |
342
+| azure_monitor.vpn_gateway.tunnel_nated_packets | nated, reverse_nated | packets/s |
343
+| azure_monitor.vpn_gateway.tunnel_nat_flows | total | flows/s |
344
+| azure_monitor.vpn_gateway.tunnel_packet_drops | egress, ingress | packets/s |
345
+| azure_monitor.vpn_gateway.tunnel_ts_mismatch_drops | egress, ingress | packets/s |
346
+| azure_monitor.vpn_gateway.tunnel_nat_packet_drops | total | packets/s |
347
+| azure_monitor.vpn_gateway.ipsec_sa | mmsa, qmsa | associations |
348
+| azure_monitor.vpn_gateway.bgp_peer_status | average | status |
349
+| azure_monitor.vpn_gateway.bgp_routes | advertised, learned | routes/s |
350
+| azure_monitor.vpn_gateway.route_counts | user_vpn, vnet_prefix | routes |
351
+| azure_monitor.vpn_gateway.er_gateway_bandwidth | average | bits/s |
352
+| azure_monitor.vpn_gateway.er_gateway_cpu | average | percentage |
353
+| azure_monitor.vpn_gateway.er_gateway_packets | average | packets/s |
354
+| azure_monitor.vpn_gateway.er_gateway_active_flows | average | flows |
355
+| azure_monitor.vpn_gateway.er_gateway_routes_advertised | maximum | routes |
356
+| azure_monitor.vpn_gateway.er_gateway_routes_learned | maximum | routes |
357
+| azure_monitor.vpn_gateway.er_gateway_route_changes | total | changes/s |
358
+| azure_monitor.vpn_gateway.er_gateway_max_flows_rate | maximum | flows/s |
359
+| azure_monitor.vpn_gateway.er_gateway_vm_count | maximum | VMs |
360
+| azure_monitor.vpn_gateway.scalable_er_bandwidth | average | bits/s |
361
+| azure_monitor.vpn_gateway.scalable_er_cpu | average | percentage |
362
+| azure_monitor.vpn_gateway.scalable_er_packets | average | packets/s |
363
+| azure_monitor.vpn_gateway.scalable_er_active_flows | average | flows |
364
+| azure_monitor.vpn_gateway.scalable_er_routes_advertised | maximum | routes |
365
+| azure_monitor.vpn_gateway.scalable_er_routes_learned | maximum | routes |
366
+| azure_monitor.vpn_gateway.scalable_er_route_changes | total | changes/s |
367
+| azure_monitor.vpn_gateway.scalable_er_max_flows_rate | maximum | flows/s |
368
+| azure_monitor.vpn_gateway.scalable_er_vm_count | maximum | VMs |
369
+| azure_monitor.vpn_gateway.scalable_er_scale_units | maximum | units |
370
+
371
+
372
+
373
## Troubleshooting
374
375
### Debug Mode
src/go/plugin/go.d/collector/beanstalk/integrations/beanstalk.md
+61
-61
@@ -52,67 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
The default configuration for this integration is not expected to impose a significant performance impact on the system.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per Beanstalk instance
64
-
65
-These metrics refer to the entire monitored application.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| beanstalk.current_jobs | ready, buried, urgent, delayed, reserved | jobs |
74
-| beanstalk.jobs_rate | created | jobs/s |
75
-| beanstalk.jobs_timeouts | timeouts | jobs/s |
76
-| beanstalk.current_tubes | tubes | tubes |
77
-| beanstalk.commands_rate | put, peek, peek-ready, peek-delayed, peek-buried, reserve, reserve-with-timeout, touch, use, watch, ignore, delete, bury, kick, stats, stats-job, stats-tube, list-tubes, list-tube-used, list-tubes-watched, pause-tube | commands/s |
78
-| beanstalk.current_connections | open, producers, workers, waiting | connections |
79
-| beanstalk.connections_rate | created | connections/s |
80
-| beanstalk.binlog_records | written, migrated | records/s |
81
-| beanstalk.cpu_usage | user, system | percent |
82
-| beanstalk.uptime | uptime | seconds |
83
-
84
-### Per tube
85
-
86
-Metrics related to Beanstalk tubes. This set of metrics is provided for each tube.
87
-
88
-Labels:
89
-
90
-| Label | Description |
91
-|:-----------|:----------------|
92
-| tube_name | Tube name. |
93
-
94
-Metrics:
95
-
96
-| Metric | Dimensions | Unit |
97
-|:------|:----------|:----|
98
-| beanstalk.tube_current_jobs | ready, buried, urgent, delayed, reserved | jobs |
99
-| beanstalk.tube_jobs_rate | created | jobs/s |
100
-| beanstalk.tube_commands_rate | delete, pause-tube | commands/s |
101
-| beanstalk.tube_current_connections | using, waiting, watching | connections |
102
-| beanstalk.tube_pause_time | since, left | seconds |
103
-
104
-
105
-
106
-## Alerts
107
-
108
-
109
-The following alerts are available:
110
-
111
-| Alert name | On metric | Description |
112
-|:------------|:----------|:------------|
113
-| [ beanstalk_server_buried_jobs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/beanstalkd.conf) | beanstalk.current_jobs | number of buried jobs across all tubes. You need to manually kick them so they can be processed. Presence of buried jobs in a tube does not affect new jobs. |
114
-
115
-
55
## Setup
56
57
@@ -231,6 +170,67 @@ jobs:
170
171
172
173
+## Alerts
174
+
175
+
176
+The following alerts are available:
177
+
178
+| Alert name | On metric | Description |
179
+|:------------|:----------|:------------|
180
+| [ beanstalk_server_buried_jobs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/beanstalkd.conf) | beanstalk.current_jobs | number of buried jobs across all tubes. You need to manually kick them so they can be processed. Presence of buried jobs in a tube does not affect new jobs. |
181
+
182
+
183
+## Metrics
184
+
185
+Metrics grouped by *scope*.
186
+
187
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
188
+
189
+
190
+
191
+### Per Beanstalk instance
192
+
193
+These metrics refer to the entire monitored application.
194
+
195
+This scope has no labels.
196
+
197
+Metrics:
198
+
199
+| Metric | Dimensions | Unit |
200
+|:------|:----------|:----|
201
+| beanstalk.current_jobs | ready, buried, urgent, delayed, reserved | jobs |
202
+| beanstalk.jobs_rate | created | jobs/s |
203
+| beanstalk.jobs_timeouts | timeouts | jobs/s |
204
+| beanstalk.current_tubes | tubes | tubes |
205
+| beanstalk.commands_rate | put, peek, peek-ready, peek-delayed, peek-buried, reserve, reserve-with-timeout, touch, use, watch, ignore, delete, bury, kick, stats, stats-job, stats-tube, list-tubes, list-tube-used, list-tubes-watched, pause-tube | commands/s |
206
+| beanstalk.current_connections | open, producers, workers, waiting | connections |
207
+| beanstalk.connections_rate | created | connections/s |
208
+| beanstalk.binlog_records | written, migrated | records/s |
209
+| beanstalk.cpu_usage | user, system | percent |
210
+| beanstalk.uptime | uptime | seconds |
211
+
212
+### Per tube
213
+
214
+Metrics related to Beanstalk tubes. This set of metrics is provided for each tube.
215
+
216
+Labels:
217
+
218
+| Label | Description |
219
+|:-----------|:----------------|
220
+| tube_name | Tube name. |
221
+
222
+Metrics:
223
+
224
+| Metric | Dimensions | Unit |
225
+|:------|:----------|:----|
226
+| beanstalk.tube_current_jobs | ready, buried, urgent, delayed, reserved | jobs |
227
+| beanstalk.tube_jobs_rate | created | jobs/s |
228
+| beanstalk.tube_commands_rate | delete, pause-tube | commands/s |
229
+| beanstalk.tube_current_connections | using, waiting, watching | connections |
230
+| beanstalk.tube_pause_time | since, left | seconds |
231
+
232
+
233
+
234
## Troubleshooting
235
236
### Debug Mode
src/go/plugin/go.d/collector/boinc/integrations/boinc.md
+38
-38
@@ -50,44 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per BOINC instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| boinc.tasks | total, active | tasks |
72
-| boinc.tasks_per_state | new, downloading, downloaded, compute_error, uploading, uploaded, aborted, upload_failed | tasks |
73
-| boinc.active_tasks_per_state | uninitialized, executing, abort_pending, quit_pending, suspended, copy_pending | tasks |
74
-| boinc.active_tasks_per_scheduler_state | uninitialized, preempted, scheduled | tasks |
75
-
76
-
77
-
78
-## Alerts
79
-
80
-
81
-The following alerts are available:
82
-
83
-| Alert name | On metric | Description |
84
-|:------------|:----------|:------------|
85
-| [ boinc_total_tasks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks | average number of total tasks over the last 10 minutes |
86
-| [ boinc_active_tasks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks | average number of active tasks over the last 10 minutes |
87
-| [ boinc_compute_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks_state | average number of compute errors over the last 10 minutes |
88
-| [ boinc_upload_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks_state | average number of failed uploads over the last 10 minutes |
89
-
90
-
53
## Setup
54
55
@@ -206,6 +168,44 @@ jobs:
168
169
170
171
+## Alerts
172
+
173
+
174
+The following alerts are available:
175
+
176
+| Alert name | On metric | Description |
177
+|:------------|:----------|:------------|
178
+| [ boinc_total_tasks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks | average number of total tasks over the last 10 minutes |
179
+| [ boinc_active_tasks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks | average number of active tasks over the last 10 minutes |
180
+| [ boinc_compute_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks_state | average number of compute errors over the last 10 minutes |
181
+| [ boinc_upload_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/boinc.conf) | boinc.tasks_state | average number of failed uploads over the last 10 minutes |
182
+
183
+
184
+## Metrics
185
+
186
+Metrics grouped by *scope*.
187
+
188
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
189
+
190
+
191
+
192
+### Per BOINC instance
193
+
194
+These metrics refer to the entire monitored application.
195
+
196
+This scope has no labels.
197
+
198
+Metrics:
199
+
200
+| Metric | Dimensions | Unit |
201
+|:------|:----------|:----|
202
+| boinc.tasks | total, active | tasks |
203
+| boinc.tasks_per_state | new, downloading, downloaded, compute_error, uploading, uploaded, aborted, upload_failed | tasks |
204
+| boinc.active_tasks_per_state | uninitialized, executing, abort_pending, quit_pending, suspended, copy_pending | tasks |
205
+| boinc.active_tasks_per_scheduler_state | uninitialized, preempted, scheduled | tasks |
206
+
207
+
208
+
209
## Troubleshooting
210
211
### Debug Mode
src/go/plugin/go.d/collector/cassandra/integrations/cassandra.md
+69
-69
@@ -51,75 +51,6 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
-## Metrics
55
-
56
-Metrics grouped by *scope*.
57
-
58
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
59
-
60
-
61
-
62
-### Per Cassandra instance
63
-
64
-These metrics refer to the entire monitored application.
65
-
66
-This scope has no labels.
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| cassandra.client_requests_rate | read, write | requests/s |
73
-| cassandra.client_request_read_latency_histogram | p50, p75, p95, p98, p99, p999 | seconds |
74
-| cassandra.client_request_write_latency_histogram | p50, p75, p95, p98, p99, p999 | seconds |
75
-| cassandra.client_requests_latency | read, write | seconds |
76
-| cassandra.row_cache_hit_ratio | hit_ratio | percentage |
77
-| cassandra.row_cache_hit_rate | hits, misses | events/s |
78
-| cassandra.row_cache_utilization | used | percentage |
79
-| cassandra.row_cache_size | size | bytes |
80
-| cassandra.key_cache_hit_ratio | hit_ratio | percentage |
81
-| cassandra.key_cache_hit_rate | hits, misses | events/s |
82
-| cassandra.key_cache_utilization | used | percentage |
83
-| cassandra.key_cache_size | size | bytes |
84
-| cassandra.storage_live_disk_space_used | used | bytes |
85
-| cassandra.compaction_completed_tasks_rate | completed | tasks/s |
86
-| cassandra.compaction_pending_tasks_count | pending | tasks |
87
-| cassandra.compaction_compacted_rate | compacted | bytes/s |
88
-| cassandra.jvm_memory_used | heap, nonheap | bytes |
89
-| cassandra.jvm_gc_rate | parnew, cms | gc/s |
90
-| cassandra.jvm_gc_time | parnew, cms | seconds |
91
-| cassandra.dropped_messages_rate | dropped | messages/s |
92
-| cassandra.client_requests_timeouts_rate | read, write | timeout/s |
93
-| cassandra.client_requests_unavailables_rate | read, write | exceptions/s |
94
-| cassandra.client_requests_failures_rate | read, write | failures/s |
95
-| cassandra.storage_exceptions_rate | storage | exceptions/s |
96
-
97
-### Per thread pool
98
-
99
-Metrics related to Cassandra's thread pools. Each thread pool provides its own set of the following metrics.
100
-
101
-Labels:
102
-
103
-| Label | Description |
104
-|:-----------|:----------------|
105
-| thread_pool | thread pool name |
106
-
107
-Metrics:
108
-
109
-| Metric | Dimensions | Unit |
110
-|:------|:----------|:----|
111
-| cassandra.thread_pool_active_tasks_count | active | tasks |
112
-| cassandra.thread_pool_pending_tasks_count | pending | tasks |
113
-| cassandra.thread_pool_blocked_tasks_count | blocked | tasks |
114
-| cassandra.thread_pool_blocked_tasks_rate | blocked | tasks/s |
115
-
116
-
117
-
118
-## Alerts
119
-
120
-There are no alerts configured by default for this integration.
121
-
122
-
54
## Setup
55
56
@@ -296,6 +227,75 @@ jobs:
227
228
229
230
+## Alerts
231
+
232
+There are no alerts configured by default for this integration.
233
+
234
+
235
+## Metrics
236
+
237
+Metrics grouped by *scope*.
238
+
239
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
240
+
241
+
242
+
243
+### Per Cassandra instance
244
+
245
+These metrics refer to the entire monitored application.
246
+
247
+This scope has no labels.
248
+
249
+Metrics:
250
+
251
+| Metric | Dimensions | Unit |
252
+|:------|:----------|:----|
253
+| cassandra.client_requests_rate | read, write | requests/s |
254
+| cassandra.client_request_read_latency_histogram | p50, p75, p95, p98, p99, p999 | seconds |
255
+| cassandra.client_request_write_latency_histogram | p50, p75, p95, p98, p99, p999 | seconds |
256
+| cassandra.client_requests_latency | read, write | seconds |
257
+| cassandra.row_cache_hit_ratio | hit_ratio | percentage |
258
+| cassandra.row_cache_hit_rate | hits, misses | events/s |
259
+| cassandra.row_cache_utilization | used | percentage |
260
+| cassandra.row_cache_size | size | bytes |
261
+| cassandra.key_cache_hit_ratio | hit_ratio | percentage |
262
+| cassandra.key_cache_hit_rate | hits, misses | events/s |
263
+| cassandra.key_cache_utilization | used | percentage |
264
+| cassandra.key_cache_size | size | bytes |
265
+| cassandra.storage_live_disk_space_used | used | bytes |
266
+| cassandra.compaction_completed_tasks_rate | completed | tasks/s |
267
+| cassandra.compaction_pending_tasks_count | pending | tasks |
268
+| cassandra.compaction_compacted_rate | compacted | bytes/s |
269
+| cassandra.jvm_memory_used | heap, nonheap | bytes |
270
+| cassandra.jvm_gc_rate | parnew, cms | gc/s |
271
+| cassandra.jvm_gc_time | parnew, cms | seconds |
272
+| cassandra.dropped_messages_rate | dropped | messages/s |
273
+| cassandra.client_requests_timeouts_rate | read, write | timeout/s |
274
+| cassandra.client_requests_unavailables_rate | read, write | exceptions/s |
275
+| cassandra.client_requests_failures_rate | read, write | failures/s |
276
+| cassandra.storage_exceptions_rate | storage | exceptions/s |
277
+
278
+### Per thread pool
279
+
280
+Metrics related to Cassandra's thread pools. Each thread pool provides its own set of the following metrics.
281
+
282
+Labels:
283
+
284
+| Label | Description |
285
+|:-----------|:----------------|
286
+| thread_pool | thread pool name |
287
+
288
+Metrics:
289
+
290
+| Metric | Dimensions | Unit |
291
+|:------|:----------|:----|
292
+| cassandra.thread_pool_active_tasks_count | active | tasks |
293
+| cassandra.thread_pool_pending_tasks_count | pending | tasks |
294
+| cassandra.thread_pool_blocked_tasks_count | blocked | tasks |
295
+| cassandra.thread_pool_blocked_tasks_rate | blocked | tasks/s |
296
+
297
+
298
+
299
## Troubleshooting
300
301
### Debug Mode
src/go/plugin/go.d/collector/ceph/integrations/ceph.md
+96
-96
@@ -61,102 +61,6 @@ The default configuration for this integration does not impose any limits on dat
61
62
The default configuration for this integration is not expected to impose a significant performance impact on the system.
63
64
-## Metrics
65
-
66
-Metrics grouped by *scope*.
67
-
68
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
69
-
70
-
71
-
72
-### Per cluster
73
-
74
-These metrics refer to the entire Ceph cluster.
75
-
76
-Labels:
77
-
78
-| Label | Description |
79
-|:-----------|:----------------|
80
-| fsid | A unique identifier of the cluster. |
81
-
82
-Metrics:
83
-
84
-| Metric | Dimensions | Unit |
85
-|:------|:----------|:----|
86
-| ceph.cluster_status | ok, err, warn | status |
87
-| ceph.cluster_hosts_count | hosts | hosts |
88
-| ceph.cluster_monitors_count | monitors | monitors |
89
-| ceph.cluster_osds_count | osds | osds |
90
-| ceph.cluster_osds_by_status_count | up, down, in, out | status |
91
-| ceph.cluster_managers_count | active, standby | managers |
92
-| ceph.cluster_object_gateways_count | object | gateways |
93
-| ceph.cluster_iscsi_gateways_count | iscsi | gateways |
94
-| ceph.cluster_iscsi_gateways_by_status_count | up, down | gateways |
95
-| ceph.cluster_physical_capacity_utilization | utilization | percent |
96
-| ceph.cluster_physical_capacity_usage | avail, used | bytes |
97
-| ceph.cluster_objects_count | objects | objects |
98
-| ceph.cluster_objects_by_status_distribution | healthy, misplaced, degraded, unfound | percent |
99
-| ceph.cluster_pools_count | pools | pools |
100
-| ceph.cluster_pgs_count | pgs | pgs |
101
-| ceph.cluster_pgs_by_status_count | clean, working, warning, unknown | pgs |
102
-| ceph.cluster_pgs_per_osd_count | per_osd | pgs |
103
-
104
-### Per osd
105
-
106
-These metrics refer to the Object Storage Daemon (OSD).
107
-
108
-Labels:
109
-
110
-| Label | Description |
111
-|:-----------|:----------------|
112
-| fsid | A unique identifier of the cluster. |
113
-| osd_uuid | OSD UUID. |
114
-| osd_name | OSD name. |
115
-| device_class | OSD device class. |
116
-
117
-Metrics:
118
-
119
-| Metric | Dimensions | Unit |
120
-|:------|:----------|:----|
121
-| ceph.osd_status | up, down, in, out | status |
122
-| ceph.osd_space_usage | avail, used | bytes |
123
-| ceph.osd_io | read, written | bytes/s |
124
-| ceph.osd_iops | read, write | ops/s |
125
-| ceph.osd_latency | commit, apply | milliseconds |
126
-
127
-### Per pool
128
-
129
-These metrics refer to the Pool.
130
-
131
-Labels:
132
-
133
-| Label | Description |
134
-|:-----------|:----------------|
135
-| fsid | A unique identifier of the cluster. |
136
-| pool_name | Pool name. |
137
-
138
-Metrics:
139
-
140
-| Metric | Dimensions | Unit |
141
-|:------|:----------|:----|
142
-| ceph.pool_space_utilization | utilization | percent |
143
-| ceph.pool_space_usage | avail, used | bytes |
144
-| ceph.pool_objects_count | object | objects |
145
-| ceph.pool_io | read, written | bytes/s |
146
-| ceph.pool_iops | read, write | ops/s |
147
-
148
-
149
-
150
-## Alerts
151
-
152
-
153
-The following alerts are available:
154
-
155
-| Alert name | On metric | Description |
156
-|:------------|:----------|:------------|
157
-| [ ceph_cluster_physical_capacity_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ceph.conf) | ceph.cluster_physical_capacity_utilization | Ceph cluster ${label:fsid} disk space utilization |
158
-
159
-
64
## Setup
65
66
@@ -287,6 +191,102 @@ jobs:
191
```
192
193
194
+## Alerts
195
+
196
+
197
+The following alerts are available:
198
+
199
+| Alert name | On metric | Description |
200
+|:------------|:----------|:------------|
201
+| [ ceph_cluster_physical_capacity_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ceph.conf) | ceph.cluster_physical_capacity_utilization | Ceph cluster ${label:fsid} disk space utilization |
202
+
203
+
204
+## Metrics
205
+
206
+Metrics grouped by *scope*.
207
+
208
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
209
+
210
+
211
+
212
+### Per cluster
213
+
214
+These metrics refer to the entire Ceph cluster.
215
+
216
+Labels:
217
+
218
+| Label | Description |
219
+|:-----------|:----------------|
220
+| fsid | A unique identifier of the cluster. |
221
+
222
+Metrics:
223
+
224
+| Metric | Dimensions | Unit |
225
+|:------|:----------|:----|
226
+| ceph.cluster_status | ok, err, warn | status |
227
+| ceph.cluster_hosts_count | hosts | hosts |
228
+| ceph.cluster_monitors_count | monitors | monitors |
229
+| ceph.cluster_osds_count | osds | osds |
230
+| ceph.cluster_osds_by_status_count | up, down, in, out | status |
231
+| ceph.cluster_managers_count | active, standby | managers |
232
+| ceph.cluster_object_gateways_count | object | gateways |
233
+| ceph.cluster_iscsi_gateways_count | iscsi | gateways |
234
+| ceph.cluster_iscsi_gateways_by_status_count | up, down | gateways |
235
+| ceph.cluster_physical_capacity_utilization | utilization | percent |
236
+| ceph.cluster_physical_capacity_usage | avail, used | bytes |
237
+| ceph.cluster_objects_count | objects | objects |
238
+| ceph.cluster_objects_by_status_distribution | healthy, misplaced, degraded, unfound | percent |
239
+| ceph.cluster_pools_count | pools | pools |
240
+| ceph.cluster_pgs_count | pgs | pgs |
241
+| ceph.cluster_pgs_by_status_count | clean, working, warning, unknown | pgs |
242
+| ceph.cluster_pgs_per_osd_count | per_osd | pgs |
243
+
244
+### Per osd
245
+
246
+These metrics refer to the Object Storage Daemon (OSD).
247
+
248
+Labels:
249
+
250
+| Label | Description |
251
+|:-----------|:----------------|
252
+| fsid | A unique identifier of the cluster. |
253
+| osd_uuid | OSD UUID. |
254
+| osd_name | OSD name. |
255
+| device_class | OSD device class. |
256
+
257
+Metrics:
258
+
259
+| Metric | Dimensions | Unit |
260
+|:------|:----------|:----|
261
+| ceph.osd_status | up, down, in, out | status |
262
+| ceph.osd_space_usage | avail, used | bytes |
263
+| ceph.osd_io | read, written | bytes/s |
264
+| ceph.osd_iops | read, write | ops/s |
265
+| ceph.osd_latency | commit, apply | milliseconds |
266
+
267
+### Per pool
268
+
269
+These metrics refer to the Pool.
270
+
271
+Labels:
272
+
273
+| Label | Description |
274
+|:-----------|:----------------|
275
+| fsid | A unique identifier of the cluster. |
276
+| pool_name | Pool name. |
277
+
278
+Metrics:
279
+
280
+| Metric | Dimensions | Unit |
281
+|:------|:----------|:----|
282
+| ceph.pool_space_utilization | utilization | percent |
283
+| ceph.pool_space_usage | avail, used | bytes |
284
+| ceph.pool_objects_count | object | objects |
285
+| ceph.pool_io | read, written | bytes/s |
286
+| ceph.pool_iops | read, write | ops/s |
287
+
288
+
289
+
290
## Troubleshooting
291
292
### Debug Mode
src/go/plugin/go.d/collector/chrony/integrations/chrony.md
+41
-41
@@ -50,47 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Chrony instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| chrony.stratum | stratum | level |
72
-| chrony.current_correction | current_correction | seconds |
73
-| chrony.root_delay | root_delay | seconds |
74
-| chrony.root_dispersion | root_delay | seconds |
75
-| chrony.last_offset | offset | seconds |
76
-| chrony.rms_offset | offset | seconds |
77
-| chrony.frequency | frequency | ppm |
78
-| chrony.residual_frequency | residual_frequency | ppm |
79
-| chrony.skew | skew | ppm |
80
-| chrony.update_interval | update_interval | seconds |
81
-| chrony.ref_measurement_time | ref_measurement_time | seconds |
82
-| chrony.leap_status | normal, insert_second, delete_second, unsynchronised | status |
83
-| chrony.activity | online, offline, burst_online, burst_offline, unresolved | sources |
84
-| chrony.ntp_packets | received, dropped | packets/s |
85
-| chrony.command_packets | received, dropped | packets/s |
86
-
87
-
88
-
89
-## Alerts
90
-
91
-There are no alerts configured by default for this integration.
92
-
93
-
53
## Setup
54
55
@@ -204,6 +163,47 @@ jobs:
163
164
165
166
+## Alerts
167
+
168
+There are no alerts configured by default for this integration.
169
+
170
+
171
+## Metrics
172
+
173
+Metrics grouped by *scope*.
174
+
175
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
176
+
177
+
178
+
179
+### Per Chrony instance
180
+
181
+These metrics refer to the entire monitored application.
182
+
183
+This scope has no labels.
184
+
185
+Metrics:
186
+
187
+| Metric | Dimensions | Unit |
188
+|:------|:----------|:----|
189
+| chrony.stratum | stratum | level |
190
+| chrony.current_correction | current_correction | seconds |
191
+| chrony.root_delay | root_delay | seconds |
192
+| chrony.root_dispersion | root_delay | seconds |
193
+| chrony.last_offset | offset | seconds |
194
+| chrony.rms_offset | offset | seconds |
195
+| chrony.frequency | frequency | ppm |
196
+| chrony.residual_frequency | residual_frequency | ppm |
197
+| chrony.skew | skew | ppm |
198
+| chrony.update_interval | update_interval | seconds |
199
+| chrony.ref_measurement_time | ref_measurement_time | seconds |
200
+| chrony.leap_status | normal, insert_second, delete_second, unsynchronised | status |
201
+| chrony.activity | online, offline, burst_online, burst_offline, unresolved | sources |
202
+| chrony.ntp_packets | received, dropped | packets/s |
203
+| chrony.command_packets | received, dropped | packets/s |
204
+
205
+
206
+
207
## Troubleshooting
208
209
### Debug Mode
src/go/plugin/go.d/collector/clickhouse/integrations/clickhouse.md
+182
-182
@@ -58,6 +58,187 @@ The default configuration for this integration does not impose any limits on dat
58
59
The default configuration for this integration is not expected to impose a significant performance impact on the system.
60
61
+## Setup
62
+
63
+
64
+You can configure the **clickhouse** collector in two ways:
65
+
66
+| Method | Best for | How to |
67
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
68
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **clickhouse**, then click **+** to add a job. |
69
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/clickhouse.conf` and add a job. |
70
+
71
+:::important
72
+
73
+UI configuration requires paid Netdata Cloud plan.
74
+
75
+:::
76
+
77
+
78
+### Prerequisites
79
+
80
+No action required.
81
+
82
+### Configuration
83
+
84
+#### Options
85
+
86
+The following options can be defined globally: update_every, autodetection_retry.
87
+
88
+
89
+<details open><summary>Config options</summary>
90
+
91
+
92
+
93
+| Group | Option | Description | Default | Required |
94
+|:------|:-----|:------------|:--------|:---------:|
95
+| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
96
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
97
+| **Target** | url | Target endpoint URL. | http://127.0.0.1:8123 | yes |
98
+| | timeout | HTTP request timeout (seconds). | 1 | no |
99
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
100
+| | password | Password for Basic HTTP authentication. | | no |
101
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
102
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
103
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
104
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
105
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
106
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
107
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
108
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
109
+| **Request** | method | HTTP method to use. | GET | no |
110
+| | body | Request body (e.g., for POST/PUT). | | no |
111
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
112
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
113
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
114
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
115
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
116
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
117
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
118
+
119
+
120
+</details>
121
+
122
+
123
+#### via UI
124
+
125
+Configure the **clickhouse** collector from the Netdata web interface:
126
+
127
+1. Go to **Nodes**.
128
+2. Select the node **where you want the clickhouse data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
129
+3. The **Collectors → Jobs** view opens by default.
130
+4. In the Search box, type _clickhouse_ (or scroll the list) to locate the **clickhouse** collector.
131
+5. Click the **+** next to the **clickhouse** collector to add a new job.
132
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
133
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
134
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
135
+
136
+
137
+#### via File
138
+
139
+The configuration file name for this integration is `go.d/clickhouse.conf`.
140
+
141
+The file format is YAML. Generally, the structure is:
142
+
143
+```yaml
144
+update_every: 1
145
+autodetection_retry: 0
146
+jobs:
147
+ - name: some_name1
148
+ - name: some_name2
149
+```
150
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
151
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
152
+
153
+```bash
154
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
155
+sudo ./edit-config go.d/clickhouse.conf
156
+```
157
+
158
+##### Examples
159
+
160
+###### Basic
161
+
162
+A basic example configuration.
163
+
164
+```yaml
165
+jobs:
166
+ - name: local
167
+ url: http://127.0.0.1:8123
168
+
169
+```
170
+###### HTTP authentication
171
+
172
+Basic HTTP authentication.
173
+
174
+<details open><summary>Config</summary>
175
+
176
+```yaml
177
+jobs:
178
+ - name: local
179
+ url: http://127.0.0.1:8123
180
+ username: username
181
+ password: password
182
+
183
+```
184
+</details>
185
+
186
+###### HTTPS with self-signed certificate
187
+
188
+ClickHouse with enabled HTTPS and self-signed certificate.
189
+
190
+<details open><summary>Config</summary>
191
+
192
+```yaml
193
+jobs:
194
+ - name: local
195
+ url: https://127.0.0.1:8123
196
+ tls_skip_verify: yes
197
+
198
+```
199
+</details>
200
+
201
+###### Multi-instance
202
+
203
+> **Note**: When you define multiple jobs, their names must be unique.
204
+
205
+Collecting metrics from local and remote instances.
206
+
207
+
208
+<details open><summary>Config</summary>
209
+
210
+```yaml
211
+jobs:
212
+ - name: local
213
+ url: http://127.0.0.1:8123
214
+
215
+ - name: remote
216
+ url: http://192.0.2.1:8123
217
+
218
+```
219
+</details>
220
+
221
+
222
+
223
+## Alerts
224
+
225
+
226
+The following alerts are available:
227
+
228
+| Alert name | On metric | Description |
229
+|:------------|:----------|:------------|
230
+| [ clickhouse_restarted ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.uptime | ClickHouse has recently been restarted |
231
+| [ clickhouse_queries_preempted ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.queries_preempted | ClickHouse has queries that are stopped and waiting due to priority setting |
232
+| [ clickhouse_long_running_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.longest_running_query_time | ClickHouse has a long-running query exceeding the threshold |
233
+| [ clickhouse_rejected_inserts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.rejected_inserts | ClickHouse has INSERT queries that are rejected due to high number of active data parts for partition in a MergeTree |
234
+| [ clickhouse_delayed_inserts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.delayed_inserts | ClickHouse has INSERT queries that are throttled due to high number of active data parts for partition in a MergeTree |
235
+| [ clickhouse_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.replicas_max_absolute_delay | ClickHouse is experiencing replication lag greater than 5 minutes |
236
+| [ clickhouse_replicated_readonly_tables ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.replicated_readonly_tables | ClickHouse has replicated tables in readonly state due to ZooKeeper session loss/startup without ZooKeeper configured |
237
+| [ clickhouse_max_part_count_for_partition ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.max_part_count_for_partition | ClickHouse high number of parts per partition |
238
+| [ clickhouse_distributed_connections_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.distributed_connections_fail_exhausted_retries | ClickHouse has failed distributed connections after exhausting all retry attempts |
239
+| [ clickhouse_distributed_files_to_insert ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.distributed_files_to_insert | ClickHouse high number of pending files to process for asynchronous insertion into Distributed tables |
240
+
241
+
242
## Metrics
243
244
Metrics grouped by *scope*.
@@ -170,7 +351,7 @@ Metrics:
351
352
353
173
-## Functions
354
+## Live Data
355
356
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
357
@@ -256,187 +437,6 @@ Aggregated query statistics from `system.query_log`, grouped by normalized query
437
438
439
259
-## Alerts
260
-
261
-
262
-The following alerts are available:
263
-
264
-| Alert name | On metric | Description |
265
-|:------------|:----------|:------------|
266
-| [ clickhouse_restarted ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.uptime | ClickHouse has recently been restarted |
267
-| [ clickhouse_queries_preempted ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.queries_preempted | ClickHouse has queries that are stopped and waiting due to priority setting |
268
-| [ clickhouse_long_running_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.longest_running_query_time | ClickHouse has a long-running query exceeding the threshold |
269
-| [ clickhouse_rejected_inserts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.rejected_inserts | ClickHouse has INSERT queries that are rejected due to high number of active data parts for partition in a MergeTree |
270
-| [ clickhouse_delayed_inserts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.delayed_inserts | ClickHouse has INSERT queries that are throttled due to high number of active data parts for partition in a MergeTree |
271
-| [ clickhouse_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.replicas_max_absolute_delay | ClickHouse is experiencing replication lag greater than 5 minutes |
272
-| [ clickhouse_replicated_readonly_tables ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.replicated_readonly_tables | ClickHouse has replicated tables in readonly state due to ZooKeeper session loss/startup without ZooKeeper configured |
273
-| [ clickhouse_max_part_count_for_partition ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.max_part_count_for_partition | ClickHouse high number of parts per partition |
274
-| [ clickhouse_distributed_connections_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.distributed_connections_fail_exhausted_retries | ClickHouse has failed distributed connections after exhausting all retry attempts |
275
-| [ clickhouse_distributed_files_to_insert ](https://github.com/netdata/netdata/blob/master/src/health/health.d/clickhouse.conf) | clickhouse.distributed_files_to_insert | ClickHouse high number of pending files to process for asynchronous insertion into Distributed tables |
276
-
277
-
278
-## Setup
279
-
280
-
281
-You can configure the **clickhouse** collector in two ways:
282
-
283
-| Method | Best for | How to |
284
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
285
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **clickhouse**, then click **+** to add a job. |
286
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/clickhouse.conf` and add a job. |
287
-
288
-:::important
289
-
290
-UI configuration requires paid Netdata Cloud plan.
291
-
292
-:::
293
-
294
-
295
-### Prerequisites
296
-
297
-No action required.
298
-
299
-### Configuration
300
-
301
-#### Options
302
-
303
-The following options can be defined globally: update_every, autodetection_retry.
304
-
305
-
306
-<details open><summary>Config options</summary>
307
-
308
-
309
-
310
-| Group | Option | Description | Default | Required |
311
-|:------|:-----|:------------|:--------|:---------:|
312
-| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
313
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
314
-| **Target** | url | Target endpoint URL. | http://127.0.0.1:8123 | yes |
315
-| | timeout | HTTP request timeout (seconds). | 1 | no |
316
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
317
-| | password | Password for Basic HTTP authentication. | | no |
318
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
319
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
320
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
321
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
322
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
323
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
324
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
325
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
326
-| **Request** | method | HTTP method to use. | GET | no |
327
-| | body | Request body (e.g., for POST/PUT). | | no |
328
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
329
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
330
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
331
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
332
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
333
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
334
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
335
-
336
-
337
-</details>
338
-
339
-
340
-#### via UI
341
-
342
-Configure the **clickhouse** collector from the Netdata web interface:
343
-
344
-1. Go to **Nodes**.
345
-2. Select the node **where you want the clickhouse data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
346
-3. The **Collectors → Jobs** view opens by default.
347
-4. In the Search box, type _clickhouse_ (or scroll the list) to locate the **clickhouse** collector.
348
-5. Click the **+** next to the **clickhouse** collector to add a new job.
349
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
350
- - **Test** runs the job with the provided settings and shows whether data can be collected.
351
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
352
-
353
-
354
-#### via File
355
-
356
-The configuration file name for this integration is `go.d/clickhouse.conf`.
357
-
358
-The file format is YAML. Generally, the structure is:
359
-
360
-```yaml
361
-update_every: 1
362
-autodetection_retry: 0
363
-jobs:
364
- - name: some_name1
365
- - name: some_name2
366
-```
367
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
368
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
369
-
370
-```bash
371
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
372
-sudo ./edit-config go.d/clickhouse.conf
373
-```
374
-
375
-##### Examples
376
-
377
-###### Basic
378
-
379
-A basic example configuration.
380
-
381
-```yaml
382
-jobs:
383
- - name: local
384
- url: http://127.0.0.1:8123
385
-
386
-```
387
-###### HTTP authentication
388
-
389
-Basic HTTP authentication.
390
-
391
-<details open><summary>Config</summary>
392
-
393
-```yaml
394
-jobs:
395
- - name: local
396
- url: http://127.0.0.1:8123
397
- username: username
398
- password: password
399
-
400
-```
401
-</details>
402
-
403
-###### HTTPS with self-signed certificate
404
-
405
-ClickHouse with enabled HTTPS and self-signed certificate.
406
-
407
-<details open><summary>Config</summary>
408
-
409
-```yaml
410
-jobs:
411
- - name: local
412
- url: https://127.0.0.1:8123
413
- tls_skip_verify: yes
414
-
415
-```
416
-</details>
417
-
418
-###### Multi-instance
419
-
420
-> **Note**: When you define multiple jobs, their names must be unique.
421
-
422
-Collecting metrics from local and remote instances.
423
-
424
-
425
-<details open><summary>Config</summary>
426
-
427
-```yaml
428
-jobs:
429
- - name: local
430
- url: http://127.0.0.1:8123
431
-
432
- - name: remote
433
- url: http://192.0.2.1:8123
434
-
435
-```
436
-</details>
437
-
438
-
439
-
440
## Troubleshooting
441
442
### Debug Mode
src/go/plugin/go.d/collector/cockroachdb/integrations/cockroachdb.md
+201
-201
@@ -53,6 +53,206 @@ The default configuration for this integration does not impose any limits on dat
53
54
The default configuration for this integration is not expected to impose a significant performance impact on the system.
55
56
+## Setup
57
+
58
+
59
+You can configure the **cockroachdb** collector in two ways:
60
+
61
+| Method | Best for | How to |
62
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
63
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **cockroachdb**, then click **+** to add a job. |
64
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/cockroachdb.conf` and add a job. |
65
+
66
+:::important
67
+
68
+UI configuration requires paid Netdata Cloud plan.
69
+
70
+:::
71
+
72
+
73
+### Prerequisites
74
+
75
+No action required.
76
+
77
+### Configuration
78
+
79
+#### Options
80
+
81
+The following options can be defined globally: update_every, autodetection_retry.
82
+
83
+
84
+<details open><summary>Config options</summary>
85
+
86
+
87
+
88
+| Group | Option | Description | Default | Required |
89
+|:------|:-----|:------------|:--------|:---------:|
90
+| **Collection** | update_every | Data collection interval (seconds). | 10 | no |
91
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
92
+| **Target** | url | Target endpoint URL. | http://127.0.0.1:8080/_status/vars | yes |
93
+| | timeout | HTTP request timeout (seconds). | 1 | no |
94
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
95
+| | password | Password for Basic HTTP authentication. | | no |
96
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
97
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
98
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
99
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
100
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
101
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
102
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
103
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
104
+| **Request** | method | HTTP method to use. | GET | no |
105
+| | body | Request body (e.g., for POST/PUT). | | no |
106
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
107
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
108
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
109
+| **Functions** | functions.dsn | SQL DSN (required for query functions). | | no |
110
+| | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
111
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
112
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
113
+| | functions.running_queries.disabled | Disable the [running-queries](#running-queries) function. | no | no |
114
+| | functions.running_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
115
+| | functions.running_queries.limit | Maximum number of queries to return. | 500 | no |
116
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
117
+
118
+
119
+</details>
120
+
121
+
122
+#### via UI
123
+
124
+Configure the **cockroachdb** collector from the Netdata web interface:
125
+
126
+1. Go to **Nodes**.
127
+2. Select the node **where you want the cockroachdb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
128
+3. The **Collectors → Jobs** view opens by default.
129
+4. In the Search box, type _cockroachdb_ (or scroll the list) to locate the **cockroachdb** collector.
130
+5. Click the **+** next to the **cockroachdb** collector to add a new job.
131
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
132
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
133
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
134
+
135
+
136
+#### via File
137
+
138
+The configuration file name for this integration is `go.d/cockroachdb.conf`.
139
+
140
+The file format is YAML. Generally, the structure is:
141
+
142
+```yaml
143
+update_every: 1
144
+autodetection_retry: 0
145
+jobs:
146
+ - name: some_name1
147
+ - name: some_name2
148
+```
149
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
150
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
151
+
152
+```bash
153
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
154
+sudo ./edit-config go.d/cockroachdb.conf
155
+```
156
+
157
+##### Examples
158
+
159
+###### Basic
160
+
161
+An example configuration.
162
+
163
+<details open><summary>Config</summary>
164
+
165
+```yaml
166
+jobs:
167
+ - name: local
168
+ url: http://127.0.0.1:8080/_status/vars
169
+
170
+```
171
+</details>
172
+
173
+###### Top queries
174
+
175
+Enable SQL query functions.
176
+
177
+<details open><summary>Config</summary>
178
+
179
+```yaml
180
+jobs:
181
+ - name: local
182
+ url: http://127.0.0.1:8080/_status/vars
183
+ functions:
184
+ dsn: postgres://root@127.0.0.1:26257/defaultdb?sslmode=disable
185
+
186
+```
187
+</details>
188
+
189
+###### HTTP authentication
190
+
191
+Local server with basic HTTP authentication.
192
+
193
+<details open><summary>Config</summary>
194
+
195
+```yaml
196
+jobs:
197
+ - name: local
198
+ url: http://127.0.0.1:8080/_status/vars
199
+ username: username
200
+ password: password
201
+
202
+```
203
+</details>
204
+
205
+###### HTTPS with self-signed certificate
206
+
207
+CockroachDB with enabled HTTPS and self-signed certificate.
208
+
209
+<details open><summary>Config</summary>
210
+
211
+```yaml
212
+jobs:
213
+ - name: local
214
+ url: https://127.0.0.1:8080/_status/vars
215
+ tls_skip_verify: yes
216
+
217
+```
218
+</details>
219
+
220
+###### Multi-instance
221
+
222
+> **Note**: When you define multiple jobs, their names must be unique.
223
+
224
+Collecting metrics from local and remote instances.
225
+
226
+
227
+<details open><summary>Config</summary>
228
+
229
+```yaml
230
+jobs:
231
+ - name: local
232
+ url: http://127.0.0.1:8080/_status/vars
233
+
234
+ - name: remote
235
+ url: http://203.0.113.10:8080/_status/vars
236
+
237
+```
238
+</details>
239
+
240
+
241
+
242
+## Alerts
243
+
244
+
245
+The following alerts are available:
246
+
247
+| Alert name | On metric | Description |
248
+|:------------|:----------|:------------|
249
+| [ cockroachdb_used_storage_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.storage_used_capacity_percentage | storage capacity utilization |
250
+| [ cockroachdb_used_usable_storage_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.storage_used_capacity_percentage | storage usable space utilization |
251
+| [ cockroachdb_unavailable_ranges ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.ranges_replication_problem | number of ranges with fewer live replicas than needed for quorum |
252
+| [ cockroachdb_underreplicated_ranges ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.ranges_replication_problem | number of ranges with fewer live replicas than the replication target |
253
+| [ cockroachdb_open_file_descriptors_limit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.process_file_descriptors | open file descriptors utilization (against softlimit) |
254
+
255
+
256
## Metrics
257
258
Metrics grouped by *scope*.
@@ -134,7 +334,7 @@ Metrics:
334
335
336
137
-## Functions
337
+## Live Data
338
339
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
340
@@ -296,206 +496,6 @@ Real-time snapshot of currently executing SQL statements across all cluster node
496
497
498
299
-## Alerts
300
-
301
-
302
-The following alerts are available:
303
-
304
-| Alert name | On metric | Description |
305
-|:------------|:----------|:------------|
306
-| [ cockroachdb_used_storage_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.storage_used_capacity_percentage | storage capacity utilization |
307
-| [ cockroachdb_used_usable_storage_capacity ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.storage_used_capacity_percentage | storage usable space utilization |
308
-| [ cockroachdb_unavailable_ranges ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.ranges_replication_problem | number of ranges with fewer live replicas than needed for quorum |
309
-| [ cockroachdb_underreplicated_ranges ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.ranges_replication_problem | number of ranges with fewer live replicas than the replication target |
310
-| [ cockroachdb_open_file_descriptors_limit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/cockroachdb.conf) | cockroachdb.process_file_descriptors | open file descriptors utilization (against softlimit) |
311
-
312
-
313
-## Setup
314
-
315
-
316
-You can configure the **cockroachdb** collector in two ways:
317
-
318
-| Method | Best for | How to |
319
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
320
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **cockroachdb**, then click **+** to add a job. |
321
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/cockroachdb.conf` and add a job. |
322
-
323
-:::important
324
-
325
-UI configuration requires paid Netdata Cloud plan.
326
-
327
-:::
328
-
329
-
330
-### Prerequisites
331
-
332
-No action required.
333
-
334
-### Configuration
335
-
336
-#### Options
337
-
338
-The following options can be defined globally: update_every, autodetection_retry.
339
-
340
-
341
-<details open><summary>Config options</summary>
342
-
343
-
344
-
345
-| Group | Option | Description | Default | Required |
346
-|:------|:-----|:------------|:--------|:---------:|
347
-| **Collection** | update_every | Data collection interval (seconds). | 10 | no |
348
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
349
-| **Target** | url | Target endpoint URL. | http://127.0.0.1:8080/_status/vars | yes |
350
-| | timeout | HTTP request timeout (seconds). | 1 | no |
351
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
352
-| | password | Password for Basic HTTP authentication. | | no |
353
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
354
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
355
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
356
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
357
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
358
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
359
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
360
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
361
-| **Request** | method | HTTP method to use. | GET | no |
362
-| | body | Request body (e.g., for POST/PUT). | | no |
363
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
364
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
365
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
366
-| **Functions** | functions.dsn | SQL DSN (required for query functions). | | no |
367
-| | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
368
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
369
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
370
-| | functions.running_queries.disabled | Disable the [running-queries](#running-queries) function. | no | no |
371
-| | functions.running_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
372
-| | functions.running_queries.limit | Maximum number of queries to return. | 500 | no |
373
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
374
-
375
-
376
-</details>
377
-
378
-
379
-#### via UI
380
-
381
-Configure the **cockroachdb** collector from the Netdata web interface:
382
-
383
-1. Go to **Nodes**.
384
-2. Select the node **where you want the cockroachdb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
385
-3. The **Collectors → Jobs** view opens by default.
386
-4. In the Search box, type _cockroachdb_ (or scroll the list) to locate the **cockroachdb** collector.
387
-5. Click the **+** next to the **cockroachdb** collector to add a new job.
388
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
389
- - **Test** runs the job with the provided settings and shows whether data can be collected.
390
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
391
-
392
-
393
-#### via File
394
-
395
-The configuration file name for this integration is `go.d/cockroachdb.conf`.
396
-
397
-The file format is YAML. Generally, the structure is:
398
-
399
-```yaml
400
-update_every: 1
401
-autodetection_retry: 0
402
-jobs:
403
- - name: some_name1
404
- - name: some_name2
405
-```
406
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
407
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
408
-
409
-```bash
410
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
411
-sudo ./edit-config go.d/cockroachdb.conf
412
-```
413
-
414
-##### Examples
415
-
416
-###### Basic
417
-
418
-An example configuration.
419
-
420
-<details open><summary>Config</summary>
421
-
422
-```yaml
423
-jobs:
424
- - name: local
425
- url: http://127.0.0.1:8080/_status/vars
426
-
427
-```
428
-</details>
429
-
430
-###### Top queries
431
-
432
-Enable SQL query functions.
433
-
434
-<details open><summary>Config</summary>
435
-
436
-```yaml
437
-jobs:
438
- - name: local
439
- url: http://127.0.0.1:8080/_status/vars
440
- functions:
441
- dsn: postgres://root@127.0.0.1:26257/defaultdb?sslmode=disable
442
-
443
-```
444
-</details>
445
-
446
-###### HTTP authentication
447
-
448
-Local server with basic HTTP authentication.
449
-
450
-<details open><summary>Config</summary>
451
-
452
-```yaml
453
-jobs:
454
- - name: local
455
- url: http://127.0.0.1:8080/_status/vars
456
- username: username
457
- password: password
458
-
459
-```
460
-</details>
461
-
462
-###### HTTPS with self-signed certificate
463
-
464
-CockroachDB with enabled HTTPS and self-signed certificate.
465
-
466
-<details open><summary>Config</summary>
467
-
468
-```yaml
469
-jobs:
470
- - name: local
471
- url: https://127.0.0.1:8080/_status/vars
472
- tls_skip_verify: yes
473
-
474
-```
475
-</details>
476
-
477
-###### Multi-instance
478
-
479
-> **Note**: When you define multiple jobs, their names must be unique.
480
-
481
-Collecting metrics from local and remote instances.
482
-
483
-
484
-<details open><summary>Config</summary>
485
-
486
-```yaml
487
-jobs:
488
- - name: local
489
- url: http://127.0.0.1:8080/_status/vars
490
-
491
- - name: remote
492
- url: http://203.0.113.10:8080/_status/vars
493
-
494
-```
495
-</details>
496
-
497
-
498
-
499
## Troubleshooting
500
501
### Debug Mode
src/go/plugin/go.d/collector/consul/integrations/consul.md
+113
-113
@@ -60,119 +60,6 @@ The default configuration for this integration does not impose any limits on dat
60
61
The default configuration for this integration is not expected to impose a significant performance impact on the system.
62
63
-## Metrics
64
-
65
-Metrics grouped by *scope*.
66
-
67
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
68
-
69
-The set of metrics depends on the [Consul Agent mode](https://developer.hashicorp.com/consul/docs/install/glossary#agent).
70
-
71
-
72
-### Per Consul instance
73
-
74
-These metrics refer to the entire monitored application.
75
-
76
-This scope has no labels.
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit | Leader | Follower | Client |
81
-|:------|:----------|:----|:---:|:---:|:---:|
82
-| consul.client_rpc_requests_rate | rpc | requests/s | • | • | • |
83
-| consul.client_rpc_requests_exceeded_rate | exceeded | requests/s | • | • | • |
84
-| consul.client_rpc_requests_failed_rate | failed | requests/s | • | • | • |
85
-| consul.memory_allocated | allocated | bytes | • | • | • |
86
-| consul.memory_sys | sys | bytes | • | • | • |
87
-| consul.gc_pause_time | gc_pause | seconds | • | • | • |
88
-| consul.kvs_apply_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | • | |
89
-| consul.kvs_apply_operations_rate | kvs_apply | ops/s | • | • | |
90
-| consul.txn_apply_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | • | |
91
-| consul.txn_apply_operations_rate | txn_apply | ops/s | • | • | |
92
-| consul.autopilot_health_status | healthy, unhealthy | status | • | • | |
93
-| consul.autopilot_failure_tolerance | failure_tolerance | servers | • | • | |
94
-| consul.autopilot_server_health_status | healthy, unhealthy | status | • | • | |
95
-| consul.autopilot_server_stable_time | stable | seconds | • | • | |
96
-| consul.autopilot_server_serf_status | active, failed, left, none | status | • | • | |
97
-| consul.autopilot_server_voter_status | voter, not_voter | status | • | • | |
98
-| consul.network_lan_rtt | min, max, avg | ms | • | • | |
99
-| consul.raft_commit_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | | |
100
-| consul.raft_commits_rate | commits | commits/s | • | | |
101
-| consul.raft_leader_last_contact_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | | |
102
-| consul.raft_leader_oldest_log_age | oldest_log_age | seconds | • | | |
103
-| consul.raft_follower_last_contact_leader_time | leader_last_contact | ms | | • | |
104
-| consul.raft_rpc_install_snapshot_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | | • | |
105
-| consul.raft_leader_elections_rate | leader | elections/s | • | • | |
106
-| consul.raft_leadership_transitions_rate | leadership | transitions/s | • | • | |
107
-| consul.server_leadership_status | leader, not_leader | status | • | • | |
108
-| consul.raft_thread_main_saturation_perc | quantile_0.5, quantile_0.9, quantile_0.99 | percentage | • | • | |
109
-| consul.raft_thread_fsm_saturation_perc | quantile_0.5, quantile_0.9, quantile_0.99 | percentage | • | • | |
110
-| consul.raft_fsm_last_restore_duration | last_restore_duration | ms | • | • | |
111
-| consul.raft_boltdb_freelist_bytes | freelist | bytes | • | • | |
112
-| consul.raft_boltdb_logs_per_batch_rate | written | logs/s | • | • | |
113
-| consul.raft_boltdb_store_logs_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | • | |
114
-| consul.license_expiration_time | license_expiration | seconds | • | • | • |
115
-
116
-### Per node check
117
-
118
-Metrics about checks on Node level.
119
-
120
-Labels:
121
-
122
-| Label | Description |
123
-|:-----------|:----------------|
124
-| datacenter | Datacenter Identifier |
125
-| node_name | The node's name |
126
-| check_name | The check's name |
127
-
128
-Metrics:
129
-
130
-| Metric | Dimensions | Unit | Leader | Follower | Client |
131
-|:------|:----------|:----|:---:|:---:|:---:|
132
-| consul.node_health_check_status | passing, maintenance, warning, critical | status | • | • | • |
133
-
134
-### Per service check
135
-
136
-Metrics about checks at a Service level.
137
-
138
-Labels:
139
-
140
-| Label | Description |
141
-|:-----------|:----------------|
142
-| datacenter | Datacenter Identifier |
143
-| node_name | The node's name |
144
-| check_name | The check's name |
145
-| service_name | The service's name |
146
-
147
-Metrics:
148
-
149
-| Metric | Dimensions | Unit | Leader | Follower | Client |
150
-|:------|:----------|:----|:---:|:---:|:---:|
151
-| consul.service_health_check_status | passing, maintenance, warning, critical | status | • | • | • |
152
-
153
-
154
-
155
-## Alerts
156
-
157
-
158
-The following alerts are available:
159
-
160
-| Alert name | On metric | Description |
161
-|:------------|:----------|:------------|
162
-| [ consul_node_health_check_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.node_health_check_status | node health check ${label:check_name} has failed on server ${label:node_name} datacenter ${label:datacenter} |
163
-| [ consul_service_health_check_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.service_health_check_status | service health check ${label:check_name} for service ${label:service_name} has failed on server ${label:node_name} datacenter ${label:datacenter} |
164
-| [ consul_client_rpc_requests_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.client_rpc_requests_exceeded_rate | number of rate-limited RPC requests made by server ${label:node_name} datacenter ${label:datacenter} |
165
-| [ consul_client_rpc_requests_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.client_rpc_requests_failed_rate | number of failed RPC requests made by server ${label:node_name} datacenter ${label:datacenter} |
166
-| [ consul_gc_pause_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.gc_pause_time | time spent in stop-the-world garbage collection pauses on server ${label:node_name} datacenter ${label:datacenter} |
167
-| [ consul_autopilot_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.autopilot_health_status | datacenter ${label:datacenter} cluster is unhealthy as reported by server ${label:node_name} |
168
-| [ consul_autopilot_server_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.autopilot_server_health_status | server ${label:node_name} from datacenter ${label:datacenter} is unhealthy |
169
-| [ consul_raft_leader_last_contact_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_leader_last_contact_time | median time elapsed since leader server ${label:node_name} datacenter ${label:datacenter} was last able to contact the follower nodes |
170
-| [ consul_raft_leadership_transitions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_leadership_transitions_rate | there has been a leadership change and server ${label:node_name} datacenter ${label:datacenter} has become the leader |
171
-| [ consul_raft_thread_main_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_thread_main_saturation_perc | average saturation of the main Raft goroutine on server ${label:node_name} datacenter ${label:datacenter} |
172
-| [ consul_raft_thread_fsm_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_thread_fsm_saturation_perc | average saturation of the FSM Raft goroutine on server ${label:node_name} datacenter ${label:datacenter} |
173
-| [ consul_license_expiration_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.license_expiration_time | Consul Enterprise licence expiration time on node ${label:node_name} datacenter ${label:datacenter} |
174
-
175
-
63
## Setup
64
65
@@ -337,6 +224,119 @@ jobs:
224
225
226
227
+## Alerts
228
+
229
+
230
+The following alerts are available:
231
+
232
+| Alert name | On metric | Description |
233
+|:------------|:----------|:------------|
234
+| [ consul_node_health_check_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.node_health_check_status | node health check ${label:check_name} has failed on server ${label:node_name} datacenter ${label:datacenter} |
235
+| [ consul_service_health_check_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.service_health_check_status | service health check ${label:check_name} for service ${label:service_name} has failed on server ${label:node_name} datacenter ${label:datacenter} |
236
+| [ consul_client_rpc_requests_exceeded ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.client_rpc_requests_exceeded_rate | number of rate-limited RPC requests made by server ${label:node_name} datacenter ${label:datacenter} |
237
+| [ consul_client_rpc_requests_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.client_rpc_requests_failed_rate | number of failed RPC requests made by server ${label:node_name} datacenter ${label:datacenter} |
238
+| [ consul_gc_pause_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.gc_pause_time | time spent in stop-the-world garbage collection pauses on server ${label:node_name} datacenter ${label:datacenter} |
239
+| [ consul_autopilot_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.autopilot_health_status | datacenter ${label:datacenter} cluster is unhealthy as reported by server ${label:node_name} |
240
+| [ consul_autopilot_server_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.autopilot_server_health_status | server ${label:node_name} from datacenter ${label:datacenter} is unhealthy |
241
+| [ consul_raft_leader_last_contact_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_leader_last_contact_time | median time elapsed since leader server ${label:node_name} datacenter ${label:datacenter} was last able to contact the follower nodes |
242
+| [ consul_raft_leadership_transitions ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_leadership_transitions_rate | there has been a leadership change and server ${label:node_name} datacenter ${label:datacenter} has become the leader |
243
+| [ consul_raft_thread_main_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_thread_main_saturation_perc | average saturation of the main Raft goroutine on server ${label:node_name} datacenter ${label:datacenter} |
244
+| [ consul_raft_thread_fsm_saturation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.raft_thread_fsm_saturation_perc | average saturation of the FSM Raft goroutine on server ${label:node_name} datacenter ${label:datacenter} |
245
+| [ consul_license_expiration_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/consul.conf) | consul.license_expiration_time | Consul Enterprise licence expiration time on node ${label:node_name} datacenter ${label:datacenter} |
246
+
247
+
248
+## Metrics
249
+
250
+Metrics grouped by *scope*.
251
+
252
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
253
+
254
+The set of metrics depends on the [Consul Agent mode](https://developer.hashicorp.com/consul/docs/install/glossary#agent).
255
+
256
+
257
+### Per Consul instance
258
+
259
+These metrics refer to the entire monitored application.
260
+
261
+This scope has no labels.
262
+
263
+Metrics:
264
+
265
+| Metric | Dimensions | Unit | Leader | Follower | Client |
266
+|:------|:----------|:----|:---:|:---:|:---:|
267
+| consul.client_rpc_requests_rate | rpc | requests/s | • | • | • |
268
+| consul.client_rpc_requests_exceeded_rate | exceeded | requests/s | • | • | • |
269
+| consul.client_rpc_requests_failed_rate | failed | requests/s | • | • | • |
270
+| consul.memory_allocated | allocated | bytes | • | • | • |
271
+| consul.memory_sys | sys | bytes | • | • | • |
272
+| consul.gc_pause_time | gc_pause | seconds | • | • | • |
273
+| consul.kvs_apply_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | • | |
274
+| consul.kvs_apply_operations_rate | kvs_apply | ops/s | • | • | |
275
+| consul.txn_apply_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | • | |
276
+| consul.txn_apply_operations_rate | txn_apply | ops/s | • | • | |
277
+| consul.autopilot_health_status | healthy, unhealthy | status | • | • | |
278
+| consul.autopilot_failure_tolerance | failure_tolerance | servers | • | • | |
279
+| consul.autopilot_server_health_status | healthy, unhealthy | status | • | • | |
280
+| consul.autopilot_server_stable_time | stable | seconds | • | • | |
281
+| consul.autopilot_server_serf_status | active, failed, left, none | status | • | • | |
282
+| consul.autopilot_server_voter_status | voter, not_voter | status | • | • | |
283
+| consul.network_lan_rtt | min, max, avg | ms | • | • | |
284
+| consul.raft_commit_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | | |
285
+| consul.raft_commits_rate | commits | commits/s | • | | |
286
+| consul.raft_leader_last_contact_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | | |
287
+| consul.raft_leader_oldest_log_age | oldest_log_age | seconds | • | | |
288
+| consul.raft_follower_last_contact_leader_time | leader_last_contact | ms | | • | |
289
+| consul.raft_rpc_install_snapshot_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | | • | |
290
+| consul.raft_leader_elections_rate | leader | elections/s | • | • | |
291
+| consul.raft_leadership_transitions_rate | leadership | transitions/s | • | • | |
292
+| consul.server_leadership_status | leader, not_leader | status | • | • | |
293
+| consul.raft_thread_main_saturation_perc | quantile_0.5, quantile_0.9, quantile_0.99 | percentage | • | • | |
294
+| consul.raft_thread_fsm_saturation_perc | quantile_0.5, quantile_0.9, quantile_0.99 | percentage | • | • | |
295
+| consul.raft_fsm_last_restore_duration | last_restore_duration | ms | • | • | |
296
+| consul.raft_boltdb_freelist_bytes | freelist | bytes | • | • | |
297
+| consul.raft_boltdb_logs_per_batch_rate | written | logs/s | • | • | |
298
+| consul.raft_boltdb_store_logs_time | quantile_0.5, quantile_0.9, quantile_0.99 | ms | • | • | |
299
+| consul.license_expiration_time | license_expiration | seconds | • | • | • |
300
+
301
+### Per node check
302
+
303
+Metrics about checks on Node level.
304
+
305
+Labels:
306
+
307
+| Label | Description |
308
+|:-----------|:----------------|
309
+| datacenter | Datacenter Identifier |
310
+| node_name | The node's name |
311
+| check_name | The check's name |
312
+
313
+Metrics:
314
+
315
+| Metric | Dimensions | Unit | Leader | Follower | Client |
316
+|:------|:----------|:----|:---:|:---:|:---:|
317
+| consul.node_health_check_status | passing, maintenance, warning, critical | status | • | • | • |
318
+
319
+### Per service check
320
+
321
+Metrics about checks at a Service level.
322
+
323
+Labels:
324
+
325
+| Label | Description |
326
+|:-----------|:----------------|
327
+| datacenter | Datacenter Identifier |
328
+| node_name | The node's name |
329
+| check_name | The check's name |
330
+| service_name | The service's name |
331
+
332
+Metrics:
333
+
334
+| Metric | Dimensions | Unit | Leader | Follower | Client |
335
+|:------|:----------|:----|:---:|:---:|:---:|
336
+| consul.service_health_check_status | passing, maintenance, warning, critical | status | • | • | • |
337
+
338
+
339
+
340
## Troubleshooting
341
342
### Debug Mode
src/go/plugin/go.d/collector/coredns/integrations/coredns.md
+78
-78
@@ -53,84 +53,6 @@ The default configuration for this integration does not impose any limits on dat
53
54
The default configuration for this integration is not expected to impose a significant performance impact on the system.
55
56
-## Metrics
57
-
58
-Metrics grouped by *scope*.
59
-
60
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
61
-
62
-
63
-
64
-### Per CoreDNS instance
65
-
66
-These metrics refer to the entire monitored application.
67
-
68
-This scope has no labels.
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| coredns.dns_request_count_total | requests | requests/s |
75
-| coredns.dns_responses_count_total | responses | responses/s |
76
-| coredns.dns_request_count_total_per_status | processed, dropped | requests/s |
77
-| coredns.dns_no_matching_zone_dropped_total | dropped | requests/s |
78
-| coredns.dns_panic_count_total | panics | panics/s |
79
-| coredns.dns_requests_count_total_per_proto | udp, tcp | requests/s |
80
-| coredns.dns_requests_count_total_per_ip_family | v4, v6 | requests/s |
81
-| coredns.dns_requests_count_total_per_per_type | a, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, other | requests/s |
82
-| coredns.dns_responses_count_total_per_rcode | noerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, other | responses/s |
83
-
84
-### Per server
85
-
86
-These metrics refer to the DNS server.
87
-
88
-Labels:
89
-
90
-| Label | Description |
91
-|:-----------|:----------------|
92
-| server_name | Server name. |
93
-
94
-Metrics:
95
-
96
-| Metric | Dimensions | Unit |
97
-|:------|:----------|:----|
98
-| coredns.server_dns_request_count_total | requests | requests/s |
99
-| coredns.server_dns_responses_count_total | responses | responses/s |
100
-| coredns.server_request_count_total_per_status | processed, dropped | requests/s |
101
-| coredns.server_requests_count_total_per_proto | udp, tcp | requests/s |
102
-| coredns.server_requests_count_total_per_ip_family | v4, v6 | requests/s |
103
-| coredns.server_requests_count_total_per_per_type | a, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, other | requests/s |
104
-| coredns.server_responses_count_total_per_rcode | noerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, other | responses/s |
105
-
106
-### Per zone
107
-
108
-These metrics refer to the DNS zone.
109
-
110
-Labels:
111
-
112
-| Label | Description |
113
-|:-----------|:----------------|
114
-| zone_name | Zone name. |
115
-
116
-Metrics:
117
-
118
-| Metric | Dimensions | Unit |
119
-|:------|:----------|:----|
120
-| coredns.zone_dns_request_count_total | requests | requests/s |
121
-| coredns.zone_dns_responses_count_total | responses | responses/s |
122
-| coredns.zone_requests_count_total_per_proto | udp, tcp | requests/s |
123
-| coredns.zone_requests_count_total_per_ip_family | v4, v6 | requests/s |
124
-| coredns.zone_requests_count_total_per_per_type | a, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, other | requests/s |
125
-| coredns.zone_responses_count_total_per_rcode | noerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, other | responses/s |
126
-
127
-
128
-
129
-## Alerts
130
-
131
-There are no alerts configured by default for this integration.
132
-
133
-
56
## Setup
57
58
@@ -319,6 +241,84 @@ jobs:
241
242
243
244
+## Alerts
245
+
246
+There are no alerts configured by default for this integration.
247
+
248
+
249
+## Metrics
250
+
251
+Metrics grouped by *scope*.
252
+
253
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
254
+
255
+
256
+
257
+### Per CoreDNS instance
258
+
259
+These metrics refer to the entire monitored application.
260
+
261
+This scope has no labels.
262
+
263
+Metrics:
264
+
265
+| Metric | Dimensions | Unit |
266
+|:------|:----------|:----|
267
+| coredns.dns_request_count_total | requests | requests/s |
268
+| coredns.dns_responses_count_total | responses | responses/s |
269
+| coredns.dns_request_count_total_per_status | processed, dropped | requests/s |
270
+| coredns.dns_no_matching_zone_dropped_total | dropped | requests/s |
271
+| coredns.dns_panic_count_total | panics | panics/s |
272
+| coredns.dns_requests_count_total_per_proto | udp, tcp | requests/s |
273
+| coredns.dns_requests_count_total_per_ip_family | v4, v6 | requests/s |
274
+| coredns.dns_requests_count_total_per_per_type | a, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, other | requests/s |
275
+| coredns.dns_responses_count_total_per_rcode | noerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, other | responses/s |
276
+
277
+### Per server
278
+
279
+These metrics refer to the DNS server.
280
+
281
+Labels:
282
+
283
+| Label | Description |
284
+|:-----------|:----------------|
285
+| server_name | Server name. |
286
+
287
+Metrics:
288
+
289
+| Metric | Dimensions | Unit |
290
+|:------|:----------|:----|
291
+| coredns.server_dns_request_count_total | requests | requests/s |
292
+| coredns.server_dns_responses_count_total | responses | responses/s |
293
+| coredns.server_request_count_total_per_status | processed, dropped | requests/s |
294
+| coredns.server_requests_count_total_per_proto | udp, tcp | requests/s |
295
+| coredns.server_requests_count_total_per_ip_family | v4, v6 | requests/s |
296
+| coredns.server_requests_count_total_per_per_type | a, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, other | requests/s |
297
+| coredns.server_responses_count_total_per_rcode | noerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, other | responses/s |
298
+
299
+### Per zone
300
+
301
+These metrics refer to the DNS zone.
302
+
303
+Labels:
304
+
305
+| Label | Description |
306
+|:-----------|:----------------|
307
+| zone_name | Zone name. |
308
+
309
+Metrics:
310
+
311
+| Metric | Dimensions | Unit |
312
+|:------|:----------|:----|
313
+| coredns.zone_dns_request_count_total | requests | requests/s |
314
+| coredns.zone_dns_responses_count_total | responses | responses/s |
315
+| coredns.zone_requests_count_total_per_proto | udp, tcp | requests/s |
316
+| coredns.zone_requests_count_total_per_ip_family | v4, v6 | requests/s |
317
+| coredns.zone_requests_count_total_per_per_type | a, aaaa, mx, soa, cname, ptr, txt, ns, ds, dnskey, rrsig, nsec, nsec3, ixfr, any, other | requests/s |
318
+| coredns.zone_responses_count_total_per_rcode | noerror, formerr, servfail, nxdomain, notimp, refused, yxdomain, yxrrset, nxrrset, notauth, notzone, badsig, badkey, badtime, badmode, badname, badalg, badtrunc, badcookie, other | responses/s |
319
+
320
+
321
+
322
## Troubleshooting
323
324
### Debug Mode
src/go/plugin/go.d/collector/couchbase/integrations/couchbase.md
+117
-117
@@ -45,123 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Couchbase instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| couchbase.bucket_quota_percent_used | a dimension per bucket | percentage |
67
-| couchbase.bucket_ops_per_sec | a dimension per bucket | ops/s |
68
-| couchbase.bucket_disk_fetches | a dimension per bucket | fetches |
69
-| couchbase.bucket_item_count | a dimension per bucket | items |
70
-| couchbase.bucket_disk_used_stats | a dimension per bucket | bytes |
71
-| couchbase.bucket_data_used | a dimension per bucket | bytes |
72
-| couchbase.bucket_mem_used | a dimension per bucket | bytes |
73
-| couchbase.bucket_vb_active_num_non_resident | a dimension per bucket | items |
74
-
75
-
76
-
77
-## Functions
78
-
79
-This collector exposes real-time functions for interactive troubleshooting in the Live tab.
80
-
81
-
82
-### Top Queries
83
-
84
-Retrieves completed N1QL query statistics from Couchbase [system:completed_requests](https://docs.couchbase.com/server/current/manage/monitor/monitoring-n1ql-query.html#sys-completed-req) keyspace.
85
-
86
-This function queries the `system:completed_requests` keyspace which stores information about recently completed N1QL requests. It provides timing metrics, result statistics, and error/warning counts for each completed query.
87
-
88
-Use cases:
89
-- Identify slow N1QL queries consuming the most elapsed time
90
-- Find queries with high error or warning counts
91
-- Analyze query patterns by user to understand workload distribution
92
-
93
-Statement text is truncated at 4096 characters for display purposes.
94
-
95
-
96
-| Aspect | Description |
97
-|:-------|:------------|
98
-| Name | `Couchbase:top-queries` |
99
-| Require Cloud | yes |
100
-| Performance | Queries `system:completed_requests` via the N1QL query service:<br/>• The `completed_requests` keyspace has a configurable size limit (`completed-limit` setting)<br/>• Default limit of 500 rows balances usefulness with performance |
101
-| Security | Query text may contain unmasked literal values including potentially sensitive data:<br/>• Personal information in WHERE clauses or INSERT values<br/>• Business data embedded in queries<br/>• Access should be restricted to authorized personnel only |
102
-| Availability | Available when:<br/>• The collector has successfully connected to Couchbase<br/>• The N1QL (Query) service is running<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the query fails<br/>• Returns HTTP 504 if the query times out |
103
-
104
-#### Prerequisites
105
-
106
-##### Grant access to `system:completed_requests`
107
-
108
-The user must have appropriate privileges to query system keyspaces and the N1QL service must be available.
109
-
110
-1. Ensure the N1QL (Query) service is running on the cluster
111
-
112
-2. Grant query system catalog privileges to the monitoring user:
113
-
114
- ```sql
115
- GRANT QUERY_SYSTEM_CATALOG TO netdata_user;
116
- ```
117
-
118
-3. Verify access to `completed_requests`:
119
-
120
- ```sql
121
- SELECT * FROM system:completed_requests LIMIT 1;
122
- ```
123
-
124
- :::info
125
-
126
- - The `system:completed_requests` keyspace stores recently completed queries based on Couchbase server settings `completed-limit` and `completed-threshold`
127
- - Only queries exceeding `completed-threshold` (default 1000ms) are logged to `completed_requests`
128
- - Adjust `completed-threshold` in Couchbase Query Settings to capture faster queries if needed
129
-
130
- :::
131
-
132
-
133
-
134
-#### Parameters
135
-
136
-| Parameter | Type | Description | Required | Default | Options |
137
-|:---------|:-----|:------------|:--------:|:--------|:--------|
138
-| Filter By | select | Select the primary sort column. Options include elapsed time, service time, request time, and result count. Defaults to elapsed time to focus on slowest queries. | yes | elapsedTime | |
139
-
140
-#### Returns
141
-
142
-Completed N1QL request statistics. Each row represents a single completed query with its timing and result metrics.
143
-
144
-| Column | Type | Unit | Visibility | Description |
145
-|:-------|:-----|:-----|:-----------|:------------|
146
-| Request ID | string | | hidden | Unique identifier for the N1QL request. Can be used for correlation with Couchbase logs. |
147
-| Request Time | timestamp | | | Timestamp when the request was received by the query service. |
148
-| Statement | string | | | The N1QL statement that was executed. Truncated to 4096 characters. |
149
-| Elapsed Time | duration | milliseconds | | Total time from request receipt to response completion, including queue time, planning, execution, and result streaming. |
150
-| Service Time | duration | milliseconds | | Time spent actively processing the request, excluding network latency and queue wait time. Compare with elapsed time to identify network or queueing delays. |
151
-| Result Count | integer | | | Number of documents/rows returned by the query. High values may indicate queries returning excessive data. |
152
-| Result Size | integer | | hidden | Total size of the result set in bytes. Large result sizes may indicate inefficient queries or missing projections. |
153
-| Error Count | integer | | hidden | Number of errors encountered during query execution. Non-zero values require investigation. |
154
-| Warning Count | integer | | hidden | Number of warnings generated during query execution. Warnings may indicate suboptimal query patterns or index usage. |
155
-| User | string | | | Couchbase user who executed the query. Useful for identifying workload by user or application. |
156
-| Client Context ID | string | | hidden | Client-provided context identifier for request tracking and correlation. |
157
-
158
-
159
-
160
-## Alerts
161
-
162
-There are no alerts configured by default for this integration.
163
-
164
-
48
## Setup
49
50
@@ -313,6 +196,123 @@ jobs:
196
197
198
199
+## Alerts
200
+
201
+There are no alerts configured by default for this integration.
202
+
203
+
204
+## Metrics
205
+
206
+Metrics grouped by *scope*.
207
+
208
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
209
+
210
+
211
+
212
+### Per Couchbase instance
213
+
214
+These metrics refer to the entire monitored application.
215
+
216
+This scope has no labels.
217
+
218
+Metrics:
219
+
220
+| Metric | Dimensions | Unit |
221
+|:------|:----------|:----|
222
+| couchbase.bucket_quota_percent_used | a dimension per bucket | percentage |
223
+| couchbase.bucket_ops_per_sec | a dimension per bucket | ops/s |
224
+| couchbase.bucket_disk_fetches | a dimension per bucket | fetches |
225
+| couchbase.bucket_item_count | a dimension per bucket | items |
226
+| couchbase.bucket_disk_used_stats | a dimension per bucket | bytes |
227
+| couchbase.bucket_data_used | a dimension per bucket | bytes |
228
+| couchbase.bucket_mem_used | a dimension per bucket | bytes |
229
+| couchbase.bucket_vb_active_num_non_resident | a dimension per bucket | items |
230
+
231
+
232
+
233
+## Live Data
234
+
235
+This collector exposes real-time functions for interactive troubleshooting in the Live tab.
236
+
237
+
238
+### Top Queries
239
+
240
+Retrieves completed N1QL query statistics from Couchbase [system:completed_requests](https://docs.couchbase.com/server/current/manage/monitor/monitoring-n1ql-query.html#sys-completed-req) keyspace.
241
+
242
+This function queries the `system:completed_requests` keyspace which stores information about recently completed N1QL requests. It provides timing metrics, result statistics, and error/warning counts for each completed query.
243
+
244
+Use cases:
245
+- Identify slow N1QL queries consuming the most elapsed time
246
+- Find queries with high error or warning counts
247
+- Analyze query patterns by user to understand workload distribution
248
+
249
+Statement text is truncated at 4096 characters for display purposes.
250
+
251
+
252
+| Aspect | Description |
253
+|:-------|:------------|
254
+| Name | `Couchbase:top-queries` |
255
+| Require Cloud | yes |
256
+| Performance | Queries `system:completed_requests` via the N1QL query service:<br/>• The `completed_requests` keyspace has a configurable size limit (`completed-limit` setting)<br/>• Default limit of 500 rows balances usefulness with performance |
257
+| Security | Query text may contain unmasked literal values including potentially sensitive data:<br/>• Personal information in WHERE clauses or INSERT values<br/>• Business data embedded in queries<br/>• Access should be restricted to authorized personnel only |
258
+| Availability | Available when:<br/>• The collector has successfully connected to Couchbase<br/>• The N1QL (Query) service is running<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the query fails<br/>• Returns HTTP 504 if the query times out |
259
+
260
+#### Prerequisites
261
+
262
+##### Grant access to `system:completed_requests`
263
+
264
+The user must have appropriate privileges to query system keyspaces and the N1QL service must be available.
265
+
266
+1. Ensure the N1QL (Query) service is running on the cluster
267
+
268
+2. Grant query system catalog privileges to the monitoring user:
269
+
270
+ ```sql
271
+ GRANT QUERY_SYSTEM_CATALOG TO netdata_user;
272
+ ```
273
+
274
+3. Verify access to `completed_requests`:
275
+
276
+ ```sql
277
+ SELECT * FROM system:completed_requests LIMIT 1;
278
+ ```
279
+
280
+ :::info
281
+
282
+ - The `system:completed_requests` keyspace stores recently completed queries based on Couchbase server settings `completed-limit` and `completed-threshold`
283
+ - Only queries exceeding `completed-threshold` (default 1000ms) are logged to `completed_requests`
284
+ - Adjust `completed-threshold` in Couchbase Query Settings to capture faster queries if needed
285
+
286
+ :::
287
+
288
+
289
+
290
+#### Parameters
291
+
292
+| Parameter | Type | Description | Required | Default | Options |
293
+|:---------|:-----|:------------|:--------:|:--------|:--------|
294
+| Filter By | select | Select the primary sort column. Options include elapsed time, service time, request time, and result count. Defaults to elapsed time to focus on slowest queries. | yes | elapsedTime | |
295
+
296
+#### Returns
297
+
298
+Completed N1QL request statistics. Each row represents a single completed query with its timing and result metrics.
299
+
300
+| Column | Type | Unit | Visibility | Description |
301
+|:-------|:-----|:-----|:-----------|:------------|
302
+| Request ID | string | | hidden | Unique identifier for the N1QL request. Can be used for correlation with Couchbase logs. |
303
+| Request Time | timestamp | | | Timestamp when the request was received by the query service. |
304
+| Statement | string | | | The N1QL statement that was executed. Truncated to 4096 characters. |
305
+| Elapsed Time | duration | milliseconds | | Total time from request receipt to response completion, including queue time, planning, execution, and result streaming. |
306
+| Service Time | duration | milliseconds | | Time spent actively processing the request, excluding network latency and queue wait time. Compare with elapsed time to identify network or queueing delays. |
307
+| Result Count | integer | | | Number of documents/rows returned by the query. High values may indicate queries returning excessive data. |
308
+| Result Size | integer | | hidden | Total size of the result set in bytes. Large result sizes may indicate inefficient queries or missing projections. |
309
+| Error Count | integer | | hidden | Number of errors encountered during query execution. Non-zero values require investigation. |
310
+| Warning Count | integer | | hidden | Number of warnings generated during query execution. Warnings may indicate suboptimal query patterns or index usage. |
311
+| User | string | | | Couchbase user who executed the query. Useful for identifying workload by user or application. |
312
+| Client Context ID | string | | hidden | Client-provided context identifier for request tracking and correlation. |
313
+
314
+
315
+
316
## Troubleshooting
317
318
### Debug Mode
src/go/plugin/go.d/collector/couchdb/integrations/couchdb.md
+42
-42
@@ -45,48 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per CouchDB instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| couchdb.activity | db_reads, db_writes, view_reads | requests/s |
67
-| couchdb.request_methods | copy, delete, get, head, options, post, put | requests/s |
68
-| couchdb.response_codes | 200, 201, 202, 204, 206, 301, 302, 304, 400, 401, 403, 404, 406, 409, 412, 413, 414, 415, 416, 417, 500, 501, 503 | responses/s |
69
-| couchdb.response_code_classes | 2xx, 3xx, 4xx, 5xx | responses/s |
70
-| couchdb.active_tasks | indexer, db_compaction, replication, view_compaction | tasks |
71
-| couchdb.replicator_jobs | running, pending, crashed, internal_replication_jobs | jobs |
72
-| couchdb.open_files | files | files |
73
-| couchdb.erlang_vm_memory | atom, binaries, code, ets, procs, other | B |
74
-| couchdb.proccounts | os_procs, erl_procs | processes |
75
-| couchdb.peakmsgqueue | peak_size | messages |
76
-| couchdb.reductions | reductions | reductions |
77
-| couchdb.db_sizes_file | a dimension per database | KiB |
78
-| couchdb.db_sizes_external | a dimension per database | KiB |
79
-| couchdb.db_sizes_active | a dimension per database | KiB |
80
-| couchdb.db_doc_count | a dimension per database | docs |
81
-| couchdb.db_doc_del_count | a dimension per database | docs |
82
-
83
-
84
-
85
-## Alerts
86
-
87
-There are no alerts configured by default for this integration.
88
-
89
-
48
## Setup
49
50
@@ -240,6 +198,48 @@ jobs:
198
199
200
201
+## Alerts
202
+
203
+There are no alerts configured by default for this integration.
204
+
205
+
206
+## Metrics
207
+
208
+Metrics grouped by *scope*.
209
+
210
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
211
+
212
+
213
+
214
+### Per CouchDB instance
215
+
216
+These metrics refer to the entire monitored application.
217
+
218
+This scope has no labels.
219
+
220
+Metrics:
221
+
222
+| Metric | Dimensions | Unit |
223
+|:------|:----------|:----|
224
+| couchdb.activity | db_reads, db_writes, view_reads | requests/s |
225
+| couchdb.request_methods | copy, delete, get, head, options, post, put | requests/s |
226
+| couchdb.response_codes | 200, 201, 202, 204, 206, 301, 302, 304, 400, 401, 403, 404, 406, 409, 412, 413, 414, 415, 416, 417, 500, 501, 503 | responses/s |
227
+| couchdb.response_code_classes | 2xx, 3xx, 4xx, 5xx | responses/s |
228
+| couchdb.active_tasks | indexer, db_compaction, replication, view_compaction | tasks |
229
+| couchdb.replicator_jobs | running, pending, crashed, internal_replication_jobs | jobs |
230
+| couchdb.open_files | files | files |
231
+| couchdb.erlang_vm_memory | atom, binaries, code, ets, procs, other | B |
232
+| couchdb.proccounts | os_procs, erl_procs | processes |
233
+| couchdb.peakmsgqueue | peak_size | messages |
234
+| couchdb.reductions | reductions | reductions |
235
+| couchdb.db_sizes_file | a dimension per database | KiB |
236
+| couchdb.db_sizes_external | a dimension per database | KiB |
237
+| couchdb.db_sizes_active | a dimension per database | KiB |
238
+| couchdb.db_doc_count | a dimension per database | docs |
239
+| couchdb.db_doc_del_count | a dimension per database | docs |
240
+
241
+
242
+
243
## Troubleshooting
244
245
### Debug Mode
src/go/plugin/go.d/collector/dcgm/integrations/nvidia_data_center_gpu_manager_dcgm.md
+196
-196
@@ -52,6 +52,202 @@ The collector applies global and per-metric time series limits to prevent excess
52
53
The impact depends on dcgm-exporter field selection and resulting series cardinality.
54
55
+## Setup
56
+
57
+
58
+You can configure the **dcgm** collector in two ways:
59
+
60
+| Method | Best for | How to |
61
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
62
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dcgm**, then click **+** to add a job. |
63
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dcgm.conf` and add a job. |
64
+
65
+:::important
66
+
67
+UI configuration requires paid Netdata Cloud plan.
68
+
69
+:::
70
+
71
+
72
+### Prerequisites
73
+
74
+#### Run dcgm-exporter
75
+
76
+Install DCGM and run `dcgm-exporter` so that a Prometheus endpoint is available (default `:9400/metrics`).
77
+
78
+#### Configure exporter field list
79
+
80
+The default exporter profile exposes a small subset of fields.
81
+Use the Netdata recommended profile:
82
+[`dcgm-exporter-netdata.csv`](https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/collector/dcgm/dcgm-exporter-netdata.csv)
83
+(raw download: `https://raw.githubusercontent.com/netdata/netdata/master/src/go/plugin/go.d/collector/dcgm/dcgm-exporter-netdata.csv`).
84
+
85
+The Netdata profile enables 127 fields by default and documents all remaining known DCGM fields as commented entries.
86
+To customize beyond the baseline, uncomment the field you need and comment one currently enabled field.
87
+
88
+Runtime validation artifact:
89
+`src/go/plugin/go.d/collector/dcgm/runtime-validation-driver-590.48.01-dcgm-exporter-4.4.1-4.5.2.md`
90
+and
91
+`src/go/plugin/go.d/collector/dcgm/runtime-validation-driver-590.48.01-dcgm-exporter-4.4.1-4.5.2.json`
92
+
93
+Validation is primarily version-scoped (NVIDIA driver + DCGM/DCGM-exporter versions), so treat it as a strong baseline rather than universal compatibility.
94
+
95
+Example:
96
+`dcgm-exporter -f /path/to/dcgm-exporter-netdata.csv`
97
+
98
+
99
+#### Keep collection intervals aligned
100
+
101
+Set Netdata `update_every` to the same value as dcgm-exporter collection interval (default 30 seconds).
102
+Example exporter interval: `dcgm-exporter -c 30000` and Netdata `update_every: 30`.
103
+
104
+
105
+#### Enable profiling capabilities (optional)
106
+
107
+Profiling fields may require additional privileges/capabilities in your runtime environment.
108
+
109
+
110
+### Configuration
111
+
112
+#### Options
113
+
114
+The following options can be defined globally: update_every, autodetection_retry.
115
+
116
+
117
+<details open><summary>Config options</summary>
118
+
119
+
120
+
121
+| Group | Option | Description | Default | Required |
122
+|:------|:-----|:------------|:--------|:---------:|
123
+| **Collection** | update_every | Data collection interval (seconds). Keep this aligned with dcgm-exporter collection interval. | 30 | no |
124
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
125
+| **Target** | url | DCGM exporter metrics endpoint URL. | http://127.0.0.1:9400/metrics | yes |
126
+| | timeout | HTTP request timeout (seconds). | 10 | no |
127
+| **Limits** | max_time_series | Global time series limit. If exceeded, collection is skipped for this cycle. | 2000 | no |
128
+| | max_time_series_per_metric | Per-metric time series limit. Metrics above this limit are skipped. | 200 | no |
129
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
130
+| | password | Password for Basic HTTP authentication. | | no |
131
+| | bearer_token_file | Path to a file containing a bearer token. | | no |
132
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
133
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
134
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
135
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
136
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
137
+| | proxy_username | Username for proxy authentication. | | no |
138
+| | proxy_password | Password for proxy authentication. | | no |
139
+| **Request** | headers | Additional HTTP headers to include in the request. | | no |
140
+| | method | HTTP method. | GET | no |
141
+| | body | HTTP request body. | | no |
142
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
143
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
144
+| **Virtual Node** | vnode | Associate this job with a Virtual Node. | | no |
145
+
146
+
147
+</details>
148
+
149
+
150
+#### via UI
151
+
152
+Configure the **dcgm** collector from the Netdata web interface:
153
+
154
+1. Go to **Nodes**.
155
+2. Select the node **where you want the dcgm data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
156
+3. The **Collectors → Jobs** view opens by default.
157
+4. In the Search box, type _dcgm_ (or scroll the list) to locate the **dcgm** collector.
158
+5. Click the **+** next to the **dcgm** collector to add a new job.
159
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
160
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
161
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
162
+
163
+
164
+#### via File
165
+
166
+The configuration file name for this integration is `go.d/dcgm.conf`.
167
+
168
+The file format is YAML. Generally, the structure is:
169
+
170
+```yaml
171
+update_every: 1
172
+autodetection_retry: 0
173
+jobs:
174
+ - name: some_name1
175
+ - name: some_name2
176
+```
177
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
178
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
179
+
180
+```bash
181
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
182
+sudo ./edit-config go.d/dcgm.conf
183
+```
184
+
185
+##### Examples
186
+
187
+###### Local exporter
188
+
189
+Collect metrics from a local dcgm-exporter endpoint.
190
+
191
+<details open><summary>Config</summary>
192
+
193
+```yaml
194
+jobs:
195
+ - name: local
196
+ url: http://127.0.0.1:9400/metrics
197
+ update_every: 30
198
+
199
+```
200
+</details>
201
+
202
+###### TLS endpoint
203
+
204
+Collect metrics over HTTPS with custom CA certificate.
205
+
206
+<details open><summary>Config</summary>
207
+
208
+```yaml
209
+jobs:
210
+ - name: secure
211
+ url: https://dcgm-exporter.example.com:9400/metrics
212
+ update_every: 30
213
+ tls_ca: /etc/netdata/certs/dcgm-ca.crt
214
+
215
+```
216
+</details>
217
+
218
+###### Increased cardinality limits
219
+
220
+Increase limits when collecting large field sets and multiple entities.
221
+
222
+<details open><summary>Config</summary>
223
+
224
+```yaml
225
+jobs:
226
+ - name: dcgm_large
227
+ url: http://127.0.0.1:9400/metrics
228
+ update_every: 30
229
+ max_time_series: 10000
230
+ max_time_series_per_metric: 2000
231
+
232
+```
233
+</details>
234
+
235
+
236
+
237
+## Alerts
238
+
239
+
240
+The following alerts are available:
241
+
242
+| Alert name | On metric | Description |
243
+|:------------|:----------|:------------|
244
+| [ dcgm_gpu_xid_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.reliability.xid | NVIDIA driver reported GPU XID error on GPU ${label:gpu} |
245
+| [ dcgm_gpu_row_remap_failure ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.reliability.row_remap_status | GPU row remapping failed on GPU ${label:gpu} |
246
+| [ dcgm_gpu_uncorrectable_remapped_rows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.reliability.row_remap_events | Uncorrectable remapped rows increased on GPU ${label:gpu} |
247
+| [ dcgm_gpu_power_violation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.throttle.violations | Power throttling detected on GPU ${label:gpu} |
248
+| [ dcgm_gpu_thermal_violation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.throttle.violations | Thermal throttling detected on GPU ${label:gpu} |
249
+
250
+
251
## Metrics
252
253
Metrics grouped by *scope*.
@@ -322,202 +518,6 @@ Metrics:
518
519
520
325
-## Alerts
326
-
327
-
328
-The following alerts are available:
329
-
330
-| Alert name | On metric | Description |
331
-|:------------|:----------|:------------|
332
-| [ dcgm_gpu_xid_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.reliability.xid | NVIDIA driver reported GPU XID error on GPU ${label:gpu} |
333
-| [ dcgm_gpu_row_remap_failure ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.reliability.row_remap_status | GPU row remapping failed on GPU ${label:gpu} |
334
-| [ dcgm_gpu_uncorrectable_remapped_rows ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.reliability.row_remap_events | Uncorrectable remapped rows increased on GPU ${label:gpu} |
335
-| [ dcgm_gpu_power_violation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.throttle.violations | Power throttling detected on GPU ${label:gpu} |
336
-| [ dcgm_gpu_thermal_violation ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dcgm.conf) | dcgm.gpu.throttle.violations | Thermal throttling detected on GPU ${label:gpu} |
337
-
338
-
339
-## Setup
340
-
341
-
342
-You can configure the **dcgm** collector in two ways:
343
-
344
-| Method | Best for | How to |
345
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
346
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dcgm**, then click **+** to add a job. |
347
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dcgm.conf` and add a job. |
348
-
349
-:::important
350
-
351
-UI configuration requires paid Netdata Cloud plan.
352
-
353
-:::
354
-
355
-
356
-### Prerequisites
357
-
358
-#### Run dcgm-exporter
359
-
360
-Install DCGM and run `dcgm-exporter` so that a Prometheus endpoint is available (default `:9400/metrics`).
361
-
362
-#### Configure exporter field list
363
-
364
-The default exporter profile exposes a small subset of fields.
365
-Use the Netdata recommended profile:
366
-[`dcgm-exporter-netdata.csv`](https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/collector/dcgm/dcgm-exporter-netdata.csv)
367
-(raw download: `https://raw.githubusercontent.com/netdata/netdata/master/src/go/plugin/go.d/collector/dcgm/dcgm-exporter-netdata.csv`).
368
-
369
-The Netdata profile enables 127 fields by default and documents all remaining known DCGM fields as commented entries.
370
-To customize beyond the baseline, uncomment the field you need and comment one currently enabled field.
371
-
372
-Runtime validation artifact:
373
-`src/go/plugin/go.d/collector/dcgm/runtime-validation-driver-590.48.01-dcgm-exporter-4.4.1-4.5.2.md`
374
-and
375
-`src/go/plugin/go.d/collector/dcgm/runtime-validation-driver-590.48.01-dcgm-exporter-4.4.1-4.5.2.json`
376
-
377
-Validation is primarily version-scoped (NVIDIA driver + DCGM/DCGM-exporter versions), so treat it as a strong baseline rather than universal compatibility.
378
-
379
-Example:
380
-`dcgm-exporter -f /path/to/dcgm-exporter-netdata.csv`
381
-
382
-
383
-#### Keep collection intervals aligned
384
-
385
-Set Netdata `update_every` to the same value as dcgm-exporter collection interval (default 30 seconds).
386
-Example exporter interval: `dcgm-exporter -c 30000` and Netdata `update_every: 30`.
387
-
388
-
389
-#### Enable profiling capabilities (optional)
390
-
391
-Profiling fields may require additional privileges/capabilities in your runtime environment.
392
-
393
-
394
-### Configuration
395
-
396
-#### Options
397
-
398
-The following options can be defined globally: update_every, autodetection_retry.
399
-
400
-
401
-<details open><summary>Config options</summary>
402
-
403
-
404
-
405
-| Group | Option | Description | Default | Required |
406
-|:------|:-----|:------------|:--------|:---------:|
407
-| **Collection** | update_every | Data collection interval (seconds). Keep this aligned with dcgm-exporter collection interval. | 30 | no |
408
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
409
-| **Target** | url | DCGM exporter metrics endpoint URL. | http://127.0.0.1:9400/metrics | yes |
410
-| | timeout | HTTP request timeout (seconds). | 10 | no |
411
-| **Limits** | max_time_series | Global time series limit. If exceeded, collection is skipped for this cycle. | 2000 | no |
412
-| | max_time_series_per_metric | Per-metric time series limit. Metrics above this limit are skipped. | 200 | no |
413
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
414
-| | password | Password for Basic HTTP authentication. | | no |
415
-| | bearer_token_file | Path to a file containing a bearer token. | | no |
416
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
417
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
418
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
419
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
420
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
421
-| | proxy_username | Username for proxy authentication. | | no |
422
-| | proxy_password | Password for proxy authentication. | | no |
423
-| **Request** | headers | Additional HTTP headers to include in the request. | | no |
424
-| | method | HTTP method. | GET | no |
425
-| | body | HTTP request body. | | no |
426
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
427
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
428
-| **Virtual Node** | vnode | Associate this job with a Virtual Node. | | no |
429
-
430
-
431
-</details>
432
-
433
-
434
-#### via UI
435
-
436
-Configure the **dcgm** collector from the Netdata web interface:
437
-
438
-1. Go to **Nodes**.
439
-2. Select the node **where you want the dcgm data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
440
-3. The **Collectors → Jobs** view opens by default.
441
-4. In the Search box, type _dcgm_ (or scroll the list) to locate the **dcgm** collector.
442
-5. Click the **+** next to the **dcgm** collector to add a new job.
443
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
444
- - **Test** runs the job with the provided settings and shows whether data can be collected.
445
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
446
-
447
-
448
-#### via File
449
-
450
-The configuration file name for this integration is `go.d/dcgm.conf`.
451
-
452
-The file format is YAML. Generally, the structure is:
453
-
454
-```yaml
455
-update_every: 1
456
-autodetection_retry: 0
457
-jobs:
458
- - name: some_name1
459
- - name: some_name2
460
-```
461
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
462
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
463
-
464
-```bash
465
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
466
-sudo ./edit-config go.d/dcgm.conf
467
-```
468
-
469
-##### Examples
470
-
471
-###### Local exporter
472
-
473
-Collect metrics from a local dcgm-exporter endpoint.
474
-
475
-<details open><summary>Config</summary>
476
-
477
-```yaml
478
-jobs:
479
- - name: local
480
- url: http://127.0.0.1:9400/metrics
481
- update_every: 30
482
-
483
-```
484
-</details>
485
-
486
-###### TLS endpoint
487
-
488
-Collect metrics over HTTPS with custom CA certificate.
489
-
490
-<details open><summary>Config</summary>
491
-
492
-```yaml
493
-jobs:
494
- - name: secure
495
- url: https://dcgm-exporter.example.com:9400/metrics
496
- update_every: 30
497
- tls_ca: /etc/netdata/certs/dcgm-ca.crt
498
-
499
-```
500
-</details>
501
-
502
-###### Increased cardinality limits
503
-
504
-Increase limits when collecting large field sets and multiple entities.
505
-
506
-<details open><summary>Config</summary>
507
-
508
-```yaml
509
-jobs:
510
- - name: dcgm_large
511
- url: http://127.0.0.1:9400/metrics
512
- update_every: 30
513
- max_time_series: 10000
514
- max_time_series_per_metric: 2000
515
-
516
-```
517
-</details>
518
-
519
-
520
-
521
## Troubleshooting
522
523
### Debug Mode
src/go/plugin/go.d/collector/dmcache/integrations/dmcache_devices.md
+36
-36
@@ -45,42 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per dmcache device
57
-
58
-These metrics refer to the DMCache device.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| device | Device name |
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| dmcache.device_cache_space_usage | free, used | bytes |
71
-| dmcache.device_metadata_space_usage | free, used | bytes |
72
-| dmcache.device_cache_read_efficiency | hits, misses | requests/s |
73
-| dmcache.device_cache_write_efficiency | hits, misses | requests/s |
74
-| dmcache.device_cache_activity | promotions, demotions | bytes/s |
75
-| dmcache.device_cache_dirty_size | dirty | bytes |
76
-
77
-
78
-
79
-## Alerts
80
-
81
-There are no alerts configured by default for this integration.
82
-
83
-
48
## Setup
49
50
@@ -175,6 +139,42 @@ jobs:
139
140
141
142
+## Alerts
143
+
144
+There are no alerts configured by default for this integration.
145
+
146
+
147
+## Metrics
148
+
149
+Metrics grouped by *scope*.
150
+
151
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
152
+
153
+
154
+
155
+### Per dmcache device
156
+
157
+These metrics refer to the DMCache device.
158
+
159
+Labels:
160
+
161
+| Label | Description |
162
+|:-----------|:----------------|
163
+| device | Device name |
164
+
165
+Metrics:
166
+
167
+| Metric | Dimensions | Unit |
168
+|:------|:----------|:----|
169
+| dmcache.device_cache_space_usage | free, used | bytes |
170
+| dmcache.device_metadata_space_usage | free, used | bytes |
171
+| dmcache.device_cache_read_efficiency | hits, misses | requests/s |
172
+| dmcache.device_cache_write_efficiency | hits, misses | requests/s |
173
+| dmcache.device_cache_activity | promotions, demotions | bytes/s |
174
+| dmcache.device_cache_dirty_size | dirty | bytes |
175
+
176
+
177
+
178
## Troubleshooting
179
180
### Debug Mode
src/go/plugin/go.d/collector/dnsdist/integrations/dnsdist.md
+38
-38
@@ -45,44 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per DNSdist instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| dnsdist.queries | all, recursive, empty | queries/s |
67
-| dnsdist.queries_dropped | rule_drop, dynamic_blocked, no_policy, non_queries | queries/s |
68
-| dnsdist.packets_dropped | acl | packets/s |
69
-| dnsdist.answers | self_answered, nxdomain, refused, trunc_failures | answers/s |
70
-| dnsdist.backend_responses | responses | responses/s |
71
-| dnsdist.backend_commerrors | send_errors | errors/s |
72
-| dnsdist.backend_errors | timeouts, servfail, non_compliant | responses/s |
73
-| dnsdist.cache | hits, misses | answers/s |
74
-| dnsdist.servercpu | system_state, user_state | ms/s |
75
-| dnsdist.servermem | memory_usage | MiB |
76
-| dnsdist.query_latency | 1ms, 10ms, 50ms, 100ms, 1sec, slow | queries/s |
77
-| dnsdist.query_latency_avg | 100, 1k, 10k, 1000k | microseconds |
78
-
79
-
80
-
81
-## Alerts
82
-
83
-There are no alerts configured by default for this integration.
84
-
85
-
48
## Setup
49
50
@@ -225,6 +187,44 @@ jobs:
187
188
189
190
+## Alerts
191
+
192
+There are no alerts configured by default for this integration.
193
+
194
+
195
+## Metrics
196
+
197
+Metrics grouped by *scope*.
198
+
199
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
200
+
201
+
202
+
203
+### Per DNSdist instance
204
+
205
+These metrics refer to the entire monitored application.
206
+
207
+This scope has no labels.
208
+
209
+Metrics:
210
+
211
+| Metric | Dimensions | Unit |
212
+|:------|:----------|:----|
213
+| dnsdist.queries | all, recursive, empty | queries/s |
214
+| dnsdist.queries_dropped | rule_drop, dynamic_blocked, no_policy, non_queries | queries/s |
215
+| dnsdist.packets_dropped | acl | packets/s |
216
+| dnsdist.answers | self_answered, nxdomain, refused, trunc_failures | answers/s |
217
+| dnsdist.backend_responses | responses | responses/s |
218
+| dnsdist.backend_commerrors | send_errors | errors/s |
219
+| dnsdist.backend_errors | timeouts, servfail, non_compliant | responses/s |
220
+| dnsdist.cache | hits, misses | answers/s |
221
+| dnsdist.servercpu | system_state, user_state | ms/s |
222
+| dnsdist.servermem | memory_usage | MiB |
223
+| dnsdist.query_latency | 1ms, 10ms, 50ms, 100ms, 1sec, slow | queries/s |
224
+| dnsdist.query_latency_avg | 100, 1k, 10k, 1000k | microseconds |
225
+
226
+
227
+
228
## Troubleshooting
229
230
### Debug Mode
src/go/plugin/go.d/collector/dnsmasq/integrations/dnsmasq.md
+30
-30
@@ -45,36 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Dnsmasq instance
57
-
58
-The metrics apply to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| dnsmasq.servers_queries | success, failed | queries/s |
67
-| dnsmasq.cache_performance | hist, misses | events/s |
68
-| dnsmasq.cache_operations | insertions, evictions | operations/s |
69
-| dnsmasq.cache_size | size | entries |
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
48
## Setup
49
50
@@ -208,6 +178,36 @@ jobs:
178
179
180
181
+## Alerts
182
+
183
+There are no alerts configured by default for this integration.
184
+
185
+
186
+## Metrics
187
+
188
+Metrics grouped by *scope*.
189
+
190
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
191
+
192
+
193
+
194
+### Per Dnsmasq instance
195
+
196
+The metrics apply to the entire monitored application.
197
+
198
+This scope has no labels.
199
+
200
+Metrics:
201
+
202
+| Metric | Dimensions | Unit |
203
+|:------|:----------|:----|
204
+| dnsmasq.servers_queries | success, failed | queries/s |
205
+| dnsmasq.cache_performance | hist, misses | events/s |
206
+| dnsmasq.cache_operations | insertions, evictions | operations/s |
207
+| dnsmasq.cache_size | size | entries |
208
+
209
+
210
+
211
## Troubleshooting
212
213
### Debug Mode
src/go/plugin/go.d/collector/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md
+50
-50
@@ -54,56 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per Dnsmasq DHCP instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| dnsmasq_dhcp.dhcp_ranges | ipv4, ipv6 | ranges |
76
-| dnsmasq_dhcp.dhcp_hosts | ipv4, ipv6 | hosts |
77
-
78
-### Per dhcp range
79
-
80
-These metrics refer to the DHCP range.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| dhcp_range | DHCP range in `START_IP:END_IP` format |
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| dnsmasq_dhcp.dhcp_range_utilization | used | percentage |
93
-| dnsmasq_dhcp.dhcp_range_allocated_leases | allocated | leases |
94
-
95
-
96
-
97
-## Alerts
98
-
99
-
100
-The following alerts are available:
101
-
102
-| Alert name | On metric | Description |
103
-|:------------|:----------|:------------|
104
-| [ dnsmasq_dhcp_dhcp_range_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dnsmasq_dhcp.conf) | dnsmasq_dhcp.dhcp_range_utilization | DHCP range utilization |
105
-
106
-
57
## Setup
58
59
@@ -219,6 +169,56 @@ jobs:
169
170
171
172
+## Alerts
173
+
174
+
175
+The following alerts are available:
176
+
177
+| Alert name | On metric | Description |
178
+|:------------|:----------|:------------|
179
+| [ dnsmasq_dhcp_dhcp_range_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dnsmasq_dhcp.conf) | dnsmasq_dhcp.dhcp_range_utilization | DHCP range utilization |
180
+
181
+
182
+## Metrics
183
+
184
+Metrics grouped by *scope*.
185
+
186
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
187
+
188
+
189
+
190
+### Per Dnsmasq DHCP instance
191
+
192
+These metrics refer to the entire monitored application.
193
+
194
+This scope has no labels.
195
+
196
+Metrics:
197
+
198
+| Metric | Dimensions | Unit |
199
+|:------|:----------|:----|
200
+| dnsmasq_dhcp.dhcp_ranges | ipv4, ipv6 | ranges |
201
+| dnsmasq_dhcp.dhcp_hosts | ipv4, ipv6 | hosts |
202
+
203
+### Per dhcp range
204
+
205
+These metrics refer to the DHCP range.
206
+
207
+Labels:
208
+
209
+| Label | Description |
210
+|:-----------|:----------------|
211
+| dhcp_range | DHCP range in `START_IP:END_IP` format |
212
+
213
+Metrics:
214
+
215
+| Metric | Dimensions | Unit |
216
+|:------|:----------|:----|
217
+| dnsmasq_dhcp.dhcp_range_utilization | used | percentage |
218
+| dnsmasq_dhcp.dhcp_range_allocated_leases | allocated | leases |
219
+
220
+
221
+
222
## Troubleshooting
223
224
### Debug Mode
src/go/plugin/go.d/collector/dnsquery/integrations/dns_query.md
+39
-39
@@ -45,45 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per server
57
-
58
-These metrics refer to the DNS server.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| server | DNS server address. |
65
-| network | Network protocol name (tcp, udp, tcp-tls). |
66
-| record_type | DNS record type (e.g. A, AAAA, CNAME). |
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| dns_query.query_status | success, network_error, dns_error | status |
73
-| dns_query.query_time | query_time | seconds |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-
80
-The following alerts are available:
81
-
82
-| Alert name | On metric | Description |
83
-|:------------|:----------|:------------|
84
-| [ dns_query_query_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dns_query.conf) | dns_query.query_status | DNS request type ${label:record_type} to server ${label:server} is unsuccessful |
85
-
86
-
48
## Setup
49
50
@@ -214,6 +175,45 @@ jobs:
175
176
177
178
+## Alerts
179
+
180
+
181
+The following alerts are available:
182
+
183
+| Alert name | On metric | Description |
184
+|:------------|:----------|:------------|
185
+| [ dns_query_query_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/dns_query.conf) | dns_query.query_status | DNS request type ${label:record_type} to server ${label:server} is unsuccessful |
186
+
187
+
188
+## Metrics
189
+
190
+Metrics grouped by *scope*.
191
+
192
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
193
+
194
+
195
+
196
+### Per server
197
+
198
+These metrics refer to the DNS server.
199
+
200
+Labels:
201
+
202
+| Label | Description |
203
+|:-----------|:----------------|
204
+| server | DNS server address. |
205
+| network | Network protocol name (tcp, udp, tcp-tls). |
206
+| record_type | DNS record type (e.g. A, AAAA, CNAME). |
207
+
208
+Metrics:
209
+
210
+| Metric | Dimensions | Unit |
211
+|:------|:----------|:----|
212
+| dns_query.query_status | success, network_error, dns_error | status |
213
+| dns_query.query_time | query_time | seconds |
214
+
215
+
216
+
217
## Troubleshooting
218
219
### Debug Mode
src/go/plugin/go.d/collector/docker/integrations/docker.md
+106
-106
@@ -53,112 +53,6 @@ The default configuration for this integration does not impose any limits on dat
53
Enabling `collect_container_size` may result in high CPU usage depending on the version of Docker Engine.
54
55
56
-## Metrics
57
-
58
-Metrics grouped by *scope*.
59
-
60
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
61
-
62
-
63
-
64
-### Per Docker instance
65
-
66
-These metrics refer to the entire monitored application.
67
-
68
-This scope has no labels.
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| docker.containers_state | running, paused, stopped | containers |
75
-| docker.containers_health_status | healthy, unhealthy, not_running_unhealthy, starting, no_healthcheck | containers |
76
-| docker.images | active, dangling | images |
77
-| docker.images_size | size | bytes |
78
-
79
-### Per container
80
-
81
-Metrics related to containers. Each container provides its own set of the following metrics.
82
-
83
-Labels:
84
-
85
-| Label | Description |
86
-|:-----------|:----------------|
87
-| container_name | The container's name |
88
-| image | The image name the container uses |
89
-
90
-Metrics:
91
-
92
-| Metric | Dimensions | Unit |
93
-|:------|:----------|:----|
94
-| docker.container_state | running, paused, exited, created, restarting, removing, dead | state |
95
-| docker.container_health_status | healthy, unhealthy, not_running_unhealthy, starting, no_healthcheck | status |
96
-| docker.container_writeable_layer_size | writeable_layer | size |
97
-
98
-
99
-
100
-## Functions
101
-
102
-This collector exposes real-time functions for interactive troubleshooting in the Live tab.
103
-
104
-
105
-### Containers
106
-
107
-Retrieves container list data equivalent to `docker ps -a`.
108
-
109
-This function calls the Docker Container List API with `all=true` and returns both running and non-running containers in a table similar to Docker CLI output.
110
-
111
-Use cases:
112
-- Quickly inspect all containers (running, exited, paused, dead) from Netdata
113
-- Correlate container lifecycle with metric changes and alerts
114
-- Verify exposed ports, image tags, and container names without shell access
115
-
116
-
117
-| Aspect | Description |
118
-|:-------|:------------|
119
-| Name | `Docker:container-ls` |
120
-| Require Cloud | yes |
121
-| Performance | Executes a single Docker API request (`ContainerList` with `all=true`):<br/>• No per-container inspect requests are issued<br/>• Response size grows with total container count<br/>• Large histories with many stopped containers may return more rows |
122
-| Security | Exposes container metadata that may include sensitive details:<br/>• Container command text may include runtime arguments<br/>• Image names, ports, and container names are visible<br/>• Restrict access to authorized operators |
123
-| Availability | Available when:<br/>• Docker collector is initialized and connected<br/>• Docker API list-containers request succeeds<br/>• Returns HTTP 503 while collector is initializing<br/>• Returns HTTP 500 on Docker API errors<br/>• Returns HTTP 504 on timeout |
124
-
125
-#### Prerequisites
126
-
127
-No additional configuration is required.
128
-
129
-#### Parameters
130
-
131
-This function has no parameters.
132
-
133
-#### Returns
134
-
135
-Container inventory from Docker Engine. Each row represents one container returned by `docker ps -a`.
136
-
137
-| Column | Type | Unit | Visibility | Description |
138
-|:-------|:-----|:-----|:-----------|:------------|
139
-| CONTAINER ID | string | | | Short container ID (12 characters). |
140
-| IMAGE | string | | | Container image reference. |
141
-| COMMAND | string | | | Container command as reported by Docker API. |
142
-| CREATED | string | | | Human-readable container creation age (for example, '5 days ago'). |
143
-| STATUS | string | | | Docker status string (for example, 'Up 3 weeks' or 'Exited (0) 4 weeks ago'). |
144
-| State (Raw) | string | | hidden | Raw Docker state value (for example, running, exited, paused, restarting, dead). |
145
-| PORTS | string | | | Published or exposed ports summary. |
146
-| NAMES | string | | | Container name. |
147
-| Container ID (Full) | string | | hidden | Full 64-character container ID. |
148
-| Created (Unix) | integer | seconds | hidden | Container creation timestamp in Unix seconds. |
149
-
150
-
151
-
152
-## Alerts
153
-
154
-
155
-The following alerts are available:
156
-
157
-| Alert name | On metric | Description |
158
-|:------------|:----------|:------------|
159
-| [ docker_container_unhealthy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/docker.conf) | docker.container_health_status | ${label:container_name} docker container health status is unhealthy |
160
-
161
-
56
## Setup
57
58
@@ -274,6 +168,112 @@ jobs:
168
169
170
171
+## Alerts
172
+
173
+
174
+The following alerts are available:
175
+
176
+| Alert name | On metric | Description |
177
+|:------------|:----------|:------------|
178
+| [ docker_container_unhealthy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/docker.conf) | docker.container_health_status | ${label:container_name} docker container health status is unhealthy |
179
+
180
+
181
+## Metrics
182
+
183
+Metrics grouped by *scope*.
184
+
185
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
186
+
187
+
188
+
189
+### Per Docker instance
190
+
191
+These metrics refer to the entire monitored application.
192
+
193
+This scope has no labels.
194
+
195
+Metrics:
196
+
197
+| Metric | Dimensions | Unit |
198
+|:------|:----------|:----|
199
+| docker.containers_state | running, paused, stopped | containers |
200
+| docker.containers_health_status | healthy, unhealthy, not_running_unhealthy, starting, no_healthcheck | containers |
201
+| docker.images | active, dangling | images |
202
+| docker.images_size | size | bytes |
203
+
204
+### Per container
205
+
206
+Metrics related to containers. Each container provides its own set of the following metrics.
207
+
208
+Labels:
209
+
210
+| Label | Description |
211
+|:-----------|:----------------|
212
+| container_name | The container's name |
213
+| image | The image name the container uses |
214
+
215
+Metrics:
216
+
217
+| Metric | Dimensions | Unit |
218
+|:------|:----------|:----|
219
+| docker.container_state | running, paused, exited, created, restarting, removing, dead | state |
220
+| docker.container_health_status | healthy, unhealthy, not_running_unhealthy, starting, no_healthcheck | status |
221
+| docker.container_writeable_layer_size | writeable_layer | size |
222
+
223
+
224
+
225
+## Live Data
226
+
227
+This collector exposes real-time functions for interactive troubleshooting in the Live tab.
228
+
229
+
230
+### Containers
231
+
232
+Retrieves container list data equivalent to `docker ps -a`.
233
+
234
+This function calls the Docker Container List API with `all=true` and returns both running and non-running containers in a table similar to Docker CLI output.
235
+
236
+Use cases:
237
+- Quickly inspect all containers (running, exited, paused, dead) from Netdata
238
+- Correlate container lifecycle with metric changes and alerts
239
+- Verify exposed ports, image tags, and container names without shell access
240
+
241
+
242
+| Aspect | Description |
243
+|:-------|:------------|
244
+| Name | `Docker:container-ls` |
245
+| Require Cloud | yes |
246
+| Performance | Executes a single Docker API request (`ContainerList` with `all=true`):<br/>• No per-container inspect requests are issued<br/>• Response size grows with total container count<br/>• Large histories with many stopped containers may return more rows |
247
+| Security | Exposes container metadata that may include sensitive details:<br/>• Container command text may include runtime arguments<br/>• Image names, ports, and container names are visible<br/>• Restrict access to authorized operators |
248
+| Availability | Available when:<br/>• Docker collector is initialized and connected<br/>• Docker API list-containers request succeeds<br/>• Returns HTTP 503 while collector is initializing<br/>• Returns HTTP 500 on Docker API errors<br/>• Returns HTTP 504 on timeout |
249
+
250
+#### Prerequisites
251
+
252
+No additional configuration is required.
253
+
254
+#### Parameters
255
+
256
+This function has no parameters.
257
+
258
+#### Returns
259
+
260
+Container inventory from Docker Engine. Each row represents one container returned by `docker ps -a`.
261
+
262
+| Column | Type | Unit | Visibility | Description |
263
+|:-------|:-----|:-----|:-----------|:------------|
264
+| CONTAINER ID | string | | | Short container ID (12 characters). |
265
+| IMAGE | string | | | Container image reference. |
266
+| COMMAND | string | | | Container command as reported by Docker API. |
267
+| CREATED | string | | | Human-readable container creation age (for example, '5 days ago'). |
268
+| STATUS | string | | | Docker status string (for example, 'Up 3 weeks' or 'Exited (0) 4 weeks ago'). |
269
+| State (Raw) | string | | hidden | Raw Docker state value (for example, running, exited, paused, restarting, dead). |
270
+| PORTS | string | | | Published or exposed ports summary. |
271
+| NAMES | string | | | Container name. |
272
+| Container ID (Full) | string | | hidden | Full 64-character container ID. |
273
+| Created (Unix) | integer | seconds | hidden | Container creation timestamp in Unix seconds. |
274
+
275
+
276
+
277
## Troubleshooting
278
279
### Debug Mode
src/go/plugin/go.d/collector/docker_engine/integrations/docker_engine.md
+34
-34
@@ -47,40 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per Docker Engine instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| docker_engine.engine_daemon_container_actions | changes, commit, create, delete, start | actions/s |
69
-| docker_engine.engine_daemon_container_states_containers | running, paused, stopped | containers |
70
-| docker_engine.builder_builds_failed_total | build_canceled, build_target_not_reachable_error, command_not_supported_error, dockerfile_empty_error, dockerfile_syntax_error, error_processing_commands_error, missing_onbuild_arguments_error, unknown_instruction_error | fails/s |
71
-| docker_engine.engine_daemon_health_checks_failed_total | fails | events/s |
72
-| docker_engine.swarm_manager_leader | is_leader | bool |
73
-| docker_engine.swarm_manager_object_store | nodes, services, tasks, networks, secrets, configs | objects |
74
-| docker_engine.swarm_manager_nodes_per_state | ready, down, unknown, disconnected | nodes |
75
-| docker_engine.swarm_manager_tasks_per_state | running, failed, ready, rejected, starting, shutdown, new, orphaned, preparing, pending, complete, remove, accepted, assigned | tasks |
76
-
77
-
78
-
79
-## Alerts
80
-
81
-There are no alerts configured by default for this integration.
82
-
83
-
50
## Setup
51
52
@@ -244,6 +210,40 @@ jobs:
210
211
212
213
+## Alerts
214
+
215
+There are no alerts configured by default for this integration.
216
+
217
+
218
+## Metrics
219
+
220
+Metrics grouped by *scope*.
221
+
222
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
223
+
224
+
225
+
226
+### Per Docker Engine instance
227
+
228
+These metrics refer to the entire monitored application.
229
+
230
+This scope has no labels.
231
+
232
+Metrics:
233
+
234
+| Metric | Dimensions | Unit |
235
+|:------|:----------|:----|
236
+| docker_engine.engine_daemon_container_actions | changes, commit, create, delete, start | actions/s |
237
+| docker_engine.engine_daemon_container_states_containers | running, paused, stopped | containers |
238
+| docker_engine.builder_builds_failed_total | build_canceled, build_target_not_reachable_error, command_not_supported_error, dockerfile_empty_error, dockerfile_syntax_error, error_processing_commands_error, missing_onbuild_arguments_error, unknown_instruction_error | fails/s |
239
+| docker_engine.engine_daemon_health_checks_failed_total | fails | events/s |
240
+| docker_engine.swarm_manager_leader | is_leader | bool |
241
+| docker_engine.swarm_manager_object_store | nodes, services, tasks, networks, secrets, configs | objects |
242
+| docker_engine.swarm_manager_nodes_per_state | ready, down, unknown, disconnected | nodes |
243
+| docker_engine.swarm_manager_tasks_per_state | running, failed, ready, rejected, starting, shutdown, new, orphaned, preparing, pending, complete, remove, accepted, assigned | tasks |
244
+
245
+
246
+
247
## Troubleshooting
248
249
### Debug Mode
src/go/plugin/go.d/collector/dockerhub/integrations/docker_hub_repository.md
+32
-32
@@ -45,38 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Docker Hub repository instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| dockerhub.pulls_sum | sum | pulls |
67
-| dockerhub.pulls | a dimension per repository | pulls |
68
-| dockerhub.pulls_rate | a dimension per repository | pulls/s |
69
-| dockerhub.stars | a dimension per repository | stars |
70
-| dockerhub.status | a dimension per repository | status |
71
-| dockerhub.last_updated | a dimension per repository | seconds |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-There are no alerts configured by default for this integration.
78
-
79
-
48
## Setup
49
50
@@ -189,6 +157,38 @@ jobs:
157
```
158
159
160
+## Alerts
161
+
162
+There are no alerts configured by default for this integration.
163
+
164
+
165
+## Metrics
166
+
167
+Metrics grouped by *scope*.
168
+
169
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
170
+
171
+
172
+
173
+### Per Docker Hub repository instance
174
+
175
+These metrics refer to the entire monitored application.
176
+
177
+This scope has no labels.
178
+
179
+Metrics:
180
+
181
+| Metric | Dimensions | Unit |
182
+|:------|:----------|:----|
183
+| dockerhub.pulls_sum | sum | pulls |
184
+| dockerhub.pulls | a dimension per repository | pulls |
185
+| dockerhub.pulls_rate | a dimension per repository | pulls/s |
186
+| dockerhub.stars | a dimension per repository | stars |
187
+| dockerhub.status | a dimension per repository | status |
188
+| dockerhub.last_updated | a dimension per repository | seconds |
189
+
190
+
191
+
192
## Troubleshooting
193
194
### Debug Mode
src/go/plugin/go.d/collector/dovecot/integrations/dovecot.md
+37
-37
@@ -50,43 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Dovecot instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| dovecot.session | active | sessions |
72
-| dovecot.logins | logins | logins |
73
-| dovecot.auth | ok, failed | attempts/s |
74
-| dovecot.commands | commands | commands |
75
-| dovecot.context_switches | voluntary, voluntary | switches/s |
76
-| dovecot.io | read, write | KiB/s |
77
-| dovecot.net | read, write | kilobits/s |
78
-| dovecot.syscalls | read, write | syscalls/s |
79
-| dovecot.lookup | path, attr | lookups/s |
80
-| dovecot.cache | hits | hits/s |
81
-| dovecot.auth_cache | hits, misses | requests/s |
82
-
83
-
84
-
85
-## Alerts
86
-
87
-There are no alerts configured by default for this integration.
88
-
89
-
53
## Setup
54
55
@@ -222,6 +185,43 @@ jobs:
185
186
187
188
+## Alerts
189
+
190
+There are no alerts configured by default for this integration.
191
+
192
+
193
+## Metrics
194
+
195
+Metrics grouped by *scope*.
196
+
197
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
198
+
199
+
200
+
201
+### Per Dovecot instance
202
+
203
+These metrics refer to the entire monitored application.
204
+
205
+This scope has no labels.
206
+
207
+Metrics:
208
+
209
+| Metric | Dimensions | Unit |
210
+|:------|:----------|:----|
211
+| dovecot.session | active | sessions |
212
+| dovecot.logins | logins | logins |
213
+| dovecot.auth | ok, failed | attempts/s |
214
+| dovecot.commands | commands | commands |
215
+| dovecot.context_switches | voluntary, voluntary | switches/s |
216
+| dovecot.io | read, write | KiB/s |
217
+| dovecot.net | read, write | kilobits/s |
218
+| dovecot.syscalls | read, write | syscalls/s |
219
+| dovecot.lookup | path, attr | lookups/s |
220
+| dovecot.cache | hits | hits/s |
221
+| dovecot.auth_cache | hits, misses | requests/s |
222
+
223
+
224
+
225
## Troubleshooting
226
227
### Debug Mode
src/go/plugin/go.d/collector/elasticsearch/integrations/elasticsearch.md
+197
-197
@@ -66,6 +66,202 @@ By default, this collector monitors only the node it is connected to. To monitor
66
67
The default configuration for this integration is not expected to impose a significant performance impact on the system.
68
69
+## Setup
70
+
71
+
72
+You can configure the **elasticsearch** collector in two ways:
73
+
74
+| Method | Best for | How to |
75
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
76
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **elasticsearch**, then click **+** to add a job. |
77
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/elasticsearch.conf` and add a job. |
78
+
79
+:::important
80
+
81
+UI configuration requires paid Netdata Cloud plan.
82
+
83
+:::
84
+
85
+
86
+### Prerequisites
87
+
88
+No action required.
89
+
90
+### Configuration
91
+
92
+#### Options
93
+
94
+The following options can be defined globally: update_every, autodetection_retry.
95
+
96
+
97
+<details open><summary>Config options</summary>
98
+
99
+
100
+
101
+| Group | Option | Description | Default | Required |
102
+|:------|:-----|:------------|:--------|:---------:|
103
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
104
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
105
+| **Target** | url | Target endpoint URL. | http://127.0.0.1:9200 | yes |
106
+| | timeout | HTTP request timeout (seconds). | 2 | no |
107
+| **Metrics Selection** | cluster_mode | Collect metrics for all nodes in the cluster (yes) or only the local node (no). | no | no |
108
+| | collect_node_stats | Collect node metrics. | yes | no |
109
+| | collect_cluster_health | Collect cluster health metrics. | yes | no |
110
+| | collect_cluster_stats | Collect cluster stats metrics. | yes | no |
111
+| | collect_indices_stats | Collect index metrics. | no | no |
112
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
113
+| | password | Password for Basic HTTP authentication. | | no |
114
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
115
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
116
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
117
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
118
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
119
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
120
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
121
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
122
+| **Request** | method | HTTP method to use. | GET | no |
123
+| | body | Request body (e.g., for POST/PUT). | | no |
124
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
125
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
126
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
127
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
128
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
129
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
130
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
131
+
132
+
133
+</details>
134
+
135
+
136
+#### via UI
137
+
138
+Configure the **elasticsearch** collector from the Netdata web interface:
139
+
140
+1. Go to **Nodes**.
141
+2. Select the node **where you want the elasticsearch data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
142
+3. The **Collectors → Jobs** view opens by default.
143
+4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
144
+5. Click the **+** next to the **elasticsearch** collector to add a new job.
145
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
146
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
147
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
148
+
149
+
150
+#### via File
151
+
152
+The configuration file name for this integration is `go.d/elasticsearch.conf`.
153
+
154
+The file format is YAML. Generally, the structure is:
155
+
156
+```yaml
157
+update_every: 1
158
+autodetection_retry: 0
159
+jobs:
160
+ - name: some_name1
161
+ - name: some_name2
162
+```
163
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
164
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
165
+
166
+```bash
167
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
168
+sudo ./edit-config go.d/elasticsearch.conf
169
+```
170
+
171
+##### Examples
172
+
173
+###### Basic single node mode
174
+
175
+A basic example configuration.
176
+
177
+```yaml
178
+jobs:
179
+ - name: local
180
+ url: http://127.0.0.1:9200
181
+
182
+```
183
+###### Cluster mode
184
+
185
+Cluster mode example configuration.
186
+
187
+<details open><summary>Config</summary>
188
+
189
+```yaml
190
+jobs:
191
+ - name: local
192
+ url: http://127.0.0.1:9200
193
+ cluster_mode: yes
194
+
195
+```
196
+</details>
197
+
198
+###### HTTP authentication
199
+
200
+Basic HTTP authentication.
201
+
202
+<details open><summary>Config</summary>
203
+
204
+```yaml
205
+jobs:
206
+ - name: local
207
+ url: http://127.0.0.1:9200
208
+ username: username
209
+ password: password
210
+
211
+```
212
+</details>
213
+
214
+###### HTTPS with self-signed certificate
215
+
216
+Elasticsearch with enabled HTTPS and self-signed certificate.
217
+
218
+<details open><summary>Config</summary>
219
+
220
+```yaml
221
+jobs:
222
+ - name: local
223
+ url: https://127.0.0.1:9200
224
+ tls_skip_verify: yes
225
+
226
+```
227
+</details>
228
+
229
+###### Multi-instance
230
+
231
+> **Note**: When you define multiple jobs, their names must be unique.
232
+
233
+Collecting metrics from local and remote instances.
234
+
235
+
236
+<details open><summary>Config</summary>
237
+
238
+```yaml
239
+jobs:
240
+ - name: local
241
+ url: http://127.0.0.1:9200
242
+
243
+ - name: remote
244
+ url: http://192.0.2.1:9200
245
+
246
+```
247
+</details>
248
+
249
+
250
+
251
+## Alerts
252
+
253
+
254
+The following alerts are available:
255
+
256
+| Alert name | On metric | Description |
257
+|:------------|:----------|:------------|
258
+| [ elasticsearch_node_indices_search_time_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, queries run slowly. |
259
+| [ elasticsearch_node_indices_search_time_fetch ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, fetches run slowly. |
260
+| [ elasticsearch_cluster_health_status_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is red. |
261
+| [ elasticsearch_cluster_health_status_yellow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is yellow. |
262
+| [ elasticsearch_node_index_health_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_index_health | node index $label:index health status is red. |
263
+
264
+
265
## Metrics
266
267
Metrics grouped by *scope*.
@@ -170,7 +366,7 @@ Metrics:
366
367
368
173
-## Functions
369
+## Live Data
370
371
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
372
@@ -250,202 +446,6 @@ Real-time snapshot of currently executing search tasks across all cluster nodes.
446
447
448
253
-## Alerts
254
-
255
-
256
-The following alerts are available:
257
-
258
-| Alert name | On metric | Description |
259
-|:------------|:----------|:------------|
260
-| [ elasticsearch_node_indices_search_time_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, queries run slowly. |
261
-| [ elasticsearch_node_indices_search_time_fetch ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, fetches run slowly. |
262
-| [ elasticsearch_cluster_health_status_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is red. |
263
-| [ elasticsearch_cluster_health_status_yellow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is yellow. |
264
-| [ elasticsearch_node_index_health_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_index_health | node index $label:index health status is red. |
265
-
266
-
267
-## Setup
268
-
269
-
270
-You can configure the **elasticsearch** collector in two ways:
271
-
272
-| Method | Best for | How to |
273
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
274
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **elasticsearch**, then click **+** to add a job. |
275
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/elasticsearch.conf` and add a job. |
276
-
277
-:::important
278
-
279
-UI configuration requires paid Netdata Cloud plan.
280
-
281
-:::
282
-
283
-
284
-### Prerequisites
285
-
286
-No action required.
287
-
288
-### Configuration
289
-
290
-#### Options
291
-
292
-The following options can be defined globally: update_every, autodetection_retry.
293
-
294
-
295
-<details open><summary>Config options</summary>
296
-
297
-
298
-
299
-| Group | Option | Description | Default | Required |
300
-|:------|:-----|:------------|:--------|:---------:|
301
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
302
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
303
-| **Target** | url | Target endpoint URL. | http://127.0.0.1:9200 | yes |
304
-| | timeout | HTTP request timeout (seconds). | 2 | no |
305
-| **Metrics Selection** | cluster_mode | Collect metrics for all nodes in the cluster (yes) or only the local node (no). | no | no |
306
-| | collect_node_stats | Collect node metrics. | yes | no |
307
-| | collect_cluster_health | Collect cluster health metrics. | yes | no |
308
-| | collect_cluster_stats | Collect cluster stats metrics. | yes | no |
309
-| | collect_indices_stats | Collect index metrics. | no | no |
310
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
311
-| | password | Password for Basic HTTP authentication. | | no |
312
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
313
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
314
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
315
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
316
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
317
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
318
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
319
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
320
-| **Request** | method | HTTP method to use. | GET | no |
321
-| | body | Request body (e.g., for POST/PUT). | | no |
322
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
323
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
324
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
325
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
326
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
327
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
328
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
329
-
330
-
331
-</details>
332
-
333
-
334
-#### via UI
335
-
336
-Configure the **elasticsearch** collector from the Netdata web interface:
337
-
338
-1. Go to **Nodes**.
339
-2. Select the node **where you want the elasticsearch data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
340
-3. The **Collectors → Jobs** view opens by default.
341
-4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
342
-5. Click the **+** next to the **elasticsearch** collector to add a new job.
343
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
344
- - **Test** runs the job with the provided settings and shows whether data can be collected.
345
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
346
-
347
-
348
-#### via File
349
-
350
-The configuration file name for this integration is `go.d/elasticsearch.conf`.
351
-
352
-The file format is YAML. Generally, the structure is:
353
-
354
-```yaml
355
-update_every: 1
356
-autodetection_retry: 0
357
-jobs:
358
- - name: some_name1
359
- - name: some_name2
360
-```
361
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
362
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
363
-
364
-```bash
365
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
366
-sudo ./edit-config go.d/elasticsearch.conf
367
-```
368
-
369
-##### Examples
370
-
371
-###### Basic single node mode
372
-
373
-A basic example configuration.
374
-
375
-```yaml
376
-jobs:
377
- - name: local
378
- url: http://127.0.0.1:9200
379
-
380
-```
381
-###### Cluster mode
382
-
383
-Cluster mode example configuration.
384
-
385
-<details open><summary>Config</summary>
386
-
387
-```yaml
388
-jobs:
389
- - name: local
390
- url: http://127.0.0.1:9200
391
- cluster_mode: yes
392
-
393
-```
394
-</details>
395
-
396
-###### HTTP authentication
397
-
398
-Basic HTTP authentication.
399
-
400
-<details open><summary>Config</summary>
401
-
402
-```yaml
403
-jobs:
404
- - name: local
405
- url: http://127.0.0.1:9200
406
- username: username
407
- password: password
408
-
409
-```
410
-</details>
411
-
412
-###### HTTPS with self-signed certificate
413
-
414
-Elasticsearch with enabled HTTPS and self-signed certificate.
415
-
416
-<details open><summary>Config</summary>
417
-
418
-```yaml
419
-jobs:
420
- - name: local
421
- url: https://127.0.0.1:9200
422
- tls_skip_verify: yes
423
-
424
-```
425
-</details>
426
-
427
-###### Multi-instance
428
-
429
-> **Note**: When you define multiple jobs, their names must be unique.
430
-
431
-Collecting metrics from local and remote instances.
432
-
433
-
434
-<details open><summary>Config</summary>
435
-
436
-```yaml
437
-jobs:
438
- - name: local
439
- url: http://127.0.0.1:9200
440
-
441
- - name: remote
442
- url: http://192.0.2.1:9200
443
-
444
-```
445
-</details>
446
-
447
-
448
-
449
## Troubleshooting
450
451
### Debug Mode
src/go/plugin/go.d/collector/elasticsearch/integrations/opensearch.md
+197
-197
@@ -66,6 +66,202 @@ By default, this collector monitors only the node it is connected to. To monitor
66
67
The default configuration for this integration is not expected to impose a significant performance impact on the system.
68
69
+## Setup
70
+
71
+
72
+You can configure the **elasticsearch** collector in two ways:
73
+
74
+| Method | Best for | How to |
75
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
76
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **elasticsearch**, then click **+** to add a job. |
77
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/elasticsearch.conf` and add a job. |
78
+
79
+:::important
80
+
81
+UI configuration requires paid Netdata Cloud plan.
82
+
83
+:::
84
+
85
+
86
+### Prerequisites
87
+
88
+No action required.
89
+
90
+### Configuration
91
+
92
+#### Options
93
+
94
+The following options can be defined globally: update_every, autodetection_retry.
95
+
96
+
97
+<details open><summary>Config options</summary>
98
+
99
+
100
+
101
+| Group | Option | Description | Default | Required |
102
+|:------|:-----|:------------|:--------|:---------:|
103
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
104
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
105
+| **Target** | url | Target endpoint URL. | http://127.0.0.1:9200 | yes |
106
+| | timeout | HTTP request timeout (seconds). | 2 | no |
107
+| **Metrics Selection** | cluster_mode | Collect metrics for all nodes in the cluster (yes) or only the local node (no). | no | no |
108
+| | collect_node_stats | Collect node metrics. | yes | no |
109
+| | collect_cluster_health | Collect cluster health metrics. | yes | no |
110
+| | collect_cluster_stats | Collect cluster stats metrics. | yes | no |
111
+| | collect_indices_stats | Collect index metrics. | no | no |
112
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
113
+| | password | Password for Basic HTTP authentication. | | no |
114
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
115
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
116
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
117
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
118
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
119
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
120
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
121
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
122
+| **Request** | method | HTTP method to use. | GET | no |
123
+| | body | Request body (e.g., for POST/PUT). | | no |
124
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
125
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
126
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
127
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
128
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
129
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
130
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
131
+
132
+
133
+</details>
134
+
135
+
136
+#### via UI
137
+
138
+Configure the **elasticsearch** collector from the Netdata web interface:
139
+
140
+1. Go to **Nodes**.
141
+2. Select the node **where you want the elasticsearch data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
142
+3. The **Collectors → Jobs** view opens by default.
143
+4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
144
+5. Click the **+** next to the **elasticsearch** collector to add a new job.
145
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
146
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
147
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
148
+
149
+
150
+#### via File
151
+
152
+The configuration file name for this integration is `go.d/elasticsearch.conf`.
153
+
154
+The file format is YAML. Generally, the structure is:
155
+
156
+```yaml
157
+update_every: 1
158
+autodetection_retry: 0
159
+jobs:
160
+ - name: some_name1
161
+ - name: some_name2
162
+```
163
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
164
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
165
+
166
+```bash
167
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
168
+sudo ./edit-config go.d/elasticsearch.conf
169
+```
170
+
171
+##### Examples
172
+
173
+###### Basic single node mode
174
+
175
+A basic example configuration.
176
+
177
+```yaml
178
+jobs:
179
+ - name: local
180
+ url: http://127.0.0.1:9200
181
+
182
+```
183
+###### Cluster mode
184
+
185
+Cluster mode example configuration.
186
+
187
+<details open><summary>Config</summary>
188
+
189
+```yaml
190
+jobs:
191
+ - name: local
192
+ url: http://127.0.0.1:9200
193
+ cluster_mode: yes
194
+
195
+```
196
+</details>
197
+
198
+###### HTTP authentication
199
+
200
+Basic HTTP authentication.
201
+
202
+<details open><summary>Config</summary>
203
+
204
+```yaml
205
+jobs:
206
+ - name: local
207
+ url: http://127.0.0.1:9200
208
+ username: username
209
+ password: password
210
+
211
+```
212
+</details>
213
+
214
+###### HTTPS with self-signed certificate
215
+
216
+Elasticsearch with enabled HTTPS and self-signed certificate.
217
+
218
+<details open><summary>Config</summary>
219
+
220
+```yaml
221
+jobs:
222
+ - name: local
223
+ url: https://127.0.0.1:9200
224
+ tls_skip_verify: yes
225
+
226
+```
227
+</details>
228
+
229
+###### Multi-instance
230
+
231
+> **Note**: When you define multiple jobs, their names must be unique.
232
+
233
+Collecting metrics from local and remote instances.
234
+
235
+
236
+<details open><summary>Config</summary>
237
+
238
+```yaml
239
+jobs:
240
+ - name: local
241
+ url: http://127.0.0.1:9200
242
+
243
+ - name: remote
244
+ url: http://192.0.2.1:9200
245
+
246
+```
247
+</details>
248
+
249
+
250
+
251
+## Alerts
252
+
253
+
254
+The following alerts are available:
255
+
256
+| Alert name | On metric | Description |
257
+|:------------|:----------|:------------|
258
+| [ elasticsearch_node_indices_search_time_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, queries run slowly. |
259
+| [ elasticsearch_node_indices_search_time_fetch ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, fetches run slowly. |
260
+| [ elasticsearch_cluster_health_status_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is red. |
261
+| [ elasticsearch_cluster_health_status_yellow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is yellow. |
262
+| [ elasticsearch_node_index_health_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_index_health | node index $label:index health status is red. |
263
+
264
+
265
## Metrics
266
267
Metrics grouped by *scope*.
@@ -170,7 +366,7 @@ Metrics:
366
367
368
173
-## Functions
369
+## Live Data
370
371
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
372
@@ -250,202 +446,6 @@ Real-time snapshot of currently executing search tasks across all cluster nodes.
446
447
448
253
-## Alerts
254
-
255
-
256
-The following alerts are available:
257
-
258
-| Alert name | On metric | Description |
259
-|:------------|:----------|:------------|
260
-| [ elasticsearch_node_indices_search_time_query ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, queries run slowly. |
261
-| [ elasticsearch_node_indices_search_time_fetch ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_indices_search_time | search performance is degraded, fetches run slowly. |
262
-| [ elasticsearch_cluster_health_status_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is red. |
263
-| [ elasticsearch_cluster_health_status_yellow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.cluster_health_status | cluster health status is yellow. |
264
-| [ elasticsearch_node_index_health_red ](https://github.com/netdata/netdata/blob/master/src/health/health.d/elasticsearch.conf) | elasticsearch.node_index_health | node index $label:index health status is red. |
265
-
266
-
267
-## Setup
268
-
269
-
270
-You can configure the **elasticsearch** collector in two ways:
271
-
272
-| Method | Best for | How to |
273
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
274
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **elasticsearch**, then click **+** to add a job. |
275
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/elasticsearch.conf` and add a job. |
276
-
277
-:::important
278
-
279
-UI configuration requires paid Netdata Cloud plan.
280
-
281
-:::
282
-
283
-
284
-### Prerequisites
285
-
286
-No action required.
287
-
288
-### Configuration
289
-
290
-#### Options
291
-
292
-The following options can be defined globally: update_every, autodetection_retry.
293
-
294
-
295
-<details open><summary>Config options</summary>
296
-
297
-
298
-
299
-| Group | Option | Description | Default | Required |
300
-|:------|:-----|:------------|:--------|:---------:|
301
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
302
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
303
-| **Target** | url | Target endpoint URL. | http://127.0.0.1:9200 | yes |
304
-| | timeout | HTTP request timeout (seconds). | 2 | no |
305
-| **Metrics Selection** | cluster_mode | Collect metrics for all nodes in the cluster (yes) or only the local node (no). | no | no |
306
-| | collect_node_stats | Collect node metrics. | yes | no |
307
-| | collect_cluster_health | Collect cluster health metrics. | yes | no |
308
-| | collect_cluster_stats | Collect cluster stats metrics. | yes | no |
309
-| | collect_indices_stats | Collect index metrics. | no | no |
310
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
311
-| | password | Password for Basic HTTP authentication. | | no |
312
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
313
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
314
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
315
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
316
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
317
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
318
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
319
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
320
-| **Request** | method | HTTP method to use. | GET | no |
321
-| | body | Request body (e.g., for POST/PUT). | | no |
322
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
323
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
324
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
325
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
326
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
327
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
328
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
329
-
330
-
331
-</details>
332
-
333
-
334
-#### via UI
335
-
336
-Configure the **elasticsearch** collector from the Netdata web interface:
337
-
338
-1. Go to **Nodes**.
339
-2. Select the node **where you want the elasticsearch data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
340
-3. The **Collectors → Jobs** view opens by default.
341
-4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
342
-5. Click the **+** next to the **elasticsearch** collector to add a new job.
343
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
344
- - **Test** runs the job with the provided settings and shows whether data can be collected.
345
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
346
-
347
-
348
-#### via File
349
-
350
-The configuration file name for this integration is `go.d/elasticsearch.conf`.
351
-
352
-The file format is YAML. Generally, the structure is:
353
-
354
-```yaml
355
-update_every: 1
356
-autodetection_retry: 0
357
-jobs:
358
- - name: some_name1
359
- - name: some_name2
360
-```
361
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
362
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
363
-
364
-```bash
365
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
366
-sudo ./edit-config go.d/elasticsearch.conf
367
-```
368
-
369
-##### Examples
370
-
371
-###### Basic single node mode
372
-
373
-A basic example configuration.
374
-
375
-```yaml
376
-jobs:
377
- - name: local
378
- url: http://127.0.0.1:9200
379
-
380
-```
381
-###### Cluster mode
382
-
383
-Cluster mode example configuration.
384
-
385
-<details open><summary>Config</summary>
386
-
387
-```yaml
388
-jobs:
389
- - name: local
390
- url: http://127.0.0.1:9200
391
- cluster_mode: yes
392
-
393
-```
394
-</details>
395
-
396
-###### HTTP authentication
397
-
398
-Basic HTTP authentication.
399
-
400
-<details open><summary>Config</summary>
401
-
402
-```yaml
403
-jobs:
404
- - name: local
405
- url: http://127.0.0.1:9200
406
- username: username
407
- password: password
408
-
409
-```
410
-</details>
411
-
412
-###### HTTPS with self-signed certificate
413
-
414
-Elasticsearch with enabled HTTPS and self-signed certificate.
415
-
416
-<details open><summary>Config</summary>
417
-
418
-```yaml
419
-jobs:
420
- - name: local
421
- url: https://127.0.0.1:9200
422
- tls_skip_verify: yes
423
-
424
-```
425
-</details>
426
-
427
-###### Multi-instance
428
-
429
-> **Note**: When you define multiple jobs, their names must be unique.
430
-
431
-Collecting metrics from local and remote instances.
432
-
433
-
434
-<details open><summary>Config</summary>
435
-
436
-```yaml
437
-jobs:
438
- - name: local
439
- url: http://127.0.0.1:9200
440
-
441
- - name: remote
442
- url: http://192.0.2.1:9200
443
-
444
-```
445
-</details>
446
-
447
-
448
-
449
## Troubleshooting
450
451
### Debug Mode
src/go/plugin/go.d/collector/envoy/integrations/envoy.md
+80
-80
@@ -50,86 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Envoy instance
62
-
63
-Envoy exposes metrics in Prometheus format. All metric labels are added to charts.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| envoy.server_state | live, draining, pre_initializing, initializing | state |
72
-| envoy.server_connections_count | connections | connections |
73
-| envoy.server_parent_connections_count | connections | connections |
74
-| envoy.server_memory_allocated_size | allocated | bytes |
75
-| envoy.server_memory_heap_size | heap | bytes |
76
-| envoy.server_memory_physical_size | physical | bytes |
77
-| envoy.server_uptime | uptime | seconds |
78
-| envoy.cluster_manager_cluster_count | active, not_active | clusters |
79
-| envoy.cluster_manager_cluster_changes_rate | added, modified, removed | clusters/s |
80
-| envoy.cluster_manager_cluster_updates_rate | cluster | updates/s |
81
-| envoy.cluster_manager_cluster_updated_via_merge_rate | via_merge | updates/s |
82
-| envoy.cluster_manager_update_merge_cancelled_rate | merge_cancelled | updates/s |
83
-| envoy.cluster_manager_update_out_of_merge_window_rate | out_of_merge_window | updates/s |
84
-| envoy.cluster_membership_endpoints_count | healthy, degraded, excluded | endpoints |
85
-| envoy.cluster_membership_changes_rate | membership | changes/s |
86
-| envoy.cluster_membership_updates_rate | success, failure, empty, no_rebuild | updates/s |
87
-| envoy.cluster_upstream_cx_active_count | active | connections |
88
-| envoy.cluster_upstream_cx_rate | created | connections/s |
89
-| envoy.cluster_upstream_cx_http_rate | http1, http2, http3 | connections/s |
90
-| envoy.cluster_upstream_cx_destroy_rate | local, remote | connections/s |
91
-| envoy.cluster_upstream_cx_connect_fail_rate | failed | connections/s |
92
-| envoy.cluster_upstream_cx_connect_timeout_rate | timeout | connections/s |
93
-| envoy.cluster_upstream_cx_bytes_rate | received, sent | bytes/s |
94
-| envoy.cluster_upstream_cx_bytes_buffered_size | received, send | bytes |
95
-| envoy.cluster_upstream_rq_active_count | active | requests |
96
-| envoy.cluster_upstream_rq_rate | requests | requests/s |
97
-| envoy.cluster_upstream_rq_failed_rate | cancelled, maintenance_mode, timeout, max_duration_reached, per_try_timeout, reset_local, reset_remote | requests/s |
98
-| envoy.cluster_upstream_rq_pending_active_count | active_pending | requests |
99
-| envoy.cluster_upstream_rq_pending_rate | pending | requests/s |
100
-| envoy.cluster_upstream_rq_pending_failed_rate | overflow, failure_eject | requests/s |
101
-| envoy.cluster_upstream_rq_retry_rate | request | retries/s |
102
-| envoy.cluster_upstream_rq_retry_success_rate | success | retries/s |
103
-| envoy.cluster_upstream_rq_retry_backoff_rate | exponential, ratelimited | retries/s |
104
-| envoy.listener_manager_listeners_count | active, warming, draining | listeners |
105
-| envoy.listener_manager_listener_changes_rate | added, modified, removed, stopped | listeners/s |
106
-| envoy.listener_manager_listener_object_events_rate | create_success, create_failure, in_place_updated | objects/s |
107
-| envoy.listener_admin_downstream_cx_active_count | active | connections |
108
-| envoy.listener_admin_downstream_cx_rate | created | connections/s |
109
-| envoy.listener_admin_downstream_cx_destroy_rate | destroyed | connections/s |
110
-| envoy.listener_admin_downstream_cx_transport_socket_connect_timeout_rate | timeout | connections/s |
111
-| envoy.listener_admin_downstream_cx_rejected_rate | overflow, overload, global_overflow | connections/s |
112
-| envoy.listener_admin_downstream_listener_filter_remote_close_rate | closed | connections/s |
113
-| envoy.listener_admin_downstream_listener_filter_error_rate | read | errors/s |
114
-| envoy.listener_admin_downstream_pre_cx_active_count | active | sockets |
115
-| envoy.listener_admin_downstream_pre_cx_timeout_rate | timeout | sockets/s |
116
-| envoy.listener_downstream_cx_active_count | active | connections |
117
-| envoy.listener_downstream_cx_rate | created | connections/s |
118
-| envoy.listener_downstream_cx_destroy_rate | destroyed | connections/s |
119
-| envoy.listener_downstream_cx_transport_socket_connect_timeout_rate | timeout | connections/s |
120
-| envoy.listener_downstream_cx_rejected_rate | overflow, overload, global_overflow | connections/s |
121
-| envoy.listener_downstream_listener_filter_remote_close_rate | closed | connections/s |
122
-| envoy.listener_downstream_listener_filter_error_rate | read | errors/s |
123
-| envoy.listener_downstream_pre_cx_active_count | active | sockets |
124
-| envoy.listener_downstream_pre_cx_timeout_rate | timeout | sockets/s |
125
-
126
-
127
-
128
-## Alerts
129
-
130
-There are no alerts configured by default for this integration.
131
-
132
-
53
## Setup
54
55
@@ -290,6 +210,86 @@ jobs:
210
211
212
213
+## Alerts
214
+
215
+There are no alerts configured by default for this integration.
216
+
217
+
218
+## Metrics
219
+
220
+Metrics grouped by *scope*.
221
+
222
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
223
+
224
+
225
+
226
+### Per Envoy instance
227
+
228
+Envoy exposes metrics in Prometheus format. All metric labels are added to charts.
229
+
230
+This scope has no labels.
231
+
232
+Metrics:
233
+
234
+| Metric | Dimensions | Unit |
235
+|:------|:----------|:----|
236
+| envoy.server_state | live, draining, pre_initializing, initializing | state |
237
+| envoy.server_connections_count | connections | connections |
238
+| envoy.server_parent_connections_count | connections | connections |
239
+| envoy.server_memory_allocated_size | allocated | bytes |
240
+| envoy.server_memory_heap_size | heap | bytes |
241
+| envoy.server_memory_physical_size | physical | bytes |
242
+| envoy.server_uptime | uptime | seconds |
243
+| envoy.cluster_manager_cluster_count | active, not_active | clusters |
244
+| envoy.cluster_manager_cluster_changes_rate | added, modified, removed | clusters/s |
245
+| envoy.cluster_manager_cluster_updates_rate | cluster | updates/s |
246
+| envoy.cluster_manager_cluster_updated_via_merge_rate | via_merge | updates/s |
247
+| envoy.cluster_manager_update_merge_cancelled_rate | merge_cancelled | updates/s |
248
+| envoy.cluster_manager_update_out_of_merge_window_rate | out_of_merge_window | updates/s |
249
+| envoy.cluster_membership_endpoints_count | healthy, degraded, excluded | endpoints |
250
+| envoy.cluster_membership_changes_rate | membership | changes/s |
251
+| envoy.cluster_membership_updates_rate | success, failure, empty, no_rebuild | updates/s |
252
+| envoy.cluster_upstream_cx_active_count | active | connections |
253
+| envoy.cluster_upstream_cx_rate | created | connections/s |
254
+| envoy.cluster_upstream_cx_http_rate | http1, http2, http3 | connections/s |
255
+| envoy.cluster_upstream_cx_destroy_rate | local, remote | connections/s |
256
+| envoy.cluster_upstream_cx_connect_fail_rate | failed | connections/s |
257
+| envoy.cluster_upstream_cx_connect_timeout_rate | timeout | connections/s |
258
+| envoy.cluster_upstream_cx_bytes_rate | received, sent | bytes/s |
259
+| envoy.cluster_upstream_cx_bytes_buffered_size | received, send | bytes |
260
+| envoy.cluster_upstream_rq_active_count | active | requests |
261
+| envoy.cluster_upstream_rq_rate | requests | requests/s |
262
+| envoy.cluster_upstream_rq_failed_rate | cancelled, maintenance_mode, timeout, max_duration_reached, per_try_timeout, reset_local, reset_remote | requests/s |
263
+| envoy.cluster_upstream_rq_pending_active_count | active_pending | requests |
264
+| envoy.cluster_upstream_rq_pending_rate | pending | requests/s |
265
+| envoy.cluster_upstream_rq_pending_failed_rate | overflow, failure_eject | requests/s |
266
+| envoy.cluster_upstream_rq_retry_rate | request | retries/s |
267
+| envoy.cluster_upstream_rq_retry_success_rate | success | retries/s |
268
+| envoy.cluster_upstream_rq_retry_backoff_rate | exponential, ratelimited | retries/s |
269
+| envoy.listener_manager_listeners_count | active, warming, draining | listeners |
270
+| envoy.listener_manager_listener_changes_rate | added, modified, removed, stopped | listeners/s |
271
+| envoy.listener_manager_listener_object_events_rate | create_success, create_failure, in_place_updated | objects/s |
272
+| envoy.listener_admin_downstream_cx_active_count | active | connections |
273
+| envoy.listener_admin_downstream_cx_rate | created | connections/s |
274
+| envoy.listener_admin_downstream_cx_destroy_rate | destroyed | connections/s |
275
+| envoy.listener_admin_downstream_cx_transport_socket_connect_timeout_rate | timeout | connections/s |
276
+| envoy.listener_admin_downstream_cx_rejected_rate | overflow, overload, global_overflow | connections/s |
277
+| envoy.listener_admin_downstream_listener_filter_remote_close_rate | closed | connections/s |
278
+| envoy.listener_admin_downstream_listener_filter_error_rate | read | errors/s |
279
+| envoy.listener_admin_downstream_pre_cx_active_count | active | sockets |
280
+| envoy.listener_admin_downstream_pre_cx_timeout_rate | timeout | sockets/s |
281
+| envoy.listener_downstream_cx_active_count | active | connections |
282
+| envoy.listener_downstream_cx_rate | created | connections/s |
283
+| envoy.listener_downstream_cx_destroy_rate | destroyed | connections/s |
284
+| envoy.listener_downstream_cx_transport_socket_connect_timeout_rate | timeout | connections/s |
285
+| envoy.listener_downstream_cx_rejected_rate | overflow, overload, global_overflow | connections/s |
286
+| envoy.listener_downstream_listener_filter_remote_close_rate | closed | connections/s |
287
+| envoy.listener_downstream_listener_filter_error_rate | read | errors/s |
288
+| envoy.listener_downstream_pre_cx_active_count | active | sockets |
289
+| envoy.listener_downstream_pre_cx_timeout_rate | timeout | sockets/s |
290
+
291
+
292
+
293
## Troubleshooting
294
295
### Debug Mode
src/go/plugin/go.d/collector/ethtool/integrations/optical_modules.md
+35
-35
@@ -47,41 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per Optical Transceiver Module
59
-
60
-Metrics collected from optical transceiver modules that support Digital Diagnostic Monitoring (DDM).
61
-
62
-Labels:
63
-
64
-| Label | Description |
65
-|:-----------|:----------------|
66
-| iface | Network interface name where the optical transceiver module is installed. |
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| ethtool.optical_module_receiver_signal_power | rx_power | dBm |
73
-| ethtool.optical_module_laser_output_power | tx_power | dBm |
74
-| ethtool.optical_module_laser_bias_current | bias_current | mA |
75
-| ethtool.optical_module_temperature | temperature | Celsius |
76
-| ethtool.optical_module_voltage | voltage | Volts |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-There are no alerts configured by default for this integration.
83
-
84
-
50
## Setup
51
52
@@ -178,6 +143,41 @@ jobs:
143
144
145
146
+## Alerts
147
+
148
+There are no alerts configured by default for this integration.
149
+
150
+
151
+## Metrics
152
+
153
+Metrics grouped by *scope*.
154
+
155
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
156
+
157
+
158
+
159
+### Per Optical Transceiver Module
160
+
161
+Metrics collected from optical transceiver modules that support Digital Diagnostic Monitoring (DDM).
162
+
163
+Labels:
164
+
165
+| Label | Description |
166
+|:-----------|:----------------|
167
+| iface | Network interface name where the optical transceiver module is installed. |
168
+
169
+Metrics:
170
+
171
+| Metric | Dimensions | Unit |
172
+|:------|:----------|:----|
173
+| ethtool.optical_module_receiver_signal_power | rx_power | dBm |
174
+| ethtool.optical_module_laser_output_power | tx_power | dBm |
175
+| ethtool.optical_module_laser_bias_current | bias_current | mA |
176
+| ethtool.optical_module_temperature | temperature | Celsius |
177
+| ethtool.optical_module_voltage | voltage | Volts |
178
+
179
+
180
+
181
## Troubleshooting
182
183
### Debug Mode
src/go/plugin/go.d/collector/exim/integrations/exim.md
+27
-27
@@ -47,33 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per Exim instance
59
-
60
-These metrics refer to the the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| exim.qemails | emails | emails |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
50
## Setup
51
52
@@ -168,6 +141,33 @@ jobs:
141
142
143
144
+## Alerts
145
+
146
+There are no alerts configured by default for this integration.
147
+
148
+
149
+## Metrics
150
+
151
+Metrics grouped by *scope*.
152
+
153
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
154
+
155
+
156
+
157
+### Per Exim instance
158
+
159
+These metrics refer to the the entire monitored application.
160
+
161
+This scope has no labels.
162
+
163
+Metrics:
164
+
165
+| Metric | Dimensions | Unit |
166
+|:------|:----------|:----|
167
+| exim.qemails | emails | emails |
168
+
169
+
170
+
171
## Troubleshooting
172
173
### Debug Mode
src/go/plugin/go.d/collector/fail2ban/integrations/fail2ban.md
+32
-32
@@ -47,38 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per jail
59
-
60
-These metrics refer to the Jail.
61
-
62
-Labels:
63
-
64
-| Label | Description |
65
-|:-----------|:----------------|
66
-| jail | Jail's name |
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| fail2ban.jail_banned_ips | banned | addresses |
73
-| fail2ban.jail_active_failures | active_failures | failures |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
50
## Setup
51
52
@@ -183,6 +151,38 @@ jobs:
151
152
153
154
+## Alerts
155
+
156
+There are no alerts configured by default for this integration.
157
+
158
+
159
+## Metrics
160
+
161
+Metrics grouped by *scope*.
162
+
163
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
164
+
165
+
166
+
167
+### Per jail
168
+
169
+These metrics refer to the Jail.
170
+
171
+Labels:
172
+
173
+| Label | Description |
174
+|:-----------|:----------------|
175
+| jail | Jail's name |
176
+
177
+Metrics:
178
+
179
+| Metric | Dimensions | Unit |
180
+|:------|:----------|:----|
181
+| fail2ban.jail_banned_ips | banned | addresses |
182
+| fail2ban.jail_active_failures | active_failures | failures |
183
+
184
+
185
+
186
## Troubleshooting
187
188
### Debug Mode
src/go/plugin/go.d/collector/filecheck/integrations/files_and_directories.md
+52
-52
@@ -47,58 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per file
59
-
60
-These metrics refer to the File.
61
-
62
-Labels:
63
-
64
-| Label | Description |
65
-|:-----------|:----------------|
66
-| file_path | File absolute path |
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| filecheck.file_existence_status | exist, not_exist | status |
73
-| filecheck.file_modification_time_ago | mtime_ago | seconds |
74
-| filecheck.file_size_bytes | size | bytes |
75
-
76
-### Per directory
77
-
78
-These metrics refer to the Directory.
79
-
80
-Labels:
81
-
82
-| Label | Description |
83
-|:-----------|:----------------|
84
-| dir_path | Directory absolute path |
85
-
86
-Metrics:
87
-
88
-| Metric | Dimensions | Unit |
89
-|:------|:----------|:----|
90
-| filecheck.dir_existence_status | exist, not_exist | status |
91
-| filecheck.dir_modification_time_ago | mtime_ago | seconds |
92
-| filecheck.dir_size_bytes | size | bytes |
93
-| filecheck.dir_files count | files | files |
94
-
95
-
96
-
97
-## Alerts
98
-
99
-There are no alerts configured by default for this integration.
100
-
101
-
50
## Setup
51
52
@@ -259,6 +207,58 @@ jobs:
207
208
209
210
+## Alerts
211
+
212
+There are no alerts configured by default for this integration.
213
+
214
+
215
+## Metrics
216
+
217
+Metrics grouped by *scope*.
218
+
219
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
220
+
221
+
222
+
223
+### Per file
224
+
225
+These metrics refer to the File.
226
+
227
+Labels:
228
+
229
+| Label | Description |
230
+|:-----------|:----------------|
231
+| file_path | File absolute path |
232
+
233
+Metrics:
234
+
235
+| Metric | Dimensions | Unit |
236
+|:------|:----------|:----|
237
+| filecheck.file_existence_status | exist, not_exist | status |
238
+| filecheck.file_modification_time_ago | mtime_ago | seconds |
239
+| filecheck.file_size_bytes | size | bytes |
240
+
241
+### Per directory
242
+
243
+These metrics refer to the Directory.
244
+
245
+Labels:
246
+
247
+| Label | Description |
248
+|:-----------|:----------------|
249
+| dir_path | Directory absolute path |
250
+
251
+Metrics:
252
+
253
+| Metric | Dimensions | Unit |
254
+|:------|:----------|:----|
255
+| filecheck.dir_existence_status | exist, not_exist | status |
256
+| filecheck.dir_modification_time_ago | mtime_ago | seconds |
257
+| filecheck.dir_size_bytes | size | bytes |
258
+| filecheck.dir_files count | files | files |
259
+
260
+
261
+
262
## Troubleshooting
263
264
### Debug Mode
src/go/plugin/go.d/collector/fluentd/integrations/fluentd.md
+29
-29
@@ -45,35 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Fluentd instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| fluentd.retry_count | a dimension per plugin | count |
67
-| fluentd.buffer_queue_length | a dimension per plugin | queue_length |
68
-| fluentd.buffer_total_queued_size | a dimension per plugin | queued_size |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
48
## Setup
49
50
@@ -237,6 +208,35 @@ jobs:
208
209
210
211
+## Alerts
212
+
213
+There are no alerts configured by default for this integration.
214
+
215
+
216
+## Metrics
217
+
218
+Metrics grouped by *scope*.
219
+
220
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
221
+
222
+
223
+
224
+### Per Fluentd instance
225
+
226
+These metrics refer to the entire monitored application.
227
+
228
+This scope has no labels.
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| fluentd.retry_count | a dimension per plugin | count |
235
+| fluentd.buffer_queue_length | a dimension per plugin | queue_length |
236
+| fluentd.buffer_total_queued_size | a dimension per plugin | queued_size |
237
+
238
+
239
+
240
## Troubleshooting
241
242
### Debug Mode
src/go/plugin/go.d/collector/freeradius/integrations/freeradius.md
+36
-36
@@ -48,42 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per FreeRADIUS instance
60
-
61
-These metrics refer to the entire monitored application.
62
-
63
-This scope has no labels.
64
-
65
-Metrics:
66
-
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| freeradius.authentication | requests, responses | packets/s |
70
-| freeradius.authentication_access_responses | accepts, rejects, challenges | packets/s |
71
-| freeradius.bad_authentication | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
72
-| freeradius.proxy_authentication | requests, responses | packets/s |
73
-| freeradius.proxy_authentication_access_responses | accepts, rejects, challenges | packets/s |
74
-| freeradius.proxy_bad_authentication | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
75
-| freeradius.accounting | requests, responses | packets/s |
76
-| freeradius.bad_accounting | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
77
-| freeradius.proxy_accounting | requests, responses | packets/s |
78
-| freeradius.proxy_bad_accounting | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
79
-
80
-
81
-
82
-## Alerts
83
-
84
-There are no alerts configured by default for this integration.
85
-
86
-
51
## Setup
52
53
@@ -213,6 +177,42 @@ jobs:
177
178
179
180
+## Alerts
181
+
182
+There are no alerts configured by default for this integration.
183
+
184
+
185
+## Metrics
186
+
187
+Metrics grouped by *scope*.
188
+
189
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
190
+
191
+
192
+
193
+### Per FreeRADIUS instance
194
+
195
+These metrics refer to the entire monitored application.
196
+
197
+This scope has no labels.
198
+
199
+Metrics:
200
+
201
+| Metric | Dimensions | Unit |
202
+|:------|:----------|:----|
203
+| freeradius.authentication | requests, responses | packets/s |
204
+| freeradius.authentication_access_responses | accepts, rejects, challenges | packets/s |
205
+| freeradius.bad_authentication | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
206
+| freeradius.proxy_authentication | requests, responses | packets/s |
207
+| freeradius.proxy_authentication_access_responses | accepts, rejects, challenges | packets/s |
208
+| freeradius.proxy_bad_authentication | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
209
+| freeradius.accounting | requests, responses | packets/s |
210
+| freeradius.bad_accounting | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
211
+| freeradius.proxy_accounting | requests, responses | packets/s |
212
+| freeradius.proxy_bad_accounting | dropped, duplicate, invalid, malformed, unknown-types | packets/s |
213
+
214
+
215
+
216
## Troubleshooting
217
218
### Debug Mode
src/go/plugin/go.d/collector/gearman/integrations/gearman.md
+46
-46
@@ -50,52 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Gearman instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| gearman.queued_jobs_activity | running, waiting | jobs |
72
-| gearman.queued_jobs_priority | high, normal, low | jobs |
73
-
74
-### Per Gearman instance
75
-
76
-These metrics refer to the Function (task).
77
-
78
-Labels:
79
-
80
-| Label | Description |
81
-|:-----------|:----------------|
82
-| function_name | Function name. |
83
-
84
-Metrics:
85
-
86
-| Metric | Dimensions | Unit |
87
-|:------|:----------|:----|
88
-| gearman.function_queued_jobs_activity | running, waiting | jobs |
89
-| gearman.function_queued_jobs_priority | high, normal, low | jobs |
90
-| gearman.function_workers | available | workers |
91
-
92
-
93
-
94
-## Alerts
95
-
96
-There are no alerts configured by default for this integration.
97
-
98
-
53
## Setup
54
55
@@ -213,6 +167,52 @@ jobs:
167
168
169
170
+## Alerts
171
+
172
+There are no alerts configured by default for this integration.
173
+
174
+
175
+## Metrics
176
+
177
+Metrics grouped by *scope*.
178
+
179
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
180
+
181
+
182
+
183
+### Per Gearman instance
184
+
185
+These metrics refer to the entire monitored application.
186
+
187
+This scope has no labels.
188
+
189
+Metrics:
190
+
191
+| Metric | Dimensions | Unit |
192
+|:------|:----------|:----|
193
+| gearman.queued_jobs_activity | running, waiting | jobs |
194
+| gearman.queued_jobs_priority | high, normal, low | jobs |
195
+
196
+### Per Gearman instance
197
+
198
+These metrics refer to the Function (task).
199
+
200
+Labels:
201
+
202
+| Label | Description |
203
+|:-----------|:----------------|
204
+| function_name | Function name. |
205
+
206
+Metrics:
207
+
208
+| Metric | Dimensions | Unit |
209
+|:------|:----------|:----|
210
+| gearman.function_queued_jobs_activity | running, waiting | jobs |
211
+| gearman.function_queued_jobs_priority | high, normal, low | jobs |
212
+| gearman.function_workers | available | workers |
213
+
214
+
215
+
216
## Troubleshooting
217
218
### Debug Mode
src/go/plugin/go.d/collector/geth/integrations/go-ethereum.md
+42
-42
@@ -50,48 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Go-ethereum instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| geth.eth_db_chaindata_ancient_io_rate | reads, writes | bytes/s |
72
-| geth.eth_db_chaindata_ancient_io | reads, writes | bytes |
73
-| geth.eth_db_chaindata_disk_io | reads, writes | bytes |
74
-| geth.goroutines | goroutines | goroutines |
75
-| geth.eth_db_chaindata_disk_io_rate | reads, writes | bytes/s |
76
-| geth.chaindata_db_size | level_db, ancient_db | bytes |
77
-| geth.chainhead | block, receipt, header | block |
78
-| geth.tx_pool_pending | invalid, pending, local, discard, no_funds, ratelimit, replace | transactions |
79
-| geth.tx_pool_current | invalid, pending, local, pool | transactions |
80
-| geth.tx_pool_queued | discard, eviction, no_funds, ratelimit | transactions |
81
-| geth.p2p_bandwidth | ingress, egress | bytes/s |
82
-| geth.reorgs | executed | reorgs |
83
-| geth.reorgs_blocks | added, dropped | blocks |
84
-| geth.p2p_peers | peers | peers |
85
-| geth.p2p_peers_calls | dials, serves | calls/s |
86
-| geth.rpc_calls | failed, successful | calls/s |
87
-
88
-
89
-
90
-## Alerts
91
-
92
-There are no alerts configured by default for this integration.
93
-
94
-
53
## Setup
54
55
@@ -233,6 +191,48 @@ jobs:
191
192
193
194
+## Alerts
195
+
196
+There are no alerts configured by default for this integration.
197
+
198
+
199
+## Metrics
200
+
201
+Metrics grouped by *scope*.
202
+
203
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
204
+
205
+
206
+
207
+### Per Go-ethereum instance
208
+
209
+These metrics refer to the entire monitored application.
210
+
211
+This scope has no labels.
212
+
213
+Metrics:
214
+
215
+| Metric | Dimensions | Unit |
216
+|:------|:----------|:----|
217
+| geth.eth_db_chaindata_ancient_io_rate | reads, writes | bytes/s |
218
+| geth.eth_db_chaindata_ancient_io | reads, writes | bytes |
219
+| geth.eth_db_chaindata_disk_io | reads, writes | bytes |
220
+| geth.goroutines | goroutines | goroutines |
221
+| geth.eth_db_chaindata_disk_io_rate | reads, writes | bytes/s |
222
+| geth.chaindata_db_size | level_db, ancient_db | bytes |
223
+| geth.chainhead | block, receipt, header | block |
224
+| geth.tx_pool_pending | invalid, pending, local, discard, no_funds, ratelimit, replace | transactions |
225
+| geth.tx_pool_current | invalid, pending, local, pool | transactions |
226
+| geth.tx_pool_queued | discard, eviction, no_funds, ratelimit | transactions |
227
+| geth.p2p_bandwidth | ingress, egress | bytes/s |
228
+| geth.reorgs | executed | reorgs |
229
+| geth.reorgs_blocks | added, dropped | blocks |
230
+| geth.p2p_peers | peers | peers |
231
+| geth.p2p_peers_calls | dials, serves | calls/s |
232
+| geth.rpc_calls | failed, successful | calls/s |
233
+
234
+
235
+
236
## Troubleshooting
237
238
### Debug Mode
src/go/plugin/go.d/collector/haproxy/integrations/haproxy.md
+44
-44
@@ -45,50 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per HAProxy instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| haproxy.backend_current_sessions | a dimension per proxy | sessions |
67
-| haproxy.backend_sessions | a dimension per proxy | sessions/s |
68
-| haproxy.backend_response_time_average | a dimension per proxy | milliseconds |
69
-| haproxy.backend_queue_time_average | a dimension per proxy | milliseconds |
70
-| haproxy.backend_current_queue | a dimension per proxy | requests |
71
-
72
-### Per proxy
73
-
74
-These metrics refer to the Proxy.
75
-
76
-This scope has no labels.
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| haproxy.backend_http_responses | 1xx, 2xx, 3xx, 4xx, 5xx, other | responses/s |
83
-| haproxy.backend_network_io | in, out | bytes/s |
84
-
85
-
86
-
87
-## Alerts
88
-
89
-There are no alerts configured by default for this integration.
90
-
91
-
48
## Setup
49
50
@@ -255,6 +211,50 @@ jobs:
211
212
213
214
+## Alerts
215
+
216
+There are no alerts configured by default for this integration.
217
+
218
+
219
+## Metrics
220
+
221
+Metrics grouped by *scope*.
222
+
223
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
224
+
225
+
226
+
227
+### Per HAProxy instance
228
+
229
+These metrics refer to the entire monitored application.
230
+
231
+This scope has no labels.
232
+
233
+Metrics:
234
+
235
+| Metric | Dimensions | Unit |
236
+|:------|:----------|:----|
237
+| haproxy.backend_current_sessions | a dimension per proxy | sessions |
238
+| haproxy.backend_sessions | a dimension per proxy | sessions/s |
239
+| haproxy.backend_response_time_average | a dimension per proxy | milliseconds |
240
+| haproxy.backend_queue_time_average | a dimension per proxy | milliseconds |
241
+| haproxy.backend_current_queue | a dimension per proxy | requests |
242
+
243
+### Per proxy
244
+
245
+These metrics refer to the Proxy.
246
+
247
+This scope has no labels.
248
+
249
+Metrics:
250
+
251
+| Metric | Dimensions | Unit |
252
+|:------|:----------|:----|
253
+| haproxy.backend_http_responses | 1xx, 2xx, 3xx, 4xx, 5xx, other | responses/s |
254
+| haproxy.backend_network_io | in, out | bytes/s |
255
+
256
+
257
+
258
## Troubleshooting
259
260
### Debug Mode
src/go/plugin/go.d/collector/hddtemp/integrations/hdd_temperature.md
+33
-33
@@ -48,39 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per disk
60
-
61
-These metrics refer to the Disk.
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| disk_id | Disk identifier. It is derived from the device path (e.g. sda or ata-HUP722020APA330_BFJ0WS3F) |
68
-| model | Disk model |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| hddtemp.disk_temperature | temperature | Celsius |
75
-| hddtemp.disk_temperature_sensor_status | ok, err, na, unk, nos, slp | status |
76
-
77
-
78
-
79
-## Alerts
80
-
81
-There are no alerts configured by default for this integration.
82
-
83
-
51
## Setup
52
53
@@ -201,6 +168,39 @@ jobs:
168
169
170
171
+## Alerts
172
+
173
+There are no alerts configured by default for this integration.
174
+
175
+
176
+## Metrics
177
+
178
+Metrics grouped by *scope*.
179
+
180
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
181
+
182
+
183
+
184
+### Per disk
185
+
186
+These metrics refer to the Disk.
187
+
188
+Labels:
189
+
190
+| Label | Description |
191
+|:-----------|:----------------|
192
+| disk_id | Disk identifier. It is derived from the device path (e.g. sda or ata-HUP722020APA330_BFJ0WS3F) |
193
+| model | Disk model |
194
+
195
+Metrics:
196
+
197
+| Metric | Dimensions | Unit |
198
+|:------|:----------|:----|
199
+| hddtemp.disk_temperature | temperature | Celsius |
200
+| hddtemp.disk_temperature_sensor_status | ok, err, na, unk, nos, slp | status |
201
+
202
+
203
+
204
## Troubleshooting
205
206
### Debug Mode
src/go/plugin/go.d/collector/hdfs/integrations/hadoop_distributed_file_system_hdfs.md
+59
-59
@@ -47,65 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per Hadoop Distributed File System (HDFS) instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit | DataNode | NameNode |
67
-|:------|:----------|:----|:---:|:---:|
68
-| hdfs.heap_memory | committed, used | MiB | • | • |
69
-| hdfs.gc_count_total | gc | events/s | • | • |
70
-| hdfs.gc_time_total | ms | ms | • | • |
71
-| hdfs.gc_threshold | info, warn | events/s | • | • |
72
-| hdfs.threads | new, runnable, blocked, waiting, timed_waiting, terminated | num | • | • |
73
-| hdfs.logs_total | info, error, warn, fatal | logs/s | • | • |
74
-| hdfs.rpc_bandwidth | received, sent | kilobits/s | • | • |
75
-| hdfs.rpc_calls | calls | calls/s | • | • |
76
-| hdfs.open_connections | open | connections | • | • |
77
-| hdfs.call_queue_length | length | num | • | • |
78
-| hdfs.avg_queue_time | time | ms | • | • |
79
-| hdfs.avg_processing_time | time | ms | • | • |
80
-| hdfs.capacity | remaining, used | KiB | | • |
81
-| hdfs.used_capacity | dfs, non_dfs | KiB | | • |
82
-| hdfs.load | load | load | | • |
83
-| hdfs.volume_failures_total | failures | events/s | | • |
84
-| hdfs.files_total | files | num | | • |
85
-| hdfs.blocks_total | blocks | num | | • |
86
-| hdfs.blocks | corrupt, missing, under_replicated | num | | • |
87
-| hdfs.data_nodes | live, dead, stale | num | | • |
88
-| hdfs.datanode_capacity | remaining, used | KiB | • | |
89
-| hdfs.datanode_used_capacity | dfs, non_dfs | KiB | • | |
90
-| hdfs.datanode_failed_volumes | failed volumes | num | • | |
91
-| hdfs.datanode_bandwidth | reads, writes | KiB/s | • | |
92
-
93
-
94
-
95
-## Alerts
96
-
97
-
98
-The following alerts are available:
99
-
100
-| Alert name | On metric | Description |
101
-|:------------|:----------|:------------|
102
-| [ hdfs_capacity_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.capacity | summary datanodes space capacity utilization |
103
-| [ hdfs_missing_blocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.blocks | number of missing blocks |
104
-| [ hdfs_stale_nodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.data_nodes | number of datanodes marked stale due to delayed heartbeat |
105
-| [ hdfs_dead_nodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.data_nodes | number of datanodes which are currently dead |
106
-| [ hdfs_num_failed_volumes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.num_failed_volumes | number of failed volumes |
107
-
108
-
50
## Setup
51
52
@@ -266,6 +207,65 @@ jobs:
207
208
209
210
+## Alerts
211
+
212
+
213
+The following alerts are available:
214
+
215
+| Alert name | On metric | Description |
216
+|:------------|:----------|:------------|
217
+| [ hdfs_capacity_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.capacity | summary datanodes space capacity utilization |
218
+| [ hdfs_missing_blocks ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.blocks | number of missing blocks |
219
+| [ hdfs_stale_nodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.data_nodes | number of datanodes marked stale due to delayed heartbeat |
220
+| [ hdfs_dead_nodes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.data_nodes | number of datanodes which are currently dead |
221
+| [ hdfs_num_failed_volumes ](https://github.com/netdata/netdata/blob/master/src/health/health.d/hdfs.conf) | hdfs.num_failed_volumes | number of failed volumes |
222
+
223
+
224
+## Metrics
225
+
226
+Metrics grouped by *scope*.
227
+
228
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
229
+
230
+
231
+
232
+### Per Hadoop Distributed File System (HDFS) instance
233
+
234
+These metrics refer to the entire monitored application.
235
+
236
+This scope has no labels.
237
+
238
+Metrics:
239
+
240
+| Metric | Dimensions | Unit | DataNode | NameNode |
241
+|:------|:----------|:----|:---:|:---:|
242
+| hdfs.heap_memory | committed, used | MiB | • | • |
243
+| hdfs.gc_count_total | gc | events/s | • | • |
244
+| hdfs.gc_time_total | ms | ms | • | • |
245
+| hdfs.gc_threshold | info, warn | events/s | • | • |
246
+| hdfs.threads | new, runnable, blocked, waiting, timed_waiting, terminated | num | • | • |
247
+| hdfs.logs_total | info, error, warn, fatal | logs/s | • | • |
248
+| hdfs.rpc_bandwidth | received, sent | kilobits/s | • | • |
249
+| hdfs.rpc_calls | calls | calls/s | • | • |
250
+| hdfs.open_connections | open | connections | • | • |
251
+| hdfs.call_queue_length | length | num | • | • |
252
+| hdfs.avg_queue_time | time | ms | • | • |
253
+| hdfs.avg_processing_time | time | ms | • | • |
254
+| hdfs.capacity | remaining, used | KiB | | • |
255
+| hdfs.used_capacity | dfs, non_dfs | KiB | | • |
256
+| hdfs.load | load | load | | • |
257
+| hdfs.volume_failures_total | failures | events/s | | • |
258
+| hdfs.files_total | files | num | | • |
259
+| hdfs.blocks_total | blocks | num | | • |
260
+| hdfs.blocks | corrupt, missing, under_replicated | num | | • |
261
+| hdfs.data_nodes | live, dead, stale | num | | • |
262
+| hdfs.datanode_capacity | remaining, used | KiB | • | |
263
+| hdfs.datanode_used_capacity | dfs, non_dfs | KiB | • | |
264
+| hdfs.datanode_failed_volumes | failed volumes | num | • | |
265
+| hdfs.datanode_bandwidth | reads, writes | KiB/s | • | |
266
+
267
+
268
+
269
## Troubleshooting
270
271
### Debug Mode
src/go/plugin/go.d/collector/hpssa/integrations/hpe_smart_arrays.md
+99
-99
@@ -51,105 +51,6 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
-## Metrics
55
-
56
-Metrics grouped by *scope*.
57
-
58
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
59
-
60
-
61
-
62
-### Per controller
63
-
64
-These metrics refer to the Controller.
65
-
66
-Labels:
67
-
68
-| Label | Description |
69
-|:-----------|:----------------|
70
-| slot | Slot number |
71
-| model | Controller model |
72
-
73
-Metrics:
74
-
75
-| Metric | Dimensions | Unit |
76
-|:------|:----------|:----|
77
-| hpssa.controller_status | ok, nok | status |
78
-| hpssa.controller_temperature | temperature | Celsius |
79
-| hpssa.controller_cache_module_presence_status | present, not_present | status |
80
-| hpssa.controller_cache_module_status | ok, nok | status |
81
-| hpssa.controller_cache_module_temperature | temperature | Celsius |
82
-| hpssa.controller_cache_module_battery_status | ok, nok | status |
83
-
84
-### Per array
85
-
86
-These metrics refer to the Array.
87
-
88
-Labels:
89
-
90
-| Label | Description |
91
-|:-----------|:----------------|
92
-| slot | Slot number |
93
-| array_id | Array id |
94
-| interface_type | Array interface type (e.g. SATA) |
95
-| array_type | Array type (e.g. Data) |
96
-
97
-Metrics:
98
-
99
-| Metric | Dimensions | Unit |
100
-|:------|:----------|:----|
101
-| hpssa.array_status | ok, nok | status |
102
-
103
-### Per logical drive
104
-
105
-These metrics refer to the Logical Drive.
106
-
107
-Labels:
108
-
109
-| Label | Description |
110
-|:-----------|:----------------|
111
-| slot | Slot number |
112
-| array_id | Array id |
113
-| logical_drive_id | Logical Drive id (number) |
114
-| disk_name | Disk name (e.g. /dev/sda) |
115
-| drive_type | Drive type (e.g. Data) |
116
-
117
-Metrics:
118
-
119
-| Metric | Dimensions | Unit |
120
-|:------|:----------|:----|
121
-| hpssa.logical_drive_status | ok, nok | status |
122
-
123
-### Per physical drive
124
-
125
-These metrics refer to the Physical Drive.
126
-
127
-Labels:
128
-
129
-| Label | Description |
130
-|:-----------|:----------------|
131
-| slot | Slot number |
132
-| array_id | Array id or "na" if unassigned |
133
-| logical_drive_id | Logical Drive id or "na" if unassigned |
134
-| location | Drive location in port:box:bay format (e.g. 1I:1:1) |
135
-| interface_type | Drive interface type (e.g. SATA) |
136
-| drive_type | Drive type (e.g. Data Drive, Unassigned Drive) |
137
-| model | Drive model |
138
-
139
-Metrics:
140
-
141
-| Metric | Dimensions | Unit |
142
-|:------|:----------|:----|
143
-| hpssa.physical_drive_status | ok, nok | status |
144
-| hpssa.physical_drive_temperature | temperature | status |
145
-
146
-
147
-
148
-## Alerts
149
-
150
-There are no alerts configured by default for this integration.
151
-
152
-
54
## Setup
55
56
@@ -248,6 +149,105 @@ jobs:
149
150
151
152
+## Alerts
153
+
154
+There are no alerts configured by default for this integration.
155
+
156
+
157
+## Metrics
158
+
159
+Metrics grouped by *scope*.
160
+
161
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
162
+
163
+
164
+
165
+### Per controller
166
+
167
+These metrics refer to the Controller.
168
+
169
+Labels:
170
+
171
+| Label | Description |
172
+|:-----------|:----------------|
173
+| slot | Slot number |
174
+| model | Controller model |
175
+
176
+Metrics:
177
+
178
+| Metric | Dimensions | Unit |
179
+|:------|:----------|:----|
180
+| hpssa.controller_status | ok, nok | status |
181
+| hpssa.controller_temperature | temperature | Celsius |
182
+| hpssa.controller_cache_module_presence_status | present, not_present | status |
183
+| hpssa.controller_cache_module_status | ok, nok | status |
184
+| hpssa.controller_cache_module_temperature | temperature | Celsius |
185
+| hpssa.controller_cache_module_battery_status | ok, nok | status |
186
+
187
+### Per array
188
+
189
+These metrics refer to the Array.
190
+
191
+Labels:
192
+
193
+| Label | Description |
194
+|:-----------|:----------------|
195
+| slot | Slot number |
196
+| array_id | Array id |
197
+| interface_type | Array interface type (e.g. SATA) |
198
+| array_type | Array type (e.g. Data) |
199
+
200
+Metrics:
201
+
202
+| Metric | Dimensions | Unit |
203
+|:------|:----------|:----|
204
+| hpssa.array_status | ok, nok | status |
205
+
206
+### Per logical drive
207
+
208
+These metrics refer to the Logical Drive.
209
+
210
+Labels:
211
+
212
+| Label | Description |
213
+|:-----------|:----------------|
214
+| slot | Slot number |
215
+| array_id | Array id |
216
+| logical_drive_id | Logical Drive id (number) |
217
+| disk_name | Disk name (e.g. /dev/sda) |
218
+| drive_type | Drive type (e.g. Data) |
219
+
220
+Metrics:
221
+
222
+| Metric | Dimensions | Unit |
223
+|:------|:----------|:----|
224
+| hpssa.logical_drive_status | ok, nok | status |
225
+
226
+### Per physical drive
227
+
228
+These metrics refer to the Physical Drive.
229
+
230
+Labels:
231
+
232
+| Label | Description |
233
+|:-----------|:----------------|
234
+| slot | Slot number |
235
+| array_id | Array id or "na" if unassigned |
236
+| logical_drive_id | Logical Drive id or "na" if unassigned |
237
+| location | Drive location in port:box:bay format (e.g. 1I:1:1) |
238
+| interface_type | Drive interface type (e.g. SATA) |
239
+| drive_type | Drive type (e.g. Data Drive, Unassigned Drive) |
240
+| model | Drive model |
241
+
242
+Metrics:
243
+
244
+| Metric | Dimensions | Unit |
245
+|:------|:----------|:----|
246
+| hpssa.physical_drive_status | ok, nok | status |
247
+| hpssa.physical_drive_temperature | temperature | status |
248
+
249
+
250
+
251
## Troubleshooting
252
253
### Debug Mode
src/go/plugin/go.d/collector/httpcheck/integrations/http_endpoints.md
+44
-44
@@ -57,50 +57,6 @@ The default configuration for this integration does not impose any limits on dat
57
58
The default configuration for this integration is not expected to impose a significant performance impact on the system.
59
60
-## Metrics
61
-
62
-Metrics grouped by *scope*.
63
-
64
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
65
-
66
-
67
-
68
-### Per target
69
-
70
-The metrics refer to the monitored target.
71
-
72
-Labels:
73
-
74
-| Label | Description |
75
-|:-----------|:----------------|
76
-| url | url value that is set in the configuration file. |
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| httpcheck.response_time | time | ms |
83
-| httpcheck.response_length | length | characters |
84
-| httpcheck.status | success, timeout, redirect, no_connection, bad_content, bad_header, bad_status | boolean |
85
-| httpcheck.in_state | time | boolean |
86
-
87
-
88
-
89
-## Alerts
90
-
91
-
92
-The following alerts are available:
93
-
94
-| Alert name | On metric | Description |
95
-|:------------|:----------|:------------|
96
-| [ httpcheck_web_service_up ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | HTTP check endpoint ${label:url} liveness status |
97
-| [ httpcheck_web_service_bad_content ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of HTTP responses from ${label:url} with unexpected content in the last 5 minutes |
98
-| [ httpcheck_web_service_bad_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of HTTP responses from ${label:url} with unexpected status in the last 5 minutes |
99
-| [ httpcheck_web_service_bad_header ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of HTTP responses from ${label:url} with unexpected header in the last 5 minutes |
100
-| [ httpcheck_web_service_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of timed-out HTTP requests to ${label:url} in the last 5 minutes |
101
-| [ httpcheck_web_service_no_connection ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of failed HTTP requests to ${label:url} in the last 5 minutes |
102
-
103
-
60
## Setup
61
62
@@ -354,6 +310,50 @@ jobs:
310
311
312
313
+## Alerts
314
+
315
+
316
+The following alerts are available:
317
+
318
+| Alert name | On metric | Description |
319
+|:------------|:----------|:------------|
320
+| [ httpcheck_web_service_up ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | HTTP check endpoint ${label:url} liveness status |
321
+| [ httpcheck_web_service_bad_content ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of HTTP responses from ${label:url} with unexpected content in the last 5 minutes |
322
+| [ httpcheck_web_service_bad_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of HTTP responses from ${label:url} with unexpected status in the last 5 minutes |
323
+| [ httpcheck_web_service_bad_header ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of HTTP responses from ${label:url} with unexpected header in the last 5 minutes |
324
+| [ httpcheck_web_service_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of timed-out HTTP requests to ${label:url} in the last 5 minutes |
325
+| [ httpcheck_web_service_no_connection ](https://github.com/netdata/netdata/blob/master/src/health/health.d/httpcheck.conf) | httpcheck.status | Percentage of failed HTTP requests to ${label:url} in the last 5 minutes |
326
+
327
+
328
+## Metrics
329
+
330
+Metrics grouped by *scope*.
331
+
332
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
333
+
334
+
335
+
336
+### Per target
337
+
338
+The metrics refer to the monitored target.
339
+
340
+Labels:
341
+
342
+| Label | Description |
343
+|:-----------|:----------------|
344
+| url | url value that is set in the configuration file. |
345
+
346
+Metrics:
347
+
348
+| Metric | Dimensions | Unit |
349
+|:------|:----------|:----|
350
+| httpcheck.response_time | time | ms |
351
+| httpcheck.response_length | length | characters |
352
+| httpcheck.status | success, timeout, redirect, no_connection, bad_content, bad_header, bad_status | boolean |
353
+| httpcheck.in_state | time | boolean |
354
+
355
+
356
+
357
## Troubleshooting
358
359
### Debug Mode
src/go/plugin/go.d/collector/icecast/integrations/icecast.md
+31
-31
@@ -44,37 +44,6 @@ The default configuration for this integration does not impose any limits on dat
44
45
The default configuration for this integration is not expected to impose a significant performance impact on the system.
46
47
-## Metrics
48
-
49
-Metrics grouped by *scope*.
50
-
51
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
52
-
53
-
54
-
55
-### Per Icecast source
56
-
57
-These metrics refer to an icecast source.
58
-
59
-Labels:
60
-
61
-| Label | Description |
62
-|:-----------|:----------------|
63
-| source | Source name. |
64
-
65
-Metrics:
66
-
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| icecast.listeners | listeners | listeners |
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
47
## Setup
48
49
@@ -206,6 +175,37 @@ jobs:
175
176
177
178
+## Alerts
179
+
180
+There are no alerts configured by default for this integration.
181
+
182
+
183
+## Metrics
184
+
185
+Metrics grouped by *scope*.
186
+
187
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
188
+
189
+
190
+
191
+### Per Icecast source
192
+
193
+These metrics refer to an icecast source.
194
+
195
+Labels:
196
+
197
+| Label | Description |
198
+|:-----------|:----------------|
199
+| source | Source name. |
200
+
201
+Metrics:
202
+
203
+| Metric | Dimensions | Unit |
204
+|:------|:----------|:----|
205
+| icecast.listeners | listeners | listeners |
206
+
207
+
208
+
209
## Troubleshooting
210
211
### Debug Mode
src/go/plugin/go.d/collector/intelgpu/integrations/intel_gpu.md
+45
-45
@@ -48,51 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per Intel GPU instance
60
-
61
-These metrics refer to the Intel GPU.
62
-
63
-This scope has no labels.
64
-
65
-Metrics:
66
-
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| intelgpu.frequency | frequency | MHz |
70
-| intelgpu.power | gpu, package | Watts |
71
-
72
-### Per engine
73
-
74
-These metrics refer to the GPU hardware engine.
75
-
76
-Labels:
77
-
78
-| Label | Description |
79
-|:-----------|:----------------|
80
-| engine_class | Engine class (Render/3D, Blitter, VideoEnhance, Video, Compute). |
81
-| engine_instance | Engine instance (e.g. Render/3D/0, Video/0, Video/1). |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| intelgpu.engine_busy_perc | busy | percentage |
88
-
89
-
90
-
91
-## Alerts
92
-
93
-There are no alerts configured by default for this integration.
94
-
95
-
51
## Setup
52
53
@@ -190,6 +145,51 @@ jobs:
145
146
147
148
+## Alerts
149
+
150
+There are no alerts configured by default for this integration.
151
+
152
+
153
+## Metrics
154
+
155
+Metrics grouped by *scope*.
156
+
157
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
158
+
159
+
160
+
161
+### Per Intel GPU instance
162
+
163
+These metrics refer to the Intel GPU.
164
+
165
+This scope has no labels.
166
+
167
+Metrics:
168
+
169
+| Metric | Dimensions | Unit |
170
+|:------|:----------|:----|
171
+| intelgpu.frequency | frequency | MHz |
172
+| intelgpu.power | gpu, package | Watts |
173
+
174
+### Per engine
175
+
176
+These metrics refer to the GPU hardware engine.
177
+
178
+Labels:
179
+
180
+| Label | Description |
181
+|:-----------|:----------------|
182
+| engine_class | Engine class (Render/3D, Blitter, VideoEnhance, Video, Compute). |
183
+| engine_instance | Engine instance (e.g. Render/3D/0, Video/0, Video/1). |
184
+
185
+Metrics:
186
+
187
+| Metric | Dimensions | Unit |
188
+|:------|:----------|:----|
189
+| intelgpu.engine_busy_perc | busy | percentage |
190
+
191
+
192
+
193
## Troubleshooting
194
195
### Debug Mode
src/go/plugin/go.d/collector/ipfs/integrations/ipfs.md
+37
-37
@@ -59,43 +59,6 @@ Calls to the following endpoints are disabled by default due to IPFS bugs:
59
**Disabled by default** due to potential high CPU usage. Consider enabling only if necessary.
60
61
62
-## Metrics
63
-
64
-Metrics grouped by *scope*.
65
-
66
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
67
-
68
-
69
-
70
-### Per IPFS instance
71
-
72
-These metrics refer to the entire monitored application.
73
-
74
-This scope has no labels.
75
-
76
-Metrics:
77
-
78
-| Metric | Dimensions | Unit |
79
-|:------|:----------|:----|
80
-| ipfs.bandwidth | in, out | bytes/s |
81
-| ipfs.peers | peers | peers |
82
-| ipfs.datastore_space_utilization | used | percent |
83
-| ipfs.repo_size | size | bytes |
84
-| ipfs.repo_objects | objects | objects |
85
-| ipfs.repo_pinned_objects | pinned, recursive_pins | objects |
86
-
87
-
88
-
89
-## Alerts
90
-
91
-
92
-The following alerts are available:
93
-
94
-| Alert name | On metric | Description |
95
-|:------------|:----------|:------------|
96
-| [ ipfs_datastore_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipfs.conf) | ipfs.datastore_space_utilization | IPFS datastore utilization |
97
-
98
-
62
## Setup
63
64
@@ -226,6 +189,43 @@ jobs:
189
190
191
192
+## Alerts
193
+
194
+
195
+The following alerts are available:
196
+
197
+| Alert name | On metric | Description |
198
+|:------------|:----------|:------------|
199
+| [ ipfs_datastore_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipfs.conf) | ipfs.datastore_space_utilization | IPFS datastore utilization |
200
+
201
+
202
+## Metrics
203
+
204
+Metrics grouped by *scope*.
205
+
206
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
207
+
208
+
209
+
210
+### Per IPFS instance
211
+
212
+These metrics refer to the entire monitored application.
213
+
214
+This scope has no labels.
215
+
216
+Metrics:
217
+
218
+| Metric | Dimensions | Unit |
219
+|:------|:----------|:----|
220
+| ipfs.bandwidth | in, out | bytes/s |
221
+| ipfs.peers | peers | peers |
222
+| ipfs.datastore_space_utilization | used | percent |
223
+| ipfs.repo_size | size | bytes |
224
+| ipfs.repo_objects | objects | objects |
225
+| ipfs.repo_pinned_objects | pinned, recursive_pins | objects |
226
+
227
+
228
+
229
## Troubleshooting
230
231
### Debug Mode
src/go/plugin/go.d/collector/isc_dhcpd/integrations/isc_dhcp.md
+44
-44
@@ -48,50 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per ISC DHCP instance
60
-
61
-These metrics refer to the entire monitored application.
62
-
63
-This scope has no labels.
64
-
65
-Metrics:
66
-
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| isc_dhcpd.active_leases_total | active | leases |
70
-
71
-### Per ISC DHCP instance
72
-
73
-These metrics refer to the DHCP pool.
74
-
75
-Labels:
76
-
77
-| Label | Description |
78
-|:-----------|:----------------|
79
-| dhcp_pool_name | The DHCP pool name defined in the collector configuration. |
80
-
81
-Metrics:
82
-
83
-| Metric | Dimensions | Unit |
84
-|:------|:----------|:----|
85
-| isc_dhcpd.dhcp_pool_utilization | utilization | percent |
86
-| isc_dhcpd.dhcp_pool_active_leases | active | leases |
87
-
88
-
89
-
90
-## Alerts
91
-
92
-There are no alerts configured by default for this integration.
93
-
94
-
51
## Setup
52
53
@@ -209,6 +165,50 @@ jobs:
165
166
167
168
+## Alerts
169
+
170
+There are no alerts configured by default for this integration.
171
+
172
+
173
+## Metrics
174
+
175
+Metrics grouped by *scope*.
176
+
177
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
178
+
179
+
180
+
181
+### Per ISC DHCP instance
182
+
183
+These metrics refer to the entire monitored application.
184
+
185
+This scope has no labels.
186
+
187
+Metrics:
188
+
189
+| Metric | Dimensions | Unit |
190
+|:------|:----------|:----|
191
+| isc_dhcpd.active_leases_total | active | leases |
192
+
193
+### Per ISC DHCP instance
194
+
195
+These metrics refer to the DHCP pool.
196
+
197
+Labels:
198
+
199
+| Label | Description |
200
+|:-----------|:----------------|
201
+| dhcp_pool_name | The DHCP pool name defined in the collector configuration. |
202
+
203
+Metrics:
204
+
205
+| Metric | Dimensions | Unit |
206
+|:------|:----------|:----|
207
+| isc_dhcpd.dhcp_pool_utilization | utilization | percent |
208
+| isc_dhcpd.dhcp_pool_active_leases | active | leases |
209
+
210
+
211
+
212
## Troubleshooting
213
214
### Debug Mode
src/go/plugin/go.d/collector/k8s_apiserver/integrations/kubernetes_api_server.md
+106
-106
@@ -69,112 +69,6 @@ The default configuration for this integration does not impose any limits on dat
69
70
The default configuration for this integration is not expected to impose a significant performance impact on the system.
71
72
-## Metrics
73
-
74
-Metrics grouped by *scope*.
75
-
76
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
77
-
78
-
79
-
80
-### Per Kubernetes API Server instance
81
-
82
-These metrics refer to the entire monitored API server instance.
83
-
84
-This scope has no labels.
85
-
86
-Metrics:
87
-
88
-| Metric | Dimensions | Unit |
89
-|:------|:----------|:----|
90
-| k8s_apiserver.requests_total | requests | requests/s |
91
-| k8s_apiserver.requests_dropped | dropped | requests/s |
92
-| k8s_apiserver.requests_by_verb | a dimension per HTTP verb | requests/s |
93
-| k8s_apiserver.requests_by_code | a dimension per HTTP status code | requests/s |
94
-| k8s_apiserver.requests_by_resource | a dimension per Kubernetes resource | requests/s |
95
-| k8s_apiserver.request_latency | p50, p90, p99 | milliseconds |
96
-| k8s_apiserver.response_size | p50, p90, p99 | bytes |
97
-| k8s_apiserver.inflight_requests | mutating, read_only | requests |
98
-| k8s_apiserver.longrunning_requests | longrunning | requests |
99
-| k8s_apiserver.rest_client_requests_by_code | a dimension per HTTP status code | requests/s |
100
-| k8s_apiserver.rest_client_requests_by_method | a dimension per HTTP method | requests/s |
101
-| k8s_apiserver.rest_client_latency | p50, p90, p99 | milliseconds |
102
-| k8s_apiserver.admission_step_latency | validate, admit | milliseconds |
103
-| k8s_apiserver.etcd_object_counts | a dimension per resource type | objects |
104
-| k8s_apiserver.audit_events | events, rejected | events/s |
105
-| k8s_apiserver.authentication_requests | authenticated | requests/s |
106
-| k8s_apiserver.goroutines | goroutines | goroutines |
107
-| k8s_apiserver.threads | threads | threads |
108
-| k8s_apiserver.process_memory | resident, virtual | bytes |
109
-| k8s_apiserver.heap_memory | alloc, inuse, stack | bytes |
110
-| k8s_apiserver.gc_duration | min, p25, p50, p75, max | seconds |
111
-| k8s_apiserver.open_fds | open, max | file descriptors |
112
-| k8s_apiserver.cpu_usage | cpu | seconds/s |
113
-
114
-### Per workqueue
115
-
116
-These metrics refer to controller work queues.
117
-
118
-Labels:
119
-
120
-| Label | Description |
121
-|:-----------|:----------------|
122
-| controller | Controller name |
123
-
124
-Metrics:
125
-
126
-| Metric | Dimensions | Unit |
127
-|:------|:----------|:----|
128
-| k8s_apiserver.workqueue_depth | depth | items |
129
-| k8s_apiserver.workqueue_latency | p50, p90, p99 | microseconds |
130
-| k8s_apiserver.workqueue_adds | adds, retries | items/s |
131
-| k8s_apiserver.workqueue_duration | p50, p90, p99 | microseconds |
132
-
133
-### Per admission controller
134
-
135
-These metrics refer to admission controllers.
136
-
137
-Labels:
138
-
139
-| Label | Description |
140
-|:-----------|:----------------|
141
-| name | Admission controller name |
142
-
143
-Metrics:
144
-
145
-| Metric | Dimensions | Unit |
146
-|:------|:----------|:----|
147
-| k8s_apiserver.admission_controller_latency | 5ms, 25ms, 100ms, 500ms, 1s, 2.5s, +Inf | events/s |
148
-
149
-### Per admission webhook
150
-
151
-These metrics refer to admission webhooks.
152
-
153
-Labels:
154
-
155
-| Label | Description |
156
-|:-----------|:----------------|
157
-| name | Webhook name |
158
-
159
-Metrics:
160
-
161
-| Metric | Dimensions | Unit |
162
-|:------|:----------|:----|
163
-| k8s_apiserver.admission_webhook_latency | 5ms, 25ms, 100ms, 500ms, 1s, 2.5s, +Inf | events/s |
164
-
165
-
166
-
167
-## Alerts
168
-
169
-
170
-The following alerts are available:
171
-
172
-| Alert name | On metric | Description |
173
-|:------------|:----------|:------------|
174
-| [ k8s_apiserver_request_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8s_apiserver.conf) | k8s_apiserver.requests_by_code | high rate of API server request errors (5xx responses) |
175
-| [ k8s_apiserver_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8s_apiserver.conf) | k8s_apiserver.request_latency | API server request latency is high |
176
-
177
-
72
## Setup
73
74
@@ -322,6 +216,112 @@ jobs:
216
217
218
219
+## Alerts
220
+
221
+
222
+The following alerts are available:
223
+
224
+| Alert name | On metric | Description |
225
+|:------------|:----------|:------------|
226
+| [ k8s_apiserver_request_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8s_apiserver.conf) | k8s_apiserver.requests_by_code | high rate of API server request errors (5xx responses) |
227
+| [ k8s_apiserver_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8s_apiserver.conf) | k8s_apiserver.request_latency | API server request latency is high |
228
+
229
+
230
+## Metrics
231
+
232
+Metrics grouped by *scope*.
233
+
234
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
235
+
236
+
237
+
238
+### Per Kubernetes API Server instance
239
+
240
+These metrics refer to the entire monitored API server instance.
241
+
242
+This scope has no labels.
243
+
244
+Metrics:
245
+
246
+| Metric | Dimensions | Unit |
247
+|:------|:----------|:----|
248
+| k8s_apiserver.requests_total | requests | requests/s |
249
+| k8s_apiserver.requests_dropped | dropped | requests/s |
250
+| k8s_apiserver.requests_by_verb | a dimension per HTTP verb | requests/s |
251
+| k8s_apiserver.requests_by_code | a dimension per HTTP status code | requests/s |
252
+| k8s_apiserver.requests_by_resource | a dimension per Kubernetes resource | requests/s |
253
+| k8s_apiserver.request_latency | p50, p90, p99 | milliseconds |
254
+| k8s_apiserver.response_size | p50, p90, p99 | bytes |
255
+| k8s_apiserver.inflight_requests | mutating, read_only | requests |
256
+| k8s_apiserver.longrunning_requests | longrunning | requests |
257
+| k8s_apiserver.rest_client_requests_by_code | a dimension per HTTP status code | requests/s |
258
+| k8s_apiserver.rest_client_requests_by_method | a dimension per HTTP method | requests/s |
259
+| k8s_apiserver.rest_client_latency | p50, p90, p99 | milliseconds |
260
+| k8s_apiserver.admission_step_latency | validate, admit | milliseconds |
261
+| k8s_apiserver.etcd_object_counts | a dimension per resource type | objects |
262
+| k8s_apiserver.audit_events | events, rejected | events/s |
263
+| k8s_apiserver.authentication_requests | authenticated | requests/s |
264
+| k8s_apiserver.goroutines | goroutines | goroutines |
265
+| k8s_apiserver.threads | threads | threads |
266
+| k8s_apiserver.process_memory | resident, virtual | bytes |
267
+| k8s_apiserver.heap_memory | alloc, inuse, stack | bytes |
268
+| k8s_apiserver.gc_duration | min, p25, p50, p75, max | seconds |
269
+| k8s_apiserver.open_fds | open, max | file descriptors |
270
+| k8s_apiserver.cpu_usage | cpu | seconds/s |
271
+
272
+### Per workqueue
273
+
274
+These metrics refer to controller work queues.
275
+
276
+Labels:
277
+
278
+| Label | Description |
279
+|:-----------|:----------------|
280
+| controller | Controller name |
281
+
282
+Metrics:
283
+
284
+| Metric | Dimensions | Unit |
285
+|:------|:----------|:----|
286
+| k8s_apiserver.workqueue_depth | depth | items |
287
+| k8s_apiserver.workqueue_latency | p50, p90, p99 | microseconds |
288
+| k8s_apiserver.workqueue_adds | adds, retries | items/s |
289
+| k8s_apiserver.workqueue_duration | p50, p90, p99 | microseconds |
290
+
291
+### Per admission controller
292
+
293
+These metrics refer to admission controllers.
294
+
295
+Labels:
296
+
297
+| Label | Description |
298
+|:-----------|:----------------|
299
+| name | Admission controller name |
300
+
301
+Metrics:
302
+
303
+| Metric | Dimensions | Unit |
304
+|:------|:----------|:----|
305
+| k8s_apiserver.admission_controller_latency | 5ms, 25ms, 100ms, 500ms, 1s, 2.5s, +Inf | events/s |
306
+
307
+### Per admission webhook
308
+
309
+These metrics refer to admission webhooks.
310
+
311
+Labels:
312
+
313
+| Label | Description |
314
+|:-----------|:----------------|
315
+| name | Webhook name |
316
+
317
+Metrics:
318
+
319
+| Metric | Dimensions | Unit |
320
+|:------|:----------|:----|
321
+| k8s_apiserver.admission_webhook_latency | 5ms, 25ms, 100ms, 500ms, 1s, 2.5s, +Inf | events/s |
322
+
323
+
324
+
325
## Troubleshooting
326
327
### Debug Mode
src/go/plugin/go.d/collector/k8s_kubelet/integrations/kubelet.md
+65
-65
@@ -54,71 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per Kubelet instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| k8s_kubelet.apiserver_audit_requests_rejected | rejected | requests/s |
76
-| k8s_kubelet.apiserver_storage_data_key_generation_failures | failures | events/s |
77
-| k8s_kubelet.apiserver_storage_data_key_generation_latencies | 5_µs, 10_µs, 20_µs, 40_µs, 80_µs, 160_µs, 320_µs, 640_µs, 1280_µs, 2560_µs, 5120_µs, 10240_µs, 20480_µs, 40960_µs, +Inf | observes/s |
78
-| k8s_kubelet.apiserver_storage_data_key_generation_latencies_percent | 5_µs, 10_µs, 20_µs, 40_µs, 80_µs, 160_µs, 320_µs, 640_µs, 1280_µs, 2560_µs, 5120_µs, 10240_µs, 20480_µs, 40960_µs, +Inf | percentage |
79
-| k8s_kubelet.apiserver_storage_envelope_transformation_cache_misses | cache misses | events/s |
80
-| k8s_kubelet.kubelet_containers_running | total | running_containers |
81
-| k8s_kubelet.kubelet_pods_running | total | running_pods |
82
-| k8s_kubelet.kubelet_pods_log_filesystem_used_bytes | a dimension per namespace and pod | B |
83
-| k8s_kubelet.kubelet_runtime_operations | a dimension per operation type | operations/s |
84
-| k8s_kubelet.kubelet_runtime_operations_errors | a dimension per operation type | errors/s |
85
-| k8s_kubelet.kubelet_docker_operations | a dimension per operation type | operations/s |
86
-| k8s_kubelet.kubelet_docker_operations_errors | a dimension per operation type | errors/s |
87
-| k8s_kubelet.kubelet_node_config_error | experiencing_error | bool |
88
-| k8s_kubelet.kubelet_pleg_relist_interval_microseconds | 0.5, 0.9, 0.99 | microseconds |
89
-| k8s_kubelet.kubelet_pleg_relist_latency_microseconds | 0.5, 0.9, 0.99 | microseconds |
90
-| k8s_kubelet.kubelet_token_requests | total, failed | token_requests/s |
91
-| k8s_kubelet.rest_client_requests_by_code | a dimension per HTTP status code | requests/s |
92
-| k8s_kubelet.rest_client_requests_by_method | a dimension per HTTP method | requests/s |
93
-
94
-### Per volume manager
95
-
96
-These metrics refer to the Volume Manager.
97
-
98
-This scope has no labels.
99
-
100
-Metrics:
101
-
102
-| Metric | Dimensions | Unit |
103
-|:------|:----------|:----|
104
-| k8s_kubelet.volume_manager_total_volumes | actual, desired | state |
105
-
106
-
107
-
108
-## Alerts
109
-
110
-
111
-The following alerts are available:
112
-
113
-| Alert name | On metric | Description |
114
-|:------------|:----------|:------------|
115
-| [ kubelet_node_config_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_node_config_error | the node is experiencing a configuration-related error (0: false, 1: true) |
116
-| [ kubelet_token_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_token_requests | number of failed Token() requests to the alternate token source |
117
-| [ kubelet_token_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_token_requests | number of failed Token() requests to the alternate token source |
118
-| [ kubelet_operations_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_operations_errors | number of Docker or runtime operation errors |
119
-| [ kubelet_operations_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_operations_errors | number of Docker or runtime operation errors |
120
-
121
-
57
## Setup
58
59
@@ -243,6 +178,71 @@ jobs:
178
179
180
181
+## Alerts
182
+
183
+
184
+The following alerts are available:
185
+
186
+| Alert name | On metric | Description |
187
+|:------------|:----------|:------------|
188
+| [ kubelet_node_config_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_node_config_error | the node is experiencing a configuration-related error (0: false, 1: true) |
189
+| [ kubelet_token_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_token_requests | number of failed Token() requests to the alternate token source |
190
+| [ kubelet_token_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_token_requests | number of failed Token() requests to the alternate token source |
191
+| [ kubelet_operations_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_operations_errors | number of Docker or runtime operation errors |
192
+| [ kubelet_operations_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/kubelet.conf) | k8s_kubelet.kubelet_operations_errors | number of Docker or runtime operation errors |
193
+
194
+
195
+## Metrics
196
+
197
+Metrics grouped by *scope*.
198
+
199
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
200
+
201
+
202
+
203
+### Per Kubelet instance
204
+
205
+These metrics refer to the entire monitored application.
206
+
207
+This scope has no labels.
208
+
209
+Metrics:
210
+
211
+| Metric | Dimensions | Unit |
212
+|:------|:----------|:----|
213
+| k8s_kubelet.apiserver_audit_requests_rejected | rejected | requests/s |
214
+| k8s_kubelet.apiserver_storage_data_key_generation_failures | failures | events/s |
215
+| k8s_kubelet.apiserver_storage_data_key_generation_latencies | 5_µs, 10_µs, 20_µs, 40_µs, 80_µs, 160_µs, 320_µs, 640_µs, 1280_µs, 2560_µs, 5120_µs, 10240_µs, 20480_µs, 40960_µs, +Inf | observes/s |
216
+| k8s_kubelet.apiserver_storage_data_key_generation_latencies_percent | 5_µs, 10_µs, 20_µs, 40_µs, 80_µs, 160_µs, 320_µs, 640_µs, 1280_µs, 2560_µs, 5120_µs, 10240_µs, 20480_µs, 40960_µs, +Inf | percentage |
217
+| k8s_kubelet.apiserver_storage_envelope_transformation_cache_misses | cache misses | events/s |
218
+| k8s_kubelet.kubelet_containers_running | total | running_containers |
219
+| k8s_kubelet.kubelet_pods_running | total | running_pods |
220
+| k8s_kubelet.kubelet_pods_log_filesystem_used_bytes | a dimension per namespace and pod | B |
221
+| k8s_kubelet.kubelet_runtime_operations | a dimension per operation type | operations/s |
222
+| k8s_kubelet.kubelet_runtime_operations_errors | a dimension per operation type | errors/s |
223
+| k8s_kubelet.kubelet_docker_operations | a dimension per operation type | operations/s |
224
+| k8s_kubelet.kubelet_docker_operations_errors | a dimension per operation type | errors/s |
225
+| k8s_kubelet.kubelet_node_config_error | experiencing_error | bool |
226
+| k8s_kubelet.kubelet_pleg_relist_interval_microseconds | 0.5, 0.9, 0.99 | microseconds |
227
+| k8s_kubelet.kubelet_pleg_relist_latency_microseconds | 0.5, 0.9, 0.99 | microseconds |
228
+| k8s_kubelet.kubelet_token_requests | total, failed | token_requests/s |
229
+| k8s_kubelet.rest_client_requests_by_code | a dimension per HTTP status code | requests/s |
230
+| k8s_kubelet.rest_client_requests_by_method | a dimension per HTTP method | requests/s |
231
+
232
+### Per volume manager
233
+
234
+These metrics refer to the Volume Manager.
235
+
236
+This scope has no labels.
237
+
238
+Metrics:
239
+
240
+| Metric | Dimensions | Unit |
241
+|:------|:----------|:----|
242
+| k8s_kubelet.volume_manager_total_volumes | actual, desired | state |
243
+
244
+
245
+
246
## Troubleshooting
247
248
### Debug Mode
src/go/plugin/go.d/collector/k8s_kubeproxy/integrations/kubeproxy.md
+32
-32
@@ -54,38 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per Kubeproxy instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| k8s_kubeproxy.kubeproxy_sync_proxy_rules | sync_proxy_rules | events/s |
76
-| k8s_kubeproxy.kubeproxy_sync_proxy_rules_latency_microsecond | 0.001, 0.002, 0.004, 0.008, 0.016, 0.032, 0.064, 0.128, 0.256, 0.512, 1.024, 2.048, 4.096, 8.192, 16.384, +Inf | observes/s |
77
-| k8s_kubeproxy.kubeproxy_sync_proxy_rules_latency | 0.001, 0.002, 0.004, 0.008, 0.016, 0.032, 0.064, 0.128, 0.256, 0.512, 1.024, 2.048, 4.096, 8.192, 16.384, +Inf | percentage |
78
-| k8s_kubeproxy.rest_client_requests_by_code | a dimension per HTTP status code | requests/s |
79
-| k8s_kubeproxy.rest_client_requests_by_method | a dimension per HTTP method | requests/s |
80
-| k8s_kubeproxy.http_request_duration | 0.5, 0.9, 0.99 | microseconds |
81
-
82
-
83
-
84
-## Alerts
85
-
86
-There are no alerts configured by default for this integration.
87
-
88
-
57
## Setup
58
59
@@ -210,6 +178,38 @@ jobs:
178
179
180
181
+## Alerts
182
+
183
+There are no alerts configured by default for this integration.
184
+
185
+
186
+## Metrics
187
+
188
+Metrics grouped by *scope*.
189
+
190
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
191
+
192
+
193
+
194
+### Per Kubeproxy instance
195
+
196
+These metrics refer to the entire monitored application.
197
+
198
+This scope has no labels.
199
+
200
+Metrics:
201
+
202
+| Metric | Dimensions | Unit |
203
+|:------|:----------|:----|
204
+| k8s_kubeproxy.kubeproxy_sync_proxy_rules | sync_proxy_rules | events/s |
205
+| k8s_kubeproxy.kubeproxy_sync_proxy_rules_latency_microsecond | 0.001, 0.002, 0.004, 0.008, 0.016, 0.032, 0.064, 0.128, 0.256, 0.512, 1.024, 2.048, 4.096, 8.192, 16.384, +Inf | observes/s |
206
+| k8s_kubeproxy.kubeproxy_sync_proxy_rules_latency | 0.001, 0.002, 0.004, 0.008, 0.016, 0.032, 0.064, 0.128, 0.256, 0.512, 1.024, 2.048, 4.096, 8.192, 16.384, +Inf | percentage |
207
+| k8s_kubeproxy.rest_client_requests_by_code | a dimension per HTTP status code | requests/s |
208
+| k8s_kubeproxy.rest_client_requests_by_method | a dimension per HTTP method | requests/s |
209
+| k8s_kubeproxy.http_request_duration | 0.5, 0.9, 0.99 | microseconds |
210
+
211
+
212
+
213
## Troubleshooting
214
215
### Debug Mode
src/go/plugin/go.d/collector/k8s_state/integrations/kubernetes_cluster_state.md
+81
-81
@@ -53,6 +53,87 @@ The default configuration for this integration does not impose any limits on dat
53
54
The default configuration for this integration is not expected to impose a significant performance impact on the system.
55
56
+## Setup
57
+
58
+
59
+You can configure the **k8s_state** collector in two ways:
60
+
61
+| Method | Best for | How to |
62
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
63
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **k8s_state**, then click **+** to add a job. |
64
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/k8s_state.conf` and add a job. |
65
+
66
+:::important
67
+
68
+UI configuration requires paid Netdata Cloud plan.
69
+
70
+:::
71
+
72
+
73
+### Prerequisites
74
+
75
+No action required.
76
+
77
+### Configuration
78
+
79
+#### Options
80
+
81
+
82
+
83
+There are no configuration options.
84
+
85
+
86
+#### via UI
87
+
88
+Configure the **k8s_state** collector from the Netdata web interface:
89
+
90
+1. Go to **Nodes**.
91
+2. Select the node **where you want the k8s_state data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
92
+3. The **Collectors → Jobs** view opens by default.
93
+4. In the Search box, type _k8s_state_ (or scroll the list) to locate the **k8s_state** collector.
94
+5. Click the **+** next to the **k8s_state** collector to add a new job.
95
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
96
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
97
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
98
+
99
+
100
+#### via File
101
+
102
+The configuration file name for this integration is `go.d/k8s_state.conf`.
103
+
104
+The file format is YAML. Generally, the structure is:
105
+
106
+```yaml
107
+update_every: 1
108
+autodetection_retry: 0
109
+jobs:
110
+ - name: some_name1
111
+ - name: some_name2
112
+```
113
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
114
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
115
+
116
+```bash
117
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
+sudo ./edit-config go.d/k8s_state.conf
119
+```
120
+
121
+##### Examples
122
+There are no configuration examples.
123
+
124
+
125
+
126
+## Alerts
127
+
128
+
129
+The following alerts are available:
130
+
131
+| Alert name | On metric | Description |
132
+|:------------|:----------|:------------|
133
+| [ k8s_state_deployment_condition_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8sstate.conf) | k8s_state.deployment_conditions | Deployment ${label:k8s_deployment_name} does not have the minimum required replicas |
134
+| [ k8s_state_cronjob_last_execution_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8sstate.conf) | k8s_state.cronjob_last_execution_status | CronJob ${label:k8s_cronjob_name} in ${label:k8s_namespace} failing |
135
+
136
+
137
## Metrics
138
139
Metrics grouped by *scope*.
@@ -208,87 +289,6 @@ Metrics:
289
290
291
211
-## Alerts
212
-
213
-
214
-The following alerts are available:
215
-
216
-| Alert name | On metric | Description |
217
-|:------------|:----------|:------------|
218
-| [ k8s_state_deployment_condition_available ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8sstate.conf) | k8s_state.deployment_conditions | Deployment ${label:k8s_deployment_name} does not have the minimum required replicas |
219
-| [ k8s_state_cronjob_last_execution_failed ](https://github.com/netdata/netdata/blob/master/src/health/health.d/k8sstate.conf) | k8s_state.cronjob_last_execution_status | CronJob ${label:k8s_cronjob_name} in ${label:k8s_namespace} failing |
220
-
221
-
222
-## Setup
223
-
224
-
225
-You can configure the **k8s_state** collector in two ways:
226
-
227
-| Method | Best for | How to |
228
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
229
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **k8s_state**, then click **+** to add a job. |
230
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/k8s_state.conf` and add a job. |
231
-
232
-:::important
233
-
234
-UI configuration requires paid Netdata Cloud plan.
235
-
236
-:::
237
-
238
-
239
-### Prerequisites
240
-
241
-No action required.
242
-
243
-### Configuration
244
-
245
-#### Options
246
-
247
-
248
-
249
-There are no configuration options.
250
-
251
-
252
-#### via UI
253
-
254
-Configure the **k8s_state** collector from the Netdata web interface:
255
-
256
-1. Go to **Nodes**.
257
-2. Select the node **where you want the k8s_state data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
258
-3. The **Collectors → Jobs** view opens by default.
259
-4. In the Search box, type _k8s_state_ (or scroll the list) to locate the **k8s_state** collector.
260
-5. Click the **+** next to the **k8s_state** collector to add a new job.
261
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
262
- - **Test** runs the job with the provided settings and shows whether data can be collected.
263
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
264
-
265
-
266
-#### via File
267
-
268
-The configuration file name for this integration is `go.d/k8s_state.conf`.
269
-
270
-The file format is YAML. Generally, the structure is:
271
-
272
-```yaml
273
-update_every: 1
274
-autodetection_retry: 0
275
-jobs:
276
- - name: some_name1
277
- - name: some_name2
278
-```
279
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
280
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
281
-
282
-```bash
283
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
284
-sudo ./edit-config go.d/k8s_state.conf
285
-```
286
-
287
-##### Examples
288
-There are no configuration examples.
289
-
290
-
291
-
292
## Troubleshooting
293
294
### Debug Mode
src/go/plugin/go.d/collector/lighttpd/integrations/lighttpd.md
+31
-31
@@ -58,37 +58,6 @@ The default configuration for this integration does not impose any limits on dat
58
59
The default configuration for this integration is not expected to impose a significant performance impact on the system.
60
61
-## Metrics
62
-
63
-Metrics grouped by *scope*.
64
-
65
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
66
-
67
-
68
-
69
-### Per Lighttpd instance
70
-
71
-These metrics refer to the entire monitored application.
72
-
73
-This scope has no labels.
74
-
75
-Metrics:
76
-
77
-| Metric | Dimensions | Unit |
78
-|:------|:----------|:----|
79
-| lighttpd.requests | requests | requests/s |
80
-| lighttpd.net | sent | kilobits/s |
81
-| lighttpd.workers | idle, busy | servers |
82
-| lighttpd.scoreboard | waiting, open, close, hard_error, keepalive, read, read_post, write, handle_request, request_start, request_end | connections |
83
-| lighttpd.uptime | uptime | seconds |
84
-
85
-
86
-
87
-## Alerts
88
-
89
-There are no alerts configured by default for this integration.
90
-
91
-
61
## Setup
62
63
@@ -252,6 +221,37 @@ jobs:
221
222
223
224
+## Alerts
225
+
226
+There are no alerts configured by default for this integration.
227
+
228
+
229
+## Metrics
230
+
231
+Metrics grouped by *scope*.
232
+
233
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
234
+
235
+
236
+
237
+### Per Lighttpd instance
238
+
239
+These metrics refer to the entire monitored application.
240
+
241
+This scope has no labels.
242
+
243
+Metrics:
244
+
245
+| Metric | Dimensions | Unit |
246
+|:------|:----------|:----|
247
+| lighttpd.requests | requests | requests/s |
248
+| lighttpd.net | sent | kilobits/s |
249
+| lighttpd.workers | idle, busy | servers |
250
+| lighttpd.scoreboard | waiting, open, close, hard_error, keepalive, read, read_post, write, handle_request, request_start, request_end | connections |
251
+| lighttpd.uptime | uptime | seconds |
252
+
253
+
254
+
255
## Troubleshooting
256
257
### Debug Mode
src/go/plugin/go.d/collector/litespeed/integrations/litespeed.md
+35
-35
@@ -47,41 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per Litespeed instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| litespeed.requests | requests | requests/s |
69
-| litespeed.requests_processing | processing | requests |
70
-| litespeed.net_throughput | in, out | kilobits/s |
71
-| litespeed.net_ssl_throughput | in, out | kilobits/s |
72
-| litespeed.connections | free, used | conns |
73
-| litespeed.ssl_connections | free, used | conns |
74
-| litespeed.public_cache | hits | hits/s |
75
-| litespeed.private_cache | hits | hits/s |
76
-| litespeed.static | hits | hits/s |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-There are no alerts configured by default for this integration.
83
-
84
-
50
## Setup
51
52
@@ -173,6 +138,41 @@ local:
138
```
139
140
141
+## Alerts
142
+
143
+There are no alerts configured by default for this integration.
144
+
145
+
146
+## Metrics
147
+
148
+Metrics grouped by *scope*.
149
+
150
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
151
+
152
+
153
+
154
+### Per Litespeed instance
155
+
156
+These metrics refer to the entire monitored application.
157
+
158
+This scope has no labels.
159
+
160
+Metrics:
161
+
162
+| Metric | Dimensions | Unit |
163
+|:------|:----------|:----|
164
+| litespeed.requests | requests | requests/s |
165
+| litespeed.requests_processing | processing | requests |
166
+| litespeed.net_throughput | in, out | kilobits/s |
167
+| litespeed.net_ssl_throughput | in, out | kilobits/s |
168
+| litespeed.connections | free, used | conns |
169
+| litespeed.ssl_connections | free, used | conns |
170
+| litespeed.public_cache | hits | hits/s |
171
+| litespeed.private_cache | hits | hits/s |
172
+| litespeed.static | hits | hits/s |
173
+
174
+
175
+
176
## Troubleshooting
177
178
### Debug Mode
src/go/plugin/go.d/collector/logind/integrations/systemd-logind_users.md
+30
-30
@@ -47,36 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per systemd-logind users instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| logind.sessions | remote, local | sessions |
69
-| logind.sessions_type | console, graphical, other | sessions |
70
-| logind.sessions_state | online, closing, active | sessions |
71
-| logind.users_state | offline, closing, online, lingering, active | users |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-There are no alerts configured by default for this integration.
78
-
79
-
50
## Setup
51
52
@@ -146,6 +116,36 @@ There are no configuration examples.
116
117
118
119
+## Alerts
120
+
121
+There are no alerts configured by default for this integration.
122
+
123
+
124
+## Metrics
125
+
126
+Metrics grouped by *scope*.
127
+
128
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
129
+
130
+
131
+
132
+### Per systemd-logind users instance
133
+
134
+These metrics refer to the entire monitored application.
135
+
136
+This scope has no labels.
137
+
138
+Metrics:
139
+
140
+| Metric | Dimensions | Unit |
141
+|:------|:----------|:----|
142
+| logind.sessions | remote, local | sessions |
143
+| logind.sessions_type | console, graphical, other | sessions |
144
+| logind.sessions_state | online, closing, active | sessions |
145
+| logind.users_state | offline, closing, online, lingering, active | users |
146
+
147
+
148
+
149
## Troubleshooting
150
151
### Debug Mode
src/go/plugin/go.d/collector/logstash/integrations/logstash.md
+55
-55
@@ -45,61 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Logstash instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| logstash.jvm_threads | threads | count |
67
-| logstash.jvm_mem_heap_used | in_use | percentage |
68
-| logstash.jvm_mem_heap | committed, used | KiB |
69
-| logstash.jvm_mem_pools_eden | committed, used | KiB |
70
-| logstash.jvm_mem_pools_survivor | committed, used | KiB |
71
-| logstash.jvm_mem_pools_old | committed, used | KiB |
72
-| logstash.jvm_gc_collector_count | eden, old | counts/s |
73
-| logstash.jvm_gc_collector_time | eden, old | ms |
74
-| logstash.open_file_descriptors | open | fd |
75
-| logstash.event | in, filtered, out | events/s |
76
-| logstash.event_duration | event, queue | seconds |
77
-| logstash.uptime | uptime | seconds |
78
-
79
-### Per pipeline
80
-
81
-These metrics refer to the pipeline.
82
-
83
-Labels:
84
-
85
-| Label | Description |
86
-|:-----------|:----------------|
87
-| pipeline | pipeline name |
88
-
89
-Metrics:
90
-
91
-| Metric | Dimensions | Unit |
92
-|:------|:----------|:----|
93
-| logstash.pipeline_event | in, filtered, out | events/s |
94
-| logstash.pipeline_event_duration | event, queue | seconds |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-There are no alerts configured by default for this integration.
101
-
102
-
48
## Setup
49
50
@@ -263,6 +208,61 @@ jobs:
208
209
210
211
+## Alerts
212
+
213
+There are no alerts configured by default for this integration.
214
+
215
+
216
+## Metrics
217
+
218
+Metrics grouped by *scope*.
219
+
220
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
221
+
222
+
223
+
224
+### Per Logstash instance
225
+
226
+These metrics refer to the entire monitored application.
227
+
228
+This scope has no labels.
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| logstash.jvm_threads | threads | count |
235
+| logstash.jvm_mem_heap_used | in_use | percentage |
236
+| logstash.jvm_mem_heap | committed, used | KiB |
237
+| logstash.jvm_mem_pools_eden | committed, used | KiB |
238
+| logstash.jvm_mem_pools_survivor | committed, used | KiB |
239
+| logstash.jvm_mem_pools_old | committed, used | KiB |
240
+| logstash.jvm_gc_collector_count | eden, old | counts/s |
241
+| logstash.jvm_gc_collector_time | eden, old | ms |
242
+| logstash.open_file_descriptors | open | fd |
243
+| logstash.event | in, filtered, out | events/s |
244
+| logstash.event_duration | event, queue | seconds |
245
+| logstash.uptime | uptime | seconds |
246
+
247
+### Per pipeline
248
+
249
+These metrics refer to the pipeline.
250
+
251
+Labels:
252
+
253
+| Label | Description |
254
+|:-----------|:----------------|
255
+| pipeline | pipeline name |
256
+
257
+Metrics:
258
+
259
+| Metric | Dimensions | Unit |
260
+|:------|:----------|:----|
261
+| logstash.pipeline_event | in, filtered, out | events/s |
262
+| logstash.pipeline_event_duration | event, queue | seconds |
263
+
264
+
265
+
266
## Troubleshooting
267
268
### Debug Mode
src/go/plugin/go.d/collector/lvm/integrations/lvm_logical_volumes.md
+40
-40
@@ -48,46 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per logical volume
60
-
61
-These metrics refer to the LVM logical volume.
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| lv_name | Logical volume name |
68
-| vg_name | Volume group name |
69
-| volume_type | Type of the volume |
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| lvm.lv_data_space_utilization | utilization | % |
76
-| lvm.lv_metadata_space_utilization | utilization | % |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-
83
-The following alerts are available:
84
-
85
-| Alert name | On metric | Description |
86
-|:------------|:----------|:------------|
87
-| [ lvm_lv_data_space_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/lvm.conf) | lvm.lv_data_space_utilization | LVM logical volume high data space usage (LV ${label:lv_name} VG ${label:vg_name} Type ${label:volume_type}) |
88
-| [ lvm_lv_metadata_space_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/lvm.conf) | lvm.lv_metadata_space_utilization | LVM logical volume high metadata space usage (LV ${label:lv_name} VG ${label:vg_name} Type ${label:volume_type}) |
89
-
90
-
51
## Setup
52
53
@@ -182,6 +142,46 @@ jobs:
142
143
144
145
+## Alerts
146
+
147
+
148
+The following alerts are available:
149
+
150
+| Alert name | On metric | Description |
151
+|:------------|:----------|:------------|
152
+| [ lvm_lv_data_space_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/lvm.conf) | lvm.lv_data_space_utilization | LVM logical volume high data space usage (LV ${label:lv_name} VG ${label:vg_name} Type ${label:volume_type}) |
153
+| [ lvm_lv_metadata_space_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/lvm.conf) | lvm.lv_metadata_space_utilization | LVM logical volume high metadata space usage (LV ${label:lv_name} VG ${label:vg_name} Type ${label:volume_type}) |
154
+
155
+
156
+## Metrics
157
+
158
+Metrics grouped by *scope*.
159
+
160
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
161
+
162
+
163
+
164
+### Per logical volume
165
+
166
+These metrics refer to the LVM logical volume.
167
+
168
+Labels:
169
+
170
+| Label | Description |
171
+|:-----------|:----------------|
172
+| lv_name | Logical volume name |
173
+| vg_name | Volume group name |
174
+| volume_type | Type of the volume |
175
+
176
+Metrics:
177
+
178
+| Metric | Dimensions | Unit |
179
+|:------|:----------|:----|
180
+| lvm.lv_data_space_utilization | utilization | % |
181
+| lvm.lv_metadata_space_utilization | utilization | % |
182
+
183
+
184
+
185
## Troubleshooting
186
187
### Debug Mode
src/go/plugin/go.d/collector/maxscale/integrations/maxscale.md
+52
-52
@@ -53,58 +53,6 @@ The default configuration for this integration does not impose any limits on dat
53
54
The default configuration for this integration is not expected to impose a significant performance impact on the system.
55
56
-## Metrics
57
-
58
-Metrics grouped by *scope*.
59
-
60
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
61
-
62
-
63
-
64
-### Per MaxScale instance
65
-
66
-These metrics refer to the monitored MaxScale instance.
67
-
68
-This scope has no labels.
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| maxscale.poll_events | reads, writes, accepts, errors, hangups | events/s |
75
-| maxscale.current_sessions | sessions | sessions |
76
-| maxscale.current_zombie_connections | zombie | connections |
77
-| maxscale.threads_by_state | active, draining, dormant | threads |
78
-| maxscale.current_fds | managed | fds |
79
-| maxscale.qc_cache_efficiency | hits, misses | requests/s |
80
-| maxscale.qc_cache_operations | inserts, evictions | operations/s |
81
-| maxscale.uptime | uptime | seconds |
82
-
83
-### Per server
84
-
85
-These metrics refer to the MariaDB server.
86
-
87
-Labels:
88
-
89
-| Label | Description |
90
-|:-----------|:----------------|
91
-| server | Server ID. |
92
-| address | Server address. |
93
-
94
-Metrics:
95
-
96
-| Metric | Dimensions | Unit |
97
-|:------|:----------|:----|
98
-| maxscale.server_state | master, slave, running, down, maintenance, draining, drained, relay_master, binlog_relay, synced | state |
99
-| maxscale.server_current_connections | connections | connections |
100
-
101
-
102
-
103
-## Alerts
104
-
105
-There are no alerts configured by default for this integration.
106
-
107
-
56
## Setup
57
58
@@ -256,6 +204,58 @@ jobs:
204
205
206
207
+## Alerts
208
+
209
+There are no alerts configured by default for this integration.
210
+
211
+
212
+## Metrics
213
+
214
+Metrics grouped by *scope*.
215
+
216
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
217
+
218
+
219
+
220
+### Per MaxScale instance
221
+
222
+These metrics refer to the monitored MaxScale instance.
223
+
224
+This scope has no labels.
225
+
226
+Metrics:
227
+
228
+| Metric | Dimensions | Unit |
229
+|:------|:----------|:----|
230
+| maxscale.poll_events | reads, writes, accepts, errors, hangups | events/s |
231
+| maxscale.current_sessions | sessions | sessions |
232
+| maxscale.current_zombie_connections | zombie | connections |
233
+| maxscale.threads_by_state | active, draining, dormant | threads |
234
+| maxscale.current_fds | managed | fds |
235
+| maxscale.qc_cache_efficiency | hits, misses | requests/s |
236
+| maxscale.qc_cache_operations | inserts, evictions | operations/s |
237
+| maxscale.uptime | uptime | seconds |
238
+
239
+### Per server
240
+
241
+These metrics refer to the MariaDB server.
242
+
243
+Labels:
244
+
245
+| Label | Description |
246
+|:-----------|:----------------|
247
+| server | Server ID. |
248
+| address | Server address. |
249
+
250
+Metrics:
251
+
252
+| Metric | Dimensions | Unit |
253
+|:------|:----------|:----|
254
+| maxscale.server_state | master, slave, running, down, maintenance, draining, drained, relay_master, binlog_relay, synced | state |
255
+| maxscale.server_current_connections | connections | connections |
256
+
257
+
258
+
259
## Troubleshooting
260
261
### Debug Mode
src/go/plugin/go.d/collector/megacli/integrations/megacli_megaraid.md
+81
-81
@@ -55,87 +55,6 @@ The default configuration for this integration does not impose any limits on dat
55
56
The default configuration for this integration is not expected to impose a significant performance impact on the system.
57
58
-## Metrics
59
-
60
-Metrics grouped by *scope*.
61
-
62
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
-
64
-
65
-
66
-### Per adapter
67
-
68
-These metrics refer to the MegaCLI Adapter.
69
-
70
-Labels:
71
-
72
-| Label | Description |
73
-|:-----------|:----------------|
74
-| adapter_number | Adapter number |
75
-
76
-Metrics:
77
-
78
-| Metric | Dimensions | Unit |
79
-|:------|:----------|:----|
80
-| megacli.adapter_health_state | optimal, degraded, partially_degraded, failed | state |
81
-
82
-### Per physical drive
83
-
84
-These metrics refer to the MegaCLI Physical Drive.
85
-
86
-Labels:
87
-
88
-| Label | Description |
89
-|:-----------|:----------------|
90
-| adapter_number | Adapter number |
91
-| wwn | World Wide Name |
92
-| slot_number | Slot number |
93
-| drive_position | Position (e.g. DiskGroup: 0, Span: 0, Arm: 2) |
94
-| drive_type | Type (e.g. SATA) |
95
-
96
-Metrics:
97
-
98
-| Metric | Dimensions | Unit |
99
-|:------|:----------|:----|
100
-| megacli.phys_drive_media_errors_rate | media_errors | errors/s |
101
-| megacli.phys_drive_predictive_failures_rate | predictive_failures | failures/s |
102
-
103
-### Per backup battery unit
104
-
105
-These metrics refer to the MegaCLI Backup Battery Unit.
106
-
107
-Labels:
108
-
109
-| Label | Description |
110
-|:-----------|:----------------|
111
-| adapter_number | Adapter number |
112
-| battery_type | Battery type (e.g. BBU) |
113
-
114
-Metrics:
115
-
116
-| Metric | Dimensions | Unit |
117
-|:------|:----------|:----|
118
-| megacli.bbu_charge | charge | percentage |
119
-| megacli.bbu_recharge_cycles | recharge | cycles |
120
-| megacli.bbu_capacity_degradation | cap_degradation | percent |
121
-| megacli.bbu_temperature | temperature | Celsius |
122
-
123
-
124
-
125
-## Alerts
126
-
127
-
128
-The following alerts are available:
129
-
130
-| Alert name | On metric | Description |
131
-|:------------|:----------|:------------|
132
-| [ megacli_adapter_health_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.adapter_health_state | MegaCLI adapter ${label:adapter_number} is in the degraded state |
133
-| [ megacli_phys_drive_media_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.phys_drive_media_errors | MegaCLI physical drive adapter ${label:adapter_number} slot ${label:slot_number} media errors |
134
-| [ megacli_phys_drive_predictive_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.phys_drive_predictive_failures | MegaCLI physical drive (adapter ${label:adapter_number} slot ${label:slot_number}) predictive failures |
135
-| [ megacli_bbu_charge ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.bbu_charge | MegaCLI Backup Battery Unit (adapter ${label:adapter_number}) average charge over the last minute |
136
-| [ megacli_bbu_recharge_cycles ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.bbu_recharge_cycles | MegaCLI Backup Battery Unit (adapter ${label:adapter_number}) average charge over the last minute |
137
-
138
-
58
## Setup
59
60
@@ -230,6 +149,87 @@ jobs:
149
150
151
152
+## Alerts
153
+
154
+
155
+The following alerts are available:
156
+
157
+| Alert name | On metric | Description |
158
+|:------------|:----------|:------------|
159
+| [ megacli_adapter_health_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.adapter_health_state | MegaCLI adapter ${label:adapter_number} is in the degraded state |
160
+| [ megacli_phys_drive_media_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.phys_drive_media_errors | MegaCLI physical drive adapter ${label:adapter_number} slot ${label:slot_number} media errors |
161
+| [ megacli_phys_drive_predictive_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.phys_drive_predictive_failures | MegaCLI physical drive (adapter ${label:adapter_number} slot ${label:slot_number}) predictive failures |
162
+| [ megacli_bbu_charge ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.bbu_charge | MegaCLI Backup Battery Unit (adapter ${label:adapter_number}) average charge over the last minute |
163
+| [ megacli_bbu_recharge_cycles ](https://github.com/netdata/netdata/blob/master/src/health/health.d/megacli.conf) | megacli.bbu_recharge_cycles | MegaCLI Backup Battery Unit (adapter ${label:adapter_number}) average charge over the last minute |
164
+
165
+
166
+## Metrics
167
+
168
+Metrics grouped by *scope*.
169
+
170
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
171
+
172
+
173
+
174
+### Per adapter
175
+
176
+These metrics refer to the MegaCLI Adapter.
177
+
178
+Labels:
179
+
180
+| Label | Description |
181
+|:-----------|:----------------|
182
+| adapter_number | Adapter number |
183
+
184
+Metrics:
185
+
186
+| Metric | Dimensions | Unit |
187
+|:------|:----------|:----|
188
+| megacli.adapter_health_state | optimal, degraded, partially_degraded, failed | state |
189
+
190
+### Per physical drive
191
+
192
+These metrics refer to the MegaCLI Physical Drive.
193
+
194
+Labels:
195
+
196
+| Label | Description |
197
+|:-----------|:----------------|
198
+| adapter_number | Adapter number |
199
+| wwn | World Wide Name |
200
+| slot_number | Slot number |
201
+| drive_position | Position (e.g. DiskGroup: 0, Span: 0, Arm: 2) |
202
+| drive_type | Type (e.g. SATA) |
203
+
204
+Metrics:
205
+
206
+| Metric | Dimensions | Unit |
207
+|:------|:----------|:----|
208
+| megacli.phys_drive_media_errors_rate | media_errors | errors/s |
209
+| megacli.phys_drive_predictive_failures_rate | predictive_failures | failures/s |
210
+
211
+### Per backup battery unit
212
+
213
+These metrics refer to the MegaCLI Backup Battery Unit.
214
+
215
+Labels:
216
+
217
+| Label | Description |
218
+|:-----------|:----------------|
219
+| adapter_number | Adapter number |
220
+| battery_type | Battery type (e.g. BBU) |
221
+
222
+Metrics:
223
+
224
+| Metric | Dimensions | Unit |
225
+|:------|:----------|:----|
226
+| megacli.bbu_charge | charge | percentage |
227
+| megacli.bbu_recharge_cycles | recharge | cycles |
228
+| megacli.bbu_capacity_degradation | cap_degradation | percent |
229
+| megacli.bbu_temperature | temperature | Celsius |
230
+
231
+
232
+
233
## Troubleshooting
234
235
### Debug Mode
src/go/plugin/go.d/collector/memcached/integrations/memcached.md
+47
-47
@@ -45,53 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Memcached instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| memcached.cache | available, used | MiB |
67
-| memcached.net | in, out | kilobits/s |
68
-| memcached.connections | current, rejected, total | connections/s |
69
-| memcached.items | current, total | items |
70
-| memcached.evicted_reclaimed | reclaimed, evicted | items |
71
-| memcached.get | hints, misses | requests |
72
-| memcached.get_rate | rate | requests/s |
73
-| memcached.set_rate | rate | requests/s |
74
-| memcached.delete | hits, misses | requests |
75
-| memcached.cas | hits, misses, bad value | requests |
76
-| memcached.increment | hits, misses | requests |
77
-| memcached.decrement | hits, misses | requests |
78
-| memcached.touch | hits, misses | requests |
79
-| memcached.touch_rate | rate | requests/s |
80
-
81
-
82
-
83
-## Alerts
84
-
85
-
86
-The following alerts are available:
87
-
88
-| Alert name | On metric | Description |
89
-|:------------|:----------|:------------|
90
-| [ memcached_cache_memory_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memcached.conf) | memcached.cache | cache memory utilization |
91
-| [ memcached_cache_fill_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memcached.conf) | memcached.cache | average rate the cache fills up (positive), or frees up (negative) space over the last hour |
92
-| [ memcached_out_of_cache_space_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memcached.conf) | memcached.cache | estimated time the cache will run out of space if the system continues to add data at the same rate as the past hour |
93
-
94
-
48
## Setup
49
50
@@ -222,6 +175,53 @@ jobs:
175
176
177
178
+## Alerts
179
+
180
+
181
+The following alerts are available:
182
+
183
+| Alert name | On metric | Description |
184
+|:------------|:----------|:------------|
185
+| [ memcached_cache_memory_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memcached.conf) | memcached.cache | cache memory utilization |
186
+| [ memcached_cache_fill_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memcached.conf) | memcached.cache | average rate the cache fills up (positive), or frees up (negative) space over the last hour |
187
+| [ memcached_out_of_cache_space_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/memcached.conf) | memcached.cache | estimated time the cache will run out of space if the system continues to add data at the same rate as the past hour |
188
+
189
+
190
+## Metrics
191
+
192
+Metrics grouped by *scope*.
193
+
194
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
195
+
196
+
197
+
198
+### Per Memcached instance
199
+
200
+These metrics refer to the entire monitored application.
201
+
202
+This scope has no labels.
203
+
204
+Metrics:
205
+
206
+| Metric | Dimensions | Unit |
207
+|:------|:----------|:----|
208
+| memcached.cache | available, used | MiB |
209
+| memcached.net | in, out | kilobits/s |
210
+| memcached.connections | current, rejected, total | connections/s |
211
+| memcached.items | current, total | items |
212
+| memcached.evicted_reclaimed | reclaimed, evicted | items |
213
+| memcached.get | hints, misses | requests |
214
+| memcached.get_rate | rate | requests/s |
215
+| memcached.set_rate | rate | requests/s |
216
+| memcached.delete | hits, misses | requests |
217
+| memcached.cas | hits, misses, bad value | requests |
218
+| memcached.increment | hits, misses | requests |
219
+| memcached.decrement | hits, misses | requests |
220
+| memcached.touch | hits, misses | requests |
221
+| memcached.touch_rate | rate | requests/s |
222
+
223
+
224
+
225
## Troubleshooting
226
227
### Debug Mode
src/go/plugin/go.d/collector/mongodb/integrations/mongodb.md
+169
-169
@@ -51,6 +51,174 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
+## Setup
55
+
56
+
57
+You can configure the **mongodb** collector in two ways:
58
+
59
+| Method | Best for | How to |
60
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
61
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mongodb**, then click **+** to add a job. |
62
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mongodb.conf` and add a job. |
63
+
64
+:::important
65
+
66
+UI configuration requires paid Netdata Cloud plan.
67
+
68
+:::
69
+
70
+
71
+### Prerequisites
72
+
73
+#### Create a read-only user
74
+
75
+Create a read-only user for Netdata in the admin database.
76
+
77
+- Authenticate as the admin user:
78
+
79
+ ```bash
80
+ use admin
81
+ db.auth("admin", "<MONGODB_ADMIN_PASSWORD>")
82
+ ```
83
+
84
+- Create a user:
85
+
86
+ ```bash
87
+ db.createUser({
88
+ "user":"netdata",
89
+ "pwd": "<UNIQUE_PASSWORD>",
90
+ "roles" : [
91
+ {role: 'read', db: 'admin' },
92
+ {role: 'clusterMonitor', db: 'admin'},
93
+ {role: 'read', db: 'local' }
94
+ ]
95
+ })
96
+ ```
97
+
98
+
99
+
100
+### Configuration
101
+
102
+#### Options
103
+
104
+The following options can be defined globally: update_every, autodetection_retry.
105
+
106
+
107
+<details open><summary>Config options</summary>
108
+
109
+
110
+
111
+| Group | Option | Description | Default | Required |
112
+|:------|:-----|:------------|:--------|:---------:|
113
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
114
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
115
+| **Target** | uri | MongoDB connection string. See [URI syntax](https://www.mongodb.com/docs/manual/reference/connection-string/). | mongodb://localhost:27017 | yes |
116
+| | timeout | Query timeout (seconds). | 1 | no |
117
+| **Filters** | databases | Database selector. Defines which databases to collect metrics from. | | no |
118
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
119
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
120
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
121
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
122
+
123
+
124
+</details>
125
+
126
+
127
+#### via UI
128
+
129
+Configure the **mongodb** collector from the Netdata web interface:
130
+
131
+1. Go to **Nodes**.
132
+2. Select the node **where you want the mongodb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
133
+3. The **Collectors → Jobs** view opens by default.
134
+4. In the Search box, type _mongodb_ (or scroll the list) to locate the **mongodb** collector.
135
+5. Click the **+** next to the **mongodb** collector to add a new job.
136
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
137
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
138
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
139
+
140
+
141
+#### via File
142
+
143
+The configuration file name for this integration is `go.d/mongodb.conf`.
144
+
145
+The file format is YAML. Generally, the structure is:
146
+
147
+```yaml
148
+update_every: 1
149
+autodetection_retry: 0
150
+jobs:
151
+ - name: some_name1
152
+ - name: some_name2
153
+```
154
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
155
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
156
+
157
+```bash
158
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
159
+sudo ./edit-config go.d/mongodb.conf
160
+```
161
+
162
+##### Examples
163
+
164
+###### TCP socket
165
+
166
+An example configuration.
167
+
168
+<details open><summary>Config</summary>
169
+
170
+```yaml
171
+jobs:
172
+ - name: local
173
+ uri: mongodb://netdata:password@localhost:27017
174
+
175
+```
176
+</details>
177
+
178
+###### With databases metrics
179
+
180
+An example configuration.
181
+
182
+<details open><summary>Config</summary>
183
+
184
+```yaml
185
+jobs:
186
+ - name: local
187
+ uri: mongodb://netdata:password@localhost:27017
188
+ databases:
189
+ includes:
190
+ - "* *"
191
+
192
+```
193
+</details>
194
+
195
+###### Multi-instance
196
+
197
+> **Note**: When you define multiple jobs, their names must be unique.
198
+
199
+Local and remote instances.
200
+
201
+
202
+<details open><summary>Config</summary>
203
+
204
+```yaml
205
+jobs:
206
+ - name: local
207
+ uri: mongodb://netdata:password@localhost:27017
208
+
209
+ - name: remote
210
+ uri: mongodb://netdata:password@203.0.113.0:27017
211
+
212
+```
213
+</details>
214
+
215
+
216
+
217
+## Alerts
218
+
219
+There are no alerts configured by default for this integration.
220
+
221
+
222
## Metrics
223
224
Metrics grouped by *scope*.
@@ -204,7 +372,7 @@ Metrics:
372
373
374
207
-## Functions
375
+## Live Data
376
377
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
378
@@ -319,174 +487,6 @@ Profiled query statistics from `system.profile`. Each row represents a single pr
487
488
489
322
-## Alerts
323
-
324
-There are no alerts configured by default for this integration.
325
-
326
-
327
-## Setup
328
-
329
-
330
-You can configure the **mongodb** collector in two ways:
331
-
332
-| Method | Best for | How to |
333
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
334
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mongodb**, then click **+** to add a job. |
335
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mongodb.conf` and add a job. |
336
-
337
-:::important
338
-
339
-UI configuration requires paid Netdata Cloud plan.
340
-
341
-:::
342
-
343
-
344
-### Prerequisites
345
-
346
-#### Create a read-only user
347
-
348
-Create a read-only user for Netdata in the admin database.
349
-
350
-- Authenticate as the admin user:
351
-
352
- ```bash
353
- use admin
354
- db.auth("admin", "<MONGODB_ADMIN_PASSWORD>")
355
- ```
356
-
357
-- Create a user:
358
-
359
- ```bash
360
- db.createUser({
361
- "user":"netdata",
362
- "pwd": "<UNIQUE_PASSWORD>",
363
- "roles" : [
364
- {role: 'read', db: 'admin' },
365
- {role: 'clusterMonitor', db: 'admin'},
366
- {role: 'read', db: 'local' }
367
- ]
368
- })
369
- ```
370
-
371
-
372
-
373
-### Configuration
374
-
375
-#### Options
376
-
377
-The following options can be defined globally: update_every, autodetection_retry.
378
-
379
-
380
-<details open><summary>Config options</summary>
381
-
382
-
383
-
384
-| Group | Option | Description | Default | Required |
385
-|:------|:-----|:------------|:--------|:---------:|
386
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
387
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
388
-| **Target** | uri | MongoDB connection string. See [URI syntax](https://www.mongodb.com/docs/manual/reference/connection-string/). | mongodb://localhost:27017 | yes |
389
-| | timeout | Query timeout (seconds). | 1 | no |
390
-| **Filters** | databases | Database selector. Defines which databases to collect metrics from. | | no |
391
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
392
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
393
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
394
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
395
-
396
-
397
-</details>
398
-
399
-
400
-#### via UI
401
-
402
-Configure the **mongodb** collector from the Netdata web interface:
403
-
404
-1. Go to **Nodes**.
405
-2. Select the node **where you want the mongodb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
406
-3. The **Collectors → Jobs** view opens by default.
407
-4. In the Search box, type _mongodb_ (or scroll the list) to locate the **mongodb** collector.
408
-5. Click the **+** next to the **mongodb** collector to add a new job.
409
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
410
- - **Test** runs the job with the provided settings and shows whether data can be collected.
411
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
412
-
413
-
414
-#### via File
415
-
416
-The configuration file name for this integration is `go.d/mongodb.conf`.
417
-
418
-The file format is YAML. Generally, the structure is:
419
-
420
-```yaml
421
-update_every: 1
422
-autodetection_retry: 0
423
-jobs:
424
- - name: some_name1
425
- - name: some_name2
426
-```
427
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
428
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
429
-
430
-```bash
431
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
432
-sudo ./edit-config go.d/mongodb.conf
433
-```
434
-
435
-##### Examples
436
-
437
-###### TCP socket
438
-
439
-An example configuration.
440
-
441
-<details open><summary>Config</summary>
442
-
443
-```yaml
444
-jobs:
445
- - name: local
446
- uri: mongodb://netdata:password@localhost:27017
447
-
448
-```
449
-</details>
450
-
451
-###### With databases metrics
452
-
453
-An example configuration.
454
-
455
-<details open><summary>Config</summary>
456
-
457
-```yaml
458
-jobs:
459
- - name: local
460
- uri: mongodb://netdata:password@localhost:27017
461
- databases:
462
- includes:
463
- - "* *"
464
-
465
-```
466
-</details>
467
-
468
-###### Multi-instance
469
-
470
-> **Note**: When you define multiple jobs, their names must be unique.
471
-
472
-Local and remote instances.
473
-
474
-
475
-<details open><summary>Config</summary>
476
-
477
-```yaml
478
-jobs:
479
- - name: local
480
- uri: mongodb://netdata:password@localhost:27017
481
-
482
- - name: remote
483
- uri: mongodb://netdata:password@203.0.113.0:27017
484
-
485
-```
486
-</details>
487
-
488
-
489
-
490
## Troubleshooting
491
492
### Debug Mode
src/go/plugin/go.d/collector/monit/integrations/monit.md
+33
-33
@@ -50,39 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per service
62
-
63
-These metrics refer to the monitored Service.
64
-
65
-Labels:
66
-
67
-| Label | Description |
68
-|:-----------|:----------------|
69
-| server_hostname | Hostname of the Monit server. |
70
-| service_check_name | Service check name. |
71
-| service_check_type | Service check type. |
72
-
73
-Metrics:
74
-
75
-| Metric | Dimensions | Unit |
76
-|:------|:----------|:----|
77
-| monit.service_check_status | ok, error, initializing, not_monitored | status |
78
-
79
-
80
-
81
-## Alerts
82
-
83
-There are no alerts configured by default for this integration.
84
-
85
-
53
## Setup
54
55
@@ -235,6 +202,39 @@ jobs:
202
203
204
205
+## Alerts
206
+
207
+There are no alerts configured by default for this integration.
208
+
209
+
210
+## Metrics
211
+
212
+Metrics grouped by *scope*.
213
+
214
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
215
+
216
+
217
+
218
+### Per service
219
+
220
+These metrics refer to the monitored Service.
221
+
222
+Labels:
223
+
224
+| Label | Description |
225
+|:-----------|:----------------|
226
+| server_hostname | Hostname of the Monit server. |
227
+| service_check_name | Service check name. |
228
+| service_check_type | Service check type. |
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| monit.service_check_status | ok, error, initializing, not_monitored | status |
235
+
236
+
237
+
238
## Troubleshooting
239
240
### Debug Mode
src/go/plugin/go.d/collector/mssql/integrations/microsoft_sql_server.md
renamed
+475
-467
@@ -85,309 +85,598 @@ The collector executes lightweight queries against system views.
85
Most queries complete in milliseconds and have minimal impact on server performance.
86
87
88
-## Metrics
88
+## Setup
89
90
-Metrics grouped by *scope*.
90
92
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
91
+You can configure the **mssql** collector in two ways:
92
93
+| Method | Best for | How to |
94
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
95
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mssql**, then click **+** to add a job. |
96
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mssql.conf` and add a job. |
97
98
+:::important
99
96
-### Per Microsoft SQL Server instance
100
+UI configuration requires paid Netdata Cloud plan.
101
98
-These metrics refer to the entire SQL Server instance.
102
+:::
103
100
-This scope has no labels.
104
102
-Metrics:
105
+### Prerequisites
106
104
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
105
-|:------|:----------|:----|:---:|:---:|
106
-| mssql.user_connections | user | connections | • | • |
107
-| mssql.session_connections | user, internal | connections | • | • |
108
-| mssql.blocked_processes | blocked | processes | • | • |
109
-| mssql.batch_requests | batch | requests/s | • | • |
110
-| mssql.compilations | compilations | compilations/s | • | • |
111
-| mssql.recompilations | recompilations | recompilations/s | • | • |
112
-| mssql.auto_param_attempts | total, safe, failed | attempts/s | • | • |
113
-| mssql.sql_errors | errors | errors/s | • | • |
114
-| mssql.buffer_cache_hit_ratio | hit_ratio | percentage | • | • |
115
-| mssql.buffer_page_life_expectancy | life_expectancy | seconds | • | • |
116
-| mssql.buffer_page_iops | read, written | pages/s | • | • |
117
-| mssql.buffer_checkpoint_pages | flushed | pages/s | • | • |
118
-| mssql.buffer_page_lookups | lookups | lookups/s | • | • |
119
-| mssql.buffer_lazy_writes | lazy_writes | writes/s | • | • |
120
-| mssql.memory_total | memory | bytes | • | • |
121
-| mssql.memory_connection | memory | bytes | • | • |
122
-| mssql.memory_pending_grants | pending | processes | • | • |
123
-| mssql.memory_external_benefit | benefit | benefit | • | • |
124
-| mssql.page_splits | page | splits/s | • | • |
125
-| mssql.process_memory_resident | resident | bytes | • | • |
126
-| mssql.process_memory_virtual | virtual | bytes | • | • |
127
-| mssql.process_memory_utilization | utilization | percentage | • | • |
128
-| mssql.process_page_faults | page_faults | faults | • | • |
129
-| mssql.os_memory | used, available | bytes | • | • |
130
-| mssql.os_pagefile | used, available | bytes | • | • |
107
+#### Create monitoring user
108
132
-### Per database
109
+Create a SQL Server login with VIEW SERVER STATE permission:
110
134
-These metrics refer to individual databases.
111
+```sql
112
+-- Create login
113
+CREATE LOGIN netdata_user WITH PASSWORD = 'YourStrongPassword!';
114
136
-Labels:
115
+-- Grant VIEW SERVER STATE (required for DMVs)
116
+GRANT VIEW SERVER STATE TO netdata_user;
117
138
-| Label | Description |
139
-|:-----------|:----------------|
140
-| database | Database name |
118
+-- Grant VIEW ANY DEFINITION (required for Always On AG monitoring)
119
+GRANT VIEW ANY DEFINITION TO netdata_user;
120
142
-Metrics:
121
+-- Grant VIEW SERVER PERFORMANCE STATE (required for HADR DMVs on SQL Server 2022+)
122
+-- GRANT VIEW SERVER PERFORMANCE STATE TO netdata_user;
123
144
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
145
-|:------|:----------|:----|:---:|:---:|
146
-| mssql.database_active_transactions | active | transactions | • | • |
147
-| mssql.database_transactions | transactions | transactions/s | • | • |
148
-| mssql.database_write_transactions | write | transactions/s | • | • |
149
-| mssql.database_log_flushes | flushes | flushes/s | • | • |
150
-| mssql.database_log_flushed | flushed | bytes/s | • | • |
151
-| mssql.database_log_growths | growths | growths | • | • |
152
-| mssql.database_io_stall | read, write | ms | • | • |
153
-| mssql.database_data_file_size | size | bytes | • | • |
154
-| mssql.database_backup_restore_throughput | throughput | bytes/s | • | • |
155
-| mssql.database_state | online, restoring, recovering, pending, suspect, emergency, offline | state | • | • |
156
-| mssql.database_read_only | read_only, read_write | status | • | • |
124
+-- Grant access to msdb for SQL Agent job monitoring (required)
125
+USE msdb;
126
+CREATE USER netdata_user FOR LOGIN netdata_user;
127
+GRANT SELECT ON dbo.sysjobs TO netdata_user;
128
158
-### Per lock stats
129
+-- Optional: Grant access to distribution database for replication monitoring
130
+-- (only if replication is configured)
131
+USE distribution;
132
+CREATE USER netdata_user FOR LOGIN netdata_user;
133
+GRANT SELECT ON dbo.MSreplication_monitordata TO netdata_user;
134
+GRANT SELECT ON dbo.MSpublications TO netdata_user;
135
+GRANT SELECT ON dbo.MSsubscriptions TO netdata_user;
136
+```
137
160
-These metrics refer to lock statistics by lock resource type (from performance counters).
138
+**Required permissions:**
139
+- `VIEW SERVER STATE` - Access to dynamic management views
140
+- `SELECT on msdb.dbo.sysjobs` - SQL Agent job status monitoring
141
162
-Labels:
142
+**Optional permissions:**
143
+- `VIEW ANY DEFINITION` - Always On Availability Group monitoring
144
+- `VIEW SERVER PERFORMANCE STATE` - HADR DMVs on SQL Server 2022+
145
+- `SELECT on distribution.dbo.MSreplication_monitordata` - Replication monitoring
146
+- `SELECT on distribution.dbo.MSpublications` - Publication information
147
+- `SELECT on distribution.dbo.MSsubscriptions` - Subscription counts
148
164
-| Label | Description |
165
-|:-----------|:----------------|
166
-| resource | Lock resource type (Database, File, Object, Page, Key, Extent, RID, HoBT, etc.) |
149
168
-Metrics:
150
170
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
171
-|:------|:----------|:----|:---:|:---:|
172
-| mssql.lock_stats_deadlocks | deadlocks | deadlocks/s | • | • |
173
-| mssql.lock_stats_waits | waits | waits/s | • | • |
174
-| mssql.lock_stats_timeouts | timeouts | timeouts/s | • | • |
175
-| mssql.lock_stats_requests | requests | requests/s | • | • |
151
+### Configuration
152
177
-### Per lock resource
153
+#### Options
154
179
-These metrics refer to lock resource types (from sys.dm_tran_locks).
155
+The following options can be defined globally: update_every, autodetection_retry.
156
181
-Labels:
157
183
-| Label | Description |
184
-|:-----------|:----------------|
185
-| resource | Lock resource type (Database, File, Object, Page, Key, etc.) |
158
+<details open><summary>Config options</summary>
159
187
-Metrics:
160
189
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
190
-|:------|:----------|:----|:---:|:---:|
191
-| mssql.locks_by_resource | locks | locks | • | • |
161
193
-### Per wait type
162
+| Group | Option | Description | Default | Required |
163
+|:------|:-----|:------------|:--------|:---------:|
164
+| **Collection** | update_every | Data collection interval (seconds). | 10 | no |
165
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
166
+| **Target** | dsn | SQL Server DSN (Data Source Name). See [DSN syntax](https://github.com/microsoft/go-mssqldb#connection-parameters-and-dsn). When `cloud_auth.provider` is `azure_ad`, use URL format with `sqlserver://` scheme. | sqlserver://localhost:1433 | yes |
167
+| **Cloud Auth** | cloud_auth.provider | Cloud auth provider (`none` or `azure_ad`). | none | no |
168
+| **Cloud Auth/Azure** | cloud_auth.azure_ad.mode | Azure AD credential mode (`service_principal`, `managed_identity`, or `default`). Required when `cloud_auth.provider` is `azure_ad`. | | yes |
169
+| | cloud_auth.azure_ad.mode_service_principal.tenant_id | Azure tenant ID. Required for `service_principal` mode. | | no |
170
+| | cloud_auth.azure_ad.mode_service_principal.client_id | Azure client ID. Required for `service_principal` mode. | | no |
171
+| | cloud_auth.azure_ad.mode_service_principal.client_secret | Azure client secret for `service_principal` mode. | | no |
172
+| | cloud_auth.azure_ad.mode_managed_identity.client_id | Optional client ID of a user-assigned managed identity (`managed_identity` mode). | | no |
173
+| **Target** | timeout | Query timeout (seconds). | 5 | no |
174
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
175
+| | functions.top_queries.timeout | Query timeout for top-queries function (seconds). Uses collector timeout if not set. | | no |
176
+| | functions.top_queries.limit | Maximum number of queries to return in the top-queries response. | 500 | no |
177
+| | functions.top_queries.time_window_days | Number of days of Query Store data to analyze. Set to 0 to include all available data. Smaller values improve query performance but show less history. | 7 | no |
178
+| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
179
+| | functions.deadlock_info.timeout | Query timeout for deadlock-info function (seconds). Uses collector timeout if not set. | | no |
180
+| | functions.deadlock_info.use_ring_buffer | Use ring_buffer instead of event_file for system_health session.<br/><br/>WARNING: Not recommended for production:<br/>• Data cleared on failover/restart<br/>• 4 MB capacity limit<br/>• High CPU load during queries<br/><br/>Use only for Azure SQL Database without Blob Storage or testing. | no | no |
181
+| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
182
+| | functions.error_info.timeout | Query timeout for error-info function (seconds). Uses collector timeout if not set. | | no |
183
+| | functions.error_info.session_name | Extended Events session name capturing error_reported events.<br/>Must be created by administrator with event_file (recommended) or ring_buffer target. | netdata_errors | no |
184
+| | functions.error_info.use_ring_buffer | Use ring_buffer instead of event_file for error events.<br/><br/>WARNING: Not recommended for production:<br/>• Data cleared on failover/restart<br/>• 4 MB capacity limit<br/>• High CPU load during queries<br/><br/>Use only for Azure SQL Database without Blob Storage or testing. | no | no |
185
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
186
195
-These metrics refer to individual wait types (from sys.dm_os_wait_stats).
187
197
-Labels:
188
+</details>
189
199
-| Label | Description |
200
-|:-----------|:----------------|
201
-| wait_type | Wait type name |
202
-| wait_category | Wait category (CPU, Lock, Latch, Buffer IO, etc.) |
190
204
-Metrics:
191
+#### via UI
192
206
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
207
-|:------|:----------|:----|:---:|:---:|
208
-| mssql.wait_total_time | duration | ms | • | • |
209
-| mssql.wait_resource_time | duration | ms | • | • |
210
-| mssql.wait_signal_time | duration | ms | • | • |
211
-| mssql.wait_max_time | max_time | ms | • | • |
212
-| mssql.wait_count | waits | waits/s | • | • |
193
+Configure the **mssql** collector from the Netdata web interface:
194
214
-### Per job
195
+1. Go to **Nodes**.
196
+2. Select the node **where you want the mssql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
197
+3. The **Collectors → Jobs** view opens by default.
198
+4. In the Search box, type _mssql_ (or scroll the list) to locate the **mssql** collector.
199
+5. Click the **+** next to the **mssql** collector to add a new job.
200
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
201
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
202
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
203
216
-These metrics refer to SQL Server Agent jobs.
204
218
-Labels:
205
+#### via File
206
220
-| Label | Description |
221
-|:-----------|:----------------|
222
-| job_name | Job name |
207
+The configuration file name for this integration is `go.d/mssql.conf`.
208
224
-Metrics:
209
+The file format is YAML. Generally, the structure is:
210
226
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
227
-|:------|:----------|:----|:---:|:---:|
228
-| mssql.job_status | enabled, disabled | status | • | • |
211
+```yaml
212
+update_every: 1
213
+autodetection_retry: 0
214
+jobs:
215
+ - name: some_name1
216
+ - name: some_name2
217
+```
218
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
219
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
220
230
-### Per replication
221
+```bash
222
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
223
+sudo ./edit-config go.d/mssql.conf
224
+```
225
232
-These metrics refer to SQL Server replication publications.
226
+##### Examples
227
234
-Labels:
228
+###### Basic configuration
229
236
-| Label | Description |
237
-|:-----------|:----------------|
238
-| publisher_db | Publisher database name |
239
-| publication | Publication name |
230
+Connect to local SQL Server with SQL authentication.
231
241
-Metrics:
232
+<details open><summary>Config</summary>
233
243
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
244
-|:------|:----------|:----|:---:|:---:|
245
-| mssql.replication_status | started, succeeded, in_progress, idle, retrying, failed | status | • | • |
246
-| mssql.replication_warning | expiration, latency, merge_expiration, merge_slow_duration, merge_fast_duration, merge_fast_speed, merge_slow_speed | flags | • | • |
247
-| mssql.replication_latency | average, best, worst | seconds | • | • |
248
-| mssql.replication_subscriptions | total, agents_running | subscriptions | • | • |
234
+```yaml
235
+jobs:
236
+ - name: local
237
+ dsn: "sqlserver://netdata_user:password@localhost:1433"
238
250
-### Per availability group
239
+```
240
+</details>
241
252
-These metrics refer to Always On Availability Groups. Auto-detected when HADR is enabled.
242
+###### Windows Authentication
243
254
-Labels:
244
+Connect using Windows integrated authentication.
245
256
-| Label | Description |
257
-|:-----------|:----------------|
258
-| ag_name | Availability group name |
246
+<details open><summary>Config</summary>
247
260
-Metrics:
248
+```yaml
249
+jobs:
250
+ - name: local
251
+ dsn: "sqlserver://localhost:1433?trusted_connection=yes"
252
262
-| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
263
-|:------|:----------|:----|:---:|:---:|
264
-| mssql.ag_sync_health | not_healthy, partially_healthy, healthy | state | • | • |
265
-| mssql.ag_recovery_health | primary_online, primary_in_progress, secondary_online, secondary_in_progress | state | • | • |
266
-| mssql.ag_threads | capture, redo, parallel_redo | threads | • | • |
253
+```
254
+</details>
255
268
-### Per availability group replica
256
+###### Named instance
257
270
-These metrics refer to per-replica state within an Availability Group. Note: on secondary replicas, the replica states DMV returns only local information.
258
+Connect to a named SQL Server instance.
259
272
-Labels:
260
+<details open><summary>Config</summary>
261
274
-| Label | Description |
275
-|:-----------|:----------------|
276
-| ag_name | Availability group name |
277
-| replica_server | Replica server name |
278
-| availability_mode | Availability mode (synchronous_commit or asynchronous_commit) |
279
-| failover_mode | Failover mode (automatic or manual) |
262
+```yaml
263
+jobs:
264
+ - name: named_instance
265
+ dsn: "sqlserver://netdata_user:password@localhost/INSTANCENAME"
266
+
267
+```
268
+</details>
269
+
270
+###### Remote server
271
+
272
+Connect to a remote SQL Server.
273
+
274
+<details open><summary>Config</summary>
275
+
276
+```yaml
277
+jobs:
278
+ - name: remote
279
+ dsn: "sqlserver://netdata_user:password@192.168.1.100:1433"
280
+
281
+```
282
+</details>
283
+
284
+###### Azure SQL with service principal
285
+
286
+Use Microsoft Entra service principal authentication for Azure SQL.
287
+
288
+<details open><summary>Config</summary>
289
+
290
+```yaml
291
+jobs:
292
+ - name: azure_sql_sp
293
+ dsn: "sqlserver://my-server.database.windows.net:1433?database=mydb"
294
+ cloud_auth:
295
+ provider: azure_ad
296
+ azure_ad:
297
+ mode: service_principal
298
+ mode_service_principal:
299
+ tenant_id: "00000000-0000-0000-0000-000000000000"
300
+ client_id: "11111111-1111-1111-1111-111111111111"
301
+ client_secret: "super-secret-value"
302
+
303
+```
304
+</details>
305
+
306
+###### Azure SQL with managed identity
307
+
308
+Use managed identity authentication (system-assigned by default).
309
+
310
+<details open><summary>Config</summary>
311
+
312
+```yaml
313
+jobs:
314
+ - name: azure_sql_mi
315
+ dsn: "sqlserver://my-server.database.windows.net:1433?database=mydb"
316
+ cloud_auth:
317
+ provider: azure_ad
318
+ azure_ad:
319
+ mode: managed_identity
320
+
321
+```
322
+</details>
323
+
324
+###### Multi-instance
325
+
326
+> **Note**: When you define multiple jobs, their names must be unique.
327
+
328
+Monitoring multiple SQL Server instances.
329
+
330
+
331
+<details open><summary>Config</summary>
332
+
333
+```yaml
334
+jobs:
335
+ - name: production
336
+ dsn: "sqlserver://netdata_user:password@prod-sql:1433"
337
+
338
+ - name: development
339
+ dsn: "sqlserver://netdata_user:password@dev-sql:1433"
340
+
341
+```
342
+</details>
343
+
344
+###### With custom function settings
345
+
346
+Configure function-specific settings like timeouts and limits.
347
+
348
+> **Warning**: Query Store may contain unmasked literal values (PII).
349
+> Disable functions if not needed or ensure proper access controls.
350
+
351
+
352
+<details open><summary>Config</summary>
353
+
354
+```yaml
355
+jobs:
356
+ - name: local
357
+ dsn: "sqlserver://netdata_user:password@localhost:1433"
358
+ functions:
359
+ top_queries:
360
+ limit: 100
361
+ time_window_days: 7
362
+ deadlock_info:
363
+ use_ring_buffer: true
364
+ error_info:
365
+ session_name: custom_errors
366
+
367
+```
368
+</details>
369
+
370
+
371
+
372
+## Alerts
373
+
374
+There are no alerts configured by default for this integration.
375
+
376
+
377
+## Metrics
378
+
379
+Metrics grouped by *scope*.
380
+
381
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
382
+
383
+
384
+
385
+### Per Microsoft SQL Server instance
386
+
387
+These metrics refer to the entire SQL Server instance.
388
+
389
+This scope has no labels.
390
391
Metrics:
392
393
| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
394
|:------|:----------|:----|:---:|:---:|
285
-| mssql.ag_replica_role | primary, secondary, resolving, unknown | state | • | • |
286
-| mssql.ag_replica_connected_state | connected, disconnected, unknown | state | • | • |
287
-| mssql.ag_replica_sync_health | not_healthy, partially_healthy, healthy | state | • | • |
395
+| mssql.user_connections | user | connections | • | • |
396
+| mssql.session_connections | user, internal | connections | • | • |
397
+| mssql.blocked_processes | blocked | processes | • | • |
398
+| mssql.batch_requests | batch | requests/s | • | • |
399
+| mssql.compilations | compilations | compilations/s | • | • |
400
+| mssql.recompilations | recompilations | recompilations/s | • | • |
401
+| mssql.auto_param_attempts | total, safe, failed | attempts/s | • | • |
402
+| mssql.sql_errors | errors | errors/s | • | • |
403
+| mssql.buffer_cache_hit_ratio | hit_ratio | percentage | • | • |
404
+| mssql.buffer_page_life_expectancy | life_expectancy | seconds | • | • |
405
+| mssql.buffer_page_iops | read, written | pages/s | • | • |
406
+| mssql.buffer_checkpoint_pages | flushed | pages/s | • | • |
407
+| mssql.buffer_page_lookups | lookups | lookups/s | • | • |
408
+| mssql.buffer_lazy_writes | lazy_writes | writes/s | • | • |
409
+| mssql.memory_total | memory | bytes | • | • |
410
+| mssql.memory_connection | memory | bytes | • | • |
411
+| mssql.memory_pending_grants | pending | processes | • | • |
412
+| mssql.memory_external_benefit | benefit | benefit | • | • |
413
+| mssql.page_splits | page | splits/s | • | • |
414
+| mssql.process_memory_resident | resident | bytes | • | • |
415
+| mssql.process_memory_virtual | virtual | bytes | • | • |
416
+| mssql.process_memory_utilization | utilization | percentage | • | • |
417
+| mssql.process_page_faults | page_faults | faults | • | • |
418
+| mssql.os_memory | used, available | bytes | • | • |
419
+| mssql.os_pagefile | used, available | bytes | • | • |
420
289
-### Per availability group database replica
421
+### Per database
422
291
-These metrics refer to per-database synchronization within an Availability Group.
423
+These metrics refer to individual databases.
424
425
Labels:
426
427
| Label | Description |
428
|:-----------|:----------------|
297
-| ag_name | Availability group name |
298
-| replica_server | Replica server name |
429
| database | Database name |
430
431
Metrics:
432
433
| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
434
|:------|:----------|:----|:---:|:---:|
305
-| mssql.ag_db_sync_state | not_synchronizing, synchronizing, synchronized, reverting, initializing | state | • | • |
306
-| mssql.ag_db_log_send_queue | queue_size | bytes | • | • |
307
-| mssql.ag_db_log_send_rate | send_rate | bytes/s | • | • |
308
-| mssql.ag_db_redo_queue | queue_size | bytes | • | • |
309
-| mssql.ag_db_redo_rate | redo_rate | bytes/s | • | • |
310
-| mssql.ag_db_filestream_send_rate | send_rate | bytes/s | • | • |
311
-| mssql.ag_db_secondary_lag | lag | seconds | • | • |
312
-| mssql.ag_db_suspended | active, suspended | state | • | • |
313
-| mssql.ag_db_failover_readiness | ready, not_ready | state | • | • |
314
-| mssql.ag_db_joined_state | joined, not_joined | state | • | • |
435
+| mssql.database_active_transactions | active | transactions | • | • |
436
+| mssql.database_transactions | transactions | transactions/s | • | • |
437
+| mssql.database_write_transactions | write | transactions/s | • | • |
438
+| mssql.database_log_flushes | flushes | flushes/s | • | • |
439
+| mssql.database_log_flushed | flushed | bytes/s | • | • |
440
+| mssql.database_log_growths | growths | growths | • | • |
441
+| mssql.database_io_stall | read, write | ms | • | • |
442
+| mssql.database_data_file_size | size | bytes | • | • |
443
+| mssql.database_backup_restore_throughput | throughput | bytes/s | • | • |
444
+| mssql.database_state | online, restoring, recovering, pending, suspect, emergency, offline | state | • | • |
445
+| mssql.database_read_only | read_only, read_write | status | • | • |
446
316
-### Per WSFC cluster
447
+### Per lock stats
448
318
-These metrics refer to the Windows Server Failover Clustering quorum state.
449
+These metrics refer to lock statistics by lock resource type (from performance counters).
450
320
-This scope has no labels.
451
+Labels:
452
+
453
+| Label | Description |
454
+|:-----------|:----------------|
455
+| resource | Lock resource type (Database, File, Object, Page, Key, Extent, RID, HoBT, etc.) |
456
457
Metrics:
458
459
| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
460
|:------|:----------|:----|:---:|:---:|
326
-| mssql.ag_cluster_quorum_state | normal, forced, unknown | state | • | • |
461
+| mssql.lock_stats_deadlocks | deadlocks | deadlocks/s | • | • |
462
+| mssql.lock_stats_waits | waits | waits/s | • | • |
463
+| mssql.lock_stats_timeouts | timeouts | timeouts/s | • | • |
464
+| mssql.lock_stats_requests | requests | requests/s | • | • |
465
328
-### Per WSFC cluster member
466
+### Per lock resource
467
330
-These metrics refer to individual WSFC cluster members.
468
+These metrics refer to lock resource types (from sys.dm_tran_locks).
469
470
Labels:
471
472
| Label | Description |
473
|:-----------|:----------------|
336
-| cluster_member | Cluster member name |
474
+| resource | Lock resource type (Database, File, Object, Page, Key, etc.) |
475
476
Metrics:
477
478
| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
479
|:------|:----------|:----|:---:|:---:|
342
-| mssql.ag_cluster_member_state | up, down | state | • | • |
343
-| mssql.ag_cluster_member_quorum_votes | votes | votes | • | • |
480
+| mssql.locks_by_resource | locks | locks | • | • |
481
345
-### Per AG page repair
482
+### Per wait type
483
347
-These metrics refer to automatic page repair events per database in an Availability Group.
484
+These metrics refer to individual wait types (from sys.dm_os_wait_stats).
485
486
Labels:
487
488
| Label | Description |
489
|:-----------|:----------------|
353
-| database | Database name |
490
+| wait_type | Wait type name |
491
+| wait_category | Wait category (CPU, Lock, Latch, Buffer IO, etc.) |
492
493
Metrics:
494
495
| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
496
|:------|:----------|:----|:---:|:---:|
359
-| mssql.ag_page_repair | successful, failed | repairs | • | • |
360
-
497
+| mssql.wait_total_time | duration | ms | • | • |
498
+| mssql.wait_resource_time | duration | ms | • | • |
499
+| mssql.wait_signal_time | duration | ms | • | • |
500
+| mssql.wait_max_time | max_time | ms | • | • |
501
+| mssql.wait_count | waits | waits/s | • | • |
502
503
+### Per job
504
363
-## Functions
505
+These metrics refer to SQL Server Agent jobs.
506
365
-This collector exposes real-time functions for interactive troubleshooting in the Live tab.
507
+Labels:
508
509
+| Label | Description |
510
+|:-----------|:----------------|
511
+| job_name | Job name |
512
368
-### Top Queries
513
+Metrics:
514
370
-Retrieves aggregated SQL query performance metrics from Microsoft SQL Server [Query Store](https://learn.microsoft.com/en-us/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store) runtime statistics.
515
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
516
+|:------|:----------|:----|:---:|:---:|
517
+| mssql.job_status | enabled, disabled | status | • | • |
518
372
-This function queries `sys.query_store_runtime_stats` and related views across all databases with Query Store enabled, aggregating execution statistics by query hash. It provides comprehensive timing, I/O, memory, and parallelism metrics.
519
+### Per replication
520
374
-Use cases:
375
-- Identify slow or resource-intensive queries consuming excessive CPU time or memory
376
-- Analyze I/O patterns (logical reads, physical reads, writes) to detect bottlenecks
377
-- Monitor parallelism (DOP) and tempdb usage for capacity planning
521
+These metrics refer to SQL Server replication publications.
522
379
-Query text is truncated at 4096 characters for display purposes. Columns are dynamically detected based on SQL Server version (some metrics only available in 2016+/2017+).
523
+Labels:
524
525
+| Label | Description |
526
+|:-----------|:----------------|
527
+| publisher_db | Publisher database name |
528
+| publication | Publication name |
529
382
-| Aspect | Description |
383
-|:-------|:------------|
384
-| Name | `Mssql:top-queries` |
385
-| Require Cloud | yes |
386
-| Performance | Executes dynamic SQL to aggregate Query Store data across all enabled databases:<br/>• Execution time depends on Query Store workload and number of monitored databases<br/>• Default limit of 500 rows balances completeness with performance |
387
-| Security | Query text may contain unmasked literal values including potentially sensitive data:<br/>• Personal information in WHERE clauses or INSERT values<br/>• Business data and internal identifiers<br/>• Access should be restricted to authorized personnel only |
388
-| Availability | Available when:<br/>• The collector has successfully connected to SQL Server<br/>• Query Store is enabled on at least one user database<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the query fails<br/>• Returns HTTP 504 if the query times out |
530
+Metrics:
531
+
532
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
533
+|:------|:----------|:----|:---:|:---:|
534
+| mssql.replication_status | started, succeeded, in_progress, idle, retrying, failed | status | • | • |
535
+| mssql.replication_warning | expiration, latency, merge_expiration, merge_slow_duration, merge_fast_duration, merge_fast_speed, merge_slow_speed | flags | • | • |
536
+| mssql.replication_latency | average, best, worst | seconds | • | • |
537
+| mssql.replication_subscriptions | total, agents_running | subscriptions | • | • |
538
+
539
+### Per availability group
540
+
541
+These metrics refer to Always On Availability Groups. Auto-detected when HADR is enabled.
542
+
543
+Labels:
544
+
545
+| Label | Description |
546
+|:-----------|:----------------|
547
+| ag_name | Availability group name |
548
+
549
+Metrics:
550
+
551
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
552
+|:------|:----------|:----|:---:|:---:|
553
+| mssql.ag_sync_health | not_healthy, partially_healthy, healthy | state | • | • |
554
+| mssql.ag_recovery_health | primary_online, primary_in_progress, secondary_online, secondary_in_progress | state | • | • |
555
+| mssql.ag_threads | capture, redo, parallel_redo | threads | • | • |
556
+
557
+### Per availability group replica
558
+
559
+These metrics refer to per-replica state within an Availability Group. Note: on secondary replicas, the replica states DMV returns only local information.
560
+
561
+Labels:
562
+
563
+| Label | Description |
564
+|:-----------|:----------------|
565
+| ag_name | Availability group name |
566
+| replica_server | Replica server name |
567
+| availability_mode | Availability mode (synchronous_commit or asynchronous_commit) |
568
+| failover_mode | Failover mode (automatic or manual) |
569
+
570
+Metrics:
571
+
572
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
573
+|:------|:----------|:----|:---:|:---:|
574
+| mssql.ag_replica_role | primary, secondary, resolving, unknown | state | • | • |
575
+| mssql.ag_replica_connected_state | connected, disconnected, unknown | state | • | • |
576
+| mssql.ag_replica_sync_health | not_healthy, partially_healthy, healthy | state | • | • |
577
+
578
+### Per availability group database replica
579
+
580
+These metrics refer to per-database synchronization within an Availability Group.
581
+
582
+Labels:
583
+
584
+| Label | Description |
585
+|:-----------|:----------------|
586
+| ag_name | Availability group name |
587
+| replica_server | Replica server name |
588
+| database | Database name |
589
+
590
+Metrics:
591
+
592
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
593
+|:------|:----------|:----|:---:|:---:|
594
+| mssql.ag_db_sync_state | not_synchronizing, synchronizing, synchronized, reverting, initializing | state | • | • |
595
+| mssql.ag_db_log_send_queue | queue_size | bytes | • | • |
596
+| mssql.ag_db_log_send_rate | send_rate | bytes/s | • | • |
597
+| mssql.ag_db_redo_queue | queue_size | bytes | • | • |
598
+| mssql.ag_db_redo_rate | redo_rate | bytes/s | • | • |
599
+| mssql.ag_db_filestream_send_rate | send_rate | bytes/s | • | • |
600
+| mssql.ag_db_secondary_lag | lag | seconds | • | • |
601
+| mssql.ag_db_suspended | active, suspended | state | • | • |
602
+| mssql.ag_db_failover_readiness | ready, not_ready | state | • | • |
603
+| mssql.ag_db_joined_state | joined, not_joined | state | • | • |
604
+
605
+### Per WSFC cluster
606
+
607
+These metrics refer to the Windows Server Failover Clustering quorum state.
608
+
609
+This scope has no labels.
610
+
611
+Metrics:
612
+
613
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
614
+|:------|:----------|:----|:---:|:---:|
615
+| mssql.ag_cluster_quorum_state | normal, forced, unknown | state | • | • |
616
+
617
+### Per WSFC cluster member
618
+
619
+These metrics refer to individual WSFC cluster members.
620
+
621
+Labels:
622
+
623
+| Label | Description |
624
+|:-----------|:----------------|
625
+| cluster_member | Cluster member name |
626
+
627
+Metrics:
628
+
629
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
630
+|:------|:----------|:----|:---:|:---:|
631
+| mssql.ag_cluster_member_state | up, down | state | • | • |
632
+| mssql.ag_cluster_member_quorum_votes | votes | votes | • | • |
633
+
634
+### Per AG page repair
635
+
636
+These metrics refer to automatic page repair events per database in an Availability Group.
637
+
638
+Labels:
639
+
640
+| Label | Description |
641
+|:-----------|:----------------|
642
+| database | Database name |
643
+
644
+Metrics:
645
+
646
+| Metric | Dimensions | Unit | SQL Server 2016+ | Azure SQL Database |
647
+|:------|:----------|:----|:---:|:---:|
648
+| mssql.ag_page_repair | successful, failed | repairs | • | • |
649
+
650
+
651
+
652
+## Live Data
653
+
654
+This collector exposes real-time functions for interactive troubleshooting in the Live tab.
655
+
656
+
657
+### Top Queries
658
+
659
+Retrieves aggregated SQL query performance metrics from Microsoft SQL Server [Query Store](https://learn.microsoft.com/en-us/sql/relational-databases/performance/monitoring-performance-by-using-the-query-store) runtime statistics.
660
+
661
+This function queries `sys.query_store_runtime_stats` and related views across all databases with Query Store enabled, aggregating execution statistics by query hash. It provides comprehensive timing, I/O, memory, and parallelism metrics.
662
+
663
+Use cases:
664
+- Identify slow or resource-intensive queries consuming excessive CPU time or memory
665
+- Analyze I/O patterns (logical reads, physical reads, writes) to detect bottlenecks
666
+- Monitor parallelism (DOP) and tempdb usage for capacity planning
667
+
668
+Query text is truncated at 4096 characters for display purposes. Columns are dynamically detected based on SQL Server version (some metrics only available in 2016+/2017+).
669
390
-#### Prerequisites
670
+
671
+| Aspect | Description |
672
+|:-------|:------------|
673
+| Name | `Mssql:top-queries` |
674
+| Require Cloud | yes |
675
+| Performance | Executes dynamic SQL to aggregate Query Store data across all enabled databases:<br/>• Execution time depends on Query Store workload and number of monitored databases<br/>• Default limit of 500 rows balances completeness with performance |
676
+| Security | Query text may contain unmasked literal values including potentially sensitive data:<br/>• Personal information in WHERE clauses or INSERT values<br/>• Business data and internal identifiers<br/>• Access should be restricted to authorized personnel only |
677
+| Availability | Available when:<br/>• The collector has successfully connected to SQL Server<br/>• Query Store is enabled on at least one user database<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the query fails<br/>• Returns HTTP 504 if the query times out |
678
+
679
+#### Prerequisites
680
681
##### Enable Query Store
682
@@ -632,295 +921,6 @@ Recent error events from the configured Extended Events session.
921
922
923
635
-## Alerts
636
-
637
-There are no alerts configured by default for this integration.
638
-
639
-
640
-## Setup
641
-
642
-
643
-You can configure the **mssql** collector in two ways:
644
-
645
-| Method | Best for | How to |
646
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
647
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mssql**, then click **+** to add a job. |
648
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mssql.conf` and add a job. |
649
-
650
-:::important
651
-
652
-UI configuration requires paid Netdata Cloud plan.
653
-
654
-:::
655
-
656
-
657
-### Prerequisites
658
-
659
-#### Create monitoring user
660
-
661
-Create a SQL Server login with VIEW SERVER STATE permission:
662
-
663
-```sql
664
-CREATE LOGIN netdata_user WITH PASSWORD = 'YourStrongPassword!';
665
-
666
-GRANT VIEW SERVER STATE TO netdata_user;
667
-
668
-GRANT VIEW ANY DEFINITION TO netdata_user;
669
-
670
-
671
-USE msdb;
672
-CREATE USER netdata_user FOR LOGIN netdata_user;
673
-GRANT SELECT ON dbo.sysjobs TO netdata_user;
674
-
675
-USE distribution;
676
-CREATE USER netdata_user FOR LOGIN netdata_user;
677
-GRANT SELECT ON dbo.MSreplication_monitordata TO netdata_user;
678
-GRANT SELECT ON dbo.MSpublications TO netdata_user;
679
-GRANT SELECT ON dbo.MSsubscriptions TO netdata_user;
680
-```
681
-
682
-**Required permissions:**
683
-- `VIEW SERVER STATE` - Access to dynamic management views
684
-- `SELECT on msdb.dbo.sysjobs` - SQL Agent job status monitoring
685
-
686
-**Optional permissions:**
687
-- `VIEW ANY DEFINITION` - Always On Availability Group monitoring
688
-- `VIEW SERVER PERFORMANCE STATE` - HADR DMVs on SQL Server 2022+
689
-- `SELECT on distribution.dbo.MSreplication_monitordata` - Replication monitoring
690
-- `SELECT on distribution.dbo.MSpublications` - Publication information
691
-- `SELECT on distribution.dbo.MSsubscriptions` - Subscription counts
692
-
693
-
694
-
695
-### Configuration
696
-
697
-#### Options
698
-
699
-The following options can be defined globally: update_every, autodetection_retry.
700
-
701
-
702
-<details open><summary>Config options</summary>
703
-
704
-
705
-
706
-| Group | Option | Description | Default | Required |
707
-|:------|:-----|:------------|:--------|:---------:|
708
-| **Collection** | update_every | Data collection interval (seconds). | 10 | no |
709
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
710
-| **Target** | dsn | SQL Server DSN (Data Source Name). See [DSN syntax](https://github.com/microsoft/go-mssqldb#connection-parameters-and-dsn). When `cloud_auth.provider` is `azure_ad`, use URL format with `sqlserver://` scheme. | sqlserver://localhost:1433 | yes |
711
-| **Cloud Auth** | cloud_auth.provider | Cloud auth provider (`none` or `azure_ad`). | none | no |
712
-| **Cloud Auth/Azure** | cloud_auth.azure_ad.mode | Azure AD credential mode (`service_principal`, `managed_identity`, or `default`). Required when `cloud_auth.provider` is `azure_ad`. | | yes |
713
-| | cloud_auth.azure_ad.mode_service_principal.tenant_id | Azure tenant ID. Required for `service_principal` mode. | | no |
714
-| | cloud_auth.azure_ad.mode_service_principal.client_id | Azure client ID. Required for `service_principal` mode. | | no |
715
-| | cloud_auth.azure_ad.mode_service_principal.client_secret | Azure client secret for `service_principal` mode. | | no |
716
-| | cloud_auth.azure_ad.mode_managed_identity.client_id | Optional client ID of a user-assigned managed identity (`managed_identity` mode). | | no |
717
-| **Target** | timeout | Query timeout (seconds). | 5 | no |
718
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
719
-| | functions.top_queries.timeout | Query timeout for top-queries function (seconds). Uses collector timeout if not set. | | no |
720
-| | functions.top_queries.limit | Maximum number of queries to return in the top-queries response. | 500 | no |
721
-| | functions.top_queries.time_window_days | Number of days of Query Store data to analyze. Set to 0 to include all available data. Smaller values improve query performance but show less history. | 7 | no |
722
-| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
723
-| | functions.deadlock_info.timeout | Query timeout for deadlock-info function (seconds). Uses collector timeout if not set. | | no |
724
-| | functions.deadlock_info.use_ring_buffer | Use ring_buffer instead of event_file for system_health session.<br/><br/>WARNING: Not recommended for production:<br/>• Data cleared on failover/restart<br/>• 4 MB capacity limit<br/>• High CPU load during queries<br/><br/>Use only for Azure SQL Database without Blob Storage or testing. | no | no |
725
-| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
726
-| | functions.error_info.timeout | Query timeout for error-info function (seconds). Uses collector timeout if not set. | | no |
727
-| | functions.error_info.session_name | Extended Events session name capturing error_reported events.<br/>Must be created by administrator with event_file (recommended) or ring_buffer target. | netdata_errors | no |
728
-| | functions.error_info.use_ring_buffer | Use ring_buffer instead of event_file for error events.<br/><br/>WARNING: Not recommended for production:<br/>• Data cleared on failover/restart<br/>• 4 MB capacity limit<br/>• High CPU load during queries<br/><br/>Use only for Azure SQL Database without Blob Storage or testing. | no | no |
729
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
730
-
731
-
732
-</details>
733
-
734
-
735
-#### via UI
736
-
737
-Configure the **mssql** collector from the Netdata web interface:
738
-
739
-1. Go to **Nodes**.
740
-2. Select the node **where you want the mssql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
741
-3. The **Collectors → Jobs** view opens by default.
742
-4. In the Search box, type _mssql_ (or scroll the list) to locate the **mssql** collector.
743
-5. Click the **+** next to the **mssql** collector to add a new job.
744
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
745
- - **Test** runs the job with the provided settings and shows whether data can be collected.
746
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
747
-
748
-
749
-#### via File
750
-
751
-The configuration file name for this integration is `go.d/mssql.conf`.
752
-
753
-The file format is YAML. Generally, the structure is:
754
-
755
-```yaml
756
-update_every: 1
757
-autodetection_retry: 0
758
-jobs:
759
- - name: some_name1
760
- - name: some_name2
761
-```
762
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
763
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
764
-
765
-```bash
766
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
767
-sudo ./edit-config go.d/mssql.conf
768
-```
769
-
770
-##### Examples
771
-
772
-###### Basic configuration
773
-
774
-Connect to local SQL Server with SQL authentication.
775
-
776
-<details open><summary>Config</summary>
777
-
778
-```yaml
779
-jobs:
780
- - name: local
781
- dsn: "sqlserver://netdata_user:password@localhost:1433"
782
-
783
-```
784
-</details>
785
-
786
-###### Windows Authentication
787
-
788
-Connect using Windows integrated authentication.
789
-
790
-<details open><summary>Config</summary>
791
-
792
-```yaml
793
-jobs:
794
- - name: local
795
- dsn: "sqlserver://localhost:1433?trusted_connection=yes"
796
-
797
-```
798
-</details>
799
-
800
-###### Named instance
801
-
802
-Connect to a named SQL Server instance.
803
-
804
-<details open><summary>Config</summary>
805
-
806
-```yaml
807
-jobs:
808
- - name: named_instance
809
- dsn: "sqlserver://netdata_user:password@localhost/INSTANCENAME"
810
-
811
-```
812
-</details>
813
-
814
-###### Remote server
815
-
816
-Connect to a remote SQL Server.
817
-
818
-<details open><summary>Config</summary>
819
-
820
-```yaml
821
-jobs:
822
- - name: remote
823
- dsn: "sqlserver://netdata_user:password@192.168.1.100:1433"
824
-
825
-```
826
-</details>
827
-
828
-###### Azure SQL with service principal
829
-
830
-Use Microsoft Entra service principal authentication for Azure SQL.
831
-
832
-<details open><summary>Config</summary>
833
-
834
-```yaml
835
-jobs:
836
- - name: azure_sql_sp
837
- dsn: "sqlserver://my-server.database.windows.net:1433?database=mydb"
838
- cloud_auth:
839
- provider: azure_ad
840
- azure_ad:
841
- mode: service_principal
842
- mode_service_principal:
843
- tenant_id: "00000000-0000-0000-0000-000000000000"
844
- client_id: "11111111-1111-1111-1111-111111111111"
845
- client_secret: "super-secret-value"
846
-
847
-```
848
-</details>
849
-
850
-###### Azure SQL with managed identity
851
-
852
-Use managed identity authentication (system-assigned by default).
853
-
854
-<details open><summary>Config</summary>
855
-
856
-```yaml
857
-jobs:
858
- - name: azure_sql_mi
859
- dsn: "sqlserver://my-server.database.windows.net:1433?database=mydb"
860
- cloud_auth:
861
- provider: azure_ad
862
- azure_ad:
863
- mode: managed_identity
864
-
865
-```
866
-</details>
867
-
868
-###### Multi-instance
869
-
870
-> **Note**: When you define multiple jobs, their names must be unique.
871
-
872
-Monitoring multiple SQL Server instances.
873
-
874
-
875
-<details open><summary>Config</summary>
876
-
877
-```yaml
878
-jobs:
879
- - name: production
880
- dsn: "sqlserver://netdata_user:password@prod-sql:1433"
881
-
882
- - name: development
883
- dsn: "sqlserver://netdata_user:password@dev-sql:1433"
884
-
885
-```
886
-</details>
887
-
888
-###### With custom function settings
889
-
890
-Configure function-specific settings like timeouts and limits.
891
-
892
-> **Warning**: Query Store may contain unmasked literal values (PII).
893
-> Disable functions if not needed or ensure proper access controls.
894
-
895
-
896
-<details open><summary>Config</summary>
897
-
898
-```yaml
899
-jobs:
900
- - name: local
901
- dsn: "sqlserver://netdata_user:password@localhost:1433"
902
- functions:
903
- top_queries:
904
- limit: 100
905
- time_window_days: 7
906
- deadlock_info:
907
- use_ring_buffer: true
908
- error_info:
909
- session_name: custom_errors
910
-
911
-```
912
-</details>
913
-
914
-
915
-
924
## Troubleshooting
925
926
### Debug Mode
src/go/plugin/go.d/collector/mysql/integrations/mariadb.md
+241
-241
@@ -65,6 +65,246 @@ The default configuration for this integration does not impose any limits on dat
65
66
The default configuration for this integration is not expected to impose a significant performance impact on the system.
67
68
+## Setup
69
+
70
+
71
+You can configure the **mysql** collector in two ways:
72
+
73
+| Method | Best for | How to |
74
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
75
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mysql**, then click **+** to add a job. |
76
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mysql.conf` and add a job. |
77
+
78
+:::important
79
+
80
+UI configuration requires paid Netdata Cloud plan.
81
+
82
+:::
83
+
84
+
85
+### Prerequisites
86
+
87
+#### Create netdata user
88
+
89
+A user account should have the following [permissions](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html):
90
+
91
+- [`USAGE`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_usage)
92
+- [`REPLICATION CLIENT`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_replication-client)
93
+- [`PROCESS`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_process)
94
+
95
+To create the `netdata` user with these permissions, execute the following in the MySQL shell:
96
+
97
+- **MySQL and MariaDB < 10.5.9**
98
+
99
+ ```mysql
100
+ CREATE USER 'netdata'@'localhost';
101
+ GRANT USAGE, REPLICATION CLIENT, PROCESS ON *.* TO 'netdata'@'localhost';
102
+ FLUSH PRIVILEGES;
103
+ ```
104
+
105
+- **MariaDB >= 10.5.9**
106
+
107
+ For MariaDB 10.5.9 and later, use the `SLAVE MONITOR` privilege instead of `REPLICATION CLIENT`:
108
+
109
+ ```mysql
110
+ CREATE USER 'netdata'@'localhost';
111
+ GRANT USAGE, SLAVE MONITOR, PROCESS ON *.* TO 'netdata'@'localhost';
112
+ FLUSH PRIVILEGES;
113
+ ```
114
+
115
+The `netdata` user will have the ability to connect to the MySQL server on localhost without a password.
116
+It will only be able to gather statistics without being able to alter or affect operations in any way.
117
+
118
+
119
+#### Enable User Statistics (optional)
120
+
121
+To collect per-user statistics, the [User Statistics](https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/query-optimizations/statistics-for-optimizing-queries/user-statistics) plugin must be enabled.
122
+This is available for **MariaDB** and **Percona**, not for MySQL.
123
+
124
+By default, statistics are not collected. To enable the plugin, set the `userstat` system variable.
125
+
126
+- **In a configuration file** (persistent, requires restart):
127
+
128
+ ```ini
129
+ [mariadb]
130
+ userstat = 1
131
+ ```
132
+
133
+- **Dynamically** (takes effect immediately, does not persist across restarts):
134
+
135
+ ```mysql
136
+ SET GLOBAL userstat=1;
137
+ ```
138
+
139
+
140
+
141
+### Configuration
142
+
143
+#### Options
144
+
145
+The following options can be defined globally: update_every, autodetection_retry.
146
+
147
+
148
+<details open><summary>Config options</summary>
149
+
150
+
151
+
152
+| Group | Option | Description | Default | Required |
153
+|:------|:-----|:------------|:--------|:---------:|
154
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
155
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
156
+| **Target** | dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
157
+| | my.cnf | Path to a `my.cnf` file to read connection settings from the `[client]` section. | | no |
158
+| | timeout | Query timeout (seconds). | 1 | no |
159
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
160
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
161
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
162
+| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
163
+| | functions.deadlock_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
164
+| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
165
+| | functions.error_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
166
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
167
+
168
+
169
+</details>
170
+
171
+
172
+#### via UI
173
+
174
+Configure the **mysql** collector from the Netdata web interface:
175
+
176
+1. Go to **Nodes**.
177
+2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
178
+3. The **Collectors → Jobs** view opens by default.
179
+4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
180
+5. Click the **+** next to the **mysql** collector to add a new job.
181
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
182
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
183
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
184
+
185
+
186
+#### via File
187
+
188
+The configuration file name for this integration is `go.d/mysql.conf`.
189
+
190
+The file format is YAML. Generally, the structure is:
191
+
192
+```yaml
193
+update_every: 1
194
+autodetection_retry: 0
195
+jobs:
196
+ - name: some_name1
197
+ - name: some_name2
198
+```
199
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
200
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
201
+
202
+```bash
203
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
204
+sudo ./edit-config go.d/mysql.conf
205
+```
206
+
207
+##### Examples
208
+
209
+###### TCP socket
210
+
211
+An example configuration.
212
+
213
+<details open><summary>Config</summary>
214
+
215
+```yaml
216
+jobs:
217
+ - name: local
218
+ dsn: netdata@tcp(127.0.0.1:3306)/
219
+
220
+```
221
+</details>
222
+
223
+###### Unix socket
224
+
225
+An example configuration.
226
+
227
+<details open><summary>Config</summary>
228
+
229
+```yaml
230
+jobs:
231
+ - name: local
232
+ dsn: netdata@unix(/var/lib/mysql/mysql.sock)/
233
+
234
+```
235
+</details>
236
+
237
+###### Connection with password
238
+
239
+An example configuration.
240
+
241
+<details open><summary>Config</summary>
242
+
243
+```yaml
244
+jobs:
245
+ - name: local
246
+ dsn: netconfig:password@tcp(127.0.0.1:3306)/
247
+
248
+```
249
+</details>
250
+
251
+###### my.cnf
252
+
253
+An example configuration.
254
+
255
+<details open><summary>Config</summary>
256
+
257
+```yaml
258
+jobs:
259
+ - name: local
260
+ my.cnf: '/etc/my.cnf'
261
+
262
+```
263
+</details>
264
+
265
+###### Multi-instance
266
+
267
+> **Note**: When you define multiple jobs, their names must be unique.
268
+
269
+Local and remote instances.
270
+
271
+
272
+<details open><summary>Config</summary>
273
+
274
+```yaml
275
+jobs:
276
+ - name: local
277
+ dsn: netdata@tcp(127.0.0.1:3306)/
278
+
279
+ - name: remote
280
+ dsn: netconfig:password@tcp(203.0.113.0:3306)/
281
+
282
+```
283
+</details>
284
+
285
+
286
+
287
+## Alerts
288
+
289
+
290
+The following alerts are available:
291
+
292
+| Alert name | On metric | Description |
293
+|:------------|:----------|:------------|
294
+| [ mysql_10s_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.queries | number of slow queries in the last 10 seconds |
295
+| [ mysql_10s_table_locks_immediate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table immediate locks in the last 10 seconds |
296
+| [ mysql_10s_table_locks_waited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table waited locks in the last 10 seconds |
297
+| [ mysql_10s_waited_locks_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | ratio of waited table locks over the last 10 seconds |
298
+| [ mysql_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.connections_active | client connections utilization |
299
+| [ mysql_replication ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_status | replication status (0: stopped, 1: working) |
300
+| [ mysql_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_behind | difference between the timestamp of the latest transaction processed by the SQL thread and the timestamp of the same transaction when it was processed on the master |
301
+| [ mysql_galera_cluster_size_max_2m ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | maximum galera cluster size in the last 2 minutes starting one minute ago |
302
+| [ mysql_galera_cluster_size ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | current galera cluster size, compared to the maximum size in the last 2 minutes |
303
+| [ mysql_galera_cluster_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Donor/Desynced or Joined |
304
+| [ mysql_galera_cluster_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Undefined or Joining or Error |
305
+| [ mysql_galera_cluster_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_status | galera node is part of a nonoperational component. This occurs in cases of multiple membership changes that result in a loss of Quorum or in cases of split-brain situations. |
306
+
307
+
308
## Metrics
309
310
Metrics grouped by *scope*.
@@ -187,7 +427,7 @@ Metrics:
427
428
429
190
-## Functions
430
+## Live Data
431
432
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
433
@@ -460,246 +700,6 @@ Most recent error per query digest from Performance Schema history tables.
700
701
702
463
-## Alerts
464
-
465
-
466
-The following alerts are available:
467
-
468
-| Alert name | On metric | Description |
469
-|:------------|:----------|:------------|
470
-| [ mysql_10s_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.queries | number of slow queries in the last 10 seconds |
471
-| [ mysql_10s_table_locks_immediate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table immediate locks in the last 10 seconds |
472
-| [ mysql_10s_table_locks_waited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table waited locks in the last 10 seconds |
473
-| [ mysql_10s_waited_locks_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | ratio of waited table locks over the last 10 seconds |
474
-| [ mysql_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.connections_active | client connections utilization |
475
-| [ mysql_replication ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_status | replication status (0: stopped, 1: working) |
476
-| [ mysql_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_behind | difference between the timestamp of the latest transaction processed by the SQL thread and the timestamp of the same transaction when it was processed on the master |
477
-| [ mysql_galera_cluster_size_max_2m ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | maximum galera cluster size in the last 2 minutes starting one minute ago |
478
-| [ mysql_galera_cluster_size ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | current galera cluster size, compared to the maximum size in the last 2 minutes |
479
-| [ mysql_galera_cluster_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Donor/Desynced or Joined |
480
-| [ mysql_galera_cluster_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Undefined or Joining or Error |
481
-| [ mysql_galera_cluster_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_status | galera node is part of a nonoperational component. This occurs in cases of multiple membership changes that result in a loss of Quorum or in cases of split-brain situations. |
482
-
483
-
484
-## Setup
485
-
486
-
487
-You can configure the **mysql** collector in two ways:
488
-
489
-| Method | Best for | How to |
490
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
491
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mysql**, then click **+** to add a job. |
492
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mysql.conf` and add a job. |
493
-
494
-:::important
495
-
496
-UI configuration requires paid Netdata Cloud plan.
497
-
498
-:::
499
-
500
-
501
-### Prerequisites
502
-
503
-#### Create netdata user
504
-
505
-A user account should have the following [permissions](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html):
506
-
507
-- [`USAGE`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_usage)
508
-- [`REPLICATION CLIENT`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_replication-client)
509
-- [`PROCESS`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_process)
510
-
511
-To create the `netdata` user with these permissions, execute the following in the MySQL shell:
512
-
513
-- **MySQL and MariaDB < 10.5.9**
514
-
515
- ```mysql
516
- CREATE USER 'netdata'@'localhost';
517
- GRANT USAGE, REPLICATION CLIENT, PROCESS ON *.* TO 'netdata'@'localhost';
518
- FLUSH PRIVILEGES;
519
- ```
520
-
521
-- **MariaDB >= 10.5.9**
522
-
523
- For MariaDB 10.5.9 and later, use the `SLAVE MONITOR` privilege instead of `REPLICATION CLIENT`:
524
-
525
- ```mysql
526
- CREATE USER 'netdata'@'localhost';
527
- GRANT USAGE, SLAVE MONITOR, PROCESS ON *.* TO 'netdata'@'localhost';
528
- FLUSH PRIVILEGES;
529
- ```
530
-
531
-The `netdata` user will have the ability to connect to the MySQL server on localhost without a password.
532
-It will only be able to gather statistics without being able to alter or affect operations in any way.
533
-
534
-
535
-#### Enable User Statistics (optional)
536
-
537
-To collect per-user statistics, the [User Statistics](https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/query-optimizations/statistics-for-optimizing-queries/user-statistics) plugin must be enabled.
538
-This is available for **MariaDB** and **Percona**, not for MySQL.
539
-
540
-By default, statistics are not collected. To enable the plugin, set the `userstat` system variable.
541
-
542
-- **In a configuration file** (persistent, requires restart):
543
-
544
- ```ini
545
- [mariadb]
546
- userstat = 1
547
- ```
548
-
549
-- **Dynamically** (takes effect immediately, does not persist across restarts):
550
-
551
- ```mysql
552
- SET GLOBAL userstat=1;
553
- ```
554
-
555
-
556
-
557
-### Configuration
558
-
559
-#### Options
560
-
561
-The following options can be defined globally: update_every, autodetection_retry.
562
-
563
-
564
-<details open><summary>Config options</summary>
565
-
566
-
567
-
568
-| Group | Option | Description | Default | Required |
569
-|:------|:-----|:------------|:--------|:---------:|
570
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
571
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
572
-| **Target** | dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
573
-| | my.cnf | Path to a `my.cnf` file to read connection settings from the `[client]` section. | | no |
574
-| | timeout | Query timeout (seconds). | 1 | no |
575
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
576
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
577
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
578
-| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
579
-| | functions.deadlock_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
580
-| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
581
-| | functions.error_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
582
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
583
-
584
-
585
-</details>
586
-
587
-
588
-#### via UI
589
-
590
-Configure the **mysql** collector from the Netdata web interface:
591
-
592
-1. Go to **Nodes**.
593
-2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
594
-3. The **Collectors → Jobs** view opens by default.
595
-4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
596
-5. Click the **+** next to the **mysql** collector to add a new job.
597
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
598
- - **Test** runs the job with the provided settings and shows whether data can be collected.
599
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
600
-
601
-
602
-#### via File
603
-
604
-The configuration file name for this integration is `go.d/mysql.conf`.
605
-
606
-The file format is YAML. Generally, the structure is:
607
-
608
-```yaml
609
-update_every: 1
610
-autodetection_retry: 0
611
-jobs:
612
- - name: some_name1
613
- - name: some_name2
614
-```
615
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
616
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
617
-
618
-```bash
619
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
620
-sudo ./edit-config go.d/mysql.conf
621
-```
622
-
623
-##### Examples
624
-
625
-###### TCP socket
626
-
627
-An example configuration.
628
-
629
-<details open><summary>Config</summary>
630
-
631
-```yaml
632
-jobs:
633
- - name: local
634
- dsn: netdata@tcp(127.0.0.1:3306)/
635
-
636
-```
637
-</details>
638
-
639
-###### Unix socket
640
-
641
-An example configuration.
642
-
643
-<details open><summary>Config</summary>
644
-
645
-```yaml
646
-jobs:
647
- - name: local
648
- dsn: netdata@unix(/var/lib/mysql/mysql.sock)/
649
-
650
-```
651
-</details>
652
-
653
-###### Connection with password
654
-
655
-An example configuration.
656
-
657
-<details open><summary>Config</summary>
658
-
659
-```yaml
660
-jobs:
661
- - name: local
662
- dsn: netconfig:password@tcp(127.0.0.1:3306)/
663
-
664
-```
665
-</details>
666
-
667
-###### my.cnf
668
-
669
-An example configuration.
670
-
671
-<details open><summary>Config</summary>
672
-
673
-```yaml
674
-jobs:
675
- - name: local
676
- my.cnf: '/etc/my.cnf'
677
-
678
-```
679
-</details>
680
-
681
-###### Multi-instance
682
-
683
-> **Note**: When you define multiple jobs, their names must be unique.
684
-
685
-Local and remote instances.
686
-
687
-
688
-<details open><summary>Config</summary>
689
-
690
-```yaml
691
-jobs:
692
- - name: local
693
- dsn: netdata@tcp(127.0.0.1:3306)/
694
-
695
- - name: remote
696
- dsn: netconfig:password@tcp(203.0.113.0:3306)/
697
-
698
-```
699
-</details>
700
-
701
-
702
-
703
## Troubleshooting
704
705
### Debug Mode
src/go/plugin/go.d/collector/mysql/integrations/mysql.md
+241
-241
@@ -65,6 +65,246 @@ The default configuration for this integration does not impose any limits on dat
65
66
The default configuration for this integration is not expected to impose a significant performance impact on the system.
67
68
+## Setup
69
+
70
+
71
+You can configure the **mysql** collector in two ways:
72
+
73
+| Method | Best for | How to |
74
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
75
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mysql**, then click **+** to add a job. |
76
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mysql.conf` and add a job. |
77
+
78
+:::important
79
+
80
+UI configuration requires paid Netdata Cloud plan.
81
+
82
+:::
83
+
84
+
85
+### Prerequisites
86
+
87
+#### Create netdata user
88
+
89
+A user account should have the following [permissions](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html):
90
+
91
+- [`USAGE`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_usage)
92
+- [`REPLICATION CLIENT`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_replication-client)
93
+- [`PROCESS`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_process)
94
+
95
+To create the `netdata` user with these permissions, execute the following in the MySQL shell:
96
+
97
+- **MySQL and MariaDB < 10.5.9**
98
+
99
+ ```mysql
100
+ CREATE USER 'netdata'@'localhost';
101
+ GRANT USAGE, REPLICATION CLIENT, PROCESS ON *.* TO 'netdata'@'localhost';
102
+ FLUSH PRIVILEGES;
103
+ ```
104
+
105
+- **MariaDB >= 10.5.9**
106
+
107
+ For MariaDB 10.5.9 and later, use the `SLAVE MONITOR` privilege instead of `REPLICATION CLIENT`:
108
+
109
+ ```mysql
110
+ CREATE USER 'netdata'@'localhost';
111
+ GRANT USAGE, SLAVE MONITOR, PROCESS ON *.* TO 'netdata'@'localhost';
112
+ FLUSH PRIVILEGES;
113
+ ```
114
+
115
+The `netdata` user will have the ability to connect to the MySQL server on localhost without a password.
116
+It will only be able to gather statistics without being able to alter or affect operations in any way.
117
+
118
+
119
+#### Enable User Statistics (optional)
120
+
121
+To collect per-user statistics, the [User Statistics](https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/query-optimizations/statistics-for-optimizing-queries/user-statistics) plugin must be enabled.
122
+This is available for **MariaDB** and **Percona**, not for MySQL.
123
+
124
+By default, statistics are not collected. To enable the plugin, set the `userstat` system variable.
125
+
126
+- **In a configuration file** (persistent, requires restart):
127
+
128
+ ```ini
129
+ [mariadb]
130
+ userstat = 1
131
+ ```
132
+
133
+- **Dynamically** (takes effect immediately, does not persist across restarts):
134
+
135
+ ```mysql
136
+ SET GLOBAL userstat=1;
137
+ ```
138
+
139
+
140
+
141
+### Configuration
142
+
143
+#### Options
144
+
145
+The following options can be defined globally: update_every, autodetection_retry.
146
+
147
+
148
+<details open><summary>Config options</summary>
149
+
150
+
151
+
152
+| Group | Option | Description | Default | Required |
153
+|:------|:-----|:------------|:--------|:---------:|
154
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
155
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
156
+| **Target** | dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
157
+| | my.cnf | Path to a `my.cnf` file to read connection settings from the `[client]` section. | | no |
158
+| | timeout | Query timeout (seconds). | 1 | no |
159
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
160
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
161
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
162
+| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
163
+| | functions.deadlock_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
164
+| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
165
+| | functions.error_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
166
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
167
+
168
+
169
+</details>
170
+
171
+
172
+#### via UI
173
+
174
+Configure the **mysql** collector from the Netdata web interface:
175
+
176
+1. Go to **Nodes**.
177
+2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
178
+3. The **Collectors → Jobs** view opens by default.
179
+4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
180
+5. Click the **+** next to the **mysql** collector to add a new job.
181
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
182
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
183
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
184
+
185
+
186
+#### via File
187
+
188
+The configuration file name for this integration is `go.d/mysql.conf`.
189
+
190
+The file format is YAML. Generally, the structure is:
191
+
192
+```yaml
193
+update_every: 1
194
+autodetection_retry: 0
195
+jobs:
196
+ - name: some_name1
197
+ - name: some_name2
198
+```
199
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
200
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
201
+
202
+```bash
203
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
204
+sudo ./edit-config go.d/mysql.conf
205
+```
206
+
207
+##### Examples
208
+
209
+###### TCP socket
210
+
211
+An example configuration.
212
+
213
+<details open><summary>Config</summary>
214
+
215
+```yaml
216
+jobs:
217
+ - name: local
218
+ dsn: netdata@tcp(127.0.0.1:3306)/
219
+
220
+```
221
+</details>
222
+
223
+###### Unix socket
224
+
225
+An example configuration.
226
+
227
+<details open><summary>Config</summary>
228
+
229
+```yaml
230
+jobs:
231
+ - name: local
232
+ dsn: netdata@unix(/var/lib/mysql/mysql.sock)/
233
+
234
+```
235
+</details>
236
+
237
+###### Connection with password
238
+
239
+An example configuration.
240
+
241
+<details open><summary>Config</summary>
242
+
243
+```yaml
244
+jobs:
245
+ - name: local
246
+ dsn: netconfig:password@tcp(127.0.0.1:3306)/
247
+
248
+```
249
+</details>
250
+
251
+###### my.cnf
252
+
253
+An example configuration.
254
+
255
+<details open><summary>Config</summary>
256
+
257
+```yaml
258
+jobs:
259
+ - name: local
260
+ my.cnf: '/etc/my.cnf'
261
+
262
+```
263
+</details>
264
+
265
+###### Multi-instance
266
+
267
+> **Note**: When you define multiple jobs, their names must be unique.
268
+
269
+Local and remote instances.
270
+
271
+
272
+<details open><summary>Config</summary>
273
+
274
+```yaml
275
+jobs:
276
+ - name: local
277
+ dsn: netdata@tcp(127.0.0.1:3306)/
278
+
279
+ - name: remote
280
+ dsn: netconfig:password@tcp(203.0.113.0:3306)/
281
+
282
+```
283
+</details>
284
+
285
+
286
+
287
+## Alerts
288
+
289
+
290
+The following alerts are available:
291
+
292
+| Alert name | On metric | Description |
293
+|:------------|:----------|:------------|
294
+| [ mysql_10s_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.queries | number of slow queries in the last 10 seconds |
295
+| [ mysql_10s_table_locks_immediate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table immediate locks in the last 10 seconds |
296
+| [ mysql_10s_table_locks_waited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table waited locks in the last 10 seconds |
297
+| [ mysql_10s_waited_locks_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | ratio of waited table locks over the last 10 seconds |
298
+| [ mysql_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.connections_active | client connections utilization |
299
+| [ mysql_replication ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_status | replication status (0: stopped, 1: working) |
300
+| [ mysql_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_behind | difference between the timestamp of the latest transaction processed by the SQL thread and the timestamp of the same transaction when it was processed on the master |
301
+| [ mysql_galera_cluster_size_max_2m ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | maximum galera cluster size in the last 2 minutes starting one minute ago |
302
+| [ mysql_galera_cluster_size ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | current galera cluster size, compared to the maximum size in the last 2 minutes |
303
+| [ mysql_galera_cluster_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Donor/Desynced or Joined |
304
+| [ mysql_galera_cluster_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Undefined or Joining or Error |
305
+| [ mysql_galera_cluster_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_status | galera node is part of a nonoperational component. This occurs in cases of multiple membership changes that result in a loss of Quorum or in cases of split-brain situations. |
306
+
307
+
308
## Metrics
309
310
Metrics grouped by *scope*.
@@ -187,7 +427,7 @@ Metrics:
427
428
429
190
-## Functions
430
+## Live Data
431
432
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
433
@@ -460,246 +700,6 @@ Most recent error per query digest from Performance Schema history tables.
700
701
702
463
-## Alerts
464
-
465
-
466
-The following alerts are available:
467
-
468
-| Alert name | On metric | Description |
469
-|:------------|:----------|:------------|
470
-| [ mysql_10s_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.queries | number of slow queries in the last 10 seconds |
471
-| [ mysql_10s_table_locks_immediate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table immediate locks in the last 10 seconds |
472
-| [ mysql_10s_table_locks_waited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table waited locks in the last 10 seconds |
473
-| [ mysql_10s_waited_locks_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | ratio of waited table locks over the last 10 seconds |
474
-| [ mysql_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.connections_active | client connections utilization |
475
-| [ mysql_replication ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_status | replication status (0: stopped, 1: working) |
476
-| [ mysql_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_behind | difference between the timestamp of the latest transaction processed by the SQL thread and the timestamp of the same transaction when it was processed on the master |
477
-| [ mysql_galera_cluster_size_max_2m ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | maximum galera cluster size in the last 2 minutes starting one minute ago |
478
-| [ mysql_galera_cluster_size ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | current galera cluster size, compared to the maximum size in the last 2 minutes |
479
-| [ mysql_galera_cluster_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Donor/Desynced or Joined |
480
-| [ mysql_galera_cluster_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Undefined or Joining or Error |
481
-| [ mysql_galera_cluster_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_status | galera node is part of a nonoperational component. This occurs in cases of multiple membership changes that result in a loss of Quorum or in cases of split-brain situations. |
482
-
483
-
484
-## Setup
485
-
486
-
487
-You can configure the **mysql** collector in two ways:
488
-
489
-| Method | Best for | How to |
490
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
491
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mysql**, then click **+** to add a job. |
492
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mysql.conf` and add a job. |
493
-
494
-:::important
495
-
496
-UI configuration requires paid Netdata Cloud plan.
497
-
498
-:::
499
-
500
-
501
-### Prerequisites
502
-
503
-#### Create netdata user
504
-
505
-A user account should have the following [permissions](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html):
506
-
507
-- [`USAGE`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_usage)
508
-- [`REPLICATION CLIENT`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_replication-client)
509
-- [`PROCESS`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_process)
510
-
511
-To create the `netdata` user with these permissions, execute the following in the MySQL shell:
512
-
513
-- **MySQL and MariaDB < 10.5.9**
514
-
515
- ```mysql
516
- CREATE USER 'netdata'@'localhost';
517
- GRANT USAGE, REPLICATION CLIENT, PROCESS ON *.* TO 'netdata'@'localhost';
518
- FLUSH PRIVILEGES;
519
- ```
520
-
521
-- **MariaDB >= 10.5.9**
522
-
523
- For MariaDB 10.5.9 and later, use the `SLAVE MONITOR` privilege instead of `REPLICATION CLIENT`:
524
-
525
- ```mysql
526
- CREATE USER 'netdata'@'localhost';
527
- GRANT USAGE, SLAVE MONITOR, PROCESS ON *.* TO 'netdata'@'localhost';
528
- FLUSH PRIVILEGES;
529
- ```
530
-
531
-The `netdata` user will have the ability to connect to the MySQL server on localhost without a password.
532
-It will only be able to gather statistics without being able to alter or affect operations in any way.
533
-
534
-
535
-#### Enable User Statistics (optional)
536
-
537
-To collect per-user statistics, the [User Statistics](https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/query-optimizations/statistics-for-optimizing-queries/user-statistics) plugin must be enabled.
538
-This is available for **MariaDB** and **Percona**, not for MySQL.
539
-
540
-By default, statistics are not collected. To enable the plugin, set the `userstat` system variable.
541
-
542
-- **In a configuration file** (persistent, requires restart):
543
-
544
- ```ini
545
- [mariadb]
546
- userstat = 1
547
- ```
548
-
549
-- **Dynamically** (takes effect immediately, does not persist across restarts):
550
-
551
- ```mysql
552
- SET GLOBAL userstat=1;
553
- ```
554
-
555
-
556
-
557
-### Configuration
558
-
559
-#### Options
560
-
561
-The following options can be defined globally: update_every, autodetection_retry.
562
-
563
-
564
-<details open><summary>Config options</summary>
565
-
566
-
567
-
568
-| Group | Option | Description | Default | Required |
569
-|:------|:-----|:------------|:--------|:---------:|
570
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
571
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
572
-| **Target** | dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
573
-| | my.cnf | Path to a `my.cnf` file to read connection settings from the `[client]` section. | | no |
574
-| | timeout | Query timeout (seconds). | 1 | no |
575
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
576
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
577
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
578
-| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
579
-| | functions.deadlock_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
580
-| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
581
-| | functions.error_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
582
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
583
-
584
-
585
-</details>
586
-
587
-
588
-#### via UI
589
-
590
-Configure the **mysql** collector from the Netdata web interface:
591
-
592
-1. Go to **Nodes**.
593
-2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
594
-3. The **Collectors → Jobs** view opens by default.
595
-4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
596
-5. Click the **+** next to the **mysql** collector to add a new job.
597
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
598
- - **Test** runs the job with the provided settings and shows whether data can be collected.
599
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
600
-
601
-
602
-#### via File
603
-
604
-The configuration file name for this integration is `go.d/mysql.conf`.
605
-
606
-The file format is YAML. Generally, the structure is:
607
-
608
-```yaml
609
-update_every: 1
610
-autodetection_retry: 0
611
-jobs:
612
- - name: some_name1
613
- - name: some_name2
614
-```
615
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
616
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
617
-
618
-```bash
619
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
620
-sudo ./edit-config go.d/mysql.conf
621
-```
622
-
623
-##### Examples
624
-
625
-###### TCP socket
626
-
627
-An example configuration.
628
-
629
-<details open><summary>Config</summary>
630
-
631
-```yaml
632
-jobs:
633
- - name: local
634
- dsn: netdata@tcp(127.0.0.1:3306)/
635
-
636
-```
637
-</details>
638
-
639
-###### Unix socket
640
-
641
-An example configuration.
642
-
643
-<details open><summary>Config</summary>
644
-
645
-```yaml
646
-jobs:
647
- - name: local
648
- dsn: netdata@unix(/var/lib/mysql/mysql.sock)/
649
-
650
-```
651
-</details>
652
-
653
-###### Connection with password
654
-
655
-An example configuration.
656
-
657
-<details open><summary>Config</summary>
658
-
659
-```yaml
660
-jobs:
661
- - name: local
662
- dsn: netconfig:password@tcp(127.0.0.1:3306)/
663
-
664
-```
665
-</details>
666
-
667
-###### my.cnf
668
-
669
-An example configuration.
670
-
671
-<details open><summary>Config</summary>
672
-
673
-```yaml
674
-jobs:
675
- - name: local
676
- my.cnf: '/etc/my.cnf'
677
-
678
-```
679
-</details>
680
-
681
-###### Multi-instance
682
-
683
-> **Note**: When you define multiple jobs, their names must be unique.
684
-
685
-Local and remote instances.
686
-
687
-
688
-<details open><summary>Config</summary>
689
-
690
-```yaml
691
-jobs:
692
- - name: local
693
- dsn: netdata@tcp(127.0.0.1:3306)/
694
-
695
- - name: remote
696
- dsn: netconfig:password@tcp(203.0.113.0:3306)/
697
-
698
-```
699
-</details>
700
-
701
-
702
-
703
## Troubleshooting
704
705
### Debug Mode
src/go/plugin/go.d/collector/mysql/integrations/percona_mysql.md
+241
-241
@@ -65,6 +65,246 @@ The default configuration for this integration does not impose any limits on dat
65
66
The default configuration for this integration is not expected to impose a significant performance impact on the system.
67
68
+## Setup
69
+
70
+
71
+You can configure the **mysql** collector in two ways:
72
+
73
+| Method | Best for | How to |
74
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
75
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mysql**, then click **+** to add a job. |
76
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mysql.conf` and add a job. |
77
+
78
+:::important
79
+
80
+UI configuration requires paid Netdata Cloud plan.
81
+
82
+:::
83
+
84
+
85
+### Prerequisites
86
+
87
+#### Create netdata user
88
+
89
+A user account should have the following [permissions](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html):
90
+
91
+- [`USAGE`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_usage)
92
+- [`REPLICATION CLIENT`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_replication-client)
93
+- [`PROCESS`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_process)
94
+
95
+To create the `netdata` user with these permissions, execute the following in the MySQL shell:
96
+
97
+- **MySQL and MariaDB < 10.5.9**
98
+
99
+ ```mysql
100
+ CREATE USER 'netdata'@'localhost';
101
+ GRANT USAGE, REPLICATION CLIENT, PROCESS ON *.* TO 'netdata'@'localhost';
102
+ FLUSH PRIVILEGES;
103
+ ```
104
+
105
+- **MariaDB >= 10.5.9**
106
+
107
+ For MariaDB 10.5.9 and later, use the `SLAVE MONITOR` privilege instead of `REPLICATION CLIENT`:
108
+
109
+ ```mysql
110
+ CREATE USER 'netdata'@'localhost';
111
+ GRANT USAGE, SLAVE MONITOR, PROCESS ON *.* TO 'netdata'@'localhost';
112
+ FLUSH PRIVILEGES;
113
+ ```
114
+
115
+The `netdata` user will have the ability to connect to the MySQL server on localhost without a password.
116
+It will only be able to gather statistics without being able to alter or affect operations in any way.
117
+
118
+
119
+#### Enable User Statistics (optional)
120
+
121
+To collect per-user statistics, the [User Statistics](https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/query-optimizations/statistics-for-optimizing-queries/user-statistics) plugin must be enabled.
122
+This is available for **MariaDB** and **Percona**, not for MySQL.
123
+
124
+By default, statistics are not collected. To enable the plugin, set the `userstat` system variable.
125
+
126
+- **In a configuration file** (persistent, requires restart):
127
+
128
+ ```ini
129
+ [mariadb]
130
+ userstat = 1
131
+ ```
132
+
133
+- **Dynamically** (takes effect immediately, does not persist across restarts):
134
+
135
+ ```mysql
136
+ SET GLOBAL userstat=1;
137
+ ```
138
+
139
+
140
+
141
+### Configuration
142
+
143
+#### Options
144
+
145
+The following options can be defined globally: update_every, autodetection_retry.
146
+
147
+
148
+<details open><summary>Config options</summary>
149
+
150
+
151
+
152
+| Group | Option | Description | Default | Required |
153
+|:------|:-----|:------------|:--------|:---------:|
154
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
155
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
156
+| **Target** | dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
157
+| | my.cnf | Path to a `my.cnf` file to read connection settings from the `[client]` section. | | no |
158
+| | timeout | Query timeout (seconds). | 1 | no |
159
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
160
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
161
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
162
+| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
163
+| | functions.deadlock_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
164
+| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
165
+| | functions.error_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
166
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
167
+
168
+
169
+</details>
170
+
171
+
172
+#### via UI
173
+
174
+Configure the **mysql** collector from the Netdata web interface:
175
+
176
+1. Go to **Nodes**.
177
+2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
178
+3. The **Collectors → Jobs** view opens by default.
179
+4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
180
+5. Click the **+** next to the **mysql** collector to add a new job.
181
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
182
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
183
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
184
+
185
+
186
+#### via File
187
+
188
+The configuration file name for this integration is `go.d/mysql.conf`.
189
+
190
+The file format is YAML. Generally, the structure is:
191
+
192
+```yaml
193
+update_every: 1
194
+autodetection_retry: 0
195
+jobs:
196
+ - name: some_name1
197
+ - name: some_name2
198
+```
199
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
200
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
201
+
202
+```bash
203
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
204
+sudo ./edit-config go.d/mysql.conf
205
+```
206
+
207
+##### Examples
208
+
209
+###### TCP socket
210
+
211
+An example configuration.
212
+
213
+<details open><summary>Config</summary>
214
+
215
+```yaml
216
+jobs:
217
+ - name: local
218
+ dsn: netdata@tcp(127.0.0.1:3306)/
219
+
220
+```
221
+</details>
222
+
223
+###### Unix socket
224
+
225
+An example configuration.
226
+
227
+<details open><summary>Config</summary>
228
+
229
+```yaml
230
+jobs:
231
+ - name: local
232
+ dsn: netdata@unix(/var/lib/mysql/mysql.sock)/
233
+
234
+```
235
+</details>
236
+
237
+###### Connection with password
238
+
239
+An example configuration.
240
+
241
+<details open><summary>Config</summary>
242
+
243
+```yaml
244
+jobs:
245
+ - name: local
246
+ dsn: netconfig:password@tcp(127.0.0.1:3306)/
247
+
248
+```
249
+</details>
250
+
251
+###### my.cnf
252
+
253
+An example configuration.
254
+
255
+<details open><summary>Config</summary>
256
+
257
+```yaml
258
+jobs:
259
+ - name: local
260
+ my.cnf: '/etc/my.cnf'
261
+
262
+```
263
+</details>
264
+
265
+###### Multi-instance
266
+
267
+> **Note**: When you define multiple jobs, their names must be unique.
268
+
269
+Local and remote instances.
270
+
271
+
272
+<details open><summary>Config</summary>
273
+
274
+```yaml
275
+jobs:
276
+ - name: local
277
+ dsn: netdata@tcp(127.0.0.1:3306)/
278
+
279
+ - name: remote
280
+ dsn: netconfig:password@tcp(203.0.113.0:3306)/
281
+
282
+```
283
+</details>
284
+
285
+
286
+
287
+## Alerts
288
+
289
+
290
+The following alerts are available:
291
+
292
+| Alert name | On metric | Description |
293
+|:------------|:----------|:------------|
294
+| [ mysql_10s_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.queries | number of slow queries in the last 10 seconds |
295
+| [ mysql_10s_table_locks_immediate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table immediate locks in the last 10 seconds |
296
+| [ mysql_10s_table_locks_waited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table waited locks in the last 10 seconds |
297
+| [ mysql_10s_waited_locks_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | ratio of waited table locks over the last 10 seconds |
298
+| [ mysql_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.connections_active | client connections utilization |
299
+| [ mysql_replication ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_status | replication status (0: stopped, 1: working) |
300
+| [ mysql_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_behind | difference between the timestamp of the latest transaction processed by the SQL thread and the timestamp of the same transaction when it was processed on the master |
301
+| [ mysql_galera_cluster_size_max_2m ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | maximum galera cluster size in the last 2 minutes starting one minute ago |
302
+| [ mysql_galera_cluster_size ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | current galera cluster size, compared to the maximum size in the last 2 minutes |
303
+| [ mysql_galera_cluster_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Donor/Desynced or Joined |
304
+| [ mysql_galera_cluster_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Undefined or Joining or Error |
305
+| [ mysql_galera_cluster_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_status | galera node is part of a nonoperational component. This occurs in cases of multiple membership changes that result in a loss of Quorum or in cases of split-brain situations. |
306
+
307
+
308
## Metrics
309
310
Metrics grouped by *scope*.
@@ -187,7 +427,7 @@ Metrics:
427
428
429
190
-## Functions
430
+## Live Data
431
432
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
433
@@ -460,246 +700,6 @@ Most recent error per query digest from Performance Schema history tables.
700
701
702
463
-## Alerts
464
-
465
-
466
-The following alerts are available:
467
-
468
-| Alert name | On metric | Description |
469
-|:------------|:----------|:------------|
470
-| [ mysql_10s_slow_queries ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.queries | number of slow queries in the last 10 seconds |
471
-| [ mysql_10s_table_locks_immediate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table immediate locks in the last 10 seconds |
472
-| [ mysql_10s_table_locks_waited ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | number of table waited locks in the last 10 seconds |
473
-| [ mysql_10s_waited_locks_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.table_locks | ratio of waited table locks over the last 10 seconds |
474
-| [ mysql_connections ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.connections_active | client connections utilization |
475
-| [ mysql_replication ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_status | replication status (0: stopped, 1: working) |
476
-| [ mysql_replication_lag ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.slave_behind | difference between the timestamp of the latest transaction processed by the SQL thread and the timestamp of the same transaction when it was processed on the master |
477
-| [ mysql_galera_cluster_size_max_2m ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | maximum galera cluster size in the last 2 minutes starting one minute ago |
478
-| [ mysql_galera_cluster_size ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_size | current galera cluster size, compared to the maximum size in the last 2 minutes |
479
-| [ mysql_galera_cluster_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Donor/Desynced or Joined |
480
-| [ mysql_galera_cluster_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_state | galera node state is either Undefined or Joining or Error |
481
-| [ mysql_galera_cluster_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/mysql.conf) | mysql.galera_cluster_status | galera node is part of a nonoperational component. This occurs in cases of multiple membership changes that result in a loss of Quorum or in cases of split-brain situations. |
482
-
483
-
484
-## Setup
485
-
486
-
487
-You can configure the **mysql** collector in two ways:
488
-
489
-| Method | Best for | How to |
490
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
491
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **mysql**, then click **+** to add a job. |
492
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/mysql.conf` and add a job. |
493
-
494
-:::important
495
-
496
-UI configuration requires paid Netdata Cloud plan.
497
-
498
-:::
499
-
500
-
501
-### Prerequisites
502
-
503
-#### Create netdata user
504
-
505
-A user account should have the following [permissions](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html):
506
-
507
-- [`USAGE`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_usage)
508
-- [`REPLICATION CLIENT`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_replication-client)
509
-- [`PROCESS`](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_process)
510
-
511
-To create the `netdata` user with these permissions, execute the following in the MySQL shell:
512
-
513
-- **MySQL and MariaDB < 10.5.9**
514
-
515
- ```mysql
516
- CREATE USER 'netdata'@'localhost';
517
- GRANT USAGE, REPLICATION CLIENT, PROCESS ON *.* TO 'netdata'@'localhost';
518
- FLUSH PRIVILEGES;
519
- ```
520
-
521
-- **MariaDB >= 10.5.9**
522
-
523
- For MariaDB 10.5.9 and later, use the `SLAVE MONITOR` privilege instead of `REPLICATION CLIENT`:
524
-
525
- ```mysql
526
- CREATE USER 'netdata'@'localhost';
527
- GRANT USAGE, SLAVE MONITOR, PROCESS ON *.* TO 'netdata'@'localhost';
528
- FLUSH PRIVILEGES;
529
- ```
530
-
531
-The `netdata` user will have the ability to connect to the MySQL server on localhost without a password.
532
-It will only be able to gather statistics without being able to alter or affect operations in any way.
533
-
534
-
535
-#### Enable User Statistics (optional)
536
-
537
-To collect per-user statistics, the [User Statistics](https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/query-optimizations/statistics-for-optimizing-queries/user-statistics) plugin must be enabled.
538
-This is available for **MariaDB** and **Percona**, not for MySQL.
539
-
540
-By default, statistics are not collected. To enable the plugin, set the `userstat` system variable.
541
-
542
-- **In a configuration file** (persistent, requires restart):
543
-
544
- ```ini
545
- [mariadb]
546
- userstat = 1
547
- ```
548
-
549
-- **Dynamically** (takes effect immediately, does not persist across restarts):
550
-
551
- ```mysql
552
- SET GLOBAL userstat=1;
553
- ```
554
-
555
-
556
-
557
-### Configuration
558
-
559
-#### Options
560
-
561
-The following options can be defined globally: update_every, autodetection_retry.
562
-
563
-
564
-<details open><summary>Config options</summary>
565
-
566
-
567
-
568
-| Group | Option | Description | Default | Required |
569
-|:------|:-----|:------------|:--------|:---------:|
570
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
571
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
572
-| **Target** | dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
573
-| | my.cnf | Path to a `my.cnf` file to read connection settings from the `[client]` section. | | no |
574
-| | timeout | Query timeout (seconds). | 1 | no |
575
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
576
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
577
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
578
-| | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no |
579
-| | functions.deadlock_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
580
-| | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no |
581
-| | functions.error_info.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
582
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
583
-
584
-
585
-</details>
586
-
587
-
588
-#### via UI
589
-
590
-Configure the **mysql** collector from the Netdata web interface:
591
-
592
-1. Go to **Nodes**.
593
-2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
594
-3. The **Collectors → Jobs** view opens by default.
595
-4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
596
-5. Click the **+** next to the **mysql** collector to add a new job.
597
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
598
- - **Test** runs the job with the provided settings and shows whether data can be collected.
599
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
600
-
601
-
602
-#### via File
603
-
604
-The configuration file name for this integration is `go.d/mysql.conf`.
605
-
606
-The file format is YAML. Generally, the structure is:
607
-
608
-```yaml
609
-update_every: 1
610
-autodetection_retry: 0
611
-jobs:
612
- - name: some_name1
613
- - name: some_name2
614
-```
615
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
616
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
617
-
618
-```bash
619
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
620
-sudo ./edit-config go.d/mysql.conf
621
-```
622
-
623
-##### Examples
624
-
625
-###### TCP socket
626
-
627
-An example configuration.
628
-
629
-<details open><summary>Config</summary>
630
-
631
-```yaml
632
-jobs:
633
- - name: local
634
- dsn: netdata@tcp(127.0.0.1:3306)/
635
-
636
-```
637
-</details>
638
-
639
-###### Unix socket
640
-
641
-An example configuration.
642
-
643
-<details open><summary>Config</summary>
644
-
645
-```yaml
646
-jobs:
647
- - name: local
648
- dsn: netdata@unix(/var/lib/mysql/mysql.sock)/
649
-
650
-```
651
-</details>
652
-
653
-###### Connection with password
654
-
655
-An example configuration.
656
-
657
-<details open><summary>Config</summary>
658
-
659
-```yaml
660
-jobs:
661
- - name: local
662
- dsn: netconfig:password@tcp(127.0.0.1:3306)/
663
-
664
-```
665
-</details>
666
-
667
-###### my.cnf
668
-
669
-An example configuration.
670
-
671
-<details open><summary>Config</summary>
672
-
673
-```yaml
674
-jobs:
675
- - name: local
676
- my.cnf: '/etc/my.cnf'
677
-
678
-```
679
-</details>
680
-
681
-###### Multi-instance
682
-
683
-> **Note**: When you define multiple jobs, their names must be unique.
684
-
685
-Local and remote instances.
686
-
687
-
688
-<details open><summary>Config</summary>
689
-
690
-```yaml
691
-jobs:
692
- - name: local
693
- dsn: netdata@tcp(127.0.0.1:3306)/
694
-
695
- - name: remote
696
- dsn: netconfig:password@tcp(203.0.113.0:3306)/
697
-
698
-```
699
-</details>
700
-
701
-
702
-
703
## Troubleshooting
704
705
### Debug Mode
src/go/plugin/go.d/collector/nats/integrations/nats.md
+169
-169
@@ -50,6 +50,175 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
+## Setup
54
+
55
+
56
+You can configure the **nats** collector in two ways:
57
+
58
+| Method | Best for | How to |
59
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
60
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nats**, then click **+** to add a job. |
61
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nats.conf` and add a job. |
62
+
63
+:::important
64
+
65
+UI configuration requires paid Netdata Cloud plan.
66
+
67
+:::
68
+
69
+
70
+### Prerequisites
71
+
72
+#### Enable NATS monitoring
73
+
74
+See [Enable monitoring](https://docs.nats.io/running-a-nats-service/nats_admin/monitoring#enabling-monitoring).
75
+
76
+
77
+
78
+### Configuration
79
+
80
+#### Options
81
+
82
+The following options can be defined globally: update_every, autodetection_retry.
83
+
84
+
85
+<details open><summary>Config options</summary>
86
+
87
+
88
+
89
+| Group | Option | Description | Default | Required |
90
+|:------|:-----|:------------|:--------|:---------:|
91
+| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
92
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
93
+| **Target** | url | Target endpoint URL. | http://127.0.0.1:8222 | yes |
94
+| | timeout | HTTP request timeout (seconds). | 1 | no |
95
+| **Validation** | healthz_check | Selects the `/healthz` [endpoint mode](https://docs.nats.io/running-a-nats-service/nats_admin/monitoring#health-healthz). Options: `default` (standard check), `js-enabled-only` (error if JetStream is disabled), `js-server-only` (skip account/stream/consumer checks). | default | no |
96
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
97
+| | password | Password for Basic HTTP authentication. | | no |
98
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
99
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
100
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
101
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
102
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
103
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
104
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
105
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
106
+| **Request** | method | HTTP method to use. | GET | no |
107
+| | body | Request body (e.g., for POST/PUT). | | no |
108
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
109
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
110
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
111
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
112
+
113
+
114
+</details>
115
+
116
+
117
+#### via UI
118
+
119
+Configure the **nats** collector from the Netdata web interface:
120
+
121
+1. Go to **Nodes**.
122
+2. Select the node **where you want the nats data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
123
+3. The **Collectors → Jobs** view opens by default.
124
+4. In the Search box, type _nats_ (or scroll the list) to locate the **nats** collector.
125
+5. Click the **+** next to the **nats** collector to add a new job.
126
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
127
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
128
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
129
+
130
+
131
+#### via File
132
+
133
+The configuration file name for this integration is `go.d/nats.conf`.
134
+
135
+The file format is YAML. Generally, the structure is:
136
+
137
+```yaml
138
+update_every: 1
139
+autodetection_retry: 0
140
+jobs:
141
+ - name: some_name1
142
+ - name: some_name2
143
+```
144
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
145
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
146
+
147
+```bash
148
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
149
+sudo ./edit-config go.d/nats.conf
150
+```
151
+
152
+##### Examples
153
+
154
+###### Basic
155
+
156
+A basic example configuration.
157
+
158
+```yaml
159
+jobs:
160
+ - name: local
161
+ url: http://127.0.0.1:8222
162
+
163
+```
164
+###### HTTP authentication
165
+
166
+Basic HTTP authentication.
167
+
168
+<details open><summary>Config</summary>
169
+
170
+```yaml
171
+jobs:
172
+ - name: local
173
+ url: http://127.0.0.1:8222
174
+ username: username
175
+ password: password
176
+
177
+```
178
+</details>
179
+
180
+###### HTTPS with self-signed certificate
181
+
182
+NATS with enabled HTTPS and self-signed certificate.
183
+
184
+<details open><summary>Config</summary>
185
+
186
+```yaml
187
+jobs:
188
+ - name: local
189
+ url: http://127.0.0.1:8222
190
+ tls_skip_verify: yes
191
+
192
+```
193
+</details>
194
+
195
+###### Multi-instance
196
+
197
+> **Note**: When you define multiple jobs, their names must be unique.
198
+
199
+Collecting metrics from local and remote instances.
200
+
201
+
202
+<details open><summary>Config</summary>
203
+
204
+```yaml
205
+jobs:
206
+ - name: local
207
+ url: http://127.0.0.1:8222
208
+
209
+ - name: remote
210
+ url: http://192.0.2.1:8222
211
+
212
+```
213
+</details>
214
+
215
+
216
+
217
+## Alerts
218
+
219
+There are no alerts configured by default for this integration.
220
+
221
+
222
## Metrics
223
224
Metrics grouped by *scope*.
@@ -233,175 +402,6 @@ Metrics:
402
403
404
236
-## Alerts
237
-
238
-There are no alerts configured by default for this integration.
239
-
240
-
241
-## Setup
242
-
243
-
244
-You can configure the **nats** collector in two ways:
245
-
246
-| Method | Best for | How to |
247
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
248
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nats**, then click **+** to add a job. |
249
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nats.conf` and add a job. |
250
-
251
-:::important
252
-
253
-UI configuration requires paid Netdata Cloud plan.
254
-
255
-:::
256
-
257
-
258
-### Prerequisites
259
-
260
-#### Enable NATS monitoring
261
-
262
-See [Enable monitoring](https://docs.nats.io/running-a-nats-service/nats_admin/monitoring#enabling-monitoring).
263
-
264
-
265
-
266
-### Configuration
267
-
268
-#### Options
269
-
270
-The following options can be defined globally: update_every, autodetection_retry.
271
-
272
-
273
-<details open><summary>Config options</summary>
274
-
275
-
276
-
277
-| Group | Option | Description | Default | Required |
278
-|:------|:-----|:------------|:--------|:---------:|
279
-| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
280
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
281
-| **Target** | url | Target endpoint URL. | http://127.0.0.1:8222 | yes |
282
-| | timeout | HTTP request timeout (seconds). | 1 | no |
283
-| **Validation** | healthz_check | Selects the `/healthz` [endpoint mode](https://docs.nats.io/running-a-nats-service/nats_admin/monitoring#health-healthz). Options: `default` (standard check), `js-enabled-only` (error if JetStream is disabled), `js-server-only` (skip account/stream/consumer checks). | default | no |
284
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
285
-| | password | Password for Basic HTTP authentication. | | no |
286
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
287
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
288
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
289
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
290
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
291
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
292
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
293
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
294
-| **Request** | method | HTTP method to use. | GET | no |
295
-| | body | Request body (e.g., for POST/PUT). | | no |
296
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
297
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
298
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
299
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
300
-
301
-
302
-</details>
303
-
304
-
305
-#### via UI
306
-
307
-Configure the **nats** collector from the Netdata web interface:
308
-
309
-1. Go to **Nodes**.
310
-2. Select the node **where you want the nats data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
311
-3. The **Collectors → Jobs** view opens by default.
312
-4. In the Search box, type _nats_ (or scroll the list) to locate the **nats** collector.
313
-5. Click the **+** next to the **nats** collector to add a new job.
314
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
315
- - **Test** runs the job with the provided settings and shows whether data can be collected.
316
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
317
-
318
-
319
-#### via File
320
-
321
-The configuration file name for this integration is `go.d/nats.conf`.
322
-
323
-The file format is YAML. Generally, the structure is:
324
-
325
-```yaml
326
-update_every: 1
327
-autodetection_retry: 0
328
-jobs:
329
- - name: some_name1
330
- - name: some_name2
331
-```
332
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
333
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
334
-
335
-```bash
336
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
337
-sudo ./edit-config go.d/nats.conf
338
-```
339
-
340
-##### Examples
341
-
342
-###### Basic
343
-
344
-A basic example configuration.
345
-
346
-```yaml
347
-jobs:
348
- - name: local
349
- url: http://127.0.0.1:8222
350
-
351
-```
352
-###### HTTP authentication
353
-
354
-Basic HTTP authentication.
355
-
356
-<details open><summary>Config</summary>
357
-
358
-```yaml
359
-jobs:
360
- - name: local
361
- url: http://127.0.0.1:8222
362
- username: username
363
- password: password
364
-
365
-```
366
-</details>
367
-
368
-###### HTTPS with self-signed certificate
369
-
370
-NATS with enabled HTTPS and self-signed certificate.
371
-
372
-<details open><summary>Config</summary>
373
-
374
-```yaml
375
-jobs:
376
- - name: local
377
- url: http://127.0.0.1:8222
378
- tls_skip_verify: yes
379
-
380
-```
381
-</details>
382
-
383
-###### Multi-instance
384
-
385
-> **Note**: When you define multiple jobs, their names must be unique.
386
-
387
-Collecting metrics from local and remote instances.
388
-
389
-
390
-<details open><summary>Config</summary>
391
-
392
-```yaml
393
-jobs:
394
- - name: local
395
- url: http://127.0.0.1:8222
396
-
397
- - name: remote
398
- url: http://192.0.2.1:8222
399
-
400
-```
401
-</details>
402
-
403
-
404
-
405
## Troubleshooting
406
407
### Debug Mode
src/go/plugin/go.d/collector/nginx/integrations/nginx.md
+30
-30
@@ -61,36 +61,6 @@ The default configuration for this integration does not impose any limits on dat
61
62
The default configuration for this integration is not expected to impose a significant performance impact on the system.
63
64
-## Metrics
65
-
66
-Metrics grouped by *scope*.
67
-
68
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
69
-
70
-
71
-
72
-### Per NGINX instance
73
-
74
-These metrics refer to the entire monitored application.
75
-
76
-This scope has no labels.
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| nginx.connections | active | connections |
83
-| nginx.connections_status | reading, writing, idle | connections |
84
-| nginx.connections_accepted_handled | accepted, handled | connections/s |
85
-| nginx.requests | requests | requests/s |
86
-
87
-
88
-
89
-## Alerts
90
-
91
-There are no alerts configured by default for this integration.
92
-
93
-
64
## Setup
65
66
@@ -291,6 +261,36 @@ jobs:
261
262
263
264
+## Alerts
265
+
266
+There are no alerts configured by default for this integration.
267
+
268
+
269
+## Metrics
270
+
271
+Metrics grouped by *scope*.
272
+
273
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
274
+
275
+
276
+
277
+### Per NGINX instance
278
+
279
+These metrics refer to the entire monitored application.
280
+
281
+This scope has no labels.
282
+
283
+Metrics:
284
+
285
+| Metric | Dimensions | Unit |
286
+|:------|:----------|:----|
287
+| nginx.connections | active | connections |
288
+| nginx.connections_status | reading, writing, idle | connections |
289
+| nginx.connections_accepted_handled | accepted, handled | connections/s |
290
+| nginx.requests | requests | requests/s |
291
+
292
+
293
+
294
## Troubleshooting
295
296
### Debug Mode
src/go/plugin/go.d/collector/nginxplus/integrations/nginx_plus.md
+172
-172
@@ -45,6 +45,178 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
+## Setup
49
+
50
+
51
+You can configure the **nginxplus** collector in two ways:
52
+
53
+| Method | Best for | How to |
54
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
55
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nginxplus**, then click **+** to add a job. |
56
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nginxplus.conf` and add a job. |
57
+
58
+:::important
59
+
60
+UI configuration requires paid Netdata Cloud plan.
61
+
62
+:::
63
+
64
+
65
+### Prerequisites
66
+
67
+#### Config API
68
+
69
+To configure API, see the [official documentation](https://docs.nginx.com/nginx/admin-guide/monitoring/live-activity-monitoring/#configuring-the-api).
70
+
71
+
72
+
73
+### Configuration
74
+
75
+#### Options
76
+
77
+The following options can be defined globally: update_every, autodetection_retry.
78
+
79
+
80
+<details open><summary>Config options</summary>
81
+
82
+
83
+
84
+| Group | Option | Description | Default | Required |
85
+|:------|:-----|:------------|:--------|:---------:|
86
+| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
87
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
88
+| **Target** | url | Target endpoint URL. | http://127.0.0.1 | yes |
89
+| | timeout | HTTP request timeout (seconds). | 1 | no |
90
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
91
+| | password | Password for Basic HTTP authentication. | | no |
92
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
93
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
94
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
95
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
96
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
97
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
98
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
99
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
100
+| **Request** | method | HTTP method to use. | GET | no |
101
+| | body | Request body (e.g., for POST/PUT). | | no |
102
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
103
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
104
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
105
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
106
+
107
+
108
+</details>
109
+
110
+
111
+#### via UI
112
+
113
+Configure the **nginxplus** collector from the Netdata web interface:
114
+
115
+1. Go to **Nodes**.
116
+2. Select the node **where you want the nginxplus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
117
+3. The **Collectors → Jobs** view opens by default.
118
+4. In the Search box, type _nginxplus_ (or scroll the list) to locate the **nginxplus** collector.
119
+5. Click the **+** next to the **nginxplus** collector to add a new job.
120
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
121
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
122
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
123
+
124
+
125
+#### via File
126
+
127
+The configuration file name for this integration is `go.d/nginxplus.conf`.
128
+
129
+The file format is YAML. Generally, the structure is:
130
+
131
+```yaml
132
+update_every: 1
133
+autodetection_retry: 0
134
+jobs:
135
+ - name: some_name1
136
+ - name: some_name2
137
+```
138
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
139
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
140
+
141
+```bash
142
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
143
+sudo ./edit-config go.d/nginxplus.conf
144
+```
145
+
146
+##### Examples
147
+
148
+###### Basic
149
+
150
+A basic example configuration.
151
+
152
+<details open><summary>Config</summary>
153
+
154
+```yaml
155
+jobs:
156
+ - name: local
157
+ url: http://127.0.0.1
158
+
159
+```
160
+</details>
161
+
162
+###### HTTP authentication
163
+
164
+Basic HTTP authentication.
165
+
166
+<details open><summary>Config</summary>
167
+
168
+```yaml
169
+jobs:
170
+ - name: local
171
+ url: http://127.0.0.1
172
+ username: username
173
+ password: password
174
+
175
+```
176
+</details>
177
+
178
+###### HTTPS with self-signed certificate
179
+
180
+NGINX Plus with enabled HTTPS and self-signed certificate.
181
+
182
+<details open><summary>Config</summary>
183
+
184
+```yaml
185
+jobs:
186
+ - name: local
187
+ url: https://127.0.0.1
188
+ tls_skip_verify: yes
189
+
190
+```
191
+</details>
192
+
193
+###### Multi-instance
194
+
195
+> **Note**: When you define multiple jobs, their names must be unique.
196
+
197
+Collecting metrics from local and remote instances.
198
+
199
+
200
+<details open><summary>Config</summary>
201
+
202
+```yaml
203
+jobs:
204
+ - name: local
205
+ url: http://127.0.0.1
206
+
207
+ - name: remote
208
+ url: http://192.0.2.1
209
+
210
+```
211
+</details>
212
+
213
+
214
+
215
+## Alerts
216
+
217
+There are no alerts configured by default for this integration.
218
+
219
+
220
## Metrics
221
222
Metrics grouped by *scope*.
@@ -256,178 +428,6 @@ Metrics:
428
429
430
259
-## Alerts
260
-
261
-There are no alerts configured by default for this integration.
262
-
263
-
264
-## Setup
265
-
266
-
267
-You can configure the **nginxplus** collector in two ways:
268
-
269
-| Method | Best for | How to |
270
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
271
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nginxplus**, then click **+** to add a job. |
272
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nginxplus.conf` and add a job. |
273
-
274
-:::important
275
-
276
-UI configuration requires paid Netdata Cloud plan.
277
-
278
-:::
279
-
280
-
281
-### Prerequisites
282
-
283
-#### Config API
284
-
285
-To configure API, see the [official documentation](https://docs.nginx.com/nginx/admin-guide/monitoring/live-activity-monitoring/#configuring-the-api).
286
-
287
-
288
-
289
-### Configuration
290
-
291
-#### Options
292
-
293
-The following options can be defined globally: update_every, autodetection_retry.
294
-
295
-
296
-<details open><summary>Config options</summary>
297
-
298
-
299
-
300
-| Group | Option | Description | Default | Required |
301
-|:------|:-----|:------------|:--------|:---------:|
302
-| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
303
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
304
-| **Target** | url | Target endpoint URL. | http://127.0.0.1 | yes |
305
-| | timeout | HTTP request timeout (seconds). | 1 | no |
306
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
307
-| | password | Password for Basic HTTP authentication. | | no |
308
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
309
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
310
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
311
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
312
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
313
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
314
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
315
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
316
-| **Request** | method | HTTP method to use. | GET | no |
317
-| | body | Request body (e.g., for POST/PUT). | | no |
318
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
319
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
320
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
321
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
322
-
323
-
324
-</details>
325
-
326
-
327
-#### via UI
328
-
329
-Configure the **nginxplus** collector from the Netdata web interface:
330
-
331
-1. Go to **Nodes**.
332
-2. Select the node **where you want the nginxplus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
333
-3. The **Collectors → Jobs** view opens by default.
334
-4. In the Search box, type _nginxplus_ (or scroll the list) to locate the **nginxplus** collector.
335
-5. Click the **+** next to the **nginxplus** collector to add a new job.
336
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
337
- - **Test** runs the job with the provided settings and shows whether data can be collected.
338
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
339
-
340
-
341
-#### via File
342
-
343
-The configuration file name for this integration is `go.d/nginxplus.conf`.
344
-
345
-The file format is YAML. Generally, the structure is:
346
-
347
-```yaml
348
-update_every: 1
349
-autodetection_retry: 0
350
-jobs:
351
- - name: some_name1
352
- - name: some_name2
353
-```
354
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
355
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
356
-
357
-```bash
358
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
359
-sudo ./edit-config go.d/nginxplus.conf
360
-```
361
-
362
-##### Examples
363
-
364
-###### Basic
365
-
366
-A basic example configuration.
367
-
368
-<details open><summary>Config</summary>
369
-
370
-```yaml
371
-jobs:
372
- - name: local
373
- url: http://127.0.0.1
374
-
375
-```
376
-</details>
377
-
378
-###### HTTP authentication
379
-
380
-Basic HTTP authentication.
381
-
382
-<details open><summary>Config</summary>
383
-
384
-```yaml
385
-jobs:
386
- - name: local
387
- url: http://127.0.0.1
388
- username: username
389
- password: password
390
-
391
-```
392
-</details>
393
-
394
-###### HTTPS with self-signed certificate
395
-
396
-NGINX Plus with enabled HTTPS and self-signed certificate.
397
-
398
-<details open><summary>Config</summary>
399
-
400
-```yaml
401
-jobs:
402
- - name: local
403
- url: https://127.0.0.1
404
- tls_skip_verify: yes
405
-
406
-```
407
-</details>
408
-
409
-###### Multi-instance
410
-
411
-> **Note**: When you define multiple jobs, their names must be unique.
412
-
413
-Collecting metrics from local and remote instances.
414
-
415
-
416
-<details open><summary>Config</summary>
417
-
418
-```yaml
419
-jobs:
420
- - name: local
421
- url: http://127.0.0.1
422
-
423
- - name: remote
424
- url: http://192.0.2.1
425
-
426
-```
427
-</details>
428
-
429
-
430
-
431
## Troubleshooting
432
433
### Debug Mode
src/go/plugin/go.d/collector/nginxunit/integrations/nginx_unit.md
+29
-29
@@ -50,35 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per NGINX Unit instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| nginxunit.requests_rate | requests | requests/s |
72
-| nginxunit.connections_rate | accepted, closed | connections/s |
73
-| nginxunit.connections_current | active, idle | connections |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
53
## Setup
54
55
@@ -242,6 +213,35 @@ jobs:
213
214
215
216
+## Alerts
217
+
218
+There are no alerts configured by default for this integration.
219
+
220
+
221
+## Metrics
222
+
223
+Metrics grouped by *scope*.
224
+
225
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
226
+
227
+
228
+
229
+### Per NGINX Unit instance
230
+
231
+These metrics refer to the entire monitored application.
232
+
233
+This scope has no labels.
234
+
235
+Metrics:
236
+
237
+| Metric | Dimensions | Unit |
238
+|:------|:----------|:----|
239
+| nginxunit.requests_rate | requests | requests/s |
240
+| nginxunit.connections_rate | accepted, closed | connections/s |
241
+| nginxunit.connections_current | active, idle | connections |
242
+
243
+
244
+
245
## Troubleshooting
246
247
### Debug Mode
src/go/plugin/go.d/collector/nginxvts/integrations/nginx_vts.md
+36
-36
@@ -54,42 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per NGINX VTS instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| nginxvts.requests_total | requests | requests/s |
76
-| nginxvts.active_connections | active | connections |
77
-| nginxvts.connections_total | reading, writing, waiting, accepted, handled | connections/s |
78
-| nginxvts.uptime | uptime | seconds |
79
-| nginxvts.shm_usage | max, used | bytes |
80
-| nginxvts.shm_used_node | used | nodes |
81
-| nginxvts.server_requests_total | requests | requests/s |
82
-| nginxvts.server_responses_total | 1xx, 2xx, 3xx, 4xx, 5xx | responses/s |
83
-| nginxvts.server_traffic_total | in, out | bytes/s |
84
-| nginxvts.server_cache_total | miss, bypass, expired, stale, updating, revalidated, hit, scarce | events/s |
85
-
86
-
87
-
88
-## Alerts
89
-
90
-There are no alerts configured by default for this integration.
91
-
92
-
57
## Setup
58
59
@@ -254,6 +218,42 @@ jobs:
218
219
220
221
+## Alerts
222
+
223
+There are no alerts configured by default for this integration.
224
+
225
+
226
+## Metrics
227
+
228
+Metrics grouped by *scope*.
229
+
230
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
231
+
232
+
233
+
234
+### Per NGINX VTS instance
235
+
236
+These metrics refer to the entire monitored application.
237
+
238
+This scope has no labels.
239
+
240
+Metrics:
241
+
242
+| Metric | Dimensions | Unit |
243
+|:------|:----------|:----|
244
+| nginxvts.requests_total | requests | requests/s |
245
+| nginxvts.active_connections | active | connections |
246
+| nginxvts.connections_total | reading, writing, waiting, accepted, handled | connections/s |
247
+| nginxvts.uptime | uptime | seconds |
248
+| nginxvts.shm_usage | max, used | bytes |
249
+| nginxvts.shm_used_node | used | nodes |
250
+| nginxvts.server_requests_total | requests | requests/s |
251
+| nginxvts.server_responses_total | 1xx, 2xx, 3xx, 4xx, 5xx | responses/s |
252
+| nginxvts.server_traffic_total | in, out | bytes/s |
253
+| nginxvts.server_cache_total | miss, bypass, expired, stale, updating, revalidated, hit, scarce | events/s |
254
+
255
+
256
+
257
## Troubleshooting
258
259
### Debug Mode
src/go/plugin/go.d/collector/nsd/integrations/nsd.md
+39
-39
@@ -51,45 +51,6 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
-## Metrics
55
-
56
-Metrics grouped by *scope*.
57
-
58
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
59
-
60
-
61
-
62
-### Per NSD instance
63
-
64
-These metrics refer to the the entire monitored application.
65
-
66
-This scope has no labels.
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| nsd.queries | queries | queries/s |
73
-| nsd.queries_by_type | A, NS, MD, MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR, HINFO, MINFO, MX, TXT, RP, AFSDB, X25, ISDN, RT, NSAP, SIG, KEY, PX, AAAA, LOC, NXT, SRV, NAPTR, KX, CERT, DNAME, OPT, APL, DS, SSHFP, IPSECKEY, RRSIG, NSEC, DNSKEY, DHCID, NSEC3, NSEC3PARAM, TLSA, SMIMEA, CDS, CDNSKEY, OPENPGPKEY, CSYNC, ZONEMD, SVCB, HTTPS, SPF, NID, L32, L64, LP, EUI48, EUI64, URI, CAA, AVC, DLV, IXFR, AXFR, MAILB, MAILA, ANY | queries/s |
74
-| nsd.queries_by_opcode | QUERY, IQUERY, STATUS, NOTIFY, UPDATE, OTHER | queries/s |
75
-| nsd.queries_by_class | IN, CS, CH, HS | queries/s |
76
-| nsd.queries_by_protocol | udp, udp6, tcp, tcp6, tls, tls6 | queries/s |
77
-| nsd.answers_by_rcode | NOERROR, FORMERR, SERVFAIL, NXDOMAIN, NOTIMP, REFUSED, YXDOMAIN, YXRRSET, NXRRSET, NOTAUTH, NOTZONE, RCODE11, RCODE12, RCODE13, RCODE14, RCODE15, BADVERS | answers/s |
78
-| nsd.errors | query, answer | errors/s |
79
-| nsd.drops | query | drops/s |
80
-| nsd.zones | master, slave | zones |
81
-| nsd.zone_transfers_requests | AXFR, IXFR | requests/s |
82
-| nsd.zone_transfer_memory | used | bytes |
83
-| nsd.database_size | disk, mem | bytes |
84
-| nsd.uptime | uptime | seconds |
85
-
86
-
87
-
88
-## Alerts
89
-
90
-There are no alerts configured by default for this integration.
91
-
92
-
54
## Setup
55
56
@@ -184,6 +145,45 @@ jobs:
145
146
147
148
+## Alerts
149
+
150
+There are no alerts configured by default for this integration.
151
+
152
+
153
+## Metrics
154
+
155
+Metrics grouped by *scope*.
156
+
157
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
158
+
159
+
160
+
161
+### Per NSD instance
162
+
163
+These metrics refer to the the entire monitored application.
164
+
165
+This scope has no labels.
166
+
167
+Metrics:
168
+
169
+| Metric | Dimensions | Unit |
170
+|:------|:----------|:----|
171
+| nsd.queries | queries | queries/s |
172
+| nsd.queries_by_type | A, NS, MD, MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR, HINFO, MINFO, MX, TXT, RP, AFSDB, X25, ISDN, RT, NSAP, SIG, KEY, PX, AAAA, LOC, NXT, SRV, NAPTR, KX, CERT, DNAME, OPT, APL, DS, SSHFP, IPSECKEY, RRSIG, NSEC, DNSKEY, DHCID, NSEC3, NSEC3PARAM, TLSA, SMIMEA, CDS, CDNSKEY, OPENPGPKEY, CSYNC, ZONEMD, SVCB, HTTPS, SPF, NID, L32, L64, LP, EUI48, EUI64, URI, CAA, AVC, DLV, IXFR, AXFR, MAILB, MAILA, ANY | queries/s |
173
+| nsd.queries_by_opcode | QUERY, IQUERY, STATUS, NOTIFY, UPDATE, OTHER | queries/s |
174
+| nsd.queries_by_class | IN, CS, CH, HS | queries/s |
175
+| nsd.queries_by_protocol | udp, udp6, tcp, tcp6, tls, tls6 | queries/s |
176
+| nsd.answers_by_rcode | NOERROR, FORMERR, SERVFAIL, NXDOMAIN, NOTIMP, REFUSED, YXDOMAIN, YXRRSET, NXRRSET, NOTAUTH, NOTZONE, RCODE11, RCODE12, RCODE13, RCODE14, RCODE15, BADVERS | answers/s |
177
+| nsd.errors | query, answer | errors/s |
178
+| nsd.drops | query | drops/s |
179
+| nsd.zones | master, slave | zones |
180
+| nsd.zone_transfers_requests | AXFR, IXFR | requests/s |
181
+| nsd.zone_transfer_memory | used | bytes |
182
+| nsd.database_size | disk, mem | bytes |
183
+| nsd.uptime | uptime | seconds |
184
+
185
+
186
+
187
## Troubleshooting
188
189
### Debug Mode
src/go/plugin/go.d/collector/ntpd/integrations/ntpd.md
+63
-63
@@ -45,69 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per NTPd instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| ntpd.sys_offset | offset | milliseconds |
67
-| ntpd.sys_jitter | system, clock | milliseconds |
68
-| ntpd.sys_frequency | frequency | ppm |
69
-| ntpd.sys_wander | clock | ppm |
70
-| ntpd.sys_rootdelay | delay | milliseconds |
71
-| ntpd.sys_rootdisp | dispersion | milliseconds |
72
-| ntpd.sys_stratum | stratum | stratum |
73
-| ntpd.sys_tc | current, minimum | log2 |
74
-| ntpd.sys_precision | precision | log2 |
75
-
76
-### Per peer
77
-
78
-These metrics refer to the NTPd peer.
79
-
80
-Labels:
81
-
82
-| Label | Description |
83
-|:-----------|:----------------|
84
-| peer_address | peer's source IP address |
85
-
86
-Metrics:
87
-
88
-| Metric | Dimensions | Unit |
89
-|:------|:----------|:----|
90
-| ntpd.peer_offset | offset | milliseconds |
91
-| ntpd.peer_delay | delay | milliseconds |
92
-| ntpd.peer_dispersion | dispersion | milliseconds |
93
-| ntpd.peer_jitter | jitter | milliseconds |
94
-| ntpd.peer_xleave | xleave | milliseconds |
95
-| ntpd.peer_rootdelay | rootdelay | milliseconds |
96
-| ntpd.peer_rootdisp | dispersion | milliseconds |
97
-| ntpd.peer_stratum | stratum | stratum |
98
-| ntpd.peer_hmode | hmode | hmode |
99
-| ntpd.peer_pmode | pmode | pmode |
100
-| ntpd.peer_hpoll | hpoll | log2 |
101
-| ntpd.peer_ppoll | ppoll | log2 |
102
-| ntpd.peer_precision | precision | log2 |
103
-
104
-
105
-
106
-## Alerts
107
-
108
-There are no alerts configured by default for this integration.
109
-
110
-
48
## Setup
49
50
@@ -241,6 +178,69 @@ jobs:
178
179
180
181
+## Alerts
182
+
183
+There are no alerts configured by default for this integration.
184
+
185
+
186
+## Metrics
187
+
188
+Metrics grouped by *scope*.
189
+
190
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
191
+
192
+
193
+
194
+### Per NTPd instance
195
+
196
+These metrics refer to the entire monitored application.
197
+
198
+This scope has no labels.
199
+
200
+Metrics:
201
+
202
+| Metric | Dimensions | Unit |
203
+|:------|:----------|:----|
204
+| ntpd.sys_offset | offset | milliseconds |
205
+| ntpd.sys_jitter | system, clock | milliseconds |
206
+| ntpd.sys_frequency | frequency | ppm |
207
+| ntpd.sys_wander | clock | ppm |
208
+| ntpd.sys_rootdelay | delay | milliseconds |
209
+| ntpd.sys_rootdisp | dispersion | milliseconds |
210
+| ntpd.sys_stratum | stratum | stratum |
211
+| ntpd.sys_tc | current, minimum | log2 |
212
+| ntpd.sys_precision | precision | log2 |
213
+
214
+### Per peer
215
+
216
+These metrics refer to the NTPd peer.
217
+
218
+Labels:
219
+
220
+| Label | Description |
221
+|:-----------|:----------------|
222
+| peer_address | peer's source IP address |
223
+
224
+Metrics:
225
+
226
+| Metric | Dimensions | Unit |
227
+|:------|:----------|:----|
228
+| ntpd.peer_offset | offset | milliseconds |
229
+| ntpd.peer_delay | delay | milliseconds |
230
+| ntpd.peer_dispersion | dispersion | milliseconds |
231
+| ntpd.peer_jitter | jitter | milliseconds |
232
+| ntpd.peer_xleave | xleave | milliseconds |
233
+| ntpd.peer_rootdelay | rootdelay | milliseconds |
234
+| ntpd.peer_rootdisp | dispersion | milliseconds |
235
+| ntpd.peer_stratum | stratum | stratum |
236
+| ntpd.peer_hmode | hmode | hmode |
237
+| ntpd.peer_pmode | pmode | pmode |
238
+| ntpd.peer_hpoll | hpoll | log2 |
239
+| ntpd.peer_ppoll | ppoll | log2 |
240
+| ntpd.peer_precision | precision | log2 |
241
+
242
+
243
+
244
## Troubleshooting
245
246
### Debug Mode
src/go/plugin/go.d/collector/nvidia_smi/integrations/nvidia_gpu.md
+67
-67
@@ -50,73 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per gpu
62
-
63
-These metrics refer to the GPU.
64
-
65
-Labels:
66
-
67
-| Label | Description |
68
-|:-----------|:----------------|
69
-| uuid | GPU uuid (e.g. GPU-27b94a00-ed54-5c24-b1fd-1054085de32a) |
70
-| index | GPU index (nvidia_smi typically orders GPUs by PCI bus ID) |
71
-| product_name | GPU product name (e.g. NVIDIA A100-SXM4-40GB) |
72
-
73
-Metrics:
74
-
75
-| Metric | Dimensions | Unit |
76
-|:------|:----------|:----|
77
-| nvidia_smi.gpu_pcie_bandwidth_usage | rx, tx | B/s |
78
-| nvidia_smi.gpu_pcie_bandwidth_utilization | rx, tx | % |
79
-| nvidia_smi.gpu_fan_speed_perc | fan_speed | % |
80
-| nvidia_smi.gpu_utilization | gpu | % |
81
-| nvidia_smi.gpu_memory_utilization | memory | % |
82
-| nvidia_smi.gpu_decoder_utilization | decoder | % |
83
-| nvidia_smi.gpu_encoder_utilization | encoder | % |
84
-| nvidia_smi.gpu_frame_buffer_memory_usage | free, used, reserved | B |
85
-| nvidia_smi.gpu_bar1_memory_usage | free, used | B |
86
-| nvidia_smi.gpu_temperature | temperature | Celsius |
87
-| nvidia_smi.gpu_voltage | voltage | V |
88
-| nvidia_smi.gpu_clock_freq | graphics, video, sm, mem | MHz |
89
-| nvidia_smi.gpu_power_draw | power_draw | Watts |
90
-| nvidia_smi.gpu_performance_state | P0-P15 | state |
91
-| nvidia_smi.gpu_mig_mode_current_status | enabled, disabled | status |
92
-| nvidia_smi.gpu_mig_devices_count | mig | devices |
93
-
94
-### Per mig
95
-
96
-These metrics refer to the Multi-Instance GPU (MIG).
97
-
98
-Labels:
99
-
100
-| Label | Description |
101
-|:-----------|:----------------|
102
-| uuid | GPU uuid (e.g. GPU-27b94a00-ed54-5c24-b1fd-1054085de32a) |
103
-| product_name | GPU product name (e.g. NVIDIA A100-SXM4-40GB) |
104
-| gpu_instance_id | GPU instance id (e.g. 1) |
105
-
106
-Metrics:
107
-
108
-| Metric | Dimensions | Unit |
109
-|:------|:----------|:----|
110
-| nvidia_smi.gpu_mig_frame_buffer_memory_usage | free, used, reserved | B |
111
-| nvidia_smi.gpu_mig_bar1_memory_usage | free, used | B |
112
-
113
-
114
-
115
-## Alerts
116
-
117
-There are no alerts configured by default for this integration.
118
-
119
-
53
## Setup
54
55
@@ -214,6 +147,73 @@ jobs:
147
148
149
150
+## Alerts
151
+
152
+There are no alerts configured by default for this integration.
153
+
154
+
155
+## Metrics
156
+
157
+Metrics grouped by *scope*.
158
+
159
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
160
+
161
+
162
+
163
+### Per gpu
164
+
165
+These metrics refer to the GPU.
166
+
167
+Labels:
168
+
169
+| Label | Description |
170
+|:-----------|:----------------|
171
+| uuid | GPU uuid (e.g. GPU-27b94a00-ed54-5c24-b1fd-1054085de32a) |
172
+| index | GPU index (nvidia_smi typically orders GPUs by PCI bus ID) |
173
+| product_name | GPU product name (e.g. NVIDIA A100-SXM4-40GB) |
174
+
175
+Metrics:
176
+
177
+| Metric | Dimensions | Unit |
178
+|:------|:----------|:----|
179
+| nvidia_smi.gpu_pcie_bandwidth_usage | rx, tx | B/s |
180
+| nvidia_smi.gpu_pcie_bandwidth_utilization | rx, tx | % |
181
+| nvidia_smi.gpu_fan_speed_perc | fan_speed | % |
182
+| nvidia_smi.gpu_utilization | gpu | % |
183
+| nvidia_smi.gpu_memory_utilization | memory | % |
184
+| nvidia_smi.gpu_decoder_utilization | decoder | % |
185
+| nvidia_smi.gpu_encoder_utilization | encoder | % |
186
+| nvidia_smi.gpu_frame_buffer_memory_usage | free, used, reserved | B |
187
+| nvidia_smi.gpu_bar1_memory_usage | free, used | B |
188
+| nvidia_smi.gpu_temperature | temperature | Celsius |
189
+| nvidia_smi.gpu_voltage | voltage | V |
190
+| nvidia_smi.gpu_clock_freq | graphics, video, sm, mem | MHz |
191
+| nvidia_smi.gpu_power_draw | power_draw | Watts |
192
+| nvidia_smi.gpu_performance_state | P0-P15 | state |
193
+| nvidia_smi.gpu_mig_mode_current_status | enabled, disabled | status |
194
+| nvidia_smi.gpu_mig_devices_count | mig | devices |
195
+
196
+### Per mig
197
+
198
+These metrics refer to the Multi-Instance GPU (MIG).
199
+
200
+Labels:
201
+
202
+| Label | Description |
203
+|:-----------|:----------------|
204
+| uuid | GPU uuid (e.g. GPU-27b94a00-ed54-5c24-b1fd-1054085de32a) |
205
+| product_name | GPU product name (e.g. NVIDIA A100-SXM4-40GB) |
206
+| gpu_instance_id | GPU instance id (e.g. 1) |
207
+
208
+Metrics:
209
+
210
+| Metric | Dimensions | Unit |
211
+|:------|:----------|:----|
212
+| nvidia_smi.gpu_mig_frame_buffer_memory_usage | free, used, reserved | B |
213
+| nvidia_smi.gpu_mig_bar1_memory_usage | free, used | B |
214
+
215
+
216
+
217
## Troubleshooting
218
219
### Debug Mode
src/go/plugin/go.d/collector/nvme/integrations/nvme_devices.md
+52
-52
@@ -48,58 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per device
60
-
61
-These metrics refer to the NVME device.
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| device | NVMe device name |
68
-| model_number | NVMe device model |
69
-
70
-Metrics:
71
-
72
-| Metric | Dimensions | Unit |
73
-|:------|:----------|:----|
74
-| nvme.device_estimated_endurance_perc | used | % |
75
-| nvme.device_available_spare_perc | spare | % |
76
-| nvme.device_composite_temperature | temperature | celsius |
77
-| nvme.device_io_transferred_count | read, written | bytes |
78
-| nvme.device_power_cycles_count | power | cycles |
79
-| nvme.device_power_on_time | power-on | seconds |
80
-| nvme.device_critical_warnings_state | available_spare, temp_threshold, nvm_subsystem_reliability, read_only, volatile_mem_backup_failed, persistent_memory_read_only | state |
81
-| nvme.device_unsafe_shutdowns_count | unsafe | shutdowns |
82
-| nvme.device_media_errors_rate | media | errors/s |
83
-| nvme.device_error_log_entries_rate | error_log | entries/s |
84
-| nvme.device_warning_composite_temperature_time | wctemp | seconds |
85
-| nvme.device_critical_composite_temperature_time | cctemp | seconds |
86
-| nvme.device_thermal_mgmt_temp1_transitions_rate | temp1 | transitions/s |
87
-| nvme.device_thermal_mgmt_temp2_transitions_rate | temp2 | transitions/s |
88
-| nvme.device_thermal_mgmt_temp1_time | temp1 | seconds |
89
-| nvme.device_thermal_mgmt_temp2_time | temp2 | seconds |
90
-
91
-
92
-
93
-## Alerts
94
-
95
-
96
-The following alerts are available:
97
-
98
-| Alert name | On metric | Description |
99
-|:------------|:----------|:------------|
100
-| [ nvme_device_critical_warnings_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nvme.conf) | nvme.device_critical_warnings_state | NVMe device ${label:device} has critical warnings |
101
-
102
-
51
## Setup
52
53
@@ -223,6 +171,58 @@ jobs:
171
172
173
174
+## Alerts
175
+
176
+
177
+The following alerts are available:
178
+
179
+| Alert name | On metric | Description |
180
+|:------------|:----------|:------------|
181
+| [ nvme_device_critical_warnings_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nvme.conf) | nvme.device_critical_warnings_state | NVMe device ${label:device} has critical warnings |
182
+
183
+
184
+## Metrics
185
+
186
+Metrics grouped by *scope*.
187
+
188
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
189
+
190
+
191
+
192
+### Per device
193
+
194
+These metrics refer to the NVME device.
195
+
196
+Labels:
197
+
198
+| Label | Description |
199
+|:-----------|:----------------|
200
+| device | NVMe device name |
201
+| model_number | NVMe device model |
202
+
203
+Metrics:
204
+
205
+| Metric | Dimensions | Unit |
206
+|:------|:----------|:----|
207
+| nvme.device_estimated_endurance_perc | used | % |
208
+| nvme.device_available_spare_perc | spare | % |
209
+| nvme.device_composite_temperature | temperature | celsius |
210
+| nvme.device_io_transferred_count | read, written | bytes |
211
+| nvme.device_power_cycles_count | power | cycles |
212
+| nvme.device_power_on_time | power-on | seconds |
213
+| nvme.device_critical_warnings_state | available_spare, temp_threshold, nvm_subsystem_reliability, read_only, volatile_mem_backup_failed, persistent_memory_read_only | state |
214
+| nvme.device_unsafe_shutdowns_count | unsafe | shutdowns |
215
+| nvme.device_media_errors_rate | media | errors/s |
216
+| nvme.device_error_log_entries_rate | error_log | entries/s |
217
+| nvme.device_warning_composite_temperature_time | wctemp | seconds |
218
+| nvme.device_critical_composite_temperature_time | cctemp | seconds |
219
+| nvme.device_thermal_mgmt_temp1_transitions_rate | temp1 | transitions/s |
220
+| nvme.device_thermal_mgmt_temp2_transitions_rate | temp2 | transitions/s |
221
+| nvme.device_thermal_mgmt_temp1_time | temp1 | seconds |
222
+| nvme.device_thermal_mgmt_temp2_time | temp2 | seconds |
223
+
224
+
225
+
226
## Troubleshooting
227
228
### Debug Mode
src/go/plugin/go.d/collector/openldap/integrations/openldap.md
+34
-34
@@ -48,40 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per OpenLDAP instance
60
-
61
-These metrics refer to the entire monitored application.
62
-
63
-This scope has no labels.
64
-
65
-Metrics:
66
-
67
-| Metric | Dimensions | Unit |
68
-|:------|:----------|:----|
69
-| openldap.current_connections | active | connections |
70
-| openldap.connections | connections | connections/s |
71
-| openldap.traffic | sent | bytes/s |
72
-| openldap.entries | sent | entries/s |
73
-| openldap.referrals | sent | referrals/s |
74
-| openldap.operations | completed, initiated | operations/s |
75
-| openldap.operations_by_type | bind, search, unbind, add, delete, modify, compare | operations/s |
76
-| openldap.waiters | write, read | waiters/s |
77
-
78
-
79
-
80
-## Alerts
81
-
82
-There are no alerts configured by default for this integration.
83
-
84
-
51
## Setup
52
53
@@ -207,6 +173,40 @@ jobs:
173
```
174
175
176
+## Alerts
177
+
178
+There are no alerts configured by default for this integration.
179
+
180
+
181
+## Metrics
182
+
183
+Metrics grouped by *scope*.
184
+
185
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
186
+
187
+
188
+
189
+### Per OpenLDAP instance
190
+
191
+These metrics refer to the entire monitored application.
192
+
193
+This scope has no labels.
194
+
195
+Metrics:
196
+
197
+| Metric | Dimensions | Unit |
198
+|:------|:----------|:----|
199
+| openldap.current_connections | active | connections |
200
+| openldap.connections | connections | connections/s |
201
+| openldap.traffic | sent | bytes/s |
202
+| openldap.entries | sent | entries/s |
203
+| openldap.referrals | sent | referrals/s |
204
+| openldap.operations | completed, initiated | operations/s |
205
+| openldap.operations_by_type | bind, search, unbind, add, delete, modify, compare | operations/s |
206
+| openldap.waiters | write, read | waiters/s |
207
+
208
+
209
+
210
## Troubleshooting
211
212
### Debug Mode
src/go/plugin/go.d/collector/openvpn/integrations/openvpn.md
+45
-45
@@ -47,51 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per OpenVPN instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| openvpn.active_clients | clients | clients |
69
-| openvpn.total_traffic | in, out | kilobits/s |
70
-
71
-### Per user
72
-
73
-These metrics refer to the VPN user.
74
-
75
-Labels:
76
-
77
-| Label | Description |
78
-|:-----------|:----------------|
79
-| username | VPN username |
80
-
81
-Metrics:
82
-
83
-| Metric | Dimensions | Unit |
84
-|:------|:----------|:----|
85
-| openvpn.user_traffic | in, out | kilobits/s |
86
-| openvpn.user_connection_time | time | seconds |
87
-
88
-
89
-
90
-## Alerts
91
-
92
-There are no alerts configured by default for this integration.
93
-
94
-
50
## Setup
51
52
@@ -236,6 +191,51 @@ jobs:
191
192
193
194
+## Alerts
195
+
196
+There are no alerts configured by default for this integration.
197
+
198
+
199
+## Metrics
200
+
201
+Metrics grouped by *scope*.
202
+
203
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
204
+
205
+
206
+
207
+### Per OpenVPN instance
208
+
209
+These metrics refer to the entire monitored application.
210
+
211
+This scope has no labels.
212
+
213
+Metrics:
214
+
215
+| Metric | Dimensions | Unit |
216
+|:------|:----------|:----|
217
+| openvpn.active_clients | clients | clients |
218
+| openvpn.total_traffic | in, out | kilobits/s |
219
+
220
+### Per user
221
+
222
+These metrics refer to the VPN user.
223
+
224
+Labels:
225
+
226
+| Label | Description |
227
+|:-----------|:----------------|
228
+| username | VPN username |
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| openvpn.user_traffic | in, out | kilobits/s |
235
+| openvpn.user_connection_time | time | seconds |
236
+
237
+
238
+
239
## Troubleshooting
240
241
### Debug Mode
src/go/plugin/go.d/collector/openvpn_status_log/integrations/openvpn_status_log.md
+45
-45
@@ -47,51 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per OpenVPN status log instance
59
-
60
-These metrics refer to the entire monitored application.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| openvpn.active_clients | clients | clients |
69
-| openvpn.total_traffic | in, out | kilobits/s |
70
-
71
-### Per user
72
-
73
-These metrics refer to the VPN user.
74
-
75
-Labels:
76
-
77
-| Label | Description |
78
-|:-----------|:----------------|
79
-| username | VPN username |
80
-
81
-Metrics:
82
-
83
-| Metric | Dimensions | Unit |
84
-|:------|:----------|:----|
85
-| openvpn.user_traffic | in, out | kilobits/s |
86
-| openvpn.user_connection_time | time | seconds |
87
-
88
-
89
-
90
-## Alerts
91
-
92
-There are no alerts configured by default for this integration.
93
-
94
-
50
## Setup
51
52
@@ -190,6 +145,51 @@ jobs:
145
146
147
148
+## Alerts
149
+
150
+There are no alerts configured by default for this integration.
151
+
152
+
153
+## Metrics
154
+
155
+Metrics grouped by *scope*.
156
+
157
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
158
+
159
+
160
+
161
+### Per OpenVPN status log instance
162
+
163
+These metrics refer to the entire monitored application.
164
+
165
+This scope has no labels.
166
+
167
+Metrics:
168
+
169
+| Metric | Dimensions | Unit |
170
+|:------|:----------|:----|
171
+| openvpn.active_clients | clients | clients |
172
+| openvpn.total_traffic | in, out | kilobits/s |
173
+
174
+### Per user
175
+
176
+These metrics refer to the VPN user.
177
+
178
+Labels:
179
+
180
+| Label | Description |
181
+|:-----------|:----------------|
182
+| username | VPN username |
183
+
184
+Metrics:
185
+
186
+| Metric | Dimensions | Unit |
187
+|:------|:----------|:----|
188
+| openvpn.user_traffic | in, out | kilobits/s |
189
+| openvpn.user_connection_time | time | seconds |
190
+
191
+
192
+
193
## Troubleshooting
194
195
### Debug Mode
src/go/plugin/go.d/collector/oracledb/integrations/oracle_db.md
+158
-158
@@ -65,6 +65,163 @@ The default configuration for this integration does not impose any limits on dat
65
66
The default configuration for this integration is not expected to impose a significant performance impact on the system.
67
68
+## Setup
69
+
70
+
71
+You can configure the **oracledb** collector in two ways:
72
+
73
+| Method | Best for | How to |
74
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
75
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **oracledb**, then click **+** to add a job. |
76
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/oracledb.conf` and add a job. |
77
+
78
+:::important
79
+
80
+UI configuration requires paid Netdata Cloud plan.
81
+
82
+:::
83
+
84
+
85
+### Prerequisites
86
+
87
+#### Create a read only user for netdata
88
+
89
+Follow the official instructions for your oracle RDBMS to create a read-only user for netdata. The operation may follow this approach
90
+
91
+Connect to your Oracle database with an administrative user and execute:
92
+
93
+```bash
94
+CREATE USER netdata IDENTIFIED BY <PASSWORD>;
95
+
96
+GRANT CONNECT TO netdata;
97
+GRANT SELECT_CATALOG_ROLE TO netdata;
98
+```
99
+
100
+The `top-queries` and `running-queries` functions require access to `V$SQLSTATS` and `V$SESSION`.
101
+
102
+
103
+
104
+### Configuration
105
+
106
+#### Options
107
+
108
+The following options can be defined globally: update_every, autodetection_retry.
109
+
110
+
111
+<details open><summary>Config options</summary>
112
+
113
+
114
+
115
+| Group | Option | Description | Default | Required |
116
+|:------|:-----|:------------|:--------|:---------:|
117
+| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
118
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
119
+| **Target** | dsn | Oracle server DSN (Data Source Name). Format: `oracle://username:password@host:port/service?param1=value1&...¶mN=valueN`. | | yes |
120
+| | timeout | Query timeout (seconds). | 1 | no |
121
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
122
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
123
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
124
+| | functions.running_queries.disabled | Disable the [running-queries](#running-queries) function. | no | no |
125
+| | functions.running_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
126
+| | functions.running_queries.limit | Maximum number of queries to return. | 500 | no |
127
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
128
+
129
+
130
+</details>
131
+
132
+
133
+#### via UI
134
+
135
+Configure the **oracledb** collector from the Netdata web interface:
136
+
137
+1. Go to **Nodes**.
138
+2. Select the node **where you want the oracledb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
139
+3. The **Collectors → Jobs** view opens by default.
140
+4. In the Search box, type _oracledb_ (or scroll the list) to locate the **oracledb** collector.
141
+5. Click the **+** next to the **oracledb** collector to add a new job.
142
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
143
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
144
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
145
+
146
+
147
+#### via File
148
+
149
+The configuration file name for this integration is `go.d/oracledb.conf`.
150
+
151
+The file format is YAML. Generally, the structure is:
152
+
153
+```yaml
154
+update_every: 1
155
+autodetection_retry: 0
156
+jobs:
157
+ - name: some_name1
158
+ - name: some_name2
159
+```
160
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
161
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
162
+
163
+```bash
164
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
165
+sudo ./edit-config go.d/oracledb.conf
166
+```
167
+
168
+##### Examples
169
+
170
+###### TCP socket
171
+
172
+An example configuration.
173
+
174
+<details open><summary>Config</summary>
175
+
176
+```yaml
177
+jobs:
178
+ - name: local
179
+ dsn: oracle://netdata:secret@127.0.0.1:1521/XE
180
+
181
+```
182
+</details>
183
+
184
+###### TLS connection (TCPS)
185
+
186
+An example configuration for TLS connection.
187
+
188
+<details open><summary>Config</summary>
189
+
190
+```yaml
191
+jobs:
192
+ - name: local
193
+ dsn: 'oracle://netdata:secret@127.0.0.1:1521/XE?ssl=true&ssl verify=true'
194
+
195
+```
196
+</details>
197
+
198
+###### Multi-instance
199
+
200
+> **Note**: When you define multiple jobs, their names must be unique.
201
+
202
+Local and remote instances.
203
+
204
+
205
+<details open><summary>Config</summary>
206
+
207
+```yaml
208
+jobs:
209
+ - name: local
210
+ dsn: oracle://netdata:secret@127.0.0.1:1521/XE
211
+
212
+ - name: remote
213
+ dsn: oracle://netdata:secret@203.0.113.0:1521/XE
214
+
215
+```
216
+</details>
217
+
218
+
219
+
220
+## Alerts
221
+
222
+There are no alerts configured by default for this integration.
223
+
224
+
225
## Metrics
226
227
Metrics grouped by *scope*.
@@ -135,7 +292,7 @@ Metrics:
292
293
294
138
-## Functions
295
+## Live Data
296
297
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
298
@@ -303,163 +460,6 @@ Real-time snapshot of currently executing SQL statements. Each row represents an
460
461
462
306
-## Alerts
307
-
308
-There are no alerts configured by default for this integration.
309
-
310
-
311
-## Setup
312
-
313
-
314
-You can configure the **oracledb** collector in two ways:
315
-
316
-| Method | Best for | How to |
317
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
318
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **oracledb**, then click **+** to add a job. |
319
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/oracledb.conf` and add a job. |
320
-
321
-:::important
322
-
323
-UI configuration requires paid Netdata Cloud plan.
324
-
325
-:::
326
-
327
-
328
-### Prerequisites
329
-
330
-#### Create a read only user for netdata
331
-
332
-Follow the official instructions for your oracle RDBMS to create a read-only user for netdata. The operation may follow this approach
333
-
334
-Connect to your Oracle database with an administrative user and execute:
335
-
336
-```bash
337
-CREATE USER netdata IDENTIFIED BY <PASSWORD>;
338
-
339
-GRANT CONNECT TO netdata;
340
-GRANT SELECT_CATALOG_ROLE TO netdata;
341
-```
342
-
343
-The `top-queries` and `running-queries` functions require access to `V$SQLSTATS` and `V$SESSION`.
344
-
345
-
346
-
347
-### Configuration
348
-
349
-#### Options
350
-
351
-The following options can be defined globally: update_every, autodetection_retry.
352
-
353
-
354
-<details open><summary>Config options</summary>
355
-
356
-
357
-
358
-| Group | Option | Description | Default | Required |
359
-|:------|:-----|:------------|:--------|:---------:|
360
-| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
361
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
362
-| **Target** | dsn | Oracle server DSN (Data Source Name). Format: `oracle://username:password@host:port/service?param1=value1&...¶mN=valueN`. | | yes |
363
-| | timeout | Query timeout (seconds). | 1 | no |
364
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
365
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
366
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
367
-| | functions.running_queries.disabled | Disable the [running-queries](#running-queries) function. | no | no |
368
-| | functions.running_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
369
-| | functions.running_queries.limit | Maximum number of queries to return. | 500 | no |
370
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
371
-
372
-
373
-</details>
374
-
375
-
376
-#### via UI
377
-
378
-Configure the **oracledb** collector from the Netdata web interface:
379
-
380
-1. Go to **Nodes**.
381
-2. Select the node **where you want the oracledb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
382
-3. The **Collectors → Jobs** view opens by default.
383
-4. In the Search box, type _oracledb_ (or scroll the list) to locate the **oracledb** collector.
384
-5. Click the **+** next to the **oracledb** collector to add a new job.
385
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
386
- - **Test** runs the job with the provided settings and shows whether data can be collected.
387
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
388
-
389
-
390
-#### via File
391
-
392
-The configuration file name for this integration is `go.d/oracledb.conf`.
393
-
394
-The file format is YAML. Generally, the structure is:
395
-
396
-```yaml
397
-update_every: 1
398
-autodetection_retry: 0
399
-jobs:
400
- - name: some_name1
401
- - name: some_name2
402
-```
403
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
404
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
405
-
406
-```bash
407
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
408
-sudo ./edit-config go.d/oracledb.conf
409
-```
410
-
411
-##### Examples
412
-
413
-###### TCP socket
414
-
415
-An example configuration.
416
-
417
-<details open><summary>Config</summary>
418
-
419
-```yaml
420
-jobs:
421
- - name: local
422
- dsn: oracle://netdata:secret@127.0.0.1:1521/XE
423
-
424
-```
425
-</details>
426
-
427
-###### TLS connection (TCPS)
428
-
429
-An example configuration for TLS connection.
430
-
431
-<details open><summary>Config</summary>
432
-
433
-```yaml
434
-jobs:
435
- - name: local
436
- dsn: 'oracle://netdata:secret@127.0.0.1:1521/XE?ssl=true&ssl verify=true'
437
-
438
-```
439
-</details>
440
-
441
-###### Multi-instance
442
-
443
-> **Note**: When you define multiple jobs, their names must be unique.
444
-
445
-Local and remote instances.
446
-
447
-
448
-<details open><summary>Config</summary>
449
-
450
-```yaml
451
-jobs:
452
- - name: local
453
- dsn: oracle://netdata:secret@127.0.0.1:1521/XE
454
-
455
- - name: remote
456
- dsn: oracle://netdata:secret@203.0.113.0:1521/XE
457
-
458
-```
459
-</details>
460
-
461
-
462
-
463
## Troubleshooting
464
465
### Debug Mode
src/go/plugin/go.d/collector/pgbouncer/integrations/pgbouncer.md
+55
-55
@@ -55,61 +55,6 @@ The default configuration for this integration does not impose any limits on dat
55
56
The default configuration for this integration is not expected to impose a significant performance impact on the system.
57
58
-## Metrics
59
-
60
-Metrics grouped by *scope*.
61
-
62
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
-
64
-
65
-
66
-### Per PgBouncer instance
67
-
68
-These metrics refer to the entire monitored application.
69
-
70
-This scope has no labels.
71
-
72
-Metrics:
73
-
74
-| Metric | Dimensions | Unit |
75
-|:------|:----------|:----|
76
-| pgbouncer.client_connections_utilization | used | percentage |
77
-
78
-### Per database
79
-
80
-These metrics refer to the database.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| database | database name |
87
-| postgres_database | Postgres database name |
88
-
89
-Metrics:
90
-
91
-| Metric | Dimensions | Unit |
92
-|:------|:----------|:----|
93
-| pgbouncer.db_client_connections | active, waiting, cancel_req | connections |
94
-| pgbouncer.db_server_connections | active, idle, used, tested, login | connections |
95
-| pgbouncer.db_server_connections_utilization | used | percentage |
96
-| pgbouncer.db_clients_wait_time | time | seconds |
97
-| pgbouncer.db_client_max_wait_time | time | seconds |
98
-| pgbouncer.db_transactions | transactions | transactions/s |
99
-| pgbouncer.db_transactions_time | time | seconds |
100
-| pgbouncer.db_transaction_avg_time | time | seconds |
101
-| pgbouncer.db_queries | queries | queries/s |
102
-| pgbouncer.db_queries_time | time | seconds |
103
-| pgbouncer.db_query_avg_time | time | seconds |
104
-| pgbouncer.db_network_io | received, sent | B/s |
105
-
106
-
107
-
108
-## Alerts
109
-
110
-There are no alerts configured by default for this integration.
111
-
112
-
58
## Setup
59
60
@@ -267,6 +212,61 @@ jobs:
212
213
214
215
+## Alerts
216
+
217
+There are no alerts configured by default for this integration.
218
+
219
+
220
+## Metrics
221
+
222
+Metrics grouped by *scope*.
223
+
224
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
225
+
226
+
227
+
228
+### Per PgBouncer instance
229
+
230
+These metrics refer to the entire monitored application.
231
+
232
+This scope has no labels.
233
+
234
+Metrics:
235
+
236
+| Metric | Dimensions | Unit |
237
+|:------|:----------|:----|
238
+| pgbouncer.client_connections_utilization | used | percentage |
239
+
240
+### Per database
241
+
242
+These metrics refer to the database.
243
+
244
+Labels:
245
+
246
+| Label | Description |
247
+|:-----------|:----------------|
248
+| database | database name |
249
+| postgres_database | Postgres database name |
250
+
251
+Metrics:
252
+
253
+| Metric | Dimensions | Unit |
254
+|:------|:----------|:----|
255
+| pgbouncer.db_client_connections | active, waiting, cancel_req | connections |
256
+| pgbouncer.db_server_connections | active, idle, used, tested, login | connections |
257
+| pgbouncer.db_server_connections_utilization | used | percentage |
258
+| pgbouncer.db_clients_wait_time | time | seconds |
259
+| pgbouncer.db_client_max_wait_time | time | seconds |
260
+| pgbouncer.db_transactions | transactions | transactions/s |
261
+| pgbouncer.db_transactions_time | time | seconds |
262
+| pgbouncer.db_transaction_avg_time | time | seconds |
263
+| pgbouncer.db_queries | queries | queries/s |
264
+| pgbouncer.db_queries_time | time | seconds |
265
+| pgbouncer.db_query_avg_time | time | seconds |
266
+| pgbouncer.db_network_io | received, sent | B/s |
267
+
268
+
269
+
270
## Troubleshooting
271
272
### Debug Mode
src/go/plugin/go.d/collector/phpdaemon/integrations/phpdaemon.md
+30
-30
@@ -45,36 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per phpDaemon instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| phpdaemon.workers | alive, shutdown | workers |
67
-| phpdaemon.alive_workers | idle, busy, reloading | workers |
68
-| phpdaemon.idle_workers | preinit, init, initialized | workers |
69
-| phpdaemon.uptime | time | seconds |
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
48
## Setup
49
50
@@ -313,6 +283,36 @@ jobs:
283
284
285
286
+## Alerts
287
+
288
+There are no alerts configured by default for this integration.
289
+
290
+
291
+## Metrics
292
+
293
+Metrics grouped by *scope*.
294
+
295
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
296
+
297
+
298
+
299
+### Per phpDaemon instance
300
+
301
+These metrics refer to the entire monitored application.
302
+
303
+This scope has no labels.
304
+
305
+Metrics:
306
+
307
+| Metric | Dimensions | Unit |
308
+|:------|:----------|:----|
309
+| phpdaemon.workers | alive, shutdown | workers |
310
+| phpdaemon.alive_workers | idle, busy, reloading | workers |
311
+| phpdaemon.idle_workers | preinit, init, initialized | workers |
312
+| phpdaemon.uptime | time | seconds |
313
+
314
+
315
+
316
## Troubleshooting
317
318
### Debug Mode
src/go/plugin/go.d/collector/phpfpm/integrations/php-fpm.md
+32
-32
@@ -45,38 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per PHP-FPM instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| phpfpm.connections | active, max_active, idle | connections |
67
-| phpfpm.requests | requests | requests/s |
68
-| phpfpm.performance | max_children_reached, slow_requests | status |
69
-| phpfpm.request_duration | min, max, avg | milliseconds |
70
-| phpfpm.request_cpu | min, max, avg | percentage |
71
-| phpfpm.request_mem | min, max, avg | KB |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-There are no alerts configured by default for this integration.
78
-
79
-
48
## Setup
49
50
@@ -244,6 +212,38 @@ jobs:
212
213
214
215
+## Alerts
216
+
217
+There are no alerts configured by default for this integration.
218
+
219
+
220
+## Metrics
221
+
222
+Metrics grouped by *scope*.
223
+
224
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
225
+
226
+
227
+
228
+### Per PHP-FPM instance
229
+
230
+These metrics refer to the entire monitored application.
231
+
232
+This scope has no labels.
233
+
234
+Metrics:
235
+
236
+| Metric | Dimensions | Unit |
237
+|:------|:----------|:----|
238
+| phpfpm.connections | active, max_active, idle | connections |
239
+| phpfpm.requests | requests | requests/s |
240
+| phpfpm.performance | max_children_reached, slow_requests | status |
241
+| phpfpm.request_duration | min, max, avg | milliseconds |
242
+| phpfpm.request_cpu | min, max, avg | percentage |
243
+| phpfpm.request_mem | min, max, avg | KB |
244
+
245
+
246
+
247
## Troubleshooting
248
249
### Debug Mode
src/go/plugin/go.d/collector/pihole/integrations/pi-hole.md
+40
-40
@@ -56,46 +56,6 @@ The default configuration for this integration does not impose any limits on dat
56
57
The default configuration for this integration is not expected to impose a significant performance impact on the system.
58
59
-## Metrics
60
-
61
-Metrics grouped by *scope*.
62
-
63
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
64
-
65
-
66
-
67
-### Per Pi-hole instance
68
-
69
-These metrics refer to the entire monitored application.
70
-
71
-This scope has no labels.
72
-
73
-Metrics:
74
-
75
-| Metric | Dimensions | Unit |
76
-|:------|:----------|:----|
77
-| pihole.dns_queries_total | queries | queries/s |
78
-| pihole.dns_queries_blocked_percent | blocked | percent |
79
-| pihole.dns_queries_by_destination | cached, blocked, forwarded | queries/s |
80
-| pihole.dns_queries_by_type | A, AAA, ANY, SRV, SOA, PTR, TXT, NAPTR, MX, DS, RRSIG, DNSKEY, NS, SVCB, HTTPS, OTHER | queries/s |
81
-| pihole.dns_queries_by_status | UNKNOWN, GRAVITY, FORWARDED, CACHE, REGEX, DENYLIST, EXTERNAL_BLOCKED_IP, EXTERNAL_BLOCKED_NULL, EXTERNAL_BLOCKED_NXRA, GRAVITY_CNAME, REGEX_CNAME, DENYLIST_CNAME, RETRIED, RETRIED_DNSSEC, IN_PROGRESS, DBBUSY, SPECIAL_DOMAIN, CACHE_STALE, EXTERNAL_BLOCKED_EDE15 | queries/s |
82
-| pihole.dns_replies_by_status | UNKNOWN, NODATA, NXDOMAIN, CNAME, IP, DOMAIN, RRNAME, SERVFAIL, REFUSED, NOTIMP, DNSSEC, NONE, OTHER | replies/s |
83
-| pihole.active_clients | active | clients |
84
-| pihole.gravity_list_blocked_domains | blocked | domains |
85
-| pihole.gravity_list_last_update_time_ago | last_update_ago | seconds |
86
-
87
-
88
-
89
-## Alerts
90
-
91
-
92
-The following alerts are available:
93
-
94
-| Alert name | On metric | Description |
95
-|:------------|:----------|:------------|
96
-| [ pihole_gravity_list_last_update ](https://github.com/netdata/netdata/blob/master/src/health/health.d/pihole.conf) | pihole.gravity_list_last_update_time_ago | gravity.list (blocklist) file last update time |
97
-
98
-
59
## Setup
60
61
@@ -256,6 +216,46 @@ jobs:
216
217
218
219
+## Alerts
220
+
221
+
222
+The following alerts are available:
223
+
224
+| Alert name | On metric | Description |
225
+|:------------|:----------|:------------|
226
+| [ pihole_gravity_list_last_update ](https://github.com/netdata/netdata/blob/master/src/health/health.d/pihole.conf) | pihole.gravity_list_last_update_time_ago | gravity.list (blocklist) file last update time |
227
+
228
+
229
+## Metrics
230
+
231
+Metrics grouped by *scope*.
232
+
233
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
234
+
235
+
236
+
237
+### Per Pi-hole instance
238
+
239
+These metrics refer to the entire monitored application.
240
+
241
+This scope has no labels.
242
+
243
+Metrics:
244
+
245
+| Metric | Dimensions | Unit |
246
+|:------|:----------|:----|
247
+| pihole.dns_queries_total | queries | queries/s |
248
+| pihole.dns_queries_blocked_percent | blocked | percent |
249
+| pihole.dns_queries_by_destination | cached, blocked, forwarded | queries/s |
250
+| pihole.dns_queries_by_type | A, AAA, ANY, SRV, SOA, PTR, TXT, NAPTR, MX, DS, RRSIG, DNSKEY, NS, SVCB, HTTPS, OTHER | queries/s |
251
+| pihole.dns_queries_by_status | UNKNOWN, GRAVITY, FORWARDED, CACHE, REGEX, DENYLIST, EXTERNAL_BLOCKED_IP, EXTERNAL_BLOCKED_NULL, EXTERNAL_BLOCKED_NXRA, GRAVITY_CNAME, REGEX_CNAME, DENYLIST_CNAME, RETRIED, RETRIED_DNSSEC, IN_PROGRESS, DBBUSY, SPECIAL_DOMAIN, CACHE_STALE, EXTERNAL_BLOCKED_EDE15 | queries/s |
252
+| pihole.dns_replies_by_status | UNKNOWN, NODATA, NXDOMAIN, CNAME, IP, DOMAIN, RRNAME, SERVFAIL, REFUSED, NOTIMP, DNSSEC, NONE, OTHER | replies/s |
253
+| pihole.active_clients | active | clients |
254
+| pihole.gravity_list_blocked_domains | blocked | domains |
255
+| pihole.gravity_list_last_update_time_ago | last_update_ago | seconds |
256
+
257
+
258
+
259
## Troubleshooting
260
261
### Debug Mode
src/go/plugin/go.d/collector/pika/integrations/pika.md
+48
-48
@@ -49,54 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Pika instance
61
-
62
-These metrics refer to the entire monitored application.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| pika.connections | accepted | connections |
71
-| pika.clients | connected | clients |
72
-| pika.memory | used | bytes |
73
-| pika.connected_replicas | connected | replicas |
74
-| pika.commands | processed | commands/s |
75
-| pika.commands_calls | a dimension per command | calls/s |
76
-| pika.database_strings_keys | a dimension per database | keys |
77
-| pika.database_strings_expires_keys | a dimension per database | keys |
78
-| pika.database_strings_invalid_keys | a dimension per database | keys |
79
-| pika.database_hashes_keys | a dimension per database | keys |
80
-| pika.database_hashes_expires_keys | a dimension per database | keys |
81
-| pika.database_hashes_invalid_keys | a dimension per database | keys |
82
-| pika.database_lists_keys | a dimension per database | keys |
83
-| pika.database_lists_expires_keys | a dimension per database | keys |
84
-| pika.database_lists_invalid_keys | a dimension per database | keys |
85
-| pika.database_zsets_keys | a dimension per database | keys |
86
-| pika.database_zsets_expires_keys | a dimension per database | keys |
87
-| pika.database_zsets_invalid_keys | a dimension per database | keys |
88
-| pika.database_sets_keys | a dimension per database | keys |
89
-| pika.database_sets_expires_keys | a dimension per database | keys |
90
-| pika.database_sets_invalid_keys | a dimension per database | keys |
91
-| pika.uptime | uptime | seconds |
92
-
93
-
94
-
95
-## Alerts
96
-
97
-There are no alerts configured by default for this integration.
98
-
99
-
52
## Setup
53
54
@@ -234,6 +186,54 @@ jobs:
186
187
188
189
+## Alerts
190
+
191
+There are no alerts configured by default for this integration.
192
+
193
+
194
+## Metrics
195
+
196
+Metrics grouped by *scope*.
197
+
198
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
199
+
200
+
201
+
202
+### Per Pika instance
203
+
204
+These metrics refer to the entire monitored application.
205
+
206
+This scope has no labels.
207
+
208
+Metrics:
209
+
210
+| Metric | Dimensions | Unit |
211
+|:------|:----------|:----|
212
+| pika.connections | accepted | connections |
213
+| pika.clients | connected | clients |
214
+| pika.memory | used | bytes |
215
+| pika.connected_replicas | connected | replicas |
216
+| pika.commands | processed | commands/s |
217
+| pika.commands_calls | a dimension per command | calls/s |
218
+| pika.database_strings_keys | a dimension per database | keys |
219
+| pika.database_strings_expires_keys | a dimension per database | keys |
220
+| pika.database_strings_invalid_keys | a dimension per database | keys |
221
+| pika.database_hashes_keys | a dimension per database | keys |
222
+| pika.database_hashes_expires_keys | a dimension per database | keys |
223
+| pika.database_hashes_invalid_keys | a dimension per database | keys |
224
+| pika.database_lists_keys | a dimension per database | keys |
225
+| pika.database_lists_expires_keys | a dimension per database | keys |
226
+| pika.database_lists_invalid_keys | a dimension per database | keys |
227
+| pika.database_zsets_keys | a dimension per database | keys |
228
+| pika.database_zsets_expires_keys | a dimension per database | keys |
229
+| pika.database_zsets_invalid_keys | a dimension per database | keys |
230
+| pika.database_sets_keys | a dimension per database | keys |
231
+| pika.database_sets_expires_keys | a dimension per database | keys |
232
+| pika.database_sets_invalid_keys | a dimension per database | keys |
233
+| pika.uptime | uptime | seconds |
234
+
235
+
236
+
237
## Troubleshooting
238
239
### Debug Mode
src/go/plugin/go.d/collector/ping/integrations/ping.md
+43
-43
@@ -69,49 +69,6 @@ The default configuration for this integration does not impose any limits on dat
69
70
The default configuration for this integration is not expected to impose a significant performance impact on the system.
71
72
-## Metrics
73
-
74
-Metrics grouped by *scope*.
75
-
76
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
77
-
78
-
79
-
80
-### Per host
81
-
82
-These metrics refer to the remote host.
83
-
84
-Labels:
85
-
86
-| Label | Description |
87
-|:-----------|:----------------|
88
-| host | remote host |
89
-
90
-Metrics:
91
-
92
-| Metric | Dimensions | Unit |
93
-|:------|:----------|:----|
94
-| ping.host_rtt | min, max, avg | milliseconds |
95
-| ping.host_std_dev_rtt | std_dev | milliseconds |
96
-| ping.host_jitter | mean, ewma, sma | milliseconds |
97
-| ping.host_rtt_variance | variance | ms² |
98
-| ping.host_packet_loss | loss | percentage |
99
-| ping.host_packets | received, sent | packets |
100
-
101
-
102
-
103
-## Alerts
104
-
105
-
106
-The following alerts are available:
107
-
108
-| Alert name | On metric | Description |
109
-|:------------|:----------|:------------|
110
-| [ ping_host_reachable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ping.conf) | ping.host_packet_loss | network host ${label:host} reachability status |
111
-| [ ping_packet_loss ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ping.conf) | ping.host_packet_loss | packet loss percentage to the network host ${label:host} over the last 10 minutes |
112
-| [ ping_host_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ping.conf) | ping.host_rtt | average latency to the network host ${label:host} over the last 10 seconds |
113
-
114
-
72
## Setup
73
74
@@ -259,6 +216,49 @@ jobs:
216
217
218
219
+## Alerts
220
+
221
+
222
+The following alerts are available:
223
+
224
+| Alert name | On metric | Description |
225
+|:------------|:----------|:------------|
226
+| [ ping_host_reachable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ping.conf) | ping.host_packet_loss | network host ${label:host} reachability status |
227
+| [ ping_packet_loss ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ping.conf) | ping.host_packet_loss | packet loss percentage to the network host ${label:host} over the last 10 minutes |
228
+| [ ping_host_latency ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ping.conf) | ping.host_rtt | average latency to the network host ${label:host} over the last 10 seconds |
229
+
230
+
231
+## Metrics
232
+
233
+Metrics grouped by *scope*.
234
+
235
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
236
+
237
+
238
+
239
+### Per host
240
+
241
+These metrics refer to the remote host.
242
+
243
+Labels:
244
+
245
+| Label | Description |
246
+|:-----------|:----------------|
247
+| host | remote host |
248
+
249
+Metrics:
250
+
251
+| Metric | Dimensions | Unit |
252
+|:------|:----------|:----|
253
+| ping.host_rtt | min, max, avg | milliseconds |
254
+| ping.host_std_dev_rtt | std_dev | milliseconds |
255
+| ping.host_jitter | mean, ewma, sma | milliseconds |
256
+| ping.host_rtt_variance | variance | ms² |
257
+| ping.host_packet_loss | loss | percentage |
258
+| ping.host_packets | received, sent | packets |
259
+
260
+
261
+
262
## Troubleshooting
263
264
### Debug Mode
src/go/plugin/go.d/collector/portcheck/integrations/tcp-udp_endpoints.md
+59
-59
@@ -66,65 +66,6 @@ The default configuration for this integration does not impose any limits on dat
66
67
The default configuration for this integration is not expected to impose a significant performance impact on the system.
68
69
-## Metrics
70
-
71
-Metrics grouped by *scope*.
72
-
73
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
74
-
75
-
76
-
77
-### Per TCP endpoint
78
-
79
-These metrics refer to the TCP endpoint.
80
-
81
-Labels:
82
-
83
-| Label | Description |
84
-|:-----------|:----------------|
85
-| host | The hostname or IP address of the target system, as specified in the configuration. |
86
-| port | The TCP port being monitored, as defined in the 'ports' configuration parameter. |
87
-
88
-Metrics:
89
-
90
-| Metric | Dimensions | Unit |
91
-|:------|:----------|:----|
92
-| portcheck.status | success, failed, timeout | boolean |
93
-| portcheck.state_duration | time | seconds |
94
-| portcheck.latency | time | ms |
95
-
96
-### Per UDP endpoint
97
-
98
-These metrics refer to the UDP endpoint.
99
-
100
-Labels:
101
-
102
-| Label | Description |
103
-|:-----------|:----------------|
104
-| host | The hostname or IP address of the target system, as specified in the configuration. |
105
-| port | The UDP port being monitored, as defined in the 'udp_ports' configuration parameter. |
106
-
107
-Metrics:
108
-
109
-| Metric | Dimensions | Unit |
110
-|:------|:----------|:----|
111
-| portcheck.udp_port_status | open/filtered, closed | status |
112
-| portcheck.udp_port_status_duration | time | seconds |
113
-
114
-
115
-
116
-## Alerts
117
-
118
-
119
-The following alerts are available:
120
-
121
-| Alert name | On metric | Description |
122
-|:------------|:----------|:------------|
123
-| [ portcheck_service_reachable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/portcheck.conf) | portcheck.status | TCP host ${label:host} port ${label:port} liveness status |
124
-| [ portcheck_connection_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/portcheck.conf) | portcheck.status | percentage of timed-out TCP connections to host ${label:host} port ${label:port} in the last 5 minutes |
125
-| [ portcheck_connection_fails ](https://github.com/netdata/netdata/blob/master/src/health/health.d/portcheck.conf) | portcheck.status | percentage of failed TCP connections to host ${label:host} port ${label:port} in the last 5 minutes |
126
-
127
-
69
## Setup
70
71
@@ -304,6 +245,65 @@ jobs:
245
246
247
248
+## Alerts
249
+
250
+
251
+The following alerts are available:
252
+
253
+| Alert name | On metric | Description |
254
+|:------------|:----------|:------------|
255
+| [ portcheck_service_reachable ](https://github.com/netdata/netdata/blob/master/src/health/health.d/portcheck.conf) | portcheck.status | TCP host ${label:host} port ${label:port} liveness status |
256
+| [ portcheck_connection_timeouts ](https://github.com/netdata/netdata/blob/master/src/health/health.d/portcheck.conf) | portcheck.status | percentage of timed-out TCP connections to host ${label:host} port ${label:port} in the last 5 minutes |
257
+| [ portcheck_connection_fails ](https://github.com/netdata/netdata/blob/master/src/health/health.d/portcheck.conf) | portcheck.status | percentage of failed TCP connections to host ${label:host} port ${label:port} in the last 5 minutes |
258
+
259
+
260
+## Metrics
261
+
262
+Metrics grouped by *scope*.
263
+
264
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
265
+
266
+
267
+
268
+### Per TCP endpoint
269
+
270
+These metrics refer to the TCP endpoint.
271
+
272
+Labels:
273
+
274
+| Label | Description |
275
+|:-----------|:----------------|
276
+| host | The hostname or IP address of the target system, as specified in the configuration. |
277
+| port | The TCP port being monitored, as defined in the 'ports' configuration parameter. |
278
+
279
+Metrics:
280
+
281
+| Metric | Dimensions | Unit |
282
+|:------|:----------|:----|
283
+| portcheck.status | success, failed, timeout | boolean |
284
+| portcheck.state_duration | time | seconds |
285
+| portcheck.latency | time | ms |
286
+
287
+### Per UDP endpoint
288
+
289
+These metrics refer to the UDP endpoint.
290
+
291
+Labels:
292
+
293
+| Label | Description |
294
+|:-----------|:----------------|
295
+| host | The hostname or IP address of the target system, as specified in the configuration. |
296
+| port | The UDP port being monitored, as defined in the 'udp_ports' configuration parameter. |
297
+
298
+Metrics:
299
+
300
+| Metric | Dimensions | Unit |
301
+|:------|:----------|:----|
302
+| portcheck.udp_port_status | open/filtered, closed | status |
303
+| portcheck.udp_port_status_duration | time | seconds |
304
+
305
+
306
+
307
## Troubleshooting
308
309
### Debug Mode
src/go/plugin/go.d/collector/postfix/integrations/postfix.md
+29
-29
@@ -48,35 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per Postfix instance
60
-
61
-These metrics refer to the entire monitored application.
62
-
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| postfix.qemails | emails | emails |
71
-| postfix.qsize | size | KiB |
72
-
73
-
74
-
75
-## Alerts
76
-
77
-There are no alerts configured by default for this integration.
78
-
79
-
51
## Setup
52
53
@@ -172,6 +143,35 @@ jobs:
143
144
145
146
+## Alerts
147
+
148
+There are no alerts configured by default for this integration.
149
+
150
+
151
+## Metrics
152
+
153
+Metrics grouped by *scope*.
154
+
155
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
156
+
157
+
158
+
159
+### Per Postfix instance
160
+
161
+These metrics refer to the entire monitored application.
162
+
163
+
164
+This scope has no labels.
165
+
166
+Metrics:
167
+
168
+| Metric | Dimensions | Unit |
169
+|:------|:----------|:----|
170
+| postfix.qemails | emails | emails |
171
+| postfix.qsize | size | KiB |
172
+
173
+
174
+
175
## Troubleshooting
176
177
### Debug Mode
src/go/plugin/go.d/collector/postgres/integrations/postgresql.md
+233
-233
@@ -58,6 +58,238 @@ These limits can be changed in the configuration file.
58
59
The default configuration for this integration is not expected to impose a significant performance impact on the system.
60
61
+## Setup
62
+
63
+
64
+You can configure the **postgres** collector in two ways:
65
+
66
+| Method | Best for | How to |
67
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
68
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **postgres**, then click **+** to add a job. |
69
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/postgres.conf` and add a job. |
70
+
71
+:::important
72
+
73
+UI configuration requires paid Netdata Cloud plan.
74
+
75
+:::
76
+
77
+
78
+### Prerequisites
79
+
80
+#### Create netdata user
81
+
82
+Create a user with granted `pg_monitor`
83
+or `pg_read_all_stat` [built-in role](https://www.postgresql.org/docs/current/predefined-roles.html).
84
+
85
+To create the `netdata` user with these permissions, execute the following in the psql session, as a user with CREATEROLE privileges:
86
+
87
+```postgresql
88
+CREATE USER netdata;
89
+GRANT pg_monitor TO netdata;
90
+```
91
+
92
+After creating the new user, restart the Netdata Agent with `sudo systemctl restart netdata`, or
93
+the [appropriate method](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/start-stop-restart.md) for your
94
+system.
95
+
96
+
97
+
98
+### Configuration
99
+
100
+#### Options
101
+
102
+The following options can be defined globally: update_every, autodetection_retry.
103
+
104
+
105
+<details open><summary>Config options</summary>
106
+
107
+
108
+
109
+| Group | Option | Description | Default | Required |
110
+|:------|:-----|:------------|:--------|:---------:|
111
+| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
112
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
113
+| **Target** | dsn | Postgres connection string (DSN). See [DSN syntax](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). | postgres://postgres:postgres@127.0.0.1:5432/postgres | yes |
114
+| **Cloud Auth** | cloud_auth.provider | Cloud auth provider (`none` or `azure_ad`). | none | no |
115
+| **Cloud Auth/Azure** | cloud_auth.azure_ad.mode | Azure AD credential mode (`service_principal`, `managed_identity`, or `default`). Required when `cloud_auth.provider` is `azure_ad`. | | yes |
116
+| | cloud_auth.azure_ad.mode_service_principal.tenant_id | Azure tenant ID. Required for `service_principal` mode. | | no |
117
+| | cloud_auth.azure_ad.mode_service_principal.client_id | Azure client ID. Required for `service_principal` mode. | | no |
118
+| | cloud_auth.azure_ad.mode_service_principal.client_secret | Azure client secret for `service_principal` mode. | | no |
119
+| | cloud_auth.azure_ad.mode_managed_identity.client_id | Optional client ID of a user-assigned managed identity (`managed_identity` mode). | | no |
120
+| **Target** | timeout | Query timeout (seconds). | 2 | no |
121
+| **Filters** | collect_databases_matching | Database selector. Controls which databases are included. Uses [simple patterns](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#simple-patterns-matcher). | | no |
122
+| **Limits** | max_db_tables | Maximum number of tables per database to collect metrics for (0 = no limit). | 50 | no |
123
+| | max_db_indexes | Maximum number of indexes per database to collect metrics for (0 = no limit). | 250 | no |
124
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
125
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
126
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
127
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
128
+
129
+
130
+</details>
131
+
132
+
133
+#### via UI
134
+
135
+Configure the **postgres** collector from the Netdata web interface:
136
+
137
+1. Go to **Nodes**.
138
+2. Select the node **where you want the postgres data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
139
+3. The **Collectors → Jobs** view opens by default.
140
+4. In the Search box, type _postgres_ (or scroll the list) to locate the **postgres** collector.
141
+5. Click the **+** next to the **postgres** collector to add a new job.
142
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
143
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
144
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
145
+
146
+
147
+#### via File
148
+
149
+The configuration file name for this integration is `go.d/postgres.conf`.
150
+
151
+The file format is YAML. Generally, the structure is:
152
+
153
+```yaml
154
+update_every: 1
155
+autodetection_retry: 0
156
+jobs:
157
+ - name: some_name1
158
+ - name: some_name2
159
+```
160
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
161
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
162
+
163
+```bash
164
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
165
+sudo ./edit-config go.d/postgres.conf
166
+```
167
+
168
+##### Examples
169
+
170
+###### TCP socket
171
+
172
+An example configuration.
173
+
174
+```yaml
175
+jobs:
176
+ - name: local
177
+ dsn: 'postgresql://netdata@127.0.0.1:5432/postgres'
178
+
179
+```
180
+###### Unix socket
181
+
182
+An example configuration.
183
+
184
+<details open><summary>Config</summary>
185
+
186
+```yaml
187
+jobs:
188
+ - name: local
189
+ dsn: 'host=/var/run/postgresql dbname=postgres user=netdata'
190
+
191
+```
192
+</details>
193
+
194
+###### Unix socket (custom port)
195
+
196
+Connect to PostgreSQL using a Unix socket with a non-default port (5433).
197
+
198
+<details open><summary>Config</summary>
199
+
200
+```yaml
201
+jobs:
202
+ - name: local
203
+ dsn: 'host=/var/run/postgresql port=5433 dbname=postgres user=netdata'
204
+
205
+```
206
+</details>
207
+
208
+###### Azure Database for PostgreSQL with service principal
209
+
210
+Use Microsoft Entra service principal authentication.
211
+
212
+<details open><summary>Config</summary>
213
+
214
+```yaml
215
+jobs:
216
+ - name: azure_postgres_sp
217
+ dsn: 'postgresql://netdata@myserver.postgres.database.azure.com:5432/postgres?sslmode=require'
218
+ cloud_auth:
219
+ provider: azure_ad
220
+ azure_ad:
221
+ mode: service_principal
222
+ mode_service_principal:
223
+ tenant_id: "00000000-0000-0000-0000-000000000000"
224
+ client_id: "11111111-1111-1111-1111-111111111111"
225
+ client_secret: "super-secret-value"
226
+
227
+```
228
+</details>
229
+
230
+###### Azure Database for PostgreSQL with managed identity
231
+
232
+Use managed identity authentication (system-assigned by default).
233
+
234
+<details open><summary>Config</summary>
235
+
236
+```yaml
237
+jobs:
238
+ - name: azure_postgres_mi
239
+ dsn: 'postgresql://netdata@myserver.postgres.database.azure.com:5432/postgres?sslmode=require'
240
+ cloud_auth:
241
+ provider: azure_ad
242
+ azure_ad:
243
+ mode: managed_identity
244
+
245
+```
246
+</details>
247
+
248
+###### Multi-instance
249
+
250
+> **Note**: When you define multiple jobs, their names must be unique.
251
+
252
+Local and remote instances.
253
+
254
+
255
+<details open><summary>Config</summary>
256
+
257
+```yaml
258
+jobs:
259
+ - name: local
260
+ dsn: 'postgresql://netdata@127.0.0.1:5432/postgres'
261
+
262
+ - name: remote
263
+ dsn: 'postgresql://netdata@203.0.113.0:5432/postgres'
264
+
265
+```
266
+</details>
267
+
268
+
269
+
270
+## Alerts
271
+
272
+
273
+The following alerts are available:
274
+
275
+| Alert name | On metric | Description |
276
+|:------------|:----------|:------------|
277
+| [ postgres_total_connection_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.connections_utilization | average total connection utilization over the last minute |
278
+| [ postgres_acquired_locks_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.locks_utilization | average acquired locks utilization over the last minute |
279
+| [ postgres_txid_exhaustion_perc ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.txid_exhaustion_perc | percent towards TXID wraparound |
280
+| [ postgres_db_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.db_cache_io_ratio | average cache hit ratio in db ${label:database} over the last minute |
281
+| [ postgres_db_transactions_rollback_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.db_cache_io_ratio | average aborted transactions percentage in db ${label:database} over the last five minutes |
282
+| [ postgres_db_deadlocks_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.db_deadlocks_rate | number of deadlocks detected in db ${label:database} in the last minute |
283
+| [ postgres_table_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_cache_io_ratio | average cache hit ratio in db ${label:database} table ${label:table} over the last minute |
284
+| [ postgres_table_index_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_index_cache_io_ratio | average index cache hit ratio in db ${label:database} table ${label:table} over the last minute |
285
+| [ postgres_table_toast_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_toast_cache_io_ratio | average TOAST hit ratio in db ${label:database} table ${label:table} over the last minute |
286
+| [ postgres_table_toast_index_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_toast_index_cache_io_ratio | average index TOAST hit ratio in db ${label:database} table ${label:table} over the last minute |
287
+| [ postgres_table_bloat_size_perc ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_bloat_size_perc | bloat size percentage in db ${label:database} table ${label:table} |
288
+| [ postgres_table_last_autovacuum_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_autovacuum_since_time | time elapsed since db ${label:database} table ${label:table} was vacuumed by the autovacuum daemon |
289
+| [ postgres_table_last_autoanalyze_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_autoanalyze_since_time | time elapsed since db ${label:database} table ${label:table} was analyzed by the autovacuum daemon |
290
+| [ postgres_index_bloat_size_perc ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.index_bloat_size_perc | bloat size percentage in db ${label:database} table ${label:table} index ${label:index} |
291
+
292
+
293
## Metrics
294
295
Metrics grouped by *scope*.
@@ -231,7 +463,7 @@ Metrics:
463
464
465
234
-## Functions
466
+## Live Data
467
468
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
469
@@ -453,238 +685,6 @@ Live query data from `pg_stat_activity`. Each row represents a currently active
685
686
687
456
-## Alerts
457
-
458
-
459
-The following alerts are available:
460
-
461
-| Alert name | On metric | Description |
462
-|:------------|:----------|:------------|
463
-| [ postgres_total_connection_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.connections_utilization | average total connection utilization over the last minute |
464
-| [ postgres_acquired_locks_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.locks_utilization | average acquired locks utilization over the last minute |
465
-| [ postgres_txid_exhaustion_perc ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.txid_exhaustion_perc | percent towards TXID wraparound |
466
-| [ postgres_db_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.db_cache_io_ratio | average cache hit ratio in db ${label:database} over the last minute |
467
-| [ postgres_db_transactions_rollback_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.db_cache_io_ratio | average aborted transactions percentage in db ${label:database} over the last five minutes |
468
-| [ postgres_db_deadlocks_rate ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.db_deadlocks_rate | number of deadlocks detected in db ${label:database} in the last minute |
469
-| [ postgres_table_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_cache_io_ratio | average cache hit ratio in db ${label:database} table ${label:table} over the last minute |
470
-| [ postgres_table_index_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_index_cache_io_ratio | average index cache hit ratio in db ${label:database} table ${label:table} over the last minute |
471
-| [ postgres_table_toast_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_toast_cache_io_ratio | average TOAST hit ratio in db ${label:database} table ${label:table} over the last minute |
472
-| [ postgres_table_toast_index_cache_io_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_toast_index_cache_io_ratio | average index TOAST hit ratio in db ${label:database} table ${label:table} over the last minute |
473
-| [ postgres_table_bloat_size_perc ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_bloat_size_perc | bloat size percentage in db ${label:database} table ${label:table} |
474
-| [ postgres_table_last_autovacuum_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_autovacuum_since_time | time elapsed since db ${label:database} table ${label:table} was vacuumed by the autovacuum daemon |
475
-| [ postgres_table_last_autoanalyze_time ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.table_autoanalyze_since_time | time elapsed since db ${label:database} table ${label:table} was analyzed by the autovacuum daemon |
476
-| [ postgres_index_bloat_size_perc ](https://github.com/netdata/netdata/blob/master/src/health/health.d/postgres.conf) | postgres.index_bloat_size_perc | bloat size percentage in db ${label:database} table ${label:table} index ${label:index} |
477
-
478
-
479
-## Setup
480
-
481
-
482
-You can configure the **postgres** collector in two ways:
483
-
484
-| Method | Best for | How to |
485
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
486
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **postgres**, then click **+** to add a job. |
487
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/postgres.conf` and add a job. |
488
-
489
-:::important
490
-
491
-UI configuration requires paid Netdata Cloud plan.
492
-
493
-:::
494
-
495
-
496
-### Prerequisites
497
-
498
-#### Create netdata user
499
-
500
-Create a user with granted `pg_monitor`
501
-or `pg_read_all_stat` [built-in role](https://www.postgresql.org/docs/current/predefined-roles.html).
502
-
503
-To create the `netdata` user with these permissions, execute the following in the psql session, as a user with CREATEROLE privileges:
504
-
505
-```postgresql
506
-CREATE USER netdata;
507
-GRANT pg_monitor TO netdata;
508
-```
509
-
510
-After creating the new user, restart the Netdata Agent with `sudo systemctl restart netdata`, or
511
-the [appropriate method](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/start-stop-restart.md) for your
512
-system.
513
-
514
-
515
-
516
-### Configuration
517
-
518
-#### Options
519
-
520
-The following options can be defined globally: update_every, autodetection_retry.
521
-
522
-
523
-<details open><summary>Config options</summary>
524
-
525
-
526
-
527
-| Group | Option | Description | Default | Required |
528
-|:------|:-----|:------------|:--------|:---------:|
529
-| **Collection** | update_every | Data collection interval (seconds). | 1 | no |
530
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
531
-| **Target** | dsn | Postgres connection string (DSN). See [DSN syntax](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). | postgres://postgres:postgres@127.0.0.1:5432/postgres | yes |
532
-| **Cloud Auth** | cloud_auth.provider | Cloud auth provider (`none` or `azure_ad`). | none | no |
533
-| **Cloud Auth/Azure** | cloud_auth.azure_ad.mode | Azure AD credential mode (`service_principal`, `managed_identity`, or `default`). Required when `cloud_auth.provider` is `azure_ad`. | | yes |
534
-| | cloud_auth.azure_ad.mode_service_principal.tenant_id | Azure tenant ID. Required for `service_principal` mode. | | no |
535
-| | cloud_auth.azure_ad.mode_service_principal.client_id | Azure client ID. Required for `service_principal` mode. | | no |
536
-| | cloud_auth.azure_ad.mode_service_principal.client_secret | Azure client secret for `service_principal` mode. | | no |
537
-| | cloud_auth.azure_ad.mode_managed_identity.client_id | Optional client ID of a user-assigned managed identity (`managed_identity` mode). | | no |
538
-| **Target** | timeout | Query timeout (seconds). | 2 | no |
539
-| **Filters** | collect_databases_matching | Database selector. Controls which databases are included. Uses [simple patterns](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#simple-patterns-matcher). | | no |
540
-| **Limits** | max_db_tables | Maximum number of tables per database to collect metrics for (0 = no limit). | 50 | no |
541
-| | max_db_indexes | Maximum number of indexes per database to collect metrics for (0 = no limit). | 250 | no |
542
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
543
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
544
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
545
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
546
-
547
-
548
-</details>
549
-
550
-
551
-#### via UI
552
-
553
-Configure the **postgres** collector from the Netdata web interface:
554
-
555
-1. Go to **Nodes**.
556
-2. Select the node **where you want the postgres data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
557
-3. The **Collectors → Jobs** view opens by default.
558
-4. In the Search box, type _postgres_ (or scroll the list) to locate the **postgres** collector.
559
-5. Click the **+** next to the **postgres** collector to add a new job.
560
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
561
- - **Test** runs the job with the provided settings and shows whether data can be collected.
562
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
563
-
564
-
565
-#### via File
566
-
567
-The configuration file name for this integration is `go.d/postgres.conf`.
568
-
569
-The file format is YAML. Generally, the structure is:
570
-
571
-```yaml
572
-update_every: 1
573
-autodetection_retry: 0
574
-jobs:
575
- - name: some_name1
576
- - name: some_name2
577
-```
578
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
579
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
580
-
581
-```bash
582
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
583
-sudo ./edit-config go.d/postgres.conf
584
-```
585
-
586
-##### Examples
587
-
588
-###### TCP socket
589
-
590
-An example configuration.
591
-
592
-```yaml
593
-jobs:
594
- - name: local
595
- dsn: 'postgresql://netdata@127.0.0.1:5432/postgres'
596
-
597
-```
598
-###### Unix socket
599
-
600
-An example configuration.
601
-
602
-<details open><summary>Config</summary>
603
-
604
-```yaml
605
-jobs:
606
- - name: local
607
- dsn: 'host=/var/run/postgresql dbname=postgres user=netdata'
608
-
609
-```
610
-</details>
611
-
612
-###### Unix socket (custom port)
613
-
614
-Connect to PostgreSQL using a Unix socket with a non-default port (5433).
615
-
616
-<details open><summary>Config</summary>
617
-
618
-```yaml
619
-jobs:
620
- - name: local
621
- dsn: 'host=/var/run/postgresql port=5433 dbname=postgres user=netdata'
622
-
623
-```
624
-</details>
625
-
626
-###### Azure Database for PostgreSQL with service principal
627
-
628
-Use Microsoft Entra service principal authentication.
629
-
630
-<details open><summary>Config</summary>
631
-
632
-```yaml
633
-jobs:
634
- - name: azure_postgres_sp
635
- dsn: 'postgresql://netdata@myserver.postgres.database.azure.com:5432/postgres?sslmode=require'
636
- cloud_auth:
637
- provider: azure_ad
638
- azure_ad:
639
- mode: service_principal
640
- mode_service_principal:
641
- tenant_id: "00000000-0000-0000-0000-000000000000"
642
- client_id: "11111111-1111-1111-1111-111111111111"
643
- client_secret: "super-secret-value"
644
-
645
-```
646
-</details>
647
-
648
-###### Azure Database for PostgreSQL with managed identity
649
-
650
-Use managed identity authentication (system-assigned by default).
651
-
652
-<details open><summary>Config</summary>
653
-
654
-```yaml
655
-jobs:
656
- - name: azure_postgres_mi
657
- dsn: 'postgresql://netdata@myserver.postgres.database.azure.com:5432/postgres?sslmode=require'
658
- cloud_auth:
659
- provider: azure_ad
660
- azure_ad:
661
- mode: managed_identity
662
-
663
-```
664
-</details>
665
-
666
-###### Multi-instance
667
-
668
-> **Note**: When you define multiple jobs, their names must be unique.
669
-
670
-Local and remote instances.
671
-
672
-
673
-<details open><summary>Config</summary>
674
-
675
-```yaml
676
-jobs:
677
- - name: local
678
- dsn: 'postgresql://netdata@127.0.0.1:5432/postgres'
679
-
680
- - name: remote
681
- dsn: 'postgresql://netdata@203.0.113.0:5432/postgres'
682
-
683
-```
684
-</details>
685
-
686
-
687
-
688
## Troubleshooting
689
690
### Debug Mode
src/go/plugin/go.d/collector/powerdns/integrations/powerdns_authoritative_server.md
+31
-31
@@ -50,37 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per PowerDNS Authoritative Server instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| powerdns.questions_in | udp, tcp | questions/s |
72
-| powerdns.questions_out | udp, tcp | questions/s |
73
-| powerdns.cache_usage | query-cache-hit, query-cache-miss, packetcache-hit, packetcache-miss | events/s |
74
-| powerdns.cache_size | query-cache, packet-cache, key-cache, meta-cache | entries |
75
-| powerdns.latency | latency | microseconds |
76
-
77
-
78
-
79
-## Alerts
80
-
81
-There are no alerts configured by default for this integration.
82
-
83
-
53
## Setup
54
55
@@ -238,6 +207,37 @@ jobs:
207
208
209
210
+## Alerts
211
+
212
+There are no alerts configured by default for this integration.
213
+
214
+
215
+## Metrics
216
+
217
+Metrics grouped by *scope*.
218
+
219
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
220
+
221
+
222
+
223
+### Per PowerDNS Authoritative Server instance
224
+
225
+These metrics refer to the entire monitored application.
226
+
227
+This scope has no labels.
228
+
229
+Metrics:
230
+
231
+| Metric | Dimensions | Unit |
232
+|:------|:----------|:----|
233
+| powerdns.questions_in | udp, tcp | questions/s |
234
+| powerdns.questions_out | udp, tcp | questions/s |
235
+| powerdns.cache_usage | query-cache-hit, query-cache-miss, packetcache-hit, packetcache-miss | events/s |
236
+| powerdns.cache_size | query-cache, packet-cache, key-cache, meta-cache | entries |
237
+| powerdns.latency | latency | microseconds |
238
+
239
+
240
+
241
## Troubleshooting
242
243
### Debug Mode
src/go/plugin/go.d/collector/powerdns_recursor/integrations/powerdns_recursor.md
+33
-33
@@ -51,39 +51,6 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
-## Metrics
55
-
56
-Metrics grouped by *scope*.
57
-
58
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
59
-
60
-
61
-
62
-### Per PowerDNS Recursor instance
63
-
64
-These metrics refer to the entire monitored application.
65
-
66
-This scope has no labels.
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| powerdns_recursor.questions_in | total, tcp, ipv6 | questions/s |
73
-| powerdns_recursor.questions_out | udp, tcp, ipv6, throttled | questions/s |
74
-| powerdns_recursor.answer_time | 0-1ms, 1-10ms, 10-100ms, 100-1000ms, slow | queries/s |
75
-| powerdns_recursor.timeouts | total, ipv4, ipv6 | timeouts/s |
76
-| powerdns_recursor.drops | over-capacity-drops, query-pipe-full-drops, too-old-drops, truncated-drops, empty-queries | drops/s |
77
-| powerdns_recursor.cache_usage | cache-hits, cache-misses, packet-cache-hits, packet-cache-misses | events/s |
78
-| powerdns_recursor.cache_size | cache, packet-cache, negative-cache | entries |
79
-
80
-
81
-
82
-## Alerts
83
-
84
-There are no alerts configured by default for this integration.
85
-
86
-
54
## Setup
55
56
@@ -241,6 +208,39 @@ jobs:
208
209
210
211
+## Alerts
212
+
213
+There are no alerts configured by default for this integration.
214
+
215
+
216
+## Metrics
217
+
218
+Metrics grouped by *scope*.
219
+
220
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
221
+
222
+
223
+
224
+### Per PowerDNS Recursor instance
225
+
226
+These metrics refer to the entire monitored application.
227
+
228
+This scope has no labels.
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| powerdns_recursor.questions_in | total, tcp, ipv6 | questions/s |
235
+| powerdns_recursor.questions_out | udp, tcp, ipv6, throttled | questions/s |
236
+| powerdns_recursor.answer_time | 0-1ms, 1-10ms, 10-100ms, 100-1000ms, slow | queries/s |
237
+| powerdns_recursor.timeouts | total, ipv4, ipv6 | timeouts/s |
238
+| powerdns_recursor.drops | over-capacity-drops, query-pipe-full-drops, too-old-drops, truncated-drops, empty-queries | drops/s |
239
+| powerdns_recursor.cache_usage | cache-hits, cache-misses, packet-cache-hits, packet-cache-misses | events/s |
240
+| powerdns_recursor.cache_size | cache, packet-cache, negative-cache | entries |
241
+
242
+
243
+
244
## Troubleshooting
245
246
### Debug Mode
src/go/plugin/go.d/collector/powerstore/integrations/dell_powerstore.md
+171
-171
@@ -86,177 +86,6 @@ API which returns pre-aggregated data, imposing minimal load on the array. Sessi
86
CSRF tokens are cached across collection cycles.
87
88
89
-## Metrics
90
-
91
-Metrics grouped by *scope*.
92
-
93
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
94
-
95
-
96
-
97
-### Per Dell PowerStore instance
98
-
99
-These metrics refer to the entire monitored PowerStore cluster.
100
-
101
-This scope has no labels.
102
-
103
-Metrics:
104
-
105
-| Metric | Dimensions | Unit |
106
-|:------|:----------|:----|
107
-| powerstore.cluster_space_usage | used, total | bytes |
108
-| powerstore.cluster_space_logical | provisioned, used, data_physical, shared | bytes |
109
-| powerstore.cluster_space_efficiency | efficiency, data_reduction, snapshot_savings, thin_savings | ratio |
110
-| powerstore.hardware_health_fan | ok, degraded, failed, unknown | fans |
111
-| powerstore.hardware_health_psu | ok, degraded, failed, unknown | PSUs |
112
-| powerstore.hardware_health_drive | ok, degraded, failed, unknown | drives |
113
-| powerstore.hardware_health_battery | ok, degraded, failed, unknown | batteries |
114
-| powerstore.hardware_health_node | ok, degraded, failed, unknown | nodes |
115
-| powerstore.alerts_active | critical, major, minor, info | alerts |
116
-| powerstore.nas_server_status | started, stopped, degraded, unknown | servers |
117
-| powerstore.copy_data | remaining, transferred | bytes |
118
-| powerstore.copy_transfer_rate | rate | bytes/s |
119
-
120
-### Per appliance
121
-
122
-These metrics refer to individual PowerStore appliances.
123
-
124
-Labels:
125
-
126
-| Label | Description |
127
-|:-----------|:----------------|
128
-| appliance | Appliance name (e.g., `Appliance-WX-D8031`). |
129
-
130
-Metrics:
131
-
132
-| Metric | Dimensions | Unit |
133
-|:------|:----------|:----|
134
-| powerstore.appliance_iops | read, write | ops/s |
135
-| powerstore.appliance_bandwidth | read, write | bytes/s |
136
-| powerstore.appliance_latency | read, write, avg | microseconds |
137
-| powerstore.appliance_cpu | utilization | percentage |
138
-| powerstore.appliance_space | used, total | bytes |
139
-| powerstore.appliance_space_logical | provisioned, used, data_physical, shared | bytes |
140
-| powerstore.appliance_space_efficiency | efficiency, data_reduction, snapshot_savings, thin_savings | ratio |
141
-
142
-### Per volume
143
-
144
-These metrics refer to individual PowerStore volumes. Volumes can be filtered using the `volume_selector` configuration option.
145
-
146
-Labels:
147
-
148
-| Label | Description |
149
-|:-----------|:----------------|
150
-| volume | Volume name (e.g., `prod-db-01`). |
151
-
152
-Metrics:
153
-
154
-| Metric | Dimensions | Unit |
155
-|:------|:----------|:----|
156
-| powerstore.volume_iops | read, write | ops/s |
157
-| powerstore.volume_bandwidth | read, write | bytes/s |
158
-| powerstore.volume_latency | read, write, avg | microseconds |
159
-| powerstore.volume_space | provisioned, used | bytes |
160
-| powerstore.volume_space_savings | thin_savings | ratio |
161
-
162
-### Per node
163
-
164
-These metrics refer to individual PowerStore nodes within an appliance.
165
-
166
-Labels:
167
-
168
-| Label | Description |
169
-|:-----------|:----------------|
170
-| node | Node name (e.g., `Appliance-WX-D8031-node-A`). |
171
-
172
-Metrics:
173
-
174
-| Metric | Dimensions | Unit |
175
-|:------|:----------|:----|
176
-| powerstore.node_iops | read, write | ops/s |
177
-| powerstore.node_bandwidth | read, write | bytes/s |
178
-| powerstore.node_latency | read, write, avg | microseconds |
179
-| powerstore.node_logins | logins | logins |
180
-
181
-### Per fc port
182
-
183
-These metrics refer to individual Fibre Channel ports used for host connectivity.
184
-
185
-Labels:
186
-
187
-| Label | Description |
188
-|:-----------|:----------------|
189
-| fc_port | FC port name (e.g., `Appliance-WX-D8031-node-A-Port-0`). |
190
-
191
-Metrics:
192
-
193
-| Metric | Dimensions | Unit |
194
-|:------|:----------|:----|
195
-| powerstore.fc_port_iops | read, write | ops/s |
196
-| powerstore.fc_port_bandwidth | read, write | bytes/s |
197
-| powerstore.fc_port_latency | read, write, avg | microseconds |
198
-| powerstore.fc_port_link_status | up | status |
199
-
200
-### Per ethernet port
201
-
202
-These metrics refer to individual Ethernet ports (management and iSCSI connectivity).
203
-
204
-Labels:
205
-
206
-| Label | Description |
207
-|:-----------|:----------------|
208
-| eth_port | Ethernet port name (e.g., `Appliance-WX-D8031-node-A-Port-eth0`). |
209
-
210
-Metrics:
211
-
212
-| Metric | Dimensions | Unit |
213
-|:------|:----------|:----|
214
-| powerstore.eth_port_bytes | received, sent | bytes/s |
215
-| powerstore.eth_port_packets | received, sent | packets/s |
216
-| powerstore.eth_port_errors | rx_crc, rx_no_buffer, tx_error | errors/s |
217
-| powerstore.eth_port_link_status | up | status |
218
-
219
-### Per file system
220
-
221
-These metrics refer to individual file systems (NFS/SMB shares).
222
-
223
-Labels:
224
-
225
-| Label | Description |
226
-|:-----------|:----------------|
227
-| filesystem | File system name (e.g., `nfs-share-01`). |
228
-
229
-Metrics:
230
-
231
-| Metric | Dimensions | Unit |
232
-|:------|:----------|:----|
233
-| powerstore.filesystem_iops | read, write | ops/s |
234
-| powerstore.filesystem_bandwidth | read, write | bytes/s |
235
-| powerstore.filesystem_latency | read, write, avg | microseconds |
236
-
237
-### Per drive
238
-
239
-These metrics refer to individual physical drives (SSDs).
240
-
241
-Labels:
242
-
243
-| Label | Description |
244
-|:-----------|:----------------|
245
-| drive | Drive name (e.g., `Drive_0_0_25`). |
246
-
247
-Metrics:
248
-
249
-| Metric | Dimensions | Unit |
250
-|:------|:----------|:----|
251
-| powerstore.drive_endurance | remaining | percentage |
252
-
253
-
254
-
255
-## Alerts
256
-
257
-There are no alerts configured by default for this integration.
258
-
259
-
89
## Setup
90
91
@@ -426,6 +255,177 @@ jobs:
255
256
257
258
+## Alerts
259
+
260
+There are no alerts configured by default for this integration.
261
+
262
+
263
+## Metrics
264
+
265
+Metrics grouped by *scope*.
266
+
267
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
268
+
269
+
270
+
271
+### Per Dell PowerStore instance
272
+
273
+These metrics refer to the entire monitored PowerStore cluster.
274
+
275
+This scope has no labels.
276
+
277
+Metrics:
278
+
279
+| Metric | Dimensions | Unit |
280
+|:------|:----------|:----|
281
+| powerstore.cluster_space_usage | used, total | bytes |
282
+| powerstore.cluster_space_logical | provisioned, used, data_physical, shared | bytes |
283
+| powerstore.cluster_space_efficiency | efficiency, data_reduction, snapshot_savings, thin_savings | ratio |
284
+| powerstore.hardware_health_fan | ok, degraded, failed, unknown | fans |
285
+| powerstore.hardware_health_psu | ok, degraded, failed, unknown | PSUs |
286
+| powerstore.hardware_health_drive | ok, degraded, failed, unknown | drives |
287
+| powerstore.hardware_health_battery | ok, degraded, failed, unknown | batteries |
288
+| powerstore.hardware_health_node | ok, degraded, failed, unknown | nodes |
289
+| powerstore.alerts_active | critical, major, minor, info | alerts |
290
+| powerstore.nas_server_status | started, stopped, degraded, unknown | servers |
291
+| powerstore.copy_data | remaining, transferred | bytes |
292
+| powerstore.copy_transfer_rate | rate | bytes/s |
293
+
294
+### Per appliance
295
+
296
+These metrics refer to individual PowerStore appliances.
297
+
298
+Labels:
299
+
300
+| Label | Description |
301
+|:-----------|:----------------|
302
+| appliance | Appliance name (e.g., `Appliance-WX-D8031`). |
303
+
304
+Metrics:
305
+
306
+| Metric | Dimensions | Unit |
307
+|:------|:----------|:----|
308
+| powerstore.appliance_iops | read, write | ops/s |
309
+| powerstore.appliance_bandwidth | read, write | bytes/s |
310
+| powerstore.appliance_latency | read, write, avg | microseconds |
311
+| powerstore.appliance_cpu | utilization | percentage |
312
+| powerstore.appliance_space | used, total | bytes |
313
+| powerstore.appliance_space_logical | provisioned, used, data_physical, shared | bytes |
314
+| powerstore.appliance_space_efficiency | efficiency, data_reduction, snapshot_savings, thin_savings | ratio |
315
+
316
+### Per volume
317
+
318
+These metrics refer to individual PowerStore volumes. Volumes can be filtered using the `volume_selector` configuration option.
319
+
320
+Labels:
321
+
322
+| Label | Description |
323
+|:-----------|:----------------|
324
+| volume | Volume name (e.g., `prod-db-01`). |
325
+
326
+Metrics:
327
+
328
+| Metric | Dimensions | Unit |
329
+|:------|:----------|:----|
330
+| powerstore.volume_iops | read, write | ops/s |
331
+| powerstore.volume_bandwidth | read, write | bytes/s |
332
+| powerstore.volume_latency | read, write, avg | microseconds |
333
+| powerstore.volume_space | provisioned, used | bytes |
334
+| powerstore.volume_space_savings | thin_savings | ratio |
335
+
336
+### Per node
337
+
338
+These metrics refer to individual PowerStore nodes within an appliance.
339
+
340
+Labels:
341
+
342
+| Label | Description |
343
+|:-----------|:----------------|
344
+| node | Node name (e.g., `Appliance-WX-D8031-node-A`). |
345
+
346
+Metrics:
347
+
348
+| Metric | Dimensions | Unit |
349
+|:------|:----------|:----|
350
+| powerstore.node_iops | read, write | ops/s |
351
+| powerstore.node_bandwidth | read, write | bytes/s |
352
+| powerstore.node_latency | read, write, avg | microseconds |
353
+| powerstore.node_logins | logins | logins |
354
+
355
+### Per fc port
356
+
357
+These metrics refer to individual Fibre Channel ports used for host connectivity.
358
+
359
+Labels:
360
+
361
+| Label | Description |
362
+|:-----------|:----------------|
363
+| fc_port | FC port name (e.g., `Appliance-WX-D8031-node-A-Port-0`). |
364
+
365
+Metrics:
366
+
367
+| Metric | Dimensions | Unit |
368
+|:------|:----------|:----|
369
+| powerstore.fc_port_iops | read, write | ops/s |
370
+| powerstore.fc_port_bandwidth | read, write | bytes/s |
371
+| powerstore.fc_port_latency | read, write, avg | microseconds |
372
+| powerstore.fc_port_link_status | up | status |
373
+
374
+### Per ethernet port
375
+
376
+These metrics refer to individual Ethernet ports (management and iSCSI connectivity).
377
+
378
+Labels:
379
+
380
+| Label | Description |
381
+|:-----------|:----------------|
382
+| eth_port | Ethernet port name (e.g., `Appliance-WX-D8031-node-A-Port-eth0`). |
383
+
384
+Metrics:
385
+
386
+| Metric | Dimensions | Unit |
387
+|:------|:----------|:----|
388
+| powerstore.eth_port_bytes | received, sent | bytes/s |
389
+| powerstore.eth_port_packets | received, sent | packets/s |
390
+| powerstore.eth_port_errors | rx_crc, rx_no_buffer, tx_error | errors/s |
391
+| powerstore.eth_port_link_status | up | status |
392
+
393
+### Per file system
394
+
395
+These metrics refer to individual file systems (NFS/SMB shares).
396
+
397
+Labels:
398
+
399
+| Label | Description |
400
+|:-----------|:----------------|
401
+| filesystem | File system name (e.g., `nfs-share-01`). |
402
+
403
+Metrics:
404
+
405
+| Metric | Dimensions | Unit |
406
+|:------|:----------|:----|
407
+| powerstore.filesystem_iops | read, write | ops/s |
408
+| powerstore.filesystem_bandwidth | read, write | bytes/s |
409
+| powerstore.filesystem_latency | read, write, avg | microseconds |
410
+
411
+### Per drive
412
+
413
+These metrics refer to individual physical drives (SSDs).
414
+
415
+Labels:
416
+
417
+| Label | Description |
418
+|:-----------|:----------------|
419
+| drive | Drive name (e.g., `Drive_0_0_25`). |
420
+
421
+Metrics:
422
+
423
+| Metric | Dimensions | Unit |
424
+|:------|:----------|:----|
425
+| powerstore.drive_endurance | remaining | percentage |
426
+
427
+
428
+
429
## Troubleshooting
430
431
### Debug Mode
src/go/plugin/go.d/collector/powervault/integrations/dell_powervault_me4-me5.md
+151
-151
@@ -75,157 +75,6 @@ The MCI API is lightweight and read-only. The collector's impact on the storage
75
Session keys are reused across collection cycles and automatically refreshed on expiry (HTTP 401).
76
77
78
-## Metrics
79
-
80
-Metrics grouped by *scope*.
81
-
82
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
83
-
84
-
85
-
86
-### Per Dell PowerVault ME4/ME5 instance
87
-
88
-These metrics refer to the entire monitored PowerVault array.
89
-
90
-This scope has no labels.
91
-
92
-Metrics:
93
-
94
-| Metric | Dimensions | Unit |
95
-|:------|:----------|:----|
96
-| powervault.system_health | health | status |
97
-| powervault.hw_health_controller | ok, degraded, fault, unknown | controllers |
98
-| powervault.hw_health_drive | ok, degraded, fault, unknown | drives |
99
-| powervault.hw_health_fan | ok, degraded, fault, unknown | fans |
100
-| powervault.hw_health_psu | ok, degraded, fault, unknown | PSUs |
101
-| powervault.hw_health_fru | ok, degraded, fault, unknown | FRUs |
102
-| powervault.hw_health_port | ok, degraded, fault, unknown | ports |
103
-
104
-### Per controller
105
-
106
-These metrics refer to individual RAID controllers (typically controller_a and controller_b in a dual-controller configuration).
107
-
108
-Labels:
109
-
110
-| Label | Description |
111
-|:-----------|:----------------|
112
-| controller | Controller durable ID (e.g., `controller_a`, `controller_b`). |
113
-
114
-Metrics:
115
-
116
-| Metric | Dimensions | Unit |
117
-|:------|:----------|:----|
118
-| powervault.controller_iops | iops | ops/s |
119
-| powervault.controller_throughput | throughput | bytes/s |
120
-| powervault.controller_cpu_load | cpu_load | percentage |
121
-| powervault.controller_write_cache_used | write_cache_used | percentage |
122
-| powervault.controller_forwarded_cmds | forwarded | commands |
123
-| powervault.controller_io | read, written | bytes |
124
-| powervault.controller_ops | read, write | ops |
125
-| powervault.controller_cache_hits | read_hits, read_misses, write_hits, write_misses | hits |
126
-
127
-### Per volume
128
-
129
-These metrics refer to individual storage volumes. Volumes can be filtered using the `volume_selector` configuration option.
130
-
131
-Labels:
132
-
133
-| Label | Description |
134
-|:-----------|:----------------|
135
-| volume | Volume name (e.g., `prod-db-01`). |
136
-
137
-Metrics:
138
-
139
-| Metric | Dimensions | Unit |
140
-|:------|:----------|:----|
141
-| powervault.volume_iops | iops | ops/s |
142
-| powervault.volume_throughput | throughput | bytes/s |
143
-| powervault.volume_write_cache_percent | write_cache | percentage |
144
-| powervault.volume_io | read, written | bytes |
145
-| powervault.volume_ops | read, write | ops |
146
-| powervault.volume_cache_hits | read_hits, read_misses, write_hits, write_misses | hits |
147
-| powervault.volume_tier_distribution | ssd, sas, sata | percentage |
148
-
149
-### Per port
150
-
151
-These metrics refer to individual host ports (SAS/FC ports used for host connectivity).
152
-
153
-Labels:
154
-
155
-| Label | Description |
156
-|:-----------|:----------------|
157
-| port | Port durable ID (e.g., `hostport_A0`). |
158
-
159
-Metrics:
160
-
161
-| Metric | Dimensions | Unit |
162
-|:------|:----------|:----|
163
-| powervault.port_io | read, written | bytes |
164
-| powervault.port_ops | read, write | ops |
165
-| powervault.phy_errors | disparity, lost_dwords, invalid_dwords | errors |
166
-
167
-### Per pool
168
-
169
-These metrics refer to individual storage pools (also known as disk groups or virtual pools).
170
-
171
-Labels:
172
-
173
-| Label | Description |
174
-|:-----------|:----------------|
175
-| pool | Pool name (e.g., `Pool-A`). |
176
-
177
-Metrics:
178
-
179
-| Metric | Dimensions | Unit |
180
-|:------|:----------|:----|
181
-| powervault.pool_capacity | total, available | bytes |
182
-
183
-### Per drive
184
-
185
-These metrics refer to individual physical drives (HDDs and SSDs).
186
-
187
-Labels:
188
-
189
-| Label | Description |
190
-|:-----------|:----------------|
191
-| drive | Drive location (e.g., `0.0` for enclosure 0, slot 0). |
192
-
193
-Metrics:
194
-
195
-| Metric | Dimensions | Unit |
196
-|:------|:----------|:----|
197
-| powervault.drive_temperature | temperature | Celsius |
198
-| powervault.drive_power_on_hours | power_on_hours | hours |
199
-| powervault.drive_ssd_life_left | life_left | percentage |
200
-
201
-### Per sensor
202
-
203
-These metrics refer to individual hardware sensors. Sensor types include temperature,
204
-voltage, current, and charge capacity (supercapacitor/battery backup units).
205
-
206
-
207
-Labels:
208
-
209
-| Label | Description |
210
-|:-----------|:----------------|
211
-| sensor | Sensor durable ID (e.g., `sensor_temp_ctrl_A.1`). |
212
-
213
-Metrics:
214
-
215
-| Metric | Dimensions | Unit |
216
-|:------|:----------|:----|
217
-| powervault.sensor_temperature | temperature | Celsius |
218
-| powervault.sensor_voltage | voltage | millivolts |
219
-| powervault.sensor_current | current | milliamps |
220
-| powervault.sensor_charge_capacity | charge_capacity | percentage |
221
-
222
-
223
-
224
-## Alerts
225
-
226
-There are no alerts configured by default for this integration.
227
-
228
-
78
## Setup
79
80
@@ -414,6 +263,157 @@ jobs:
263
264
265
266
+## Alerts
267
+
268
+There are no alerts configured by default for this integration.
269
+
270
+
271
+## Metrics
272
+
273
+Metrics grouped by *scope*.
274
+
275
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
276
+
277
+
278
+
279
+### Per Dell PowerVault ME4/ME5 instance
280
+
281
+These metrics refer to the entire monitored PowerVault array.
282
+
283
+This scope has no labels.
284
+
285
+Metrics:
286
+
287
+| Metric | Dimensions | Unit |
288
+|:------|:----------|:----|
289
+| powervault.system_health | health | status |
290
+| powervault.hw_health_controller | ok, degraded, fault, unknown | controllers |
291
+| powervault.hw_health_drive | ok, degraded, fault, unknown | drives |
292
+| powervault.hw_health_fan | ok, degraded, fault, unknown | fans |
293
+| powervault.hw_health_psu | ok, degraded, fault, unknown | PSUs |
294
+| powervault.hw_health_fru | ok, degraded, fault, unknown | FRUs |
295
+| powervault.hw_health_port | ok, degraded, fault, unknown | ports |
296
+
297
+### Per controller
298
+
299
+These metrics refer to individual RAID controllers (typically controller_a and controller_b in a dual-controller configuration).
300
+
301
+Labels:
302
+
303
+| Label | Description |
304
+|:-----------|:----------------|
305
+| controller | Controller durable ID (e.g., `controller_a`, `controller_b`). |
306
+
307
+Metrics:
308
+
309
+| Metric | Dimensions | Unit |
310
+|:------|:----------|:----|
311
+| powervault.controller_iops | iops | ops/s |
312
+| powervault.controller_throughput | throughput | bytes/s |
313
+| powervault.controller_cpu_load | cpu_load | percentage |
314
+| powervault.controller_write_cache_used | write_cache_used | percentage |
315
+| powervault.controller_forwarded_cmds | forwarded | commands |
316
+| powervault.controller_io | read, written | bytes |
317
+| powervault.controller_ops | read, write | ops |
318
+| powervault.controller_cache_hits | read_hits, read_misses, write_hits, write_misses | hits |
319
+
320
+### Per volume
321
+
322
+These metrics refer to individual storage volumes. Volumes can be filtered using the `volume_selector` configuration option.
323
+
324
+Labels:
325
+
326
+| Label | Description |
327
+|:-----------|:----------------|
328
+| volume | Volume name (e.g., `prod-db-01`). |
329
+
330
+Metrics:
331
+
332
+| Metric | Dimensions | Unit |
333
+|:------|:----------|:----|
334
+| powervault.volume_iops | iops | ops/s |
335
+| powervault.volume_throughput | throughput | bytes/s |
336
+| powervault.volume_write_cache_percent | write_cache | percentage |
337
+| powervault.volume_io | read, written | bytes |
338
+| powervault.volume_ops | read, write | ops |
339
+| powervault.volume_cache_hits | read_hits, read_misses, write_hits, write_misses | hits |
340
+| powervault.volume_tier_distribution | ssd, sas, sata | percentage |
341
+
342
+### Per port
343
+
344
+These metrics refer to individual host ports (SAS/FC ports used for host connectivity).
345
+
346
+Labels:
347
+
348
+| Label | Description |
349
+|:-----------|:----------------|
350
+| port | Port durable ID (e.g., `hostport_A0`). |
351
+
352
+Metrics:
353
+
354
+| Metric | Dimensions | Unit |
355
+|:------|:----------|:----|
356
+| powervault.port_io | read, written | bytes |
357
+| powervault.port_ops | read, write | ops |
358
+| powervault.phy_errors | disparity, lost_dwords, invalid_dwords | errors |
359
+
360
+### Per pool
361
+
362
+These metrics refer to individual storage pools (also known as disk groups or virtual pools).
363
+
364
+Labels:
365
+
366
+| Label | Description |
367
+|:-----------|:----------------|
368
+| pool | Pool name (e.g., `Pool-A`). |
369
+
370
+Metrics:
371
+
372
+| Metric | Dimensions | Unit |
373
+|:------|:----------|:----|
374
+| powervault.pool_capacity | total, available | bytes |
375
+
376
+### Per drive
377
+
378
+These metrics refer to individual physical drives (HDDs and SSDs).
379
+
380
+Labels:
381
+
382
+| Label | Description |
383
+|:-----------|:----------------|
384
+| drive | Drive location (e.g., `0.0` for enclosure 0, slot 0). |
385
+
386
+Metrics:
387
+
388
+| Metric | Dimensions | Unit |
389
+|:------|:----------|:----|
390
+| powervault.drive_temperature | temperature | Celsius |
391
+| powervault.drive_power_on_hours | power_on_hours | hours |
392
+| powervault.drive_ssd_life_left | life_left | percentage |
393
+
394
+### Per sensor
395
+
396
+These metrics refer to individual hardware sensors. Sensor types include temperature,
397
+voltage, current, and charge capacity (supercapacitor/battery backup units).
398
+
399
+
400
+Labels:
401
+
402
+| Label | Description |
403
+|:-----------|:----------------|
404
+| sensor | Sensor durable ID (e.g., `sensor_temp_ctrl_A.1`). |
405
+
406
+Metrics:
407
+
408
+| Metric | Dimensions | Unit |
409
+|:------|:----------|:----|
410
+| powervault.sensor_temperature | temperature | Celsius |
411
+| powervault.sensor_voltage | voltage | millivolts |
412
+| powervault.sensor_current | current | milliamps |
413
+| powervault.sensor_charge_capacity | charge_capacity | percentage |
414
+
415
+
416
+
417
## Troubleshooting
418
419
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/4d_server.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/8430ft_modem.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/alamos_fe2_server.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/amd_cpu_&_gpu.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/apicast.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/authlog.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_compute_instances.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/aws_quota.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/aws_rds.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/bird_routing_daemon.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/blackbox.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/bosh.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/bungeecord.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/celery.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/chia.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cilium_agent.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cilium_operator.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cilium_proxy.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/clamav_daemon.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/clamscan_results.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/clash.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry_firehose.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cloudwatch.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/clustercontrol_cmon.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/collectd.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/concourse.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/craftbeerpi.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/crowdsec.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/cryptowatch.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/discourse.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/dmarc.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/dnsbl.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/dutch_electricity_smart_meter.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/dynatrace.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/elgato_key_light_devices..md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/energomera_smart_power_meters.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/eos.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/etcd.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -303,6 +274,35 @@ jobs:
274
275
276
277
+## Alerts
278
+
279
+There are no alerts configured by default for this integration.
280
+
281
+
282
+## Metrics
283
+
284
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
285
+
286
+| Metric | Chart | Dimension(s) | Algorithm |
287
+|---------------------------|-------------------------------------------|----------------------|-------------|
288
+| Gauge | for each label set | one, the metric name | absolute |
289
+| Counter | for each label set | one, the metric name | incremental |
290
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
291
+| Summary (sum and count) | for each label set | the metric name | incremental |
292
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
293
+| Histogram (sum and count) | for each label set | the metric name | incremental |
294
+
295
+Untyped metrics (have no '# TYPE') processing:
296
+
297
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
298
+- As Counter if it has suffix '_total'.
299
+- As Summary if it has 'quantile' label.
300
+- As Histogram if it has 'le' label.
301
+
302
+**The rest are ignored**.
303
+
304
+
305
+
306
## Troubleshooting
307
308
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/fastd.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/freebsd_nfs.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/freebsd_rctl-racct.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/freifunk_network.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/frrouting.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/gcp_gce.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/generic_storage_enclosure_tool.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/github_api_rate_limit.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/github_repository.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/gitlab_runner.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/gobetween.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -303,6 +274,35 @@ jobs:
274
275
276
277
+## Alerts
278
+
279
+There are no alerts configured by default for this integration.
280
+
281
+
282
+## Metrics
283
+
284
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
285
+
286
+| Metric | Chart | Dimension(s) | Algorithm |
287
+|---------------------------|-------------------------------------------|----------------------|-------------|
288
+| Gauge | for each label set | one, the metric name | absolute |
289
+| Counter | for each label set | one, the metric name | incremental |
290
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
291
+| Summary (sum and count) | for each label set | the metric name | incremental |
292
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
293
+| Histogram (sum and count) | for each label set | the metric name | incremental |
294
+
295
+Untyped metrics (have no '# TYPE') processing:
296
+
297
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
298
+- As Counter if it has suffix '_total'.
299
+- As Summary if it has 'quantile' label.
300
+- As Histogram if it has 'le' label.
301
+
302
+**The rest are ignored**.
303
+
304
+
305
+
306
## Troubleshooting
307
308
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/google_cloud_platform.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/google_pagespeed.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/google_stackdriver.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/gpsd.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/grafana.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -303,6 +274,35 @@ jobs:
274
275
276
277
+## Alerts
278
+
279
+There are no alerts configured by default for this integration.
280
+
281
+
282
+## Metrics
283
+
284
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
285
+
286
+| Metric | Chart | Dimension(s) | Algorithm |
287
+|---------------------------|-------------------------------------------|----------------------|-------------|
288
+| Gauge | for each label set | one, the metric name | absolute |
289
+| Counter | for each label set | one, the metric name | incremental |
290
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
291
+| Summary (sum and count) | for each label set | the metric name | incremental |
292
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
293
+| Histogram (sum and count) | for each label set | the metric name | incremental |
294
+
295
+Untyped metrics (have no '# TYPE') processing:
296
+
297
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
298
+- As Counter if it has suffix '_total'.
299
+- As Summary if it has 'quantile' label.
300
+- As Histogram if it has 'le' label.
301
+
302
+**The rest are ignored**.
303
+
304
+
305
+
306
## Troubleshooting
307
308
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/graylog_server.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/halon.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/hana.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/hitron_coda_cable_modem.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/homebridge.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/homey.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/honeypot.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/hubble.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ibm_aix_systems_njmon.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ibm_cryptoexpress_cex_cards.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ibm_mq.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum_virtualize.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ibm_z_hardware_management_console.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/influxdb.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/jarvis_standing_desk.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/jenkins.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/jmx.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/journald.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/kafka.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/kafka_consumer_lag.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/kafka_zookeeper.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/kannel.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/keepalived.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/linode.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/loki.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/lustre_metadata.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/lynis_audit_reports.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/meilisearch.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/mesos.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/minecraft.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/modbus_protocol.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/mogilefs.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/mosquitto.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/mqtt_blackbox.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/mtail.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/nature_remo_e_lite_devices.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/netapp_ontap_api.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/netapp_solidfire.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/netatmo_sensors.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/nextcloud_servers.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/nextdns.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/nrpe_daemon.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/obs_studio.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/open_vswitch.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/openrc.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/openroadm_devices.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -308,6 +279,35 @@ jobs:
279
280
281
282
+## Alerts
283
+
284
+There are no alerts configured by default for this integration.
285
+
286
+
287
+## Metrics
288
+
289
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
290
+
291
+| Metric | Chart | Dimension(s) | Algorithm |
292
+|---------------------------|-------------------------------------------|----------------------|-------------|
293
+| Gauge | for each label set | one, the metric name | absolute |
294
+| Counter | for each label set | one, the metric name | incremental |
295
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
296
+| Summary (sum and count) | for each label set | the metric name | incremental |
297
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
298
+| Histogram (sum and count) | for each label set | the metric name | incremental |
299
+
300
+Untyped metrics (have no '# TYPE') processing:
301
+
302
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
303
+- As Counter if it has suffix '_total'.
304
+- As Summary if it has 'quantile' label.
305
+- As Histogram if it has 'le' label.
306
+
307
+**The rest are ignored**.
308
+
309
+
310
+
311
## Troubleshooting
312
313
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/openweathermap.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/patroni.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/personal_weather_station.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/pgbackrest.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/pgpool-ii.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/philips_hue.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/pimoroni_enviro+.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/podman.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/powerpal_devices.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/proftpd.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/prometheus_endpoint.md
+29
-29
@@ -47,35 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
53
-
54
-| Metric | Chart | Dimension(s) | Algorithm |
55
-|---------------------------|-------------------------------------------|----------------------|-------------|
56
-| Gauge | for each label set | one, the metric name | absolute |
57
-| Counter | for each label set | one, the metric name | incremental |
58
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
59
-| Summary (sum and count) | for each label set | the metric name | incremental |
60
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
61
-| Histogram (sum and count) | for each label set | the metric name | incremental |
62
-
63
-Untyped metrics (have no '# TYPE') processing:
64
-
65
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
66
-- As Counter if it has suffix '_total'.
67
-- As Summary if it has 'quantile' label.
68
-- As Histogram if it has 'le' label.
69
-
70
-**The rest are ignored**.
71
-
72
-
73
-
74
-## Alerts
75
-
76
-There are no alerts configured by default for this integration.
77
-
78
-
50
## Setup
51
52
@@ -304,6 +275,35 @@ jobs:
275
276
277
278
+## Alerts
279
+
280
+There are no alerts configured by default for this integration.
281
+
282
+
283
+## Metrics
284
+
285
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
286
+
287
+| Metric | Chart | Dimension(s) | Algorithm |
288
+|---------------------------|-------------------------------------------|----------------------|-------------|
289
+| Gauge | for each label set | one, the metric name | absolute |
290
+| Counter | for each label set | one, the metric name | incremental |
291
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
292
+| Summary (sum and count) | for each label set | the metric name | incremental |
293
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
294
+| Histogram (sum and count) | for each label set | the metric name | incremental |
295
+
296
+Untyped metrics (have no '# TYPE') processing:
297
+
298
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
299
+- As Counter if it has suffix '_total'.
300
+- As Summary if it has 'quantile' label.
301
+- As Histogram if it has 'le' label.
302
+
303
+**The rest are ignored**.
304
+
305
+
306
+
307
## Troubleshooting
308
309
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/proxmox_ve.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/radio_thermostat.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/radius.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/raritan_pdu.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/redis_queue.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ripe_atlas.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sabnzbd.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/salicru_eqx_inverter.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/scylladb.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -303,6 +274,35 @@ jobs:
274
275
276
277
+## Alerts
278
+
279
+There are no alerts configured by default for this integration.
280
+
281
+
282
+## Metrics
283
+
284
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
285
+
286
+| Metric | Chart | Dimension(s) | Algorithm |
287
+|---------------------------|-------------------------------------------|----------------------|-------------|
288
+| Gauge | for each label set | one, the metric name | absolute |
289
+| Counter | for each label set | one, the metric name | incremental |
290
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
291
+| Summary (sum and count) | for each label set | the metric name | incremental |
292
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
293
+| Histogram (sum and count) | for each label set | the metric name | incremental |
294
+
295
+Untyped metrics (have no '# TYPE') processing:
296
+
297
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
298
+- As Counter if it has suffix '_total'.
299
+- As Summary if it has 'quantile' label.
300
+- As Histogram if it has 'le' label.
301
+
302
+**The rest are ignored**.
303
+
304
+
305
+
306
## Troubleshooting
307
308
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sense_energy.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/shelly_humidity_sensor.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/siemens_s7_plc.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/site_24x7.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/slurm.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sma_inverters.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/smart_meters_sml.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/softether_vpn_server.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/solar_logging_stick.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/solis_ginlong_5g_inverters.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sonic_nos.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/spacelift.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sphinx.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/starlink_spacex.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/statuspage.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/steam.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/storidge.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/strongswan.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sunspec_solar_energy.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/suricata.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/synology_activebackup.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/sysload.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/tacacs.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/tado_smart_heating_solution.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/tankerkoenig_api.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/tesla_vehicle.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/tesla_wall_connector.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/twitch.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/ubiquiti_ufiber_olt.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/uptimerobot.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/vault_pki.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/vertica.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/vscode.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/warp10.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/xiaomi_mi_flora.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/yourls_url_shortener.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/prometheus/integrations/zerto.md
+29
-29
@@ -46,35 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
52
-
53
-| Metric | Chart | Dimension(s) | Algorithm |
54
-|---------------------------|-------------------------------------------|----------------------|-------------|
55
-| Gauge | for each label set | one, the metric name | absolute |
56
-| Counter | for each label set | one, the metric name | incremental |
57
-| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
58
-| Summary (sum and count) | for each label set | the metric name | incremental |
59
-| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
60
-| Histogram (sum and count) | for each label set | the metric name | incremental |
61
-
62
-Untyped metrics (have no '# TYPE') processing:
63
-
64
-- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
65
-- As Counter if it has suffix '_total'.
66
-- As Summary if it has 'quantile' label.
67
-- As Histogram if it has 'le' label.
68
-
69
-**The rest are ignored**.
70
-
71
-
72
-
73
-## Alerts
74
-
75
-There are no alerts configured by default for this integration.
76
-
77
-
49
## Setup
50
51
@@ -307,6 +278,35 @@ jobs:
278
279
280
281
+## Alerts
282
+
283
+There are no alerts configured by default for this integration.
284
+
285
+
286
+## Metrics
287
+
288
+This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
289
+
290
+| Metric | Chart | Dimension(s) | Algorithm |
291
+|---------------------------|-------------------------------------------|----------------------|-------------|
292
+| Gauge | for each label set | one, the metric name | absolute |
293
+| Counter | for each label set | one, the metric name | incremental |
294
+| Summary (quantiles) | for each label set (excluding 'quantile') | for each quantile | absolute |
295
+| Summary (sum and count) | for each label set | the metric name | incremental |
296
+| Histogram (buckets) | for each label set (excluding 'le') | for each bucket | incremental |
297
+| Histogram (sum and count) | for each label set | the metric name | incremental |
298
+
299
+Untyped metrics (have no '# TYPE') processing:
300
+
301
+- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
302
+- As Counter if it has suffix '_total'.
303
+- As Summary if it has 'quantile' label.
304
+- As Histogram if it has 'le' label.
305
+
306
+**The rest are ignored**.
307
+
308
+
309
+
310
## Troubleshooting
311
312
### Debug Mode
src/go/plugin/go.d/collector/proxysql/integrations/proxysql.md
+147
-147
@@ -45,6 +45,152 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
+## Setup
49
+
50
+
51
+You can configure the **proxysql** collector in two ways:
52
+
53
+| Method | Best for | How to |
54
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
55
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **proxysql**, then click **+** to add a job. |
56
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/proxysql.conf` and add a job. |
57
+
58
+:::important
59
+
60
+UI configuration requires paid Netdata Cloud plan.
61
+
62
+:::
63
+
64
+
65
+### Prerequisites
66
+
67
+No action required.
68
+
69
+### Configuration
70
+
71
+#### Options
72
+
73
+The following options can be defined globally: update_every, autodetection_retry.
74
+
75
+
76
+<details open><summary>Config options</summary>
77
+
78
+
79
+
80
+| Group | Option | Description | Default | Required |
81
+|:------|:-----|:------------|:--------|:---------:|
82
+| **Collection** | update_every | Data collection frequency (seconds). | 1 | no |
83
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
84
+| **Target** | dsn | ProxySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | stats:stats@tcp(127.0.0.1:6032)/ | yes |
85
+| | timeout | Query timeout (seconds). | 1 | no |
86
+| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
87
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
88
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
89
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
90
+
91
+
92
+</details>
93
+
94
+
95
+#### via UI
96
+
97
+Configure the **proxysql** collector from the Netdata web interface:
98
+
99
+1. Go to **Nodes**.
100
+2. Select the node **where you want the proxysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
101
+3. The **Collectors → Jobs** view opens by default.
102
+4. In the Search box, type _proxysql_ (or scroll the list) to locate the **proxysql** collector.
103
+5. Click the **+** next to the **proxysql** collector to add a new job.
104
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
105
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
106
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
107
+
108
+
109
+#### via File
110
+
111
+The configuration file name for this integration is `go.d/proxysql.conf`.
112
+
113
+The file format is YAML. Generally, the structure is:
114
+
115
+```yaml
116
+update_every: 1
117
+autodetection_retry: 0
118
+jobs:
119
+ - name: some_name1
120
+ - name: some_name2
121
+```
122
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
123
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
124
+
125
+```bash
126
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
127
+sudo ./edit-config go.d/proxysql.conf
128
+```
129
+
130
+##### Examples
131
+
132
+###### TCP socket
133
+
134
+An example configuration.
135
+
136
+<details open><summary>Config</summary>
137
+
138
+```yaml
139
+jobs:
140
+ - name: local
141
+ dsn: stats:stats@tcp(127.0.0.1:6032)/
142
+
143
+```
144
+</details>
145
+
146
+###### my.cnf
147
+
148
+An example configuration.
149
+
150
+<details open><summary>Config</summary>
151
+
152
+```yaml
153
+jobs:
154
+ - name: local
155
+ my.cnf: '/etc/my.cnf'
156
+
157
+```
158
+</details>
159
+
160
+###### Multi-instance
161
+
162
+> **Note**: When you define multiple jobs, their names must be unique.
163
+
164
+Local and remote instances.
165
+
166
+
167
+<details open><summary>Config</summary>
168
+
169
+```yaml
170
+jobs:
171
+ - name: local
172
+ dsn: stats:stats@tcp(127.0.0.1:6032)/
173
+
174
+ - name: remote
175
+ dsn: stats:stats@tcp(203.0.113.0:6032)/
176
+
177
+```
178
+</details>
179
+
180
+
181
+
182
+## Alerts
183
+
184
+
185
+The following alerts are available:
186
+
187
+| Alert name | On metric | Description |
188
+|:------------|:----------|:------------|
189
+| [ proxysql_hostgroup_no_online_backends ](https://github.com/netdata/netdata/blob/master/src/health/health.d/proxysql.conf) | proxysql.hostgroup_backends_status | ProxySQL hostgroup ${label:hostgroup} has no ONLINE backends |
190
+| [ proxysql_backend_shunned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/proxysql.conf) | proxysql.backend_status | ProxySQL backend SHUNNED (${label:host}:${label:port} hostgroup ${label:hostgroup}) |
191
+| [ proxysql_backend_offline_hard ](https://github.com/netdata/netdata/blob/master/src/health/health.d/proxysql.conf) | proxysql.backend_status | ProxySQL backend OFFLINE_HARD (${label:host}:${label:port} hostgroup ${label:hostgroup}) |
192
+
193
+
194
## Metrics
195
196
Metrics grouped by *scope*.
@@ -168,7 +314,7 @@ Metrics:
314
315
316
171
-## Functions
317
+## Live Data
318
319
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
320
@@ -230,152 +376,6 @@ Aggregated query digest statistics from ProxySQL, providing comprehensive perfor
376
377
378
233
-## Alerts
234
-
235
-
236
-The following alerts are available:
237
-
238
-| Alert name | On metric | Description |
239
-|:------------|:----------|:------------|
240
-| [ proxysql_hostgroup_no_online_backends ](https://github.com/netdata/netdata/blob/master/src/health/health.d/proxysql.conf) | proxysql.hostgroup_backends_status | ProxySQL hostgroup ${label:hostgroup} has no ONLINE backends |
241
-| [ proxysql_backend_shunned ](https://github.com/netdata/netdata/blob/master/src/health/health.d/proxysql.conf) | proxysql.backend_status | ProxySQL backend SHUNNED (${label:host}:${label:port} hostgroup ${label:hostgroup}) |
242
-| [ proxysql_backend_offline_hard ](https://github.com/netdata/netdata/blob/master/src/health/health.d/proxysql.conf) | proxysql.backend_status | ProxySQL backend OFFLINE_HARD (${label:host}:${label:port} hostgroup ${label:hostgroup}) |
243
-
244
-
245
-## Setup
246
-
247
-
248
-You can configure the **proxysql** collector in two ways:
249
-
250
-| Method | Best for | How to |
251
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
252
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **proxysql**, then click **+** to add a job. |
253
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/proxysql.conf` and add a job. |
254
-
255
-:::important
256
-
257
-UI configuration requires paid Netdata Cloud plan.
258
-
259
-:::
260
-
261
-
262
-### Prerequisites
263
-
264
-No action required.
265
-
266
-### Configuration
267
-
268
-#### Options
269
-
270
-The following options can be defined globally: update_every, autodetection_retry.
271
-
272
-
273
-<details open><summary>Config options</summary>
274
-
275
-
276
-
277
-| Group | Option | Description | Default | Required |
278
-|:------|:-----|:------------|:--------|:---------:|
279
-| **Collection** | update_every | Data collection frequency (seconds). | 1 | no |
280
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
281
-| **Target** | dsn | ProxySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | stats:stats@tcp(127.0.0.1:6032)/ | yes |
282
-| | timeout | Query timeout (seconds). | 1 | no |
283
-| **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
284
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
285
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
286
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
287
-
288
-
289
-</details>
290
-
291
-
292
-#### via UI
293
-
294
-Configure the **proxysql** collector from the Netdata web interface:
295
-
296
-1. Go to **Nodes**.
297
-2. Select the node **where you want the proxysql data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
298
-3. The **Collectors → Jobs** view opens by default.
299
-4. In the Search box, type _proxysql_ (or scroll the list) to locate the **proxysql** collector.
300
-5. Click the **+** next to the **proxysql** collector to add a new job.
301
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
302
- - **Test** runs the job with the provided settings and shows whether data can be collected.
303
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
304
-
305
-
306
-#### via File
307
-
308
-The configuration file name for this integration is `go.d/proxysql.conf`.
309
-
310
-The file format is YAML. Generally, the structure is:
311
-
312
-```yaml
313
-update_every: 1
314
-autodetection_retry: 0
315
-jobs:
316
- - name: some_name1
317
- - name: some_name2
318
-```
319
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
320
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
321
-
322
-```bash
323
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
324
-sudo ./edit-config go.d/proxysql.conf
325
-```
326
-
327
-##### Examples
328
-
329
-###### TCP socket
330
-
331
-An example configuration.
332
-
333
-<details open><summary>Config</summary>
334
-
335
-```yaml
336
-jobs:
337
- - name: local
338
- dsn: stats:stats@tcp(127.0.0.1:6032)/
339
-
340
-```
341
-</details>
342
-
343
-###### my.cnf
344
-
345
-An example configuration.
346
-
347
-<details open><summary>Config</summary>
348
-
349
-```yaml
350
-jobs:
351
- - name: local
352
- my.cnf: '/etc/my.cnf'
353
-
354
-```
355
-</details>
356
-
357
-###### Multi-instance
358
-
359
-> **Note**: When you define multiple jobs, their names must be unique.
360
-
361
-Local and remote instances.
362
-
363
-
364
-<details open><summary>Config</summary>
365
-
366
-```yaml
367
-jobs:
368
- - name: local
369
- dsn: stats:stats@tcp(127.0.0.1:6032)/
370
-
371
- - name: remote
372
- dsn: stats:stats@tcp(203.0.113.0:6032)/
373
-
374
-```
375
-</details>
376
-
377
-
378
-
379
## Troubleshooting
380
381
### Debug Mode
src/go/plugin/go.d/collector/pulsar/integrations/apache_pulsar.md
+87
-87
@@ -51,93 +51,6 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
-## Metrics
55
-
56
-Metrics grouped by *scope*.
57
-
58
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
59
-
60
-- topic_* metrics are available when `exposeTopicLevelMetricsInPrometheus` is set to true.
61
-- subscription_* and namespace_subscription metrics are available when `exposeTopicLevelMetricsInPrometheus` si set to true.
62
-- replication_* and namespace_replication_* metrics are available when replication is configured and `replicationMetricsEnabled` is set to true.
63
-
64
-
65
-### Per Apache Pulsar instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| pulsar.broker_components | namespaces, topics, subscriptions, producers, consumers | components |
76
-| pulsar.messages_rate | publish, dispatch | messages/s |
77
-| pulsar.throughput_rate | publish, dispatch | KiB/s |
78
-| pulsar.storage_size | used | KiB |
79
-| pulsar.storage_operations_rate | read, write | message batches/s |
80
-| pulsar.msg_backlog | backlog | messages |
81
-| pulsar.storage_write_latency | <=0.5ms, <=1ms, <=5ms, =10ms, <=20ms, <=50ms, <=100ms, <=200ms, <=1s, >1s | entries/s |
82
-| pulsar.entry_size | <=128B, <=512B, <=1KB, <=2KB, <=4KB, <=16KB, <=100KB, <=1MB, >1MB | entries/s |
83
-| pulsar.subscription_delayed | delayed | message batches |
84
-| pulsar.subscription_msg_rate_redeliver | redelivered | messages/s |
85
-| pulsar.subscription_blocked_on_unacked_messages | blocked | subscriptions |
86
-| pulsar.replication_rate | in, out | messages/s |
87
-| pulsar.replication_throughput_rate | in, out | KiB/s |
88
-| pulsar.replication_backlog | backlog | messages |
89
-
90
-### Per namespace
91
-
92
-TBD
93
-
94
-This scope has no labels.
95
-
96
-Metrics:
97
-
98
-| Metric | Dimensions | Unit |
99
-|:------|:----------|:----|
100
-| pulsar.namespace_broker_components | topics, subscriptions, producers, consumers | components |
101
-| pulsar.namespace_messages_rate | publish, dispatch | messages/s |
102
-| pulsar.namespace_throughput_rate | publish, dispatch | KiB/s |
103
-| pulsar.namespace_storage_size | used | KiB |
104
-| pulsar.namespace_storage_operations_rate | read, write | message batches/s |
105
-| pulsar.namespace_msg_backlog | backlog | messages |
106
-| pulsar.namespace_storage_write_latency | <=0.5ms, <=1ms, <=5ms, =10ms, <=20ms, <=50ms, <=100ms, <=200ms, <=1s, >1s | entries/s |
107
-| pulsar.namespace_entry_size | <=128B, <=512B, <=1KB, <=2KB, <=4KB, <=16KB, <=100KB, <=1MB, >1MB | entries/s |
108
-| pulsar.namespace_subscription_delayed | delayed | message batches |
109
-| pulsar.namespace_subscription_msg_rate_redeliver | redelivered | messages/s |
110
-| pulsar.namespace_subscription_blocked_on_unacked_messages | blocked | subscriptions |
111
-| pulsar.namespace_replication_rate | in, out | messages/s |
112
-| pulsar.namespace_replication_throughput_rate | in, out | KiB/s |
113
-| pulsar.namespace_replication_backlog | backlog | messages |
114
-| pulsar.topic_producers | a dimension per topic | producers |
115
-| pulsar.topic_subscriptions | a dimension per topic | subscriptions |
116
-| pulsar.topic_consumers | a dimension per topic | consumers |
117
-| pulsar.topic_messages_rate_in | a dimension per topic | publishes/s |
118
-| pulsar.topic_messages_rate_out | a dimension per topic | dispatches/s |
119
-| pulsar.topic_throughput_rate_in | a dimension per topic | KiB/s |
120
-| pulsar.topic_throughput_rate_out | a dimension per topic | KiB/s |
121
-| pulsar.topic_storage_size | a dimension per topic | KiB |
122
-| pulsar.topic_storage_read_rate | a dimension per topic | message batches/s |
123
-| pulsar.topic_storage_write_rate | a dimension per topic | message batches/s |
124
-| pulsar.topic_msg_backlog | a dimension per topic | messages |
125
-| pulsar.topic_subscription_delayed | a dimension per topic | message batches |
126
-| pulsar.topic_subscription_msg_rate_redeliver | a dimension per topic | messages/s |
127
-| pulsar.topic_subscription_blocked_on_unacked_messages | a dimension per topic | blocked subscriptions |
128
-| pulsar.topic_replication_rate_in | a dimension per topic | messages/s |
129
-| pulsar.topic_replication_rate_out | a dimension per topic | messages/s |
130
-| pulsar.topic_replication_throughput_rate_in | a dimension per topic | messages/s |
131
-| pulsar.topic_replication_throughput_rate_out | a dimension per topic | messages/s |
132
-| pulsar.topic_replication_backlog | a dimension per topic | messages |
133
-
134
-
135
-
136
-## Alerts
137
-
138
-There are no alerts configured by default for this integration.
139
-
140
-
54
## Setup
55
56
@@ -298,6 +211,93 @@ jobs:
211
212
213
214
+## Alerts
215
+
216
+There are no alerts configured by default for this integration.
217
+
218
+
219
+## Metrics
220
+
221
+Metrics grouped by *scope*.
222
+
223
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
224
+
225
+- topic_* metrics are available when `exposeTopicLevelMetricsInPrometheus` is set to true.
226
+- subscription_* and namespace_subscription metrics are available when `exposeTopicLevelMetricsInPrometheus` si set to true.
227
+- replication_* and namespace_replication_* metrics are available when replication is configured and `replicationMetricsEnabled` is set to true.
228
+
229
+
230
+### Per Apache Pulsar instance
231
+
232
+These metrics refer to the entire monitored application.
233
+
234
+This scope has no labels.
235
+
236
+Metrics:
237
+
238
+| Metric | Dimensions | Unit |
239
+|:------|:----------|:----|
240
+| pulsar.broker_components | namespaces, topics, subscriptions, producers, consumers | components |
241
+| pulsar.messages_rate | publish, dispatch | messages/s |
242
+| pulsar.throughput_rate | publish, dispatch | KiB/s |
243
+| pulsar.storage_size | used | KiB |
244
+| pulsar.storage_operations_rate | read, write | message batches/s |
245
+| pulsar.msg_backlog | backlog | messages |
246
+| pulsar.storage_write_latency | <=0.5ms, <=1ms, <=5ms, =10ms, <=20ms, <=50ms, <=100ms, <=200ms, <=1s, >1s | entries/s |
247
+| pulsar.entry_size | <=128B, <=512B, <=1KB, <=2KB, <=4KB, <=16KB, <=100KB, <=1MB, >1MB | entries/s |
248
+| pulsar.subscription_delayed | delayed | message batches |
249
+| pulsar.subscription_msg_rate_redeliver | redelivered | messages/s |
250
+| pulsar.subscription_blocked_on_unacked_messages | blocked | subscriptions |
251
+| pulsar.replication_rate | in, out | messages/s |
252
+| pulsar.replication_throughput_rate | in, out | KiB/s |
253
+| pulsar.replication_backlog | backlog | messages |
254
+
255
+### Per namespace
256
+
257
+TBD
258
+
259
+This scope has no labels.
260
+
261
+Metrics:
262
+
263
+| Metric | Dimensions | Unit |
264
+|:------|:----------|:----|
265
+| pulsar.namespace_broker_components | topics, subscriptions, producers, consumers | components |
266
+| pulsar.namespace_messages_rate | publish, dispatch | messages/s |
267
+| pulsar.namespace_throughput_rate | publish, dispatch | KiB/s |
268
+| pulsar.namespace_storage_size | used | KiB |
269
+| pulsar.namespace_storage_operations_rate | read, write | message batches/s |
270
+| pulsar.namespace_msg_backlog | backlog | messages |
271
+| pulsar.namespace_storage_write_latency | <=0.5ms, <=1ms, <=5ms, =10ms, <=20ms, <=50ms, <=100ms, <=200ms, <=1s, >1s | entries/s |
272
+| pulsar.namespace_entry_size | <=128B, <=512B, <=1KB, <=2KB, <=4KB, <=16KB, <=100KB, <=1MB, >1MB | entries/s |
273
+| pulsar.namespace_subscription_delayed | delayed | message batches |
274
+| pulsar.namespace_subscription_msg_rate_redeliver | redelivered | messages/s |
275
+| pulsar.namespace_subscription_blocked_on_unacked_messages | blocked | subscriptions |
276
+| pulsar.namespace_replication_rate | in, out | messages/s |
277
+| pulsar.namespace_replication_throughput_rate | in, out | KiB/s |
278
+| pulsar.namespace_replication_backlog | backlog | messages |
279
+| pulsar.topic_producers | a dimension per topic | producers |
280
+| pulsar.topic_subscriptions | a dimension per topic | subscriptions |
281
+| pulsar.topic_consumers | a dimension per topic | consumers |
282
+| pulsar.topic_messages_rate_in | a dimension per topic | publishes/s |
283
+| pulsar.topic_messages_rate_out | a dimension per topic | dispatches/s |
284
+| pulsar.topic_throughput_rate_in | a dimension per topic | KiB/s |
285
+| pulsar.topic_throughput_rate_out | a dimension per topic | KiB/s |
286
+| pulsar.topic_storage_size | a dimension per topic | KiB |
287
+| pulsar.topic_storage_read_rate | a dimension per topic | message batches/s |
288
+| pulsar.topic_storage_write_rate | a dimension per topic | message batches/s |
289
+| pulsar.topic_msg_backlog | a dimension per topic | messages |
290
+| pulsar.topic_subscription_delayed | a dimension per topic | message batches |
291
+| pulsar.topic_subscription_msg_rate_redeliver | a dimension per topic | messages/s |
292
+| pulsar.topic_subscription_blocked_on_unacked_messages | a dimension per topic | blocked subscriptions |
293
+| pulsar.topic_replication_rate_in | a dimension per topic | messages/s |
294
+| pulsar.topic_replication_rate_out | a dimension per topic | messages/s |
295
+| pulsar.topic_replication_throughput_rate_in | a dimension per topic | messages/s |
296
+| pulsar.topic_replication_throughput_rate_out | a dimension per topic | messages/s |
297
+| pulsar.topic_replication_backlog | a dimension per topic | messages |
298
+
299
+
300
+
301
## Troubleshooting
302
303
### Debug Mode
src/go/plugin/go.d/collector/puppet/integrations/puppet.md
+30
-30
@@ -50,36 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Puppet instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| puppet.jvm_heap | committed, used | MiB |
72
-| puppet.jvm_nonheap | committed, used | MiB |
73
-| puppet.cpu | execution, GC | percentage |
74
-| puppet.fdopen | used | descriptors |
75
-
76
-
77
-
78
-## Alerts
79
-
80
-There are no alerts configured by default for this integration.
81
-
82
-
53
## Setup
54
55
@@ -215,6 +185,36 @@ jobs:
185
186
187
188
+## Alerts
189
+
190
+There are no alerts configured by default for this integration.
191
+
192
+
193
+## Metrics
194
+
195
+Metrics grouped by *scope*.
196
+
197
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
198
+
199
+
200
+
201
+### Per Puppet instance
202
+
203
+These metrics refer to the entire monitored application.
204
+
205
+This scope has no labels.
206
+
207
+Metrics:
208
+
209
+| Metric | Dimensions | Unit |
210
+|:------|:----------|:----|
211
+| puppet.jvm_heap | committed, used | MiB |
212
+| puppet.jvm_nonheap | committed, used | MiB |
213
+| puppet.cpu | execution, GC | percentage |
214
+| puppet.fdopen | used | descriptors |
215
+
216
+
217
+
218
## Troubleshooting
219
220
### Debug Mode
src/go/plugin/go.d/collector/rabbitmq/integrations/rabbitmq.md
+137
-137
@@ -54,143 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per cluster
66
-
67
-These metrics refer to the RabbitMQ Cluster.
68
-
69
-Labels:
70
-
71
-| Label | Description |
72
-|:-----------|:----------------|
73
-| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
74
-| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name`. If not set, it will be "unset". |
75
-
76
-Metrics:
77
-
78
-| Metric | Dimensions | Unit |
79
-|:------|:----------|:----|
80
-| rabbitmq.messages_count | ready, unacknowledged | messages |
81
-| rabbitmq.messages_rate | ack, publish, publish_in, publish_out, confirm, deliver, deliver_no_ack, get, get_empty, get_no_ack, deliver_get, redeliver, return_unroutable | messages/s |
82
-| rabbitmq.objects_count | channels, consumers, connections, queues, exchanges | messages |
83
-| rabbitmq.connection_churn_rate | created, closed | operations/s |
84
-| rabbitmq.channel_churn_rate | created, closed | operations/s |
85
-| rabbitmq.queue_churn_rate | created, deleted, declared | operations/s |
86
-
87
-### Per node
88
-
89
-These metrics refer to the RabbitMQ node.
90
-
91
-Labels:
92
-
93
-| Label | Description |
94
-|:-----------|:----------------|
95
-| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
96
-| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
97
-| node | Name of the node. |
98
-
99
-Metrics:
100
-
101
-| Metric | Dimensions | Unit |
102
-|:------|:----------|:----|
103
-| rabbitmq.node_avail_status | running, down | status |
104
-| rabbitmq.node_network_partition_status | clear, detected | status |
105
-| rabbitmq.node_mem_alarm_status | clear, triggered | status |
106
-| rabbitmq.node_disk_free_alarm_status | clear, triggered | status |
107
-| rabbitmq.node_file_descriptors_usage | used | fd |
108
-| rabbitmq.node_sockets_usage | used | sockets |
109
-| rabbitmq.node_erlang_processes_usage | used | processes |
110
-| rabbitmq.node_erlang_run_queue_processes_count | length | processes |
111
-| rabbitmq.node_memory_usage | used | bytes |
112
-| rabbitmq.node_disk_space_free_size | free | bytes |
113
-| rabbitmq.node_uptime | uptime | seconds |
114
-
115
-### Per cluster peer
116
-
117
-These metrics refer to the RabbiMQ cluster peer.
118
-
119
-Labels:
120
-
121
-| Label | Description |
122
-|:-----------|:----------------|
123
-| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
124
-| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
125
-| node | Name of the node. |
126
-| peer | Name of the remote node in the cluster. |
127
-
128
-Metrics:
129
-
130
-| Metric | Dimensions | Unit |
131
-|:------|:----------|:----|
132
-| rabbitmq.node_peer_cluster_link_traffic | received, sent | bytes/s |
133
-
134
-### Per vhost
135
-
136
-These metrics refer to the virtual host.
137
-
138
-Labels:
139
-
140
-| Label | Description |
141
-|:-----------|:----------------|
142
-| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
143
-| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
144
-| vhost | Name of the virtual host. |
145
-
146
-Metrics:
147
-
148
-| Metric | Dimensions | Unit |
149
-|:------|:----------|:----|
150
-| rabbitmq.vhost_status | running, stopped, partial | status |
151
-| rabbitmq.vhost_messages_count | ready, unacknowledged | messages |
152
-| rabbitmq.vhost_messages_rate | ack, publish, publish_in, publish_out, confirm, deliver, deliver_no_ack, get, get_no_ack, deliver_get, redeliver, return_unroutable | messages/s |
153
-
154
-### Per queue
155
-
156
-These metrics refer to the virtual host queue.
157
-
158
-Labels:
159
-
160
-| Label | Description |
161
-|:-----------|:----------------|
162
-| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
163
-| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
164
-| node | Name of the node. |
165
-| vhost | Name of the virtual host. |
166
-| queue | Name of the queue. |
167
-
168
-Metrics:
169
-
170
-| Metric | Dimensions | Unit |
171
-|:------|:----------|:----|
172
-| rabbitmq.queue_status | running, down, idle, crashed, stopped, minority, terminated | status |
173
-| rabbitmq.queue_messages_count | ready, unacknowledged, paged_out, persistent | messages |
174
-| rabbitmq.queue_messages_rate | ack, publish, publish_in, publish_out, confirm, deliver, deliver_no_ack, get, get_no_ack, deliver_get, redeliver, return_unroutable | messages/s |
175
-
176
-
177
-
178
-## Alerts
179
-
180
-
181
-The following alerts are available:
182
-
183
-| Alert name | On metric | Description |
184
-|:------------|:----------|:------------|
185
-| [ rabbitmq_node_avail_status_down ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_avail_status | RabbitMQ node is down (node ${label:node} cluster ${label:cluster_id}) |
186
-| [ rabbitmq_node_network_partition_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_network_partition_status | RabbitMQ network partition detected (node ${label:node} cluster ${label:cluster_id}) |
187
-| [ rabbitmq_node_mem_alarm_status_triggered ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_mem_alarm_status | RabbitMQ mem alarm triggered (node ${label:node} cluster ${label:cluster_id}) |
188
-| [ rabbitmq.node_disk_free_alarm_status_triggered ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_disk_free_alarm_status | RabbitMQ disk free alarm triggered (node ${label:node} cluster ${label:cluster_id}) |
189
-| [ rabbitmq_vhost_status_unhealthy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.vhost_status | RabbitMQ vhost is not healthy (vhost ${label:vhost} cluster ${label:cluster_id}) |
190
-| [ rabbitmq_queue_status_minority ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.queue_status | RabbitMQ queue insufficient online members (queue ${label:queue} node ${label:node} cluster ${label:cluster_id}) |
191
-| [ rabbitmq_queue_status_unhealthy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.queue_status | RabbitMQ queue is unhealthy (queue ${label:queue} node ${label:node} cluster ${label:cluster_id}) |
192
-
193
-
57
## Setup
58
59
@@ -345,6 +208,143 @@ jobs:
208
209
210
211
+## Alerts
212
+
213
+
214
+The following alerts are available:
215
+
216
+| Alert name | On metric | Description |
217
+|:------------|:----------|:------------|
218
+| [ rabbitmq_node_avail_status_down ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_avail_status | RabbitMQ node is down (node ${label:node} cluster ${label:cluster_id}) |
219
+| [ rabbitmq_node_network_partition_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_network_partition_status | RabbitMQ network partition detected (node ${label:node} cluster ${label:cluster_id}) |
220
+| [ rabbitmq_node_mem_alarm_status_triggered ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_mem_alarm_status | RabbitMQ mem alarm triggered (node ${label:node} cluster ${label:cluster_id}) |
221
+| [ rabbitmq.node_disk_free_alarm_status_triggered ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.node_disk_free_alarm_status | RabbitMQ disk free alarm triggered (node ${label:node} cluster ${label:cluster_id}) |
222
+| [ rabbitmq_vhost_status_unhealthy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.vhost_status | RabbitMQ vhost is not healthy (vhost ${label:vhost} cluster ${label:cluster_id}) |
223
+| [ rabbitmq_queue_status_minority ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.queue_status | RabbitMQ queue insufficient online members (queue ${label:queue} node ${label:node} cluster ${label:cluster_id}) |
224
+| [ rabbitmq_queue_status_unhealthy ](https://github.com/netdata/netdata/blob/master/src/health/health.d/rabbitmq.conf) | rabbitmq.queue_status | RabbitMQ queue is unhealthy (queue ${label:queue} node ${label:node} cluster ${label:cluster_id}) |
225
+
226
+
227
+## Metrics
228
+
229
+Metrics grouped by *scope*.
230
+
231
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
232
+
233
+
234
+
235
+### Per cluster
236
+
237
+These metrics refer to the RabbitMQ Cluster.
238
+
239
+Labels:
240
+
241
+| Label | Description |
242
+|:-----------|:----------------|
243
+| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
244
+| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name`. If not set, it will be "unset". |
245
+
246
+Metrics:
247
+
248
+| Metric | Dimensions | Unit |
249
+|:------|:----------|:----|
250
+| rabbitmq.messages_count | ready, unacknowledged | messages |
251
+| rabbitmq.messages_rate | ack, publish, publish_in, publish_out, confirm, deliver, deliver_no_ack, get, get_empty, get_no_ack, deliver_get, redeliver, return_unroutable | messages/s |
252
+| rabbitmq.objects_count | channels, consumers, connections, queues, exchanges | messages |
253
+| rabbitmq.connection_churn_rate | created, closed | operations/s |
254
+| rabbitmq.channel_churn_rate | created, closed | operations/s |
255
+| rabbitmq.queue_churn_rate | created, deleted, declared | operations/s |
256
+
257
+### Per node
258
+
259
+These metrics refer to the RabbitMQ node.
260
+
261
+Labels:
262
+
263
+| Label | Description |
264
+|:-----------|:----------------|
265
+| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
266
+| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
267
+| node | Name of the node. |
268
+
269
+Metrics:
270
+
271
+| Metric | Dimensions | Unit |
272
+|:------|:----------|:----|
273
+| rabbitmq.node_avail_status | running, down | status |
274
+| rabbitmq.node_network_partition_status | clear, detected | status |
275
+| rabbitmq.node_mem_alarm_status | clear, triggered | status |
276
+| rabbitmq.node_disk_free_alarm_status | clear, triggered | status |
277
+| rabbitmq.node_file_descriptors_usage | used | fd |
278
+| rabbitmq.node_sockets_usage | used | sockets |
279
+| rabbitmq.node_erlang_processes_usage | used | processes |
280
+| rabbitmq.node_erlang_run_queue_processes_count | length | processes |
281
+| rabbitmq.node_memory_usage | used | bytes |
282
+| rabbitmq.node_disk_space_free_size | free | bytes |
283
+| rabbitmq.node_uptime | uptime | seconds |
284
+
285
+### Per cluster peer
286
+
287
+These metrics refer to the RabbiMQ cluster peer.
288
+
289
+Labels:
290
+
291
+| Label | Description |
292
+|:-----------|:----------------|
293
+| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
294
+| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
295
+| node | Name of the node. |
296
+| peer | Name of the remote node in the cluster. |
297
+
298
+Metrics:
299
+
300
+| Metric | Dimensions | Unit |
301
+|:------|:----------|:----|
302
+| rabbitmq.node_peer_cluster_link_traffic | received, sent | bytes/s |
303
+
304
+### Per vhost
305
+
306
+These metrics refer to the virtual host.
307
+
308
+Labels:
309
+
310
+| Label | Description |
311
+|:-----------|:----------------|
312
+| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
313
+| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
314
+| vhost | Name of the virtual host. |
315
+
316
+Metrics:
317
+
318
+| Metric | Dimensions | Unit |
319
+|:------|:----------|:----|
320
+| rabbitmq.vhost_status | running, stopped, partial | status |
321
+| rabbitmq.vhost_messages_count | ready, unacknowledged | messages |
322
+| rabbitmq.vhost_messages_rate | ack, publish, publish_in, publish_out, confirm, deliver, deliver_no_ack, get, get_no_ack, deliver_get, redeliver, return_unroutable | messages/s |
323
+
324
+### Per queue
325
+
326
+These metrics refer to the virtual host queue.
327
+
328
+Labels:
329
+
330
+| Label | Description |
331
+|:-----------|:----------------|
332
+| cluster_id | Unique identifier for the cluster, automatically assigned by RabbitMQ. |
333
+| cluster_name | User-defined name of the cluster as set using `rabbitmqctl set_cluster_name <NAME>`. If not set, it will be "unset". |
334
+| node | Name of the node. |
335
+| vhost | Name of the virtual host. |
336
+| queue | Name of the queue. |
337
+
338
+Metrics:
339
+
340
+| Metric | Dimensions | Unit |
341
+|:------|:----------|:----|
342
+| rabbitmq.queue_status | running, down, idle, crashed, stopped, minority, terminated | status |
343
+| rabbitmq.queue_messages_count | ready, unacknowledged, paged_out, persistent | messages |
344
+| rabbitmq.queue_messages_rate | ack, publish, publish_in, publish_out, confirm, deliver, deliver_no_ack, get, get_no_ack, deliver_get, redeliver, return_unroutable | messages/s |
345
+
346
+
347
+
348
## Troubleshooting
349
350
### Debug Mode
src/go/plugin/go.d/collector/redis/integrations/redis.md
+112
-112
@@ -60,118 +60,6 @@ The default configuration for this integration does not impose any limits on dat
60
61
The default configuration for this integration is not expected to impose a significant performance impact on the system.
62
63
-## Metrics
64
-
65
-Metrics grouped by *scope*.
66
-
67
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
68
-
69
-
70
-
71
-### Per Redis instance
72
-
73
-These metrics refer to the entire monitored application.
74
-
75
-This scope has no labels.
76
-
77
-Metrics:
78
-
79
-| Metric | Dimensions | Unit |
80
-|:------|:----------|:----|
81
-| redis.connections | accepted, rejected | connections/s |
82
-| redis.clients | connected, blocked, tracking, in_timeout_table | clients |
83
-| redis.ping_latency | min, max, avg | seconds |
84
-| redis.commands | processes | commands/s |
85
-| redis.keyspace_lookup_hit_rate | lookup_hit_rate | percentage |
86
-| redis.memory | max, used, rss, peak, dataset, lua, scripts | bytes |
87
-| redis.mem_fragmentation_ratio | mem_fragmentation | ratio |
88
-| redis.key_eviction_events | evicted | keys/s |
89
-| redis.net | received, sent | kilobits/s |
90
-| redis.rdb_changes | changes | operations |
91
-| redis.bgsave_now | current_bgsave_time | seconds |
92
-| redis.bgsave_health | last_bgsave | status |
93
-| redis.bgsave_last_rdb_save_since_time | last_bgsave_time | seconds |
94
-| redis.aof_file_size | current, base | bytes |
95
-| redis.commands_calls | a dimension per command | calls |
96
-| redis.commands_usec | a dimension per command | microseconds |
97
-| redis.commands_usec_per_sec | a dimension per command | microseconds/s |
98
-| redis.key_expiration_events | expired | keys/s |
99
-| redis.database_keys | a dimension per database | keys |
100
-| redis.database_expires_keys | a dimension per database | keys |
101
-| redis.connected_replicas | connected | replicas |
102
-| redis.master_link_status | up, down | status |
103
-| redis.master_last_io_since_time | time | seconds |
104
-| redis.master_link_down_since_time | time | seconds |
105
-| redis.uptime | uptime | seconds |
106
-
107
-
108
-
109
-## Functions
110
-
111
-This collector exposes real-time functions for interactive troubleshooting in the Live tab.
112
-
113
-
114
-### Top Queries
115
-
116
-Retrieves slow command entries from Redis [SLOWLOG](https://redis.io/docs/latest/commands/slowlog/).
117
-
118
-This function executes the `SLOWLOG GET` command to retrieve entries of commands that exceeded the configured execution time threshold (`slowlog-log-slower-than`). It provides command details, execution duration, and client information for each slow command.
119
-
120
-Use cases:
121
-- Identify slow commands that may need optimization
122
-- Analyze command patterns to detect performance hotspots
123
-- Investigate client sources of slow commands
124
-
125
-Command text is truncated at 4096 characters for display purposes.
126
-
127
-
128
-| Aspect | Description |
129
-|:-------|:------------|
130
-| Name | `Redis:top-queries` |
131
-| Require Cloud | yes |
132
-| Performance | Executes `SLOWLOG GET` command to retrieve entries from Redis memory:<br/>• Minimal overhead as SLOWLOG is stored in memory<br/>• Default limit of 500 entries balances completeness with performance<br/>• Large slowlogs with many entries may take slightly longer to transfer |
133
-| Security | Command arguments may contain unmasked literal values including potentially sensitive data:<br/>• Redis keys and values in command arguments<br/>• Application-specific identifiers or session tokens<br/>• Access should be restricted to authorized personnel only |
134
-| Availability | Available when:<br/>• The collector has successfully connected to Redis<br/>• SLOWLOG is enabled (`slowlog-log-slower-than` > 0)<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the command fails<br/>• Returns HTTP 504 if the command times out |
135
-
136
-#### Prerequisites
137
-
138
-No additional configuration is required.
139
-
140
-#### Parameters
141
-
142
-| Parameter | Type | Description | Required | Default | Options |
143
-|:---------|:-----|:------------|:--------:|:--------|:--------|
144
-| Filter By | select | Select the primary sort column. Options include duration, timestamp, ID, and command name. Defaults to duration to focus on slowest commands. | yes | duration | |
145
-
146
-#### Returns
147
-
148
-Slowlog entries with command timing and client metadata, providing insight into Redis performance patterns. Each row represents a single slow command execution that exceeded the configured threshold.
149
-
150
-| Column | Type | Unit | Visibility | Description |
151
-|:-------|:-----|:-----|:-----------|:------------|
152
-| ID | integer | | hidden | Unique identifier for the slowlog entry. Allows tracking individual command executions. |
153
-| Timestamp | timestamp | | | Date and time when the slow command was executed. Useful for correlating slow commands with application events or system changes. |
154
-| Command | string | | | Full command text including all arguments. May contain sensitive data (keys, values) depending on application implementation. Truncated to 4096 characters. |
155
-| Command Name | string | | | The Redis command name (e.g., SET, GET, HGETALL, ZADD). Useful for grouping and analyzing slow commands by type. |
156
-| Duration | duration | milliseconds | | Execution time that exceeded the slowlog threshold. Higher values indicate slower commands that may need optimization or investigation. |
157
-| Client Address | string | | hidden | IP address of the client that executed the slow command. Useful for identifying problematic clients or network segments. |
158
-| Client Name | string | | hidden | Client identifier or name reported by Redis. Useful for identifying specific applications or services generating slow commands. |
159
-
160
-
161
-
162
-## Alerts
163
-
164
-
165
-The following alerts are available:
166
-
167
-| Alert name | On metric | Description |
168
-|:------------|:----------|:------------|
169
-| [ redis_connections_rejected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.connections | connections rejected because of maxclients limit in the last minute |
170
-| [ redis_bgsave_slow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.bgsave_now | duration of the on-going RDB save operation |
171
-| [ redis_bgsave_broken ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.bgsave_health | status of the last RDB save operation (0: ok, 1: error) |
172
-| [ redis_master_link_down ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.master_link_down_since_time | time elapsed since the link between master and slave is down |
173
-
174
-
63
## Setup
64
65
@@ -326,6 +214,118 @@ jobs:
214
215
216
217
+## Alerts
218
+
219
+
220
+The following alerts are available:
221
+
222
+| Alert name | On metric | Description |
223
+|:------------|:----------|:------------|
224
+| [ redis_connections_rejected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.connections | connections rejected because of maxclients limit in the last minute |
225
+| [ redis_bgsave_slow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.bgsave_now | duration of the on-going RDB save operation |
226
+| [ redis_bgsave_broken ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.bgsave_health | status of the last RDB save operation (0: ok, 1: error) |
227
+| [ redis_master_link_down ](https://github.com/netdata/netdata/blob/master/src/health/health.d/redis.conf) | redis.master_link_down_since_time | time elapsed since the link between master and slave is down |
228
+
229
+
230
+## Metrics
231
+
232
+Metrics grouped by *scope*.
233
+
234
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
235
+
236
+
237
+
238
+### Per Redis instance
239
+
240
+These metrics refer to the entire monitored application.
241
+
242
+This scope has no labels.
243
+
244
+Metrics:
245
+
246
+| Metric | Dimensions | Unit |
247
+|:------|:----------|:----|
248
+| redis.connections | accepted, rejected | connections/s |
249
+| redis.clients | connected, blocked, tracking, in_timeout_table | clients |
250
+| redis.ping_latency | min, max, avg | seconds |
251
+| redis.commands | processes | commands/s |
252
+| redis.keyspace_lookup_hit_rate | lookup_hit_rate | percentage |
253
+| redis.memory | max, used, rss, peak, dataset, lua, scripts | bytes |
254
+| redis.mem_fragmentation_ratio | mem_fragmentation | ratio |
255
+| redis.key_eviction_events | evicted | keys/s |
256
+| redis.net | received, sent | kilobits/s |
257
+| redis.rdb_changes | changes | operations |
258
+| redis.bgsave_now | current_bgsave_time | seconds |
259
+| redis.bgsave_health | last_bgsave | status |
260
+| redis.bgsave_last_rdb_save_since_time | last_bgsave_time | seconds |
261
+| redis.aof_file_size | current, base | bytes |
262
+| redis.commands_calls | a dimension per command | calls |
263
+| redis.commands_usec | a dimension per command | microseconds |
264
+| redis.commands_usec_per_sec | a dimension per command | microseconds/s |
265
+| redis.key_expiration_events | expired | keys/s |
266
+| redis.database_keys | a dimension per database | keys |
267
+| redis.database_expires_keys | a dimension per database | keys |
268
+| redis.connected_replicas | connected | replicas |
269
+| redis.master_link_status | up, down | status |
270
+| redis.master_last_io_since_time | time | seconds |
271
+| redis.master_link_down_since_time | time | seconds |
272
+| redis.uptime | uptime | seconds |
273
+
274
+
275
+
276
+## Live Data
277
+
278
+This collector exposes real-time functions for interactive troubleshooting in the Live tab.
279
+
280
+
281
+### Top Queries
282
+
283
+Retrieves slow command entries from Redis [SLOWLOG](https://redis.io/docs/latest/commands/slowlog/).
284
+
285
+This function executes the `SLOWLOG GET` command to retrieve entries of commands that exceeded the configured execution time threshold (`slowlog-log-slower-than`). It provides command details, execution duration, and client information for each slow command.
286
+
287
+Use cases:
288
+- Identify slow commands that may need optimization
289
+- Analyze command patterns to detect performance hotspots
290
+- Investigate client sources of slow commands
291
+
292
+Command text is truncated at 4096 characters for display purposes.
293
+
294
+
295
+| Aspect | Description |
296
+|:-------|:------------|
297
+| Name | `Redis:top-queries` |
298
+| Require Cloud | yes |
299
+| Performance | Executes `SLOWLOG GET` command to retrieve entries from Redis memory:<br/>• Minimal overhead as SLOWLOG is stored in memory<br/>• Default limit of 500 entries balances completeness with performance<br/>• Large slowlogs with many entries may take slightly longer to transfer |
300
+| Security | Command arguments may contain unmasked literal values including potentially sensitive data:<br/>• Redis keys and values in command arguments<br/>• Application-specific identifiers or session tokens<br/>• Access should be restricted to authorized personnel only |
301
+| Availability | Available when:<br/>• The collector has successfully connected to Redis<br/>• SLOWLOG is enabled (`slowlog-log-slower-than` > 0)<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the command fails<br/>• Returns HTTP 504 if the command times out |
302
+
303
+#### Prerequisites
304
+
305
+No additional configuration is required.
306
+
307
+#### Parameters
308
+
309
+| Parameter | Type | Description | Required | Default | Options |
310
+|:---------|:-----|:------------|:--------:|:--------|:--------|
311
+| Filter By | select | Select the primary sort column. Options include duration, timestamp, ID, and command name. Defaults to duration to focus on slowest commands. | yes | duration | |
312
+
313
+#### Returns
314
+
315
+Slowlog entries with command timing and client metadata, providing insight into Redis performance patterns. Each row represents a single slow command execution that exceeded the configured threshold.
316
+
317
+| Column | Type | Unit | Visibility | Description |
318
+|:-------|:-----|:-----|:-----------|:------------|
319
+| ID | integer | | hidden | Unique identifier for the slowlog entry. Allows tracking individual command executions. |
320
+| Timestamp | timestamp | | | Date and time when the slow command was executed. Useful for correlating slow commands with application events or system changes. |
321
+| Command | string | | | Full command text including all arguments. May contain sensitive data (keys, values) depending on application implementation. Truncated to 4096 characters. |
322
+| Command Name | string | | | The Redis command name (e.g., SET, GET, HGETALL, ZADD). Useful for grouping and analyzing slow commands by type. |
323
+| Duration | duration | milliseconds | | Execution time that exceeded the slowlog threshold. Higher values indicate slower commands that may need optimization or investigation. |
324
+| Client Address | string | | hidden | IP address of the client that executed the slow command. Useful for identifying problematic clients or network segments. |
325
+| Client Name | string | | hidden | Client identifier or name reported by Redis. Useful for identifying specific applications or services generating slow commands. |
326
+
327
+
328
+
329
## Troubleshooting
330
331
### Debug Mode
src/go/plugin/go.d/collector/rethinkdb/integrations/rethinkdb.md
+126
-126
@@ -49,132 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per RethinkDB instance
61
-
62
-These metrics refer to the entire monitored application.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| rethinkdb.cluster_servers_stats_request | success, timeout | servers |
71
-| rethinkdb.cluster_client_connections | connections | connections |
72
-| rethinkdb.cluster_active_clients | active | clients |
73
-| rethinkdb.cluster_queries | queries | queries/s |
74
-| rethinkdb.cluster_documents | read, written | documents/s |
75
-
76
-### Per server
77
-
78
-These metrics refer to the server (cluster member).
79
-
80
-Labels:
81
-
82
-| Label | Description |
83
-|:-----------|:----------------|
84
-| server_uuid | Server UUID. |
85
-| server_name | Server name. |
86
-
87
-Metrics:
88
-
89
-| Metric | Dimensions | Unit |
90
-|:------|:----------|:----|
91
-| rethinkdb.server_stats_request_status | success, timeout | status |
92
-| rethinkdb.server_client_connections | connections | connections |
93
-| rethinkdb.server_active_clients | active | clients |
94
-| rethinkdb.server_queries | queries | queries/s |
95
-| rethinkdb.server_documents | read, written | documents/s |
96
-
97
-
98
-
99
-## Functions
100
-
101
-This collector exposes real-time functions for interactive troubleshooting in the Live tab.
102
-
103
-
104
-### Running Queries
105
-
106
-Retrieves currently executing queries from the RethinkDB [rethinkdb.jobs](https://rethinkdb.com/docs/system-jobs/) system table.
107
-
108
-This function queries the `rethinkdb.jobs` system table which contains information about background tasks and queries currently running on the cluster. It provides query text, execution duration, client information, and involved servers.
109
-
110
-Use cases:
111
-- Identify long-running queries that may be blocking resources
112
-- Monitor active query load across the cluster
113
-- Investigate client connections generating heavy workloads
114
-
115
-Query text is truncated at 4096 characters for display purposes.
116
-
117
-
118
-| Aspect | Description |
119
-|:-------|:------------|
120
-| Name | `Rethinkdb:running-queries` |
121
-| Require Cloud | yes |
122
-| Performance | Queries the `rethinkdb.jobs` system table:<br/>• Minimal overhead as it reads from an in-memory system table<br/>• Default limit of 500 rows balances completeness with performance<br/>• Returns only currently active queries (no historical data) |
123
-| Security | Query text may contain unmasked literal values including potentially sensitive data:<br/>• Document field values in filter conditions<br/>• User-provided data in insert/update operations<br/>• Access should be restricted to authorized personnel only |
124
-| Availability | Available when:<br/>• The collector has successfully connected to RethinkDB<br/>• The user has admin access to `rethinkdb.jobs` table<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the query fails<br/>• Returns HTTP 504 if the query times out |
125
-
126
-#### Prerequisites
127
-
128
-##### Grant admin access to `rethinkdb.jobs`
129
-
130
-The user must have admin privileges to query the `rethinkdb.jobs` system table.
131
-
132
-1. Connect with an admin user account that has access to system tables
133
-
134
-2. Verify access to `rethinkdb.jobs`:
135
-
136
- ```javascript
137
- r.db('rethinkdb').table('jobs').run(conn)
138
- ```
139
-
140
-:::info
141
-
142
-- The `rethinkdb.jobs` table is only accessible to admin users
143
-- Non-admin users will receive a permission error when attempting to query this table
144
-- The collector's regular metrics do not require admin access
145
-
146
-:::
147
-
148
-
149
-
150
-#### Parameters
151
-
152
-| Parameter | Type | Description | Required | Default | Options |
153
-|:---------|:-----|:------------|:--------:|:--------|:--------|
154
-| Filter By | select | Select the primary sort column. Defaults to duration to focus on longest-running queries. | yes | durationMs | |
155
-
156
-#### Returns
157
-
158
-Currently running queries from the `rethinkdb.jobs` system table. Each row represents a single active query with its execution context.
159
-
160
-| Column | Type | Unit | Visibility | Description |
161
-|:-------|:-----|:-----|:-----------|:------------|
162
-| Job ID | string | | hidden | Unique identifier for the job entry. Can be used to track or kill specific queries. |
163
-| Query | string | | | The ReQL query text being executed. Truncated to 4096 characters. May contain literal values from application code. |
164
-| Duration | duration | milliseconds | | Time elapsed since the query started executing. High values indicate long-running queries that may need investigation. |
165
-| Type | string | | | Job type (e.g., query, index_construction, disk_compaction). Useful for distinguishing user queries from background tasks. |
166
-| User | string | | | RethinkDB user account that initiated the query. Useful for identifying workload by user or application. |
167
-| Client Address | string | | hidden | IP address of the client connection that submitted the query. |
168
-| Client Port | integer | | hidden | Port number of the client connection. |
169
-| Servers | string | | hidden | Comma-separated list of servers involved in executing this query. |
170
-
171
-
172
-
173
-## Alerts
174
-
175
-There are no alerts configured by default for this integration.
176
-
177
-
52
## Setup
53
54
@@ -313,6 +187,132 @@ jobs:
187
188
189
190
+## Alerts
191
+
192
+There are no alerts configured by default for this integration.
193
+
194
+
195
+## Metrics
196
+
197
+Metrics grouped by *scope*.
198
+
199
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
200
+
201
+
202
+
203
+### Per RethinkDB instance
204
+
205
+These metrics refer to the entire monitored application.
206
+
207
+This scope has no labels.
208
+
209
+Metrics:
210
+
211
+| Metric | Dimensions | Unit |
212
+|:------|:----------|:----|
213
+| rethinkdb.cluster_servers_stats_request | success, timeout | servers |
214
+| rethinkdb.cluster_client_connections | connections | connections |
215
+| rethinkdb.cluster_active_clients | active | clients |
216
+| rethinkdb.cluster_queries | queries | queries/s |
217
+| rethinkdb.cluster_documents | read, written | documents/s |
218
+
219
+### Per server
220
+
221
+These metrics refer to the server (cluster member).
222
+
223
+Labels:
224
+
225
+| Label | Description |
226
+|:-----------|:----------------|
227
+| server_uuid | Server UUID. |
228
+| server_name | Server name. |
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| rethinkdb.server_stats_request_status | success, timeout | status |
235
+| rethinkdb.server_client_connections | connections | connections |
236
+| rethinkdb.server_active_clients | active | clients |
237
+| rethinkdb.server_queries | queries | queries/s |
238
+| rethinkdb.server_documents | read, written | documents/s |
239
+
240
+
241
+
242
+## Live Data
243
+
244
+This collector exposes real-time functions for interactive troubleshooting in the Live tab.
245
+
246
+
247
+### Running Queries
248
+
249
+Retrieves currently executing queries from the RethinkDB [rethinkdb.jobs](https://rethinkdb.com/docs/system-jobs/) system table.
250
+
251
+This function queries the `rethinkdb.jobs` system table which contains information about background tasks and queries currently running on the cluster. It provides query text, execution duration, client information, and involved servers.
252
+
253
+Use cases:
254
+- Identify long-running queries that may be blocking resources
255
+- Monitor active query load across the cluster
256
+- Investigate client connections generating heavy workloads
257
+
258
+Query text is truncated at 4096 characters for display purposes.
259
+
260
+
261
+| Aspect | Description |
262
+|:-------|:------------|
263
+| Name | `Rethinkdb:running-queries` |
264
+| Require Cloud | yes |
265
+| Performance | Queries the `rethinkdb.jobs` system table:<br/>• Minimal overhead as it reads from an in-memory system table<br/>• Default limit of 500 rows balances completeness with performance<br/>• Returns only currently active queries (no historical data) |
266
+| Security | Query text may contain unmasked literal values including potentially sensitive data:<br/>• Document field values in filter conditions<br/>• User-provided data in insert/update operations<br/>• Access should be restricted to authorized personnel only |
267
+| Availability | Available when:<br/>• The collector has successfully connected to RethinkDB<br/>• The user has admin access to `rethinkdb.jobs` table<br/>• Returns HTTP 503 if collector is still initializing<br/>• Returns HTTP 500 if the query fails<br/>• Returns HTTP 504 if the query times out |
268
+
269
+#### Prerequisites
270
+
271
+##### Grant admin access to `rethinkdb.jobs`
272
+
273
+The user must have admin privileges to query the `rethinkdb.jobs` system table.
274
+
275
+1. Connect with an admin user account that has access to system tables
276
+
277
+2. Verify access to `rethinkdb.jobs`:
278
+
279
+ ```javascript
280
+ r.db('rethinkdb').table('jobs').run(conn)
281
+ ```
282
+
283
+:::info
284
+
285
+- The `rethinkdb.jobs` table is only accessible to admin users
286
+- Non-admin users will receive a permission error when attempting to query this table
287
+- The collector's regular metrics do not require admin access
288
+
289
+:::
290
+
291
+
292
+
293
+#### Parameters
294
+
295
+| Parameter | Type | Description | Required | Default | Options |
296
+|:---------|:-----|:------------|:--------:|:--------|:--------|
297
+| Filter By | select | Select the primary sort column. Defaults to duration to focus on longest-running queries. | yes | durationMs | |
298
+
299
+#### Returns
300
+
301
+Currently running queries from the `rethinkdb.jobs` system table. Each row represents a single active query with its execution context.
302
+
303
+| Column | Type | Unit | Visibility | Description |
304
+|:-------|:-----|:-----|:-----------|:------------|
305
+| Job ID | string | | hidden | Unique identifier for the job entry. Can be used to track or kill specific queries. |
306
+| Query | string | | | The ReQL query text being executed. Truncated to 4096 characters. May contain literal values from application code. |
307
+| Duration | duration | milliseconds | | Time elapsed since the query started executing. High values indicate long-running queries that may need investigation. |
308
+| Type | string | | | Job type (e.g., query, index_construction, disk_compaction). Useful for distinguishing user queries from background tasks. |
309
+| User | string | | | RethinkDB user account that initiated the query. Useful for identifying workload by user or application. |
310
+| Client Address | string | | hidden | IP address of the client connection that submitted the query. |
311
+| Client Port | integer | | hidden | Port number of the client connection. |
312
+| Servers | string | | hidden | Comma-separated list of servers involved in executing this query. |
313
+
314
+
315
+
316
## Troubleshooting
317
318
### Debug Mode
src/go/plugin/go.d/collector/riakkv/integrations/riak_kv.md
+50
-50
@@ -50,56 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Riak KV instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| riak.kv.throughput | gets, puts | operations/s |
72
-| riak.dt.vnode_updates | counters, sets, maps | operations/s |
73
-| riak.search | queries | queries/s |
74
-| riak.search.documents | indexed | documents/s |
75
-| riak.consistent.operations | gets, puts | operations/s |
76
-| riak.kv.latency.get | mean, median, 95, 99, 100 | ms |
77
-| riak.kv.latency.put | mean, median, 95, 99, 100 | ms |
78
-| riak.dt.latency.counter_merge | mean, median, 95, 99, 100 | ms |
79
-| riak.dt.latency.set_merge | mean, median, 95, 99, 100 | ms |
80
-| riak.dt.latency.map_merge | mean, median, 95, 99, 100 | ms |
81
-| riak.search.latency.query | median, min, 95, 99, 999, max | ms |
82
-| riak.search.latency.index | median, min, 95, 99, 999, max | ms |
83
-| riak.consistent.latency.get | mean, median, 95, 99, 100 | ms |
84
-| riak.consistent.latency.put | mean, median, 95, 99, 100 | ms |
85
-| riak.vm | processes | total |
86
-| riak.vm.memory.processes | allocated, used | MB |
87
-| riak.kv.siblings_encountered.get | mean, median, 95, 99, 100 | siblings |
88
-| riak.kv.objsize.get | mean, median, 95, 99, 100 | KB |
89
-| riak.search.vnodeq_size | mean, median, 95, 99, 100 | messages |
90
-| riak.search.index | index_fail, bad_entry, extract_fail | errors |
91
-| riak.core.protobuf_connections | active | connections |
92
-| riak.core.repairs | read | repairs |
93
-| riak.core.fsm_active | get, put, secondary index, list keys | fsms |
94
-| riak.core.fsm_rejected | get, put | fsms |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-There are no alerts configured by default for this integration.
101
-
102
-
53
## Setup
54
55
@@ -263,6 +213,56 @@ jobs:
213
214
215
216
+## Alerts
217
+
218
+There are no alerts configured by default for this integration.
219
+
220
+
221
+## Metrics
222
+
223
+Metrics grouped by *scope*.
224
+
225
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
226
+
227
+
228
+
229
+### Per Riak KV instance
230
+
231
+These metrics refer to the entire monitored application.
232
+
233
+This scope has no labels.
234
+
235
+Metrics:
236
+
237
+| Metric | Dimensions | Unit |
238
+|:------|:----------|:----|
239
+| riak.kv.throughput | gets, puts | operations/s |
240
+| riak.dt.vnode_updates | counters, sets, maps | operations/s |
241
+| riak.search | queries | queries/s |
242
+| riak.search.documents | indexed | documents/s |
243
+| riak.consistent.operations | gets, puts | operations/s |
244
+| riak.kv.latency.get | mean, median, 95, 99, 100 | ms |
245
+| riak.kv.latency.put | mean, median, 95, 99, 100 | ms |
246
+| riak.dt.latency.counter_merge | mean, median, 95, 99, 100 | ms |
247
+| riak.dt.latency.set_merge | mean, median, 95, 99, 100 | ms |
248
+| riak.dt.latency.map_merge | mean, median, 95, 99, 100 | ms |
249
+| riak.search.latency.query | median, min, 95, 99, 999, max | ms |
250
+| riak.search.latency.index | median, min, 95, 99, 999, max | ms |
251
+| riak.consistent.latency.get | mean, median, 95, 99, 100 | ms |
252
+| riak.consistent.latency.put | mean, median, 95, 99, 100 | ms |
253
+| riak.vm | processes | total |
254
+| riak.vm.memory.processes | allocated, used | MB |
255
+| riak.kv.siblings_encountered.get | mean, median, 95, 99, 100 | siblings |
256
+| riak.kv.objsize.get | mean, median, 95, 99, 100 | KB |
257
+| riak.search.vnodeq_size | mean, median, 95, 99, 100 | messages |
258
+| riak.search.index | index_fail, bad_entry, extract_fail | errors |
259
+| riak.core.protobuf_connections | active | connections |
260
+| riak.core.repairs | read | repairs |
261
+| riak.core.fsm_active | get, put, secondary index, list keys | fsms |
262
+| riak.core.fsm_rejected | get, put | fsms |
263
+
264
+
265
+
266
## Troubleshooting
267
268
### Debug Mode
src/go/plugin/go.d/collector/rspamd/integrations/rspamd.md
+32
-32
@@ -52,38 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
The default configuration for this integration is not expected to impose a significant performance impact on the system.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per Rspamd instance
64
-
65
-These metrics refer to the entire monitored application.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| rspamd.classifications | ham, spam | messages/s |
74
-| rspamd.actions | reject, soft_reject, rewrite_subject, add_header, greylist, custom, discard, quarantine, no_action | messages/s |
75
-| rspamd.scans | scanned | messages/s |
76
-| rspamd.learns | learned | messages/s |
77
-| rspamd.connections | connections | connections/s |
78
-| rspamd.control_connections | control_connections | connections/s |
79
-
80
-
81
-
82
-## Alerts
83
-
84
-There are no alerts configured by default for this integration.
85
-
86
-
55
## Setup
56
57
@@ -228,6 +196,38 @@ jobs:
196
197
198
199
+## Alerts
200
+
201
+There are no alerts configured by default for this integration.
202
+
203
+
204
+## Metrics
205
+
206
+Metrics grouped by *scope*.
207
+
208
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
209
+
210
+
211
+
212
+### Per Rspamd instance
213
+
214
+These metrics refer to the entire monitored application.
215
+
216
+This scope has no labels.
217
+
218
+Metrics:
219
+
220
+| Metric | Dimensions | Unit |
221
+|:------|:----------|:----|
222
+| rspamd.classifications | ham, spam | messages/s |
223
+| rspamd.actions | reject, soft_reject, rewrite_subject, add_header, greylist, custom, discard, quarantine, no_action | messages/s |
224
+| rspamd.scans | scanned | messages/s |
225
+| rspamd.learns | learned | messages/s |
226
+| rspamd.connections | connections | connections/s |
227
+| rspamd.control_connections | control_connections | connections/s |
228
+
229
+
230
+
231
## Troubleshooting
232
233
### Debug Mode
src/go/plugin/go.d/collector/samba/integrations/samba.md
+49
-49
@@ -47,55 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per syscall
59
-
60
-These metrics refer to the the Syscall.
61
-
62
-Labels:
63
-
64
-| Label | Description |
65
-|:-----------|:----------------|
66
-| syscall | Syscall name |
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| samba.syscall_calls | syscalls | calls/s |
73
-| samba.syscall_transferred_data | transferred | bytes/s |
74
-
75
-### Per smb2call
76
-
77
-These metrics refer to the the SMB2 Call.
78
-
79
-Labels:
80
-
81
-| Label | Description |
82
-|:-----------|:----------------|
83
-| smb2call | SMB2 call name |
84
-
85
-Metrics:
86
-
87
-| Metric | Dimensions | Unit |
88
-|:------|:----------|:----|
89
-| samba.smb2_call_calls | smb2 | calls/s |
90
-| samba.smb2_call_transferred_data | in, out | bytes/s |
91
-
92
-
93
-
94
-## Alerts
95
-
96
-There are no alerts configured by default for this integration.
97
-
98
-
50
## Setup
51
52
@@ -217,6 +168,55 @@ jobs:
168
169
170
171
+## Alerts
172
+
173
+There are no alerts configured by default for this integration.
174
+
175
+
176
+## Metrics
177
+
178
+Metrics grouped by *scope*.
179
+
180
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
181
+
182
+
183
+
184
+### Per syscall
185
+
186
+These metrics refer to the the Syscall.
187
+
188
+Labels:
189
+
190
+| Label | Description |
191
+|:-----------|:----------------|
192
+| syscall | Syscall name |
193
+
194
+Metrics:
195
+
196
+| Metric | Dimensions | Unit |
197
+|:------|:----------|:----|
198
+| samba.syscall_calls | syscalls | calls/s |
199
+| samba.syscall_transferred_data | transferred | bytes/s |
200
+
201
+### Per smb2call
202
+
203
+These metrics refer to the the SMB2 Call.
204
+
205
+Labels:
206
+
207
+| Label | Description |
208
+|:-----------|:----------------|
209
+| smb2call | SMB2 call name |
210
+
211
+Metrics:
212
+
213
+| Metric | Dimensions | Unit |
214
+|:------|:----------|:----|
215
+| samba.smb2_call_calls | smb2 | calls/s |
216
+| samba.smb2_call_transferred_data | in, out | bytes/s |
217
+
218
+
219
+
220
## Troubleshooting
221
222
### Debug Mode
src/go/plugin/go.d/collector/scaleio/integrations/dell_emc_scaleio.md
+78
-78
@@ -51,84 +51,6 @@ The default configuration for this integration does not impose any limits on dat
51
52
The default configuration for this integration is not expected to impose a significant performance impact on the system.
53
54
-## Metrics
55
-
56
-Metrics grouped by *scope*.
57
-
58
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
59
-
60
-
61
-
62
-### Per Dell EMC ScaleIO instance
63
-
64
-These metrics refer to the entire monitored application.
65
-
66
-This scope has no labels.
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| scaleio.system_capacity_total | total | KiB |
73
-| scaleio.system_capacity_in_use | in_use | KiB |
74
-| scaleio.system_capacity_usage | thick, decreased, thin, snapshot, spare, unused | KiB |
75
-| scaleio.system_capacity_available_volume_allocation | available | KiB |
76
-| scaleio.system_capacity_health_state | protected, degraded, in_maintenance, failed, unavailable | KiB |
77
-| scaleio.system_workload_primary_bandwidth_total | total | KiB/s |
78
-| scaleio.system_workload_primary_bandwidth | read, write | KiB/s |
79
-| scaleio.system_workload_primary_iops_total | total | iops/s |
80
-| scaleio.system_workload_primary_iops | read, write | iops/s |
81
-| scaleio.system_workload_primary_io_size_total | io_size | KiB |
82
-| scaleio.system_rebalance | read, write | KiB/s |
83
-| scaleio.system_rebalance_left | left | KiB |
84
-| scaleio.system_rebalance_time_until_finish | time | seconds |
85
-| scaleio.system_rebuild | read, write | KiB/s |
86
-| scaleio.system_rebuild_left | left | KiB |
87
-| scaleio.system_defined_components | devices, fault_sets, protection_domains, rfcache_devices, sdc, sds, snapshots, storage_pools, volumes, vtrees | components |
88
-| scaleio.system_components_volumes_by_type | thick, thin | volumes |
89
-| scaleio.system_components_volumes_by_mapping | mapped, unmapped | volumes |
90
-
91
-### Per storage pool
92
-
93
-These metrics refer to the storage pool.
94
-
95
-This scope has no labels.
96
-
97
-Metrics:
98
-
99
-| Metric | Dimensions | Unit |
100
-|:------|:----------|:----|
101
-| scaleio.storage_pool_capacity_total | total | KiB |
102
-| scaleio.storage_pool_capacity_in_use | in_use | KiB |
103
-| scaleio.storage_pool_capacity_usage | thick, decreased, thin, snapshot, spare, unused | KiB |
104
-| scaleio.storage_pool_capacity_utilization | used | percentage |
105
-| scaleio.storage_pool_capacity_available_volume_allocation | available | KiB |
106
-| scaleio.storage_pool_capacity_health_state | protected, degraded, in_maintenance, failed, unavailable | KiB |
107
-| scaleio.storage_pool_components | devices, snapshots, volumes, vtrees | components |
108
-
109
-### Per sdc
110
-
111
-These metrics refer to the SDC (ScaleIO Data Client).
112
-
113
-This scope has no labels.
114
-
115
-Metrics:
116
-
117
-| Metric | Dimensions | Unit |
118
-|:------|:----------|:----|
119
-| scaleio.sdc_mdm_connection_state | connected | boolean |
120
-| scaleio.sdc_bandwidth | read, write | KiB/s |
121
-| scaleio.sdc_iops | read, write | iops/s |
122
-| scaleio.sdc_io_size | read, write | KiB |
123
-| scaleio.sdc_num_of_mapped_volumed | mapped | volumes |
124
-
125
-
126
-
127
-## Alerts
128
-
129
-There are no alerts configured by default for this integration.
130
-
131
-
54
## Setup
55
56
@@ -270,6 +192,84 @@ jobs:
192
193
194
195
+## Alerts
196
+
197
+There are no alerts configured by default for this integration.
198
+
199
+
200
+## Metrics
201
+
202
+Metrics grouped by *scope*.
203
+
204
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
205
+
206
+
207
+
208
+### Per Dell EMC ScaleIO instance
209
+
210
+These metrics refer to the entire monitored application.
211
+
212
+This scope has no labels.
213
+
214
+Metrics:
215
+
216
+| Metric | Dimensions | Unit |
217
+|:------|:----------|:----|
218
+| scaleio.system_capacity_total | total | KiB |
219
+| scaleio.system_capacity_in_use | in_use | KiB |
220
+| scaleio.system_capacity_usage | thick, decreased, thin, snapshot, spare, unused | KiB |
221
+| scaleio.system_capacity_available_volume_allocation | available | KiB |
222
+| scaleio.system_capacity_health_state | protected, degraded, in_maintenance, failed, unavailable | KiB |
223
+| scaleio.system_workload_primary_bandwidth_total | total | KiB/s |
224
+| scaleio.system_workload_primary_bandwidth | read, write | KiB/s |
225
+| scaleio.system_workload_primary_iops_total | total | iops/s |
226
+| scaleio.system_workload_primary_iops | read, write | iops/s |
227
+| scaleio.system_workload_primary_io_size_total | io_size | KiB |
228
+| scaleio.system_rebalance | read, write | KiB/s |
229
+| scaleio.system_rebalance_left | left | KiB |
230
+| scaleio.system_rebalance_time_until_finish | time | seconds |
231
+| scaleio.system_rebuild | read, write | KiB/s |
232
+| scaleio.system_rebuild_left | left | KiB |
233
+| scaleio.system_defined_components | devices, fault_sets, protection_domains, rfcache_devices, sdc, sds, snapshots, storage_pools, volumes, vtrees | components |
234
+| scaleio.system_components_volumes_by_type | thick, thin | volumes |
235
+| scaleio.system_components_volumes_by_mapping | mapped, unmapped | volumes |
236
+
237
+### Per storage pool
238
+
239
+These metrics refer to the storage pool.
240
+
241
+This scope has no labels.
242
+
243
+Metrics:
244
+
245
+| Metric | Dimensions | Unit |
246
+|:------|:----------|:----|
247
+| scaleio.storage_pool_capacity_total | total | KiB |
248
+| scaleio.storage_pool_capacity_in_use | in_use | KiB |
249
+| scaleio.storage_pool_capacity_usage | thick, decreased, thin, snapshot, spare, unused | KiB |
250
+| scaleio.storage_pool_capacity_utilization | used | percentage |
251
+| scaleio.storage_pool_capacity_available_volume_allocation | available | KiB |
252
+| scaleio.storage_pool_capacity_health_state | protected, degraded, in_maintenance, failed, unavailable | KiB |
253
+| scaleio.storage_pool_components | devices, snapshots, volumes, vtrees | components |
254
+
255
+### Per sdc
256
+
257
+These metrics refer to the SDC (ScaleIO Data Client).
258
+
259
+This scope has no labels.
260
+
261
+Metrics:
262
+
263
+| Metric | Dimensions | Unit |
264
+|:------|:----------|:----|
265
+| scaleio.sdc_mdm_connection_state | connected | boolean |
266
+| scaleio.sdc_bandwidth | read, write | KiB/s |
267
+| scaleio.sdc_iops | read, write | iops/s |
268
+| scaleio.sdc_io_size | read, write | KiB |
269
+| scaleio.sdc_num_of_mapped_volumed | mapped | volumes |
270
+
271
+
272
+
273
## Troubleshooting
274
275
### Debug Mode
src/go/plugin/go.d/collector/sensors/integrations/linux_sensors.md
+49
-49
@@ -59,55 +59,6 @@ The default configuration for this integration does not impose any limits on dat
59
60
The default configuration for this integration is not expected to impose a significant performance impact on the system.
61
62
-## Metrics
63
-
64
-Metrics grouped by *scope*.
65
-
66
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
67
-
68
-
69
-
70
-### Per sensor
71
-
72
-These metrics refer to the system sensor.
73
-
74
-Labels:
75
-
76
-| Label | Description |
77
-|:-----------|:----------------|
78
-| chip | The path to the sensor's chip device, excluding the /sys/devices prefix. This provides a unique identifier for the physical hardware component. |
79
-| chip_id | A unique identifier for the sensor's chip, formatted as `chipName-busType-hash`. |
80
-| sensor | The name of the specific sensor within the chip device. This provides a direct identifier for the individual measurement point. |
81
-| label | A label provided by the kernel driver to indicate the intended use or purpose of the sensor. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| sensors.chip_sensor_temperature | input | Celsius |
88
-| sensors.chip_sensor_temperature_alarm | clear, triggered | status |
89
-| sensors.chip_sensor_voltage | input | Volts |
90
-| sensors.chip_sensor_voltage_average | average | Volts |
91
-| sensors.chip_sensor_voltage_alarm | clear, triggered | status |
92
-| sensors.chip_sensor_fan | input | RPM |
93
-| sensors.chip_sensor_fan_alarm | clear, triggered | status |
94
-| sensors.chip_sensor_current | input | Amperes |
95
-| sensors.chip_sensor_current_average | average | Amperes |
96
-| sensors.chip_sensor_current_alarm | clear, triggered | status |
97
-| sensors.chip_sensor_power | input | Watts |
98
-| sensors.chip_sensor_power_average | average | Watts |
99
-| sensors.chip_sensor_power_alarm | clear, triggered | status |
100
-| sensors.chip_sensor_energy | input | Joules |
101
-| sensors.chip_sensor_humidity | input | percent |
102
-| sensors.chip_sensor_intrusion_alarm | clear, triggered | status |
103
-
104
-
105
-
106
-## Alerts
107
-
108
-There are no alerts configured by default for this integration.
109
-
110
-
62
## Setup
63
64
@@ -226,6 +177,55 @@ jobs:
177
178
179
180
+## Alerts
181
+
182
+There are no alerts configured by default for this integration.
183
+
184
+
185
+## Metrics
186
+
187
+Metrics grouped by *scope*.
188
+
189
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
190
+
191
+
192
+
193
+### Per sensor
194
+
195
+These metrics refer to the system sensor.
196
+
197
+Labels:
198
+
199
+| Label | Description |
200
+|:-----------|:----------------|
201
+| chip | The path to the sensor's chip device, excluding the /sys/devices prefix. This provides a unique identifier for the physical hardware component. |
202
+| chip_id | A unique identifier for the sensor's chip, formatted as `chipName-busType-hash`. |
203
+| sensor | The name of the specific sensor within the chip device. This provides a direct identifier for the individual measurement point. |
204
+| label | A label provided by the kernel driver to indicate the intended use or purpose of the sensor. |
205
+
206
+Metrics:
207
+
208
+| Metric | Dimensions | Unit |
209
+|:------|:----------|:----|
210
+| sensors.chip_sensor_temperature | input | Celsius |
211
+| sensors.chip_sensor_temperature_alarm | clear, triggered | status |
212
+| sensors.chip_sensor_voltage | input | Volts |
213
+| sensors.chip_sensor_voltage_average | average | Volts |
214
+| sensors.chip_sensor_voltage_alarm | clear, triggered | status |
215
+| sensors.chip_sensor_fan | input | RPM |
216
+| sensors.chip_sensor_fan_alarm | clear, triggered | status |
217
+| sensors.chip_sensor_current | input | Amperes |
218
+| sensors.chip_sensor_current_average | average | Amperes |
219
+| sensors.chip_sensor_current_alarm | clear, triggered | status |
220
+| sensors.chip_sensor_power | input | Watts |
221
+| sensors.chip_sensor_power_average | average | Watts |
222
+| sensors.chip_sensor_power_alarm | clear, triggered | status |
223
+| sensors.chip_sensor_energy | input | Joules |
224
+| sensors.chip_sensor_humidity | input | percent |
225
+| sensors.chip_sensor_intrusion_alarm | clear, triggered | status |
226
+
227
+
228
+
229
## Troubleshooting
230
231
### Debug Mode
src/go/plugin/go.d/collector/smartctl/integrations/s.m.a.r.t..md
+43
-43
@@ -55,49 +55,6 @@ The default configuration for this integration does not impose any limits on dat
55
56
The default configuration for this integration is not expected to impose a significant performance impact on the system.
57
58
-## Metrics
59
-
60
-Metrics grouped by *scope*.
61
-
62
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
-
64
-
65
-
66
-### Per controller
67
-
68
-These metrics refer to the Storage Device.
69
-
70
-Labels:
71
-
72
-| Label | Description |
73
-|:-----------|:----------------|
74
-| device_name | Device name |
75
-| device_type | Device type |
76
-| model_name | Model name |
77
-| serial_number | Serial number |
78
-
79
-Metrics:
80
-
81
-| Metric | Dimensions | Unit |
82
-|:------|:----------|:----|
83
-| smartctl.device_smart_status | passed, failed | status |
84
-| smartctl.device_ata_smart_error_log_count | error_log | logs |
85
-| smartctl.device_power_on_time | power_on_time | seconds |
86
-| smartctl.device_temperature | temperature | Celsius |
87
-| smartctl.device_power_cycles_count | power | cycles |
88
-| smartctl.device_read_errors_rate | corrected, uncorrected | errors/s |
89
-| smartctl.device_write_errors_rate | corrected, uncorrected | errors/s |
90
-| smartctl.device_verify_errors_rate | corrected, uncorrected | errors/s |
91
-| smartctl.device_smart_attr_{attribute_name} | {attribute_name} | {attribute_unit} |
92
-| smartctl.device_smart_attr_{attribute_name}_normalized | {attribute_name} | value |
93
-
94
-
95
-
96
-## Alerts
97
-
98
-There are no alerts configured by default for this integration.
99
-
100
-
58
## Setup
59
60
@@ -277,6 +234,49 @@ jobs:
234
235
236
237
+## Alerts
238
+
239
+There are no alerts configured by default for this integration.
240
+
241
+
242
+## Metrics
243
+
244
+Metrics grouped by *scope*.
245
+
246
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
247
+
248
+
249
+
250
+### Per controller
251
+
252
+These metrics refer to the Storage Device.
253
+
254
+Labels:
255
+
256
+| Label | Description |
257
+|:-----------|:----------------|
258
+| device_name | Device name |
259
+| device_type | Device type |
260
+| model_name | Model name |
261
+| serial_number | Serial number |
262
+
263
+Metrics:
264
+
265
+| Metric | Dimensions | Unit |
266
+|:------|:----------|:----|
267
+| smartctl.device_smart_status | passed, failed | status |
268
+| smartctl.device_ata_smart_error_log_count | error_log | logs |
269
+| smartctl.device_power_on_time | power_on_time | seconds |
270
+| smartctl.device_temperature | temperature | Celsius |
271
+| smartctl.device_power_cycles_count | power | cycles |
272
+| smartctl.device_read_errors_rate | corrected, uncorrected | errors/s |
273
+| smartctl.device_write_errors_rate | corrected, uncorrected | errors/s |
274
+| smartctl.device_verify_errors_rate | corrected, uncorrected | errors/s |
275
+| smartctl.device_smart_attr_{attribute_name} | {attribute_name} | {attribute_unit} |
276
+| smartctl.device_smart_attr_{attribute_name}_normalized | {attribute_name} | value |
277
+
278
+
279
+
280
## Troubleshooting
281
282
### Debug Mode
src/go/plugin/go.d/collector/snmp/integrations/snmp_devices.md
+84
-84
@@ -110,90 +110,6 @@ The default configuration for this integration does not impose any limits on dat
110
**Concurrent polling**: Parallel access by multiple tools may cause missed counters on some devices. Increase the collection interval (`update_every`) to reduce request pressure.
111
112
113
-## Metrics
114
-
115
-Metrics and charts are **defined by the matched SNMP profile(s)** at runtime. They differ by vendor/model/OS and may include, for example, interface counters, optics, CPU/memory, temperature, VLANs, and more. Use the **Metrics** tab on the device’s dashboard to see exactly what is collected for that device.
116
-
117
-:::tip
118
-
119
-To understand the structure of these profiles (metrics, tags, virtual metrics, etc.), see **[SNMP Profile Format](https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/collector/snmp/profile-format.md)**.
120
-
121
-:::
122
-
123
-If `ping.enabled` is true, ICMP latency/packet-loss charts are also provided (or exclusively, when `ping_only: true`).
124
-
125
-
126
-
127
-## Functions
128
-
129
-This collector exposes real-time functions for interactive troubleshooting in the Live tab.
130
-
131
-
132
-### Network Interfaces
133
-
134
-Provides detailed network interface traffic and status metrics from SNMP-enabled devices.
135
-
136
-This function queries cached SNMP interface data collected during regular polling cycles and presents it in a sortable, filterable table. Each row represents a network interface on the monitored SNMP device, with comprehensive metrics for traffic analysis, error monitoring, and operational status tracking.
137
-
138
-Use cases:
139
-- Identify top bandwidth-consuming interfaces on routers, switches, and access points
140
-- Monitor interface operational and administrative status for network health
141
-- Investigate packet errors, discards, and unusual traffic patterns
142
-
143
-Data is sourced from the IF-MIB (RFC 2863) interface counters and is cached from the last successful SNMP collection. No additional SNMP requests are triggered when calling this function.
144
-
145
-
146
-| Aspect | Description |
147
-|:-------|:------------|
148
-| Name | `Snmp:interfaces` |
149
-| Require Cloud | no |
150
-| Performance | Uses cached SNMP data only, no additional SNMP requests are triggered:<br/>• Responses are instantaneous from memory cache<br/>• Large devices with many interfaces may return many rows |
151
-| Security | Exposes interface names, operational status, and traffic counters only:<br/>• No packet payloads or authentication credentials are exposed<br/>• No device configuration details are exposed |
152
-| Availability | Available when:<br/>• The collector has completed at least one data collection cycle<br/>• Interface data is cached from the last successful SNMP collection<br/>• Returns HTTP 503 if cache is not ready yet |
153
-
154
-#### Prerequisites
155
-
156
-No additional configuration is required.
157
-
158
-#### Parameters
159
-
160
-| Parameter | Type | Description | Required | Default | Options |
161
-|:---------|:-----|:------------|:--------:|:--------|:--------|
162
-| Type Group | select | Filter interfaces by their type classification group. Custom mapping categorizes IANA interface types into practical groups for easier filtering. | yes | ethernet | Ethernet (default), Aggregation, Virtual, Other |
163
-
164
-#### Returns
165
-
166
-Network interface metrics from cached SNMP data, including traffic rates, packet statistics, operational status, and error counters. Each row represents one physical or virtual interface.
167
-
168
-| Column | Type | Unit | Visibility | Description |
169
-|:-------|:-----|:-----|:-----------|:------------|
170
-| Interface | string | | | Network interface name or identifier (e.g., eth0, GigabitEthernet1/0/1, Vlan100) |
171
-| Type | string | | | IANA-assigned interface type from IF-MIB (e.g., ethernetCsmacd, ieee80211, softwareLoopback) |
172
-| Type Group | string | | | Custom categorization mapping IANA interface types into practical groups: Ethernet (physical Ethernet interfaces), Aggregation (LAG/port-channels, bonds), Virtual (VLANs, loopbacks), or Other (all remaining types) |
173
-| Admin Status | string | | | Administrative state configured on the interface: up (enabled for use), down (administratively disabled), or testing (currently in test mode). Different from operational status. |
174
-| Oper Status | string | | | Current operational state of the interface: up (operational and passing traffic), down (not operational), testing (in test mode), unknown (status cannot be determined), dormant (waiting for external actions), notPresent (interface removed but configuration remains), or lowerLayerDown (interface down due to lower-layer issues) |
175
-| Traffic In | float | bit/s | | Inbound network traffic rate in bits per second. High values indicate heavy inbound data flow that may require capacity planning. |
176
-| Traffic Out | float | bit/s | | Outbound network traffic rate in bits per second. High values indicate heavy outbound data flow. Compare with Traffic In to identify asymmetric usage patterns. |
177
-| Unicast In | float | packets/s | hidden | Rate of unicast packets (destined for a single recipient) received per second. Normal traffic pattern for point-to-point communications. |
178
-| Unicast Out | float | packets/s | hidden | Rate of unicast packets (addressed to a single destination) transmitted per second. |
179
-| Broadcast In | float | packets/s | hidden | Rate of broadcast packets (sent to all nodes on network) received per second. High values may indicate network storms, ARP flooding, or misconfigured devices. |
180
-| Broadcast Out | float | packets/s | hidden | Rate of broadcast packets transmitted per second. Consistently high broadcast rates can degrade network performance. |
181
-| Packets In | float | packets/s | | Total inbound packet rate (sum of unicast, broadcast, and multicast) per second. Useful for overall interface load assessment. |
182
-| Packets Out | float | packets/s | | Total outbound packet rate (sum of unicast, broadcast, and multicast) per second. |
183
-| Errors In | float | packets/s | hidden | Rate of inbound packets with errors that prevented delivery. Non-zero values indicate physical layer issues (cable problems, signal integrity) or buffer overruns. |
184
-| Errors Out | float | packets/s | hidden | Rate of outbound packets with transmission errors. Non-zero values may indicate interface hardware issues, cabling problems, or duplex mismatches. |
185
-| Discards In | float | packets/s | | Rate of inbound packets deliberately discarded by the device (often due to resource constraints, security policies, or unrecognized frames). Unlike errors, the interface may have been functioning correctly but chose to drop the packet. |
186
-| Discards Out | float | packets/s | | Rate of outbound packets deliberately discarded. Can indicate output queue overflows, ACL drops, or security policy rejections. |
187
-| Multicast In | float | packets/s | hidden | Rate of multicast packets (destined for a group) received per second. Common in video streaming, multicast applications, and routing protocols. |
188
-| Multicast Out | float | packets/s | hidden | Rate of multicast packets transmitted per second. |
189
-
190
-
191
-
192
-## Alerts
193
-
194
-There are no alerts configured by default for this integration.
195
-
196
-
113
## Setup
114
115
@@ -442,6 +358,90 @@ jobs:
358
359
360
361
+## Alerts
362
+
363
+There are no alerts configured by default for this integration.
364
+
365
+
366
+## Metrics
367
+
368
+Metrics and charts are **defined by the matched SNMP profile(s)** at runtime. They differ by vendor/model/OS and may include, for example, interface counters, optics, CPU/memory, temperature, VLANs, and more. Use the **Metrics** tab on the device’s dashboard to see exactly what is collected for that device.
369
+
370
+:::tip
371
+
372
+To understand the structure of these profiles (metrics, tags, virtual metrics, etc.), see **[SNMP Profile Format](https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/collector/snmp/profile-format.md)**.
373
+
374
+:::
375
+
376
+If `ping.enabled` is true, ICMP latency/packet-loss charts are also provided (or exclusively, when `ping_only: true`).
377
+
378
+
379
+
380
+## Live Data
381
+
382
+This collector exposes real-time functions for interactive troubleshooting in the Live tab.
383
+
384
+
385
+### Network Interfaces
386
+
387
+Provides detailed network interface traffic and status metrics from SNMP-enabled devices.
388
+
389
+This function queries cached SNMP interface data collected during regular polling cycles and presents it in a sortable, filterable table. Each row represents a network interface on the monitored SNMP device, with comprehensive metrics for traffic analysis, error monitoring, and operational status tracking.
390
+
391
+Use cases:
392
+- Identify top bandwidth-consuming interfaces on routers, switches, and access points
393
+- Monitor interface operational and administrative status for network health
394
+- Investigate packet errors, discards, and unusual traffic patterns
395
+
396
+Data is sourced from the IF-MIB (RFC 2863) interface counters and is cached from the last successful SNMP collection. No additional SNMP requests are triggered when calling this function.
397
+
398
+
399
+| Aspect | Description |
400
+|:-------|:------------|
401
+| Name | `Snmp:interfaces` |
402
+| Require Cloud | no |
403
+| Performance | Uses cached SNMP data only, no additional SNMP requests are triggered:<br/>• Responses are instantaneous from memory cache<br/>• Large devices with many interfaces may return many rows |
404
+| Security | Exposes interface names, operational status, and traffic counters only:<br/>• No packet payloads or authentication credentials are exposed<br/>• No device configuration details are exposed |
405
+| Availability | Available when:<br/>• The collector has completed at least one data collection cycle<br/>• Interface data is cached from the last successful SNMP collection<br/>• Returns HTTP 503 if cache is not ready yet |
406
+
407
+#### Prerequisites
408
+
409
+No additional configuration is required.
410
+
411
+#### Parameters
412
+
413
+| Parameter | Type | Description | Required | Default | Options |
414
+|:---------|:-----|:------------|:--------:|:--------|:--------|
415
+| Type Group | select | Filter interfaces by their type classification group. Custom mapping categorizes IANA interface types into practical groups for easier filtering. | yes | ethernet | Ethernet (default), Aggregation, Virtual, Other |
416
+
417
+#### Returns
418
+
419
+Network interface metrics from cached SNMP data, including traffic rates, packet statistics, operational status, and error counters. Each row represents one physical or virtual interface.
420
+
421
+| Column | Type | Unit | Visibility | Description |
422
+|:-------|:-----|:-----|:-----------|:------------|
423
+| Interface | string | | | Network interface name or identifier (e.g., eth0, GigabitEthernet1/0/1, Vlan100) |
424
+| Type | string | | | IANA-assigned interface type from IF-MIB (e.g., ethernetCsmacd, ieee80211, softwareLoopback) |
425
+| Type Group | string | | | Custom categorization mapping IANA interface types into practical groups: Ethernet (physical Ethernet interfaces), Aggregation (LAG/port-channels, bonds), Virtual (VLANs, loopbacks), or Other (all remaining types) |
426
+| Admin Status | string | | | Administrative state configured on the interface: up (enabled for use), down (administratively disabled), or testing (currently in test mode). Different from operational status. |
427
+| Oper Status | string | | | Current operational state of the interface: up (operational and passing traffic), down (not operational), testing (in test mode), unknown (status cannot be determined), dormant (waiting for external actions), notPresent (interface removed but configuration remains), or lowerLayerDown (interface down due to lower-layer issues) |
428
+| Traffic In | float | bit/s | | Inbound network traffic rate in bits per second. High values indicate heavy inbound data flow that may require capacity planning. |
429
+| Traffic Out | float | bit/s | | Outbound network traffic rate in bits per second. High values indicate heavy outbound data flow. Compare with Traffic In to identify asymmetric usage patterns. |
430
+| Unicast In | float | packets/s | hidden | Rate of unicast packets (destined for a single recipient) received per second. Normal traffic pattern for point-to-point communications. |
431
+| Unicast Out | float | packets/s | hidden | Rate of unicast packets (addressed to a single destination) transmitted per second. |
432
+| Broadcast In | float | packets/s | hidden | Rate of broadcast packets (sent to all nodes on network) received per second. High values may indicate network storms, ARP flooding, or misconfigured devices. |
433
+| Broadcast Out | float | packets/s | hidden | Rate of broadcast packets transmitted per second. Consistently high broadcast rates can degrade network performance. |
434
+| Packets In | float | packets/s | | Total inbound packet rate (sum of unicast, broadcast, and multicast) per second. Useful for overall interface load assessment. |
435
+| Packets Out | float | packets/s | | Total outbound packet rate (sum of unicast, broadcast, and multicast) per second. |
436
+| Errors In | float | packets/s | hidden | Rate of inbound packets with errors that prevented delivery. Non-zero values indicate physical layer issues (cable problems, signal integrity) or buffer overruns. |
437
+| Errors Out | float | packets/s | hidden | Rate of outbound packets with transmission errors. Non-zero values may indicate interface hardware issues, cabling problems, or duplex mismatches. |
438
+| Discards In | float | packets/s | | Rate of inbound packets deliberately discarded by the device (often due to resource constraints, security policies, or unrecognized frames). Unlike errors, the interface may have been functioning correctly but chose to drop the packet. |
439
+| Discards Out | float | packets/s | | Rate of outbound packets deliberately discarded. Can indicate output queue overflows, ACL drops, or security policy rejections. |
440
+| Multicast In | float | packets/s | hidden | Rate of multicast packets (destined for a group) received per second. Common in video streaming, multicast applications, and routing protocols. |
441
+| Multicast Out | float | packets/s | hidden | Rate of multicast packets transmitted per second. |
442
+
443
+
444
+
445
## Troubleshooting
446
447
### Debug Mode
src/go/plugin/go.d/collector/spigotmc/integrations/spigotmc.md
+29
-29
@@ -50,35 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per SpigotMC instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| spigotmc.players | players | players |
72
-| spigotmc.avg_tps | 1min, 5min, 15min | ticks |
73
-| spigotmc.memory | used, alloc | bytes |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
53
## Setup
54
55
@@ -200,6 +171,35 @@ jobs:
171
172
173
174
+## Alerts
175
+
176
+There are no alerts configured by default for this integration.
177
+
178
+
179
+## Metrics
180
+
181
+Metrics grouped by *scope*.
182
+
183
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
184
+
185
+
186
+
187
+### Per SpigotMC instance
188
+
189
+These metrics refer to the entire monitored application.
190
+
191
+This scope has no labels.
192
+
193
+Metrics:
194
+
195
+| Metric | Dimensions | Unit |
196
+|:------|:----------|:----|
197
+| spigotmc.players | players | players |
198
+| spigotmc.avg_tps | 1min, 5min, 15min | ticks |
199
+| spigotmc.memory | used, alloc | bytes |
200
+
201
+
202
+
203
## Troubleshooting
204
205
### Debug Mode
src/go/plugin/go.d/collector/sql/integrations/sql_databases_generic.md
+39
-39
@@ -98,45 +98,6 @@ Prefer indexed reads, avoid full table scans or heavy aggregations, and
98
consider using database views tailored for monitoring.
99
100
101
-## Metrics
102
-
103
-Metrics and charts are **defined by your SQL queries and metric blocks** at runtime. They differ by database engine, schema, and configuration, and may include, for example, connection counts, cache hit ratios, row throughput, lock statistics, or custom business KPIs. Use the **Metrics** tab on the job’s dashboard to see exactly what is collected for that job.
104
-
105
-:::tip
106
-
107
- To change what is collected, edit the `metrics` (and optionally `queries`) sections in `go.d/sql.conf` for the corresponding job. Each change is reflected in Netdata charts after the next data collection.
108
-
109
-:::
110
-
111
-
112
-
113
-## Functions
114
-
115
-This collector supports user-defined SQL functions that expose query results as
116
-interactive table views in Netdata's **Live** tab. Functions are configured per job
117
-in the `functions` section of the job configuration. Since functions are entirely
118
-user-defined, no predefined functions are listed here.
119
-
120
-In the Live tab, functions appear in a hierarchical menu:
121
-
122
-```
123
-Databases
124
-└── SQL
125
- └── <job_name>
126
- ├── <function_name_1>
127
- └── <function_name_2>
128
-```
129
-
130
-Each job creates its own group containing all functions defined for that job.
131
-
132
-
133
-
134
-
135
-## Alerts
136
-
137
-There are no alerts configured by default for this integration.
138
-
139
-
101
## Setup
102
103
@@ -831,6 +792,45 @@ jobs:
792
793
794
795
+## Alerts
796
+
797
+There are no alerts configured by default for this integration.
798
+
799
+
800
+## Metrics
801
+
802
+Metrics and charts are **defined by your SQL queries and metric blocks** at runtime. They differ by database engine, schema, and configuration, and may include, for example, connection counts, cache hit ratios, row throughput, lock statistics, or custom business KPIs. Use the **Metrics** tab on the job’s dashboard to see exactly what is collected for that job.
803
+
804
+:::tip
805
+
806
+ To change what is collected, edit the `metrics` (and optionally `queries`) sections in `go.d/sql.conf` for the corresponding job. Each change is reflected in Netdata charts after the next data collection.
807
+
808
+:::
809
+
810
+
811
+
812
+## Live Data
813
+
814
+This collector supports user-defined SQL functions that expose query results as
815
+interactive table views in Netdata's **Live** tab. Functions are configured per job
816
+in the `functions` section of the job configuration. Since functions are entirely
817
+user-defined, no predefined functions are listed here.
818
+
819
+In the Live tab, functions appear in a hierarchical menu:
820
+
821
+```
822
+Databases
823
+└── SQL
824
+ └── <job_name>
825
+ ├── <function_name_1>
826
+ └── <function_name_2>
827
+```
828
+
829
+Each job creates its own group containing all functions defined for that job.
830
+
831
+
832
+
833
+
834
## Troubleshooting
835
836
### Debug Mode
src/go/plugin/go.d/collector/squid/integrations/squid.md
+30
-30
@@ -49,36 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Squid instance
61
-
62
-These metrics refer to each monitored Squid instance.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| squid.clients_net | in, out, hits | kilobits/s |
71
-| squid.clients_requests | requests, hits, errors | requests/s |
72
-| squid.servers_net | in, out | kilobits/s |
73
-| squid.servers_requests | requests, errors | requests/s |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
52
## Setup
53
54
@@ -207,6 +177,36 @@ jobs:
177
178
179
180
+## Alerts
181
+
182
+There are no alerts configured by default for this integration.
183
+
184
+
185
+## Metrics
186
+
187
+Metrics grouped by *scope*.
188
+
189
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
190
+
191
+
192
+
193
+### Per Squid instance
194
+
195
+These metrics refer to each monitored Squid instance.
196
+
197
+This scope has no labels.
198
+
199
+Metrics:
200
+
201
+| Metric | Dimensions | Unit |
202
+|:------|:----------|:----|
203
+| squid.clients_net | in, out, hits | kilobits/s |
204
+| squid.clients_requests | requests, hits, errors | requests/s |
205
+| squid.servers_net | in, out | kilobits/s |
206
+| squid.servers_requests | requests, errors | requests/s |
207
+
208
+
209
+
210
## Troubleshooting
211
212
### Debug Mode
src/go/plugin/go.d/collector/squidlog/integrations/squid_log_files.md
+44
-44
@@ -46,50 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-Metrics grouped by *scope*.
52
-
53
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
54
-
55
-
56
-
57
-### Per Squid log files instance
58
-
59
-These metrics refer to the entire monitored application.
60
-
61
-This scope has no labels.
62
-
63
-Metrics:
64
-
65
-| Metric | Dimensions | Unit |
66
-|:------|:----------|:----|
67
-| squidlog.requests | requests | requests/s |
68
-| squidlog.excluded_requests | unmatched | requests/s |
69
-| squidlog.type_requests | success, bad, redirect, error | requests/s |
70
-| squidlog.http_status_code_class_responses | 1xx, 2xx, 3xx, 4xx, 5xx | responses/s |
71
-| squidlog.http_status_code_responses | a dimension per HTTP response code | responses/s |
72
-| squidlog.bandwidth | sent | kilobits/s |
73
-| squidlog.response_time | min, max, avg | milliseconds |
74
-| squidlog.uniq_clients | clients | clients |
75
-| squidlog.cache_result_code_requests | a dimension per cache result code | requests/s |
76
-| squidlog.cache_result_code_transport_tag_requests | a dimension per cache result delivery transport tag | requests/s |
77
-| squidlog.cache_result_code_handling_tag_requests | a dimension per cache result handling tag | requests/s |
78
-| squidlog.cache_code_object_tag_requests | a dimension per cache result produced object tag | requests/s |
79
-| squidlog.cache_code_load_source_tag_requests | a dimension per cache result load source tag | requests/s |
80
-| squidlog.cache_code_error_tag_requests | a dimension per cache result error tag | requests/s |
81
-| squidlog.http_method_requests | a dimension per HTTP method | requests/s |
82
-| squidlog.mime_type_requests | a dimension per MIME type | requests/s |
83
-| squidlog.hier_code_requests | a dimension per hierarchy code | requests/s |
84
-| squidlog.server_address_forwarded_requests | a dimension per server address | requests/s |
85
-
86
-
87
-
88
-## Alerts
89
-
90
-There are no alerts configured by default for this integration.
91
-
92
-
49
## Setup
50
51
@@ -207,6 +163,50 @@ There are no configuration examples.
163
164
165
166
+## Alerts
167
+
168
+There are no alerts configured by default for this integration.
169
+
170
+
171
+## Metrics
172
+
173
+Metrics grouped by *scope*.
174
+
175
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
176
+
177
+
178
+
179
+### Per Squid log files instance
180
+
181
+These metrics refer to the entire monitored application.
182
+
183
+This scope has no labels.
184
+
185
+Metrics:
186
+
187
+| Metric | Dimensions | Unit |
188
+|:------|:----------|:----|
189
+| squidlog.requests | requests | requests/s |
190
+| squidlog.excluded_requests | unmatched | requests/s |
191
+| squidlog.type_requests | success, bad, redirect, error | requests/s |
192
+| squidlog.http_status_code_class_responses | 1xx, 2xx, 3xx, 4xx, 5xx | responses/s |
193
+| squidlog.http_status_code_responses | a dimension per HTTP response code | responses/s |
194
+| squidlog.bandwidth | sent | kilobits/s |
195
+| squidlog.response_time | min, max, avg | milliseconds |
196
+| squidlog.uniq_clients | clients | clients |
197
+| squidlog.cache_result_code_requests | a dimension per cache result code | requests/s |
198
+| squidlog.cache_result_code_transport_tag_requests | a dimension per cache result delivery transport tag | requests/s |
199
+| squidlog.cache_result_code_handling_tag_requests | a dimension per cache result handling tag | requests/s |
200
+| squidlog.cache_code_object_tag_requests | a dimension per cache result produced object tag | requests/s |
201
+| squidlog.cache_code_load_source_tag_requests | a dimension per cache result load source tag | requests/s |
202
+| squidlog.cache_code_error_tag_requests | a dimension per cache result error tag | requests/s |
203
+| squidlog.http_method_requests | a dimension per HTTP method | requests/s |
204
+| squidlog.mime_type_requests | a dimension per MIME type | requests/s |
205
+| squidlog.hier_code_requests | a dimension per hierarchy code | requests/s |
206
+| squidlog.server_address_forwarded_requests | a dimension per server address | requests/s |
207
+
208
+
209
+
210
## Troubleshooting
211
212
### Debug Mode
src/go/plugin/go.d/collector/storcli/integrations/storecli_raid.md
+84
-84
@@ -55,90 +55,6 @@ The default configuration for this integration does not impose any limits on dat
55
56
The default configuration for this integration is not expected to impose a significant performance impact on the system.
57
58
-## Metrics
59
-
60
-Metrics grouped by *scope*.
61
-
62
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
-
64
-
65
-
66
-### Per controller
67
-
68
-These metrics refer to the Controller.
69
-
70
-Labels:
71
-
72
-| Label | Description |
73
-|:-----------|:----------------|
74
-| controller_number | Controller number (index) |
75
-| model | Controller model |
76
-| driver_name | Controller driver (megaraid_sas or mpt3sas) |
77
-
78
-Metrics:
79
-
80
-| Metric | Dimensions | Unit |
81
-|:------|:----------|:----|
82
-| storcli.controller_health_status | healthy, unhealthy | status |
83
-| storcli.controller_status | optimal, degraded, partially_degraded, failed | status |
84
-| storcli.controller_bbu_status | healthy, unhealthy, na | status |
85
-| storcli.controller_roc_temperature | temperature | Celsius |
86
-
87
-### Per physical drive
88
-
89
-These metrics refer to the Physical Drive.
90
-
91
-Labels:
92
-
93
-| Label | Description |
94
-|:-----------|:----------------|
95
-| controller_number | Controller number (index) |
96
-| enclosure_number | Enclosure number (index) |
97
-| slot_number | Slot number (index) |
98
-| media type | Media type (e.g. HDD) |
99
-
100
-Metrics:
101
-
102
-| Metric | Dimensions | Unit |
103
-|:------|:----------|:----|
104
-| storcli.phys_drive_errors | media, other | errors/s |
105
-| storcli.phys_drive_predictive_failures | predictive_failures | failures/s |
106
-| storcli.phys_drive_smart_alert_status | active, inactive | status |
107
-| storcli.phys_drive_temperature | temperature | Celsius |
108
-
109
-### Per bbu
110
-
111
-These metrics refer to the Backup Battery Unit.
112
-
113
-Labels:
114
-
115
-| Label | Description |
116
-|:-----------|:----------------|
117
-| controller_number | Controller number (index) |
118
-| bbu_number | BBU number (index) |
119
-| model | BBU model |
120
-
121
-Metrics:
122
-
123
-| Metric | Dimensions | Unit |
124
-|:------|:----------|:----|
125
-| storcli.bbu_temperature | temperature | Celsius |
126
-
127
-
128
-
129
-## Alerts
130
-
131
-
132
-The following alerts are available:
133
-
134
-| Alert name | On metric | Description |
135
-|:------------|:----------|:------------|
136
-| [ storcli_controller_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.controller_health_status | RAID controller ${label:controller_number} is unhealthy |
137
-| [ storcli_controller_bbu_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.controller_bbu_status | RAID controller ${label:controller_number} BBU is unhealthy |
138
-| [ storcli_phys_drive_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.phys_drive_errors | RAID physical drive c${label:controller_number}/e${label:enclosure_number}/s${label:slot_number} errors |
139
-| [ storcli_phys_drive_predictive_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.phys_drive_predictive_failures | RAID physical drive c${label:controller_number}/e${label:enclosure_number}/s${label:slot_number} predictive failures |
140
-
141
-
58
## Setup
59
60
@@ -233,6 +149,90 @@ jobs:
149
150
151
152
+## Alerts
153
+
154
+
155
+The following alerts are available:
156
+
157
+| Alert name | On metric | Description |
158
+|:------------|:----------|:------------|
159
+| [ storcli_controller_health_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.controller_health_status | RAID controller ${label:controller_number} is unhealthy |
160
+| [ storcli_controller_bbu_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.controller_bbu_status | RAID controller ${label:controller_number} BBU is unhealthy |
161
+| [ storcli_phys_drive_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.phys_drive_errors | RAID physical drive c${label:controller_number}/e${label:enclosure_number}/s${label:slot_number} errors |
162
+| [ storcli_phys_drive_predictive_failures ](https://github.com/netdata/netdata/blob/master/src/health/health.d/storcli.conf) | storcli.phys_drive_predictive_failures | RAID physical drive c${label:controller_number}/e${label:enclosure_number}/s${label:slot_number} predictive failures |
163
+
164
+
165
+## Metrics
166
+
167
+Metrics grouped by *scope*.
168
+
169
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
170
+
171
+
172
+
173
+### Per controller
174
+
175
+These metrics refer to the Controller.
176
+
177
+Labels:
178
+
179
+| Label | Description |
180
+|:-----------|:----------------|
181
+| controller_number | Controller number (index) |
182
+| model | Controller model |
183
+| driver_name | Controller driver (megaraid_sas or mpt3sas) |
184
+
185
+Metrics:
186
+
187
+| Metric | Dimensions | Unit |
188
+|:------|:----------|:----|
189
+| storcli.controller_health_status | healthy, unhealthy | status |
190
+| storcli.controller_status | optimal, degraded, partially_degraded, failed | status |
191
+| storcli.controller_bbu_status | healthy, unhealthy, na | status |
192
+| storcli.controller_roc_temperature | temperature | Celsius |
193
+
194
+### Per physical drive
195
+
196
+These metrics refer to the Physical Drive.
197
+
198
+Labels:
199
+
200
+| Label | Description |
201
+|:-----------|:----------------|
202
+| controller_number | Controller number (index) |
203
+| enclosure_number | Enclosure number (index) |
204
+| slot_number | Slot number (index) |
205
+| media type | Media type (e.g. HDD) |
206
+
207
+Metrics:
208
+
209
+| Metric | Dimensions | Unit |
210
+|:------|:----------|:----|
211
+| storcli.phys_drive_errors | media, other | errors/s |
212
+| storcli.phys_drive_predictive_failures | predictive_failures | failures/s |
213
+| storcli.phys_drive_smart_alert_status | active, inactive | status |
214
+| storcli.phys_drive_temperature | temperature | Celsius |
215
+
216
+### Per bbu
217
+
218
+These metrics refer to the Backup Battery Unit.
219
+
220
+Labels:
221
+
222
+| Label | Description |
223
+|:-----------|:----------------|
224
+| controller_number | Controller number (index) |
225
+| bbu_number | BBU number (index) |
226
+| model | BBU model |
227
+
228
+Metrics:
229
+
230
+| Metric | Dimensions | Unit |
231
+|:------|:----------|:----|
232
+| storcli.bbu_temperature | temperature | Celsius |
233
+
234
+
235
+
236
## Troubleshooting
237
238
### Debug Mode
src/go/plugin/go.d/collector/supervisord/integrations/supervisor.md
+43
-43
@@ -54,49 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per Supervisor instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| supervisord.summary_processes | running, non-running | processes |
76
-
77
-### Per process group
78
-
79
-These metrics refer to the process group.
80
-
81
-This scope has no labels.
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| supervisord.processes | running, non-running | processes |
88
-| supervisord.process_state_code | a dimension per process | code |
89
-| supervisord.process_exit_status | a dimension per process | exit status |
90
-| supervisord.process_uptime | a dimension per process | seconds |
91
-| supervisord.process_downtime | a dimension per process | seconds |
92
-
93
-
94
-
95
-## Alerts
96
-
97
-There are no alerts configured by default for this integration.
98
-
99
-
57
## Setup
58
59
@@ -227,6 +184,49 @@ jobs:
184
185
186
187
+## Alerts
188
+
189
+There are no alerts configured by default for this integration.
190
+
191
+
192
+## Metrics
193
+
194
+Metrics grouped by *scope*.
195
+
196
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
197
+
198
+
199
+
200
+### Per Supervisor instance
201
+
202
+These metrics refer to the entire monitored application.
203
+
204
+This scope has no labels.
205
+
206
+Metrics:
207
+
208
+| Metric | Dimensions | Unit |
209
+|:------|:----------|:----|
210
+| supervisord.summary_processes | running, non-running | processes |
211
+
212
+### Per process group
213
+
214
+These metrics refer to the process group.
215
+
216
+This scope has no labels.
217
+
218
+Metrics:
219
+
220
+| Metric | Dimensions | Unit |
221
+|:------|:----------|:----|
222
+| supervisord.processes | running, non-running | processes |
223
+| supervisord.process_state_code | a dimension per process | code |
224
+| supervisord.process_exit_status | a dimension per process | exit status |
225
+| supervisord.process_uptime | a dimension per process | seconds |
226
+| supervisord.process_downtime | a dimension per process | seconds |
227
+
228
+
229
+
230
## Troubleshooting
231
232
### Debug Mode
src/go/plugin/go.d/collector/systemdunits/integrations/systemd_units.md
+73
-73
@@ -45,79 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per unit
57
-
58
-These metrics refer to the systemd unit.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| unit_name | systemd unit name |
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| systemd.service_unit_state | active, inactive, activating, deactivating, failed | state |
71
-| systemd.socket_unit_state | active, inactive, activating, deactivating, failed | state |
72
-| systemd.target_unit_state | active, inactive, activating, deactivating, failed | state |
73
-| systemd.path_unit_state | active, inactive, activating, deactivating, failed | state |
74
-| systemd.device_unit_state | active, inactive, activating, deactivating, failed | state |
75
-| systemd.mount_unit_state | active, inactive, activating, deactivating, failed | state |
76
-| systemd.automount_unit_state | active, inactive, activating, deactivating, failed | state |
77
-| systemd.swap_unit_state | active, inactive, activating, deactivating, failed | state |
78
-| systemd.timer_unit_state | active, inactive, activating, deactivating, failed | state |
79
-| systemd.scope_unit_state | active, inactive, activating, deactivating, failed | state |
80
-| systemd.slice_unit_state | active, inactive, activating, deactivating, failed | state |
81
-
82
-### Per unit file
83
-
84
-These metrics refer to the systemd unit file.
85
-
86
-Labels:
87
-
88
-| Label | Description |
89
-|:-----------|:----------------|
90
-| unit_file_name | systemd unit file name |
91
-| unit_file_type | systemd unit file type |
92
-
93
-Metrics:
94
-
95
-| Metric | Dimensions | Unit |
96
-|:------|:----------|:----|
97
-| systemd.unit_file_state | enabled, enabled-runtime, linked, linked-runtime, alias, masked, masked-runtime, static, disabled, indirect, generated, transient, bad | state |
98
-
99
-
100
-
101
-## Alerts
102
-
103
-
104
-The following alerts are available:
105
-
106
-| Alert name | On metric | Description |
107
-|:------------|:----------|:------------|
108
-| [ systemd_service_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.service_unit_state | systemd service unit in the failed state |
109
-| [ systemd_socket_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.socket_unit_state | systemd socket unit in the failed state |
110
-| [ systemd_target_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.target_unit_state | systemd target unit in the failed state |
111
-| [ systemd_path_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.path_unit_state | systemd path unit in the failed state |
112
-| [ systemd_device_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.device_unit_state | systemd device unit in the failed state |
113
-| [ systemd_mount_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.mount_unit_state | systemd mount unit in the failed state |
114
-| [ systemd_automount_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.automount_unit_state | systemd automount unit in the failed state |
115
-| [ systemd_swap_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.swap_unit_state | systemd swap unit in the failed state |
116
-| [ systemd_scope_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.scope_unit_state | systemd scope unit in the failed state |
117
-| [ systemd_slice_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.slice_unit_state | systemd slice unit in the failed state |
118
-| [ systemd_timer_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.timer_unit_state | systemd timer unit in the failed state |
119
-
120
-
48
## Setup
49
50
@@ -303,6 +230,79 @@ jobs:
230
231
232
233
+## Alerts
234
+
235
+
236
+The following alerts are available:
237
+
238
+| Alert name | On metric | Description |
239
+|:------------|:----------|:------------|
240
+| [ systemd_service_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.service_unit_state | systemd service unit in the failed state |
241
+| [ systemd_socket_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.socket_unit_state | systemd socket unit in the failed state |
242
+| [ systemd_target_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.target_unit_state | systemd target unit in the failed state |
243
+| [ systemd_path_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.path_unit_state | systemd path unit in the failed state |
244
+| [ systemd_device_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.device_unit_state | systemd device unit in the failed state |
245
+| [ systemd_mount_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.mount_unit_state | systemd mount unit in the failed state |
246
+| [ systemd_automount_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.automount_unit_state | systemd automount unit in the failed state |
247
+| [ systemd_swap_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.swap_unit_state | systemd swap unit in the failed state |
248
+| [ systemd_scope_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.scope_unit_state | systemd scope unit in the failed state |
249
+| [ systemd_slice_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.slice_unit_state | systemd slice unit in the failed state |
250
+| [ systemd_timer_unit_failed_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/systemdunits.conf) | systemd.timer_unit_state | systemd timer unit in the failed state |
251
+
252
+
253
+## Metrics
254
+
255
+Metrics grouped by *scope*.
256
+
257
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
258
+
259
+
260
+
261
+### Per unit
262
+
263
+These metrics refer to the systemd unit.
264
+
265
+Labels:
266
+
267
+| Label | Description |
268
+|:-----------|:----------------|
269
+| unit_name | systemd unit name |
270
+
271
+Metrics:
272
+
273
+| Metric | Dimensions | Unit |
274
+|:------|:----------|:----|
275
+| systemd.service_unit_state | active, inactive, activating, deactivating, failed | state |
276
+| systemd.socket_unit_state | active, inactive, activating, deactivating, failed | state |
277
+| systemd.target_unit_state | active, inactive, activating, deactivating, failed | state |
278
+| systemd.path_unit_state | active, inactive, activating, deactivating, failed | state |
279
+| systemd.device_unit_state | active, inactive, activating, deactivating, failed | state |
280
+| systemd.mount_unit_state | active, inactive, activating, deactivating, failed | state |
281
+| systemd.automount_unit_state | active, inactive, activating, deactivating, failed | state |
282
+| systemd.swap_unit_state | active, inactive, activating, deactivating, failed | state |
283
+| systemd.timer_unit_state | active, inactive, activating, deactivating, failed | state |
284
+| systemd.scope_unit_state | active, inactive, activating, deactivating, failed | state |
285
+| systemd.slice_unit_state | active, inactive, activating, deactivating, failed | state |
286
+
287
+### Per unit file
288
+
289
+These metrics refer to the systemd unit file.
290
+
291
+Labels:
292
+
293
+| Label | Description |
294
+|:-----------|:----------------|
295
+| unit_file_name | systemd unit file name |
296
+| unit_file_type | systemd unit file type |
297
+
298
+Metrics:
299
+
300
+| Metric | Dimensions | Unit |
301
+|:------|:----------|:----|
302
+| systemd.unit_file_state | enabled, enabled-runtime, linked, linked-runtime, alias, masked, masked-runtime, static, disabled, indirect, generated, transient, bad | state |
303
+
304
+
305
+
306
## Troubleshooting
307
308
### Debug Mode
src/go/plugin/go.d/collector/tengine/integrations/tengine.md
+34
-34
@@ -45,40 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Tengine instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| tengine.bandwidth_total | in, out | B/s |
67
-| tengine.connections_total | accepted | connections/s |
68
-| tengine.requests_total | processed | requests/s |
69
-| tengine.requests_per_response_code_family_total | 2xx, 3xx, 4xx, 5xx, other | requests/s |
70
-| tengine.requests_per_response_code_detailed_total | 200, 206, 302, 304, 403, 404, 419, 499, 500, 502, 503, 504, 508, other | requests/s |
71
-| tengine.requests_upstream_total | requests | requests/s |
72
-| tengine.tries_upstream_total | calls | calls/s |
73
-| tengine.requests_upstream_per_response_code_family_total | 4xx, 5xx | requests/s |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-There are no alerts configured by default for this integration.
80
-
81
-
48
## Setup
49
50
@@ -247,6 +213,40 @@ jobs:
213
214
215
216
+## Alerts
217
+
218
+There are no alerts configured by default for this integration.
219
+
220
+
221
+## Metrics
222
+
223
+Metrics grouped by *scope*.
224
+
225
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
226
+
227
+
228
+
229
+### Per Tengine instance
230
+
231
+These metrics refer to the entire monitored application.
232
+
233
+This scope has no labels.
234
+
235
+Metrics:
236
+
237
+| Metric | Dimensions | Unit |
238
+|:------|:----------|:----|
239
+| tengine.bandwidth_total | in, out | B/s |
240
+| tengine.connections_total | accepted | connections/s |
241
+| tengine.requests_total | processed | requests/s |
242
+| tengine.requests_per_response_code_family_total | 2xx, 3xx, 4xx, 5xx, other | requests/s |
243
+| tengine.requests_per_response_code_detailed_total | 200, 206, 302, 304, 403, 404, 419, 499, 500, 502, 503, 504, 508, other | requests/s |
244
+| tengine.requests_upstream_total | requests | requests/s |
245
+| tengine.tries_upstream_total | calls | calls/s |
246
+| tengine.requests_upstream_per_response_code_family_total | 4xx, 5xx | requests/s |
247
+
248
+
249
+
250
## Troubleshooting
251
252
### Debug Mode
src/go/plugin/go.d/collector/tomcat/integrations/tomcat.md
+64
-64
@@ -49,70 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per Tomcat instance
61
-
62
-These metrics refer to the entire monitored application.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| tomcat.jvm_memory_usage | free, used | bytes |
71
-
72
-### Per jvm memory pool
73
-
74
-These metrics refer to the JVM memory pool.
75
-
76
-Labels:
77
-
78
-| Label | Description |
79
-|:-----------|:----------------|
80
-| mempool_name | Memory Pool name. |
81
-| mempool_type | Memory Pool type. |
82
-
83
-Metrics:
84
-
85
-| Metric | Dimensions | Unit |
86
-|:------|:----------|:----|
87
-| tomcat.jvm_mem_pool_memory_usage | commited, used, max | bytes |
88
-
89
-### Per connector
90
-
91
-These metrics refer to the connector.
92
-
93
-Labels:
94
-
95
-| Label | Description |
96
-|:-----------|:----------------|
97
-| connector_name | Connector name. |
98
-
99
-Metrics:
100
-
101
-| Metric | Dimensions | Unit |
102
-|:------|:----------|:----|
103
-| tomcat.connector_requests | requests | requests/s |
104
-| tomcat.connector_bandwidth | received, sent | bytes/s |
105
-| tomcat.connector_requests_processing_time | processing_time | milliseconds |
106
-| tomcat.connector_errors | errors | errors/s |
107
-| tomcat.connector_request_threads | idle, busy | threads |
108
-
109
-
110
-
111
-## Alerts
112
-
113
-There are no alerts configured by default for this integration.
114
-
115
-
52
## Setup
53
54
@@ -255,6 +191,70 @@ jobs:
191
192
193
194
+## Alerts
195
+
196
+There are no alerts configured by default for this integration.
197
+
198
+
199
+## Metrics
200
+
201
+Metrics grouped by *scope*.
202
+
203
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
204
+
205
+
206
+
207
+### Per Tomcat instance
208
+
209
+These metrics refer to the entire monitored application.
210
+
211
+This scope has no labels.
212
+
213
+Metrics:
214
+
215
+| Metric | Dimensions | Unit |
216
+|:------|:----------|:----|
217
+| tomcat.jvm_memory_usage | free, used | bytes |
218
+
219
+### Per jvm memory pool
220
+
221
+These metrics refer to the JVM memory pool.
222
+
223
+Labels:
224
+
225
+| Label | Description |
226
+|:-----------|:----------------|
227
+| mempool_name | Memory Pool name. |
228
+| mempool_type | Memory Pool type. |
229
+
230
+Metrics:
231
+
232
+| Metric | Dimensions | Unit |
233
+|:------|:----------|:----|
234
+| tomcat.jvm_mem_pool_memory_usage | commited, used, max | bytes |
235
+
236
+### Per connector
237
+
238
+These metrics refer to the connector.
239
+
240
+Labels:
241
+
242
+| Label | Description |
243
+|:-----------|:----------------|
244
+| connector_name | Connector name. |
245
+
246
+Metrics:
247
+
248
+| Metric | Dimensions | Unit |
249
+|:------|:----------|:----|
250
+| tomcat.connector_requests | requests | requests/s |
251
+| tomcat.connector_bandwidth | received, sent | bytes/s |
252
+| tomcat.connector_requests_processing_time | processing_time | milliseconds |
253
+| tomcat.connector_errors | errors | errors/s |
254
+| tomcat.connector_request_threads | idle, busy | threads |
255
+
256
+
257
+
258
## Troubleshooting
259
260
### Debug Mode
src/go/plugin/go.d/collector/tor/integrations/tor.md
+28
-28
@@ -50,34 +50,6 @@ The default configuration for this integration does not impose any limits on dat
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per Tor instance
62
-
63
-These metrics refer to the entire monitored application.
64
-
65
-This scope has no labels.
66
-
67
-Metrics:
68
-
69
-| Metric | Dimensions | Unit |
70
-|:------|:----------|:----|
71
-| tor.traffic | read, write | KiB/s |
72
-| tor.uptime | uptime | seconds |
73
-
74
-
75
-
76
-## Alerts
77
-
78
-There are no alerts configured by default for this integration.
79
-
80
-
53
## Setup
54
55
@@ -202,6 +174,34 @@ jobs:
174
175
176
177
+## Alerts
178
+
179
+There are no alerts configured by default for this integration.
180
+
181
+
182
+## Metrics
183
+
184
+Metrics grouped by *scope*.
185
+
186
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
187
+
188
+
189
+
190
+### Per Tor instance
191
+
192
+These metrics refer to the entire monitored application.
193
+
194
+This scope has no labels.
195
+
196
+Metrics:
197
+
198
+| Metric | Dimensions | Unit |
199
+|:------|:----------|:----|
200
+| tor.traffic | read, write | KiB/s |
201
+| tor.uptime | uptime | seconds |
202
+
203
+
204
+
205
## Troubleshooting
206
207
### Debug Mode
src/go/plugin/go.d/collector/traefik/integrations/traefik.md
+29
-29
@@ -45,35 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per entrypoint, protocol
57
-
58
-These metrics refer to the endpoint.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| traefik.entrypoint_requests | 1xx, 2xx, 3xx, 4xx, 5xx | requests/s |
67
-| traefik.entrypoint_request_duration_average | 1xx, 2xx, 3xx, 4xx, 5xx | milliseconds |
68
-| traefik.entrypoint_open_connections | a dimension per HTTP method | connections |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
48
## Setup
49
50
@@ -226,6 +197,35 @@ jobs:
197
198
199
200
+## Alerts
201
+
202
+There are no alerts configured by default for this integration.
203
+
204
+
205
+## Metrics
206
+
207
+Metrics grouped by *scope*.
208
+
209
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
210
+
211
+
212
+
213
+### Per entrypoint, protocol
214
+
215
+These metrics refer to the endpoint.
216
+
217
+This scope has no labels.
218
+
219
+Metrics:
220
+
221
+| Metric | Dimensions | Unit |
222
+|:------|:----------|:----|
223
+| traefik.entrypoint_requests | 1xx, 2xx, 3xx, 4xx, 5xx | requests/s |
224
+| traefik.entrypoint_request_duration_average | 1xx, 2xx, 3xx, 4xx, 5xx | milliseconds |
225
+| traefik.entrypoint_open_connections | a dimension per HTTP method | connections |
226
+
227
+
228
+
229
## Troubleshooting
230
231
### Debug Mode
src/go/plugin/go.d/collector/typesense/integrations/typesense.md
+31
-31
@@ -54,37 +54,6 @@ The default configuration for this integration does not impose any limits on dat
54
55
The default configuration for this integration is not expected to impose a significant performance impact on the system.
56
57
-## Metrics
58
-
59
-Metrics grouped by *scope*.
60
-
61
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
62
-
63
-
64
-
65
-### Per Typesense instance
66
-
67
-These metrics refer to the entire monitored application.
68
-
69
-This scope has no labels.
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| typesense.health_status | ok, out_of_disk, out_of_memory | status |
76
-| typesense.total_requests | requests | requests/s |
77
-| typesense.requests_by_operation | search, write, import, delete | requests/s |
78
-| typesense.latency_by_operation | search, write, import, delete | milliseconds |
79
-| typesense.overloaded_requests | overloaded | requests/s |
80
-
81
-
82
-
83
-## Alerts
84
-
85
-There are no alerts configured by default for this integration.
86
-
87
-
57
## Setup
58
59
@@ -225,6 +194,37 @@ jobs:
194
195
196
197
+## Alerts
198
+
199
+There are no alerts configured by default for this integration.
200
+
201
+
202
+## Metrics
203
+
204
+Metrics grouped by *scope*.
205
+
206
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
207
+
208
+
209
+
210
+### Per Typesense instance
211
+
212
+These metrics refer to the entire monitored application.
213
+
214
+This scope has no labels.
215
+
216
+Metrics:
217
+
218
+| Metric | Dimensions | Unit |
219
+|:------|:----------|:----|
220
+| typesense.health_status | ok, out_of_disk, out_of_memory | status |
221
+| typesense.total_requests | requests | requests/s |
222
+| typesense.requests_by_operation | search, write, import, delete | requests/s |
223
+| typesense.latency_by_operation | search, write, import, delete | milliseconds |
224
+| typesense.overloaded_requests | overloaded | requests/s |
225
+
226
+
227
+
228
## Troubleshooting
229
230
### Debug Mode
src/go/plugin/go.d/collector/unbound/integrations/unbound.md
+75
-75
@@ -45,81 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per Unbound instance
57
-
58
-These metrics refer to the entire monitored application.
59
-
60
-This scope has no labels.
61
-
62
-Metrics:
63
-
64
-| Metric | Dimensions | Unit |
65
-|:------|:----------|:----|
66
-| unbound.queries | queries | queries |
67
-| unbound.queries_ip_ratelimited | ratelimited | queries |
68
-| unbound.dnscrypt_queries | crypted, cert, cleartext, malformed | queries |
69
-| unbound.cache | hits, miss | events |
70
-| unbound.cache_percentage | hits, miss | percentage |
71
-| unbound.prefetch | prefetches | prefetches |
72
-| unbound.expired | expired | replies |
73
-| unbound.zero_ttl_replies | zero_ttl | replies |
74
-| unbound.recursive_replies | recursive | replies |
75
-| unbound.recursion_time | avg, median | milliseconds |
76
-| unbound.request_list_usage | avg, max | queries |
77
-| unbound.current_request_list_usage | all, users | queries |
78
-| unbound.request_list_jostle_list | overwritten, dropped | queries |
79
-| unbound.tcpusage | usage | buffers |
80
-| unbound.uptime | time | seconds |
81
-| unbound.cache_memory | message, rrset, dnscrypt_nonce, dnscrypt_shared_secret | KB |
82
-| unbound.mod_memory | iterator, respip, validator, subnet, ipsec | KB |
83
-| unbound.mem_streamwait | streamwait | KB |
84
-| unbound.cache_count | infra, key, msg, rrset, dnscrypt_nonce, shared_secret | items |
85
-| unbound.type_queries | a dimension per query type | queries |
86
-| unbound.class_queries | a dimension per query class | queries |
87
-| unbound.opcode_queries | a dimension per query opcode | queries |
88
-| unbound.flag_queries | qr, aa, tc, rd, ra, z, ad, cd | queries |
89
-| unbound.rcode_answers | a dimension per reply rcode | replies |
90
-
91
-### Per thread
92
-
93
-These metrics refer to threads.
94
-
95
-This scope has no labels.
96
-
97
-Metrics:
98
-
99
-| Metric | Dimensions | Unit |
100
-|:------|:----------|:----|
101
-| unbound.thread_queries | queries | queries |
102
-| unbound.thread_queries_ip_ratelimited | ratelimited | queries |
103
-| unbound.thread_dnscrypt_queries | crypted, cert, cleartext, malformed | queries |
104
-| unbound.thread_cache | hits, miss | events |
105
-| unbound.thread_cache_percentage | hits, miss | percentage |
106
-| unbound.thread_prefetch | prefetches | prefetches |
107
-| unbound.thread_expired | expired | replies |
108
-| unbound.thread_zero_ttl_replies | zero_ttl | replies |
109
-| unbound.thread_recursive_replies | recursive | replies |
110
-| unbound.thread_recursion_time | avg, median | milliseconds |
111
-| unbound.thread_request_list_usage | avg, max | queries |
112
-| unbound.thread_current_request_list_usage | all, users | queries |
113
-| unbound.thread_request_list_jostle_list | overwritten, dropped | queries |
114
-| unbound.thread_tcpusage | usage | buffers |
115
-
116
-
117
-
118
-## Alerts
119
-
120
-There are no alerts configured by default for this integration.
121
-
122
-
48
## Setup
49
50
@@ -282,6 +207,81 @@ jobs:
207
208
209
210
+## Alerts
211
+
212
+There are no alerts configured by default for this integration.
213
+
214
+
215
+## Metrics
216
+
217
+Metrics grouped by *scope*.
218
+
219
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
220
+
221
+
222
+
223
+### Per Unbound instance
224
+
225
+These metrics refer to the entire monitored application.
226
+
227
+This scope has no labels.
228
+
229
+Metrics:
230
+
231
+| Metric | Dimensions | Unit |
232
+|:------|:----------|:----|
233
+| unbound.queries | queries | queries |
234
+| unbound.queries_ip_ratelimited | ratelimited | queries |
235
+| unbound.dnscrypt_queries | crypted, cert, cleartext, malformed | queries |
236
+| unbound.cache | hits, miss | events |
237
+| unbound.cache_percentage | hits, miss | percentage |
238
+| unbound.prefetch | prefetches | prefetches |
239
+| unbound.expired | expired | replies |
240
+| unbound.zero_ttl_replies | zero_ttl | replies |
241
+| unbound.recursive_replies | recursive | replies |
242
+| unbound.recursion_time | avg, median | milliseconds |
243
+| unbound.request_list_usage | avg, max | queries |
244
+| unbound.current_request_list_usage | all, users | queries |
245
+| unbound.request_list_jostle_list | overwritten, dropped | queries |
246
+| unbound.tcpusage | usage | buffers |
247
+| unbound.uptime | time | seconds |
248
+| unbound.cache_memory | message, rrset, dnscrypt_nonce, dnscrypt_shared_secret | KB |
249
+| unbound.mod_memory | iterator, respip, validator, subnet, ipsec | KB |
250
+| unbound.mem_streamwait | streamwait | KB |
251
+| unbound.cache_count | infra, key, msg, rrset, dnscrypt_nonce, shared_secret | items |
252
+| unbound.type_queries | a dimension per query type | queries |
253
+| unbound.class_queries | a dimension per query class | queries |
254
+| unbound.opcode_queries | a dimension per query opcode | queries |
255
+| unbound.flag_queries | qr, aa, tc, rd, ra, z, ad, cd | queries |
256
+| unbound.rcode_answers | a dimension per reply rcode | replies |
257
+
258
+### Per thread
259
+
260
+These metrics refer to threads.
261
+
262
+This scope has no labels.
263
+
264
+Metrics:
265
+
266
+| Metric | Dimensions | Unit |
267
+|:------|:----------|:----|
268
+| unbound.thread_queries | queries | queries |
269
+| unbound.thread_queries_ip_ratelimited | ratelimited | queries |
270
+| unbound.thread_dnscrypt_queries | crypted, cert, cleartext, malformed | queries |
271
+| unbound.thread_cache | hits, miss | events |
272
+| unbound.thread_cache_percentage | hits, miss | percentage |
273
+| unbound.thread_prefetch | prefetches | prefetches |
274
+| unbound.thread_expired | expired | replies |
275
+| unbound.thread_zero_ttl_replies | zero_ttl | replies |
276
+| unbound.thread_recursive_replies | recursive | replies |
277
+| unbound.thread_recursion_time | avg, median | milliseconds |
278
+| unbound.thread_request_list_usage | avg, max | queries |
279
+| unbound.thread_current_request_list_usage | all, users | queries |
280
+| unbound.thread_request_list_jostle_list | overwritten, dropped | queries |
281
+| unbound.thread_tcpusage | usage | buffers |
282
+
283
+
284
+
285
## Troubleshooting
286
287
### Debug Mode
src/go/plugin/go.d/collector/upsd/integrations/ups_nut.md
+62
-62
@@ -45,68 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per ups
57
-
58
-These metrics refer to the UPS unit.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| ups_name | UPS name. |
65
-| battery_type | Battery type (chemistry). "battery.type" variable value. |
66
-| device_model | Device model. "device.mode" variable value. |
67
-| device_serial | Device serial number. "device.serial" variable value. |
68
-| device_manufacturer | Device manufacturer. "device.mfr" variable value. |
69
-| device_type | Device type (ups, pdu, scd, psu, ats). "device.type" variable value. |
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| upsd.ups_load | load | percentage |
76
-| upsd.ups_load_usage | load_usage | Watts |
77
-| upsd.ups_status | on_line, on_battery, low_battery, high_battery, replace_battery, charging, discharging, bypass, calibration, offline, overloaded, trim_input_voltage, boost_input_voltage, forced_shutdown, other | status |
78
-| upsd.ups_temperature | temperature | Celsius |
79
-| upsd.ups_battery_charge | charge | percentage |
80
-| upsd.ups_battery_estimated_runtime | runtime | seconds |
81
-| upsd.ups_battery_voltage | voltage | Volts |
82
-| upsd.ups_battery_voltage_nominal | nominal_voltage | Volts |
83
-| upsd.ups_input_voltage | voltage | Volts |
84
-| upsd.ups_input_voltage_nominal | nominal_voltage | Volts |
85
-| upsd.ups_input_current | current | Ampere |
86
-| upsd.ups_input_current_nominal | nominal_current | Ampere |
87
-| upsd.ups_input_frequency | frequency | Hz |
88
-| upsd.ups_input_frequency_nominal | nominal_frequency | Hz |
89
-| upsd.ups_output_voltage | voltage | Volts |
90
-| upsd.ups_output_voltage_nominal | nominal_voltage | Volts |
91
-| upsd.ups_output_current | current | Ampere |
92
-| upsd.ups_output_current_nominal | nominal_current | Ampere |
93
-| upsd.ups_output_frequency | frequency | Hz |
94
-| upsd.ups_output_frequency_nominal | nominal_frequency | Hz |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-
101
-The following alerts are available:
102
-
103
-| Alert name | On metric | Description |
104
-|:------------|:----------|:------------|
105
-| [ upsd_10min_ups_load ](https://github.com/netdata/netdata/blob/master/src/health/health.d/upsd.conf) | upsd.ups_load | UPS ${label:ups_name} average load over the last 10 minutes |
106
-| [ upsd_ups_battery_charge ](https://github.com/netdata/netdata/blob/master/src/health/health.d/upsd.conf) | upsd.ups_battery_charge | UPS ${label:ups_name} average battery charge over the last minute |
107
-| [ upsd_ups_last_collected_secs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/upsd.conf) | upsd.ups_load | UPS ${label:ups_name} number of seconds since the last successful data collection |
108
-
109
-
48
## Setup
49
50
@@ -226,6 +164,68 @@ jobs:
164
165
166
167
+## Alerts
168
+
169
+
170
+The following alerts are available:
171
+
172
+| Alert name | On metric | Description |
173
+|:------------|:----------|:------------|
174
+| [ upsd_10min_ups_load ](https://github.com/netdata/netdata/blob/master/src/health/health.d/upsd.conf) | upsd.ups_load | UPS ${label:ups_name} average load over the last 10 minutes |
175
+| [ upsd_ups_battery_charge ](https://github.com/netdata/netdata/blob/master/src/health/health.d/upsd.conf) | upsd.ups_battery_charge | UPS ${label:ups_name} average battery charge over the last minute |
176
+| [ upsd_ups_last_collected_secs ](https://github.com/netdata/netdata/blob/master/src/health/health.d/upsd.conf) | upsd.ups_load | UPS ${label:ups_name} number of seconds since the last successful data collection |
177
+
178
+
179
+## Metrics
180
+
181
+Metrics grouped by *scope*.
182
+
183
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
184
+
185
+
186
+
187
+### Per ups
188
+
189
+These metrics refer to the UPS unit.
190
+
191
+Labels:
192
+
193
+| Label | Description |
194
+|:-----------|:----------------|
195
+| ups_name | UPS name. |
196
+| battery_type | Battery type (chemistry). "battery.type" variable value. |
197
+| device_model | Device model. "device.mode" variable value. |
198
+| device_serial | Device serial number. "device.serial" variable value. |
199
+| device_manufacturer | Device manufacturer. "device.mfr" variable value. |
200
+| device_type | Device type (ups, pdu, scd, psu, ats). "device.type" variable value. |
201
+
202
+Metrics:
203
+
204
+| Metric | Dimensions | Unit |
205
+|:------|:----------|:----|
206
+| upsd.ups_load | load | percentage |
207
+| upsd.ups_load_usage | load_usage | Watts |
208
+| upsd.ups_status | on_line, on_battery, low_battery, high_battery, replace_battery, charging, discharging, bypass, calibration, offline, overloaded, trim_input_voltage, boost_input_voltage, forced_shutdown, other | status |
209
+| upsd.ups_temperature | temperature | Celsius |
210
+| upsd.ups_battery_charge | charge | percentage |
211
+| upsd.ups_battery_estimated_runtime | runtime | seconds |
212
+| upsd.ups_battery_voltage | voltage | Volts |
213
+| upsd.ups_battery_voltage_nominal | nominal_voltage | Volts |
214
+| upsd.ups_input_voltage | voltage | Volts |
215
+| upsd.ups_input_voltage_nominal | nominal_voltage | Volts |
216
+| upsd.ups_input_current | current | Ampere |
217
+| upsd.ups_input_current_nominal | nominal_current | Ampere |
218
+| upsd.ups_input_frequency | frequency | Hz |
219
+| upsd.ups_input_frequency_nominal | nominal_frequency | Hz |
220
+| upsd.ups_output_voltage | voltage | Volts |
221
+| upsd.ups_output_voltage_nominal | nominal_voltage | Volts |
222
+| upsd.ups_output_current | current | Ampere |
223
+| upsd.ups_output_current_nominal | nominal_current | Ampere |
224
+| upsd.ups_output_frequency | frequency | Hz |
225
+| upsd.ups_output_frequency_nominal | nominal_frequency | Hz |
226
+
227
+
228
+
229
## Troubleshooting
230
231
### Debug Mode
src/go/plugin/go.d/collector/uwsgi/integrations/uwsgi.md
+56
-56
@@ -49,62 +49,6 @@ The default configuration for this integration does not impose any limits on dat
49
50
The default configuration for this integration is not expected to impose a significant performance impact on the system.
51
52
-## Metrics
53
-
54
-Metrics grouped by *scope*.
55
-
56
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
57
-
58
-
59
-
60
-### Per uWSGI instance
61
-
62
-These metrics refer to the entire monitored application.
63
-
64
-This scope has no labels.
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| uwsgi.transmitted_data | tx | bytes/s |
71
-| uwsgi.requests | requests | requests/s |
72
-| uwsgi.harakiris | harakiris | harakiris/s |
73
-| uwsgi.respawns | respawns | respawns/s |
74
-
75
-### Per worker
76
-
77
-These metrics refer to the Worker process.
78
-
79
-Labels:
80
-
81
-| Label | Description |
82
-|:-----------|:----------------|
83
-| worker_id | Worker ID. |
84
-
85
-Metrics:
86
-
87
-| Metric | Dimensions | Unit |
88
-|:------|:----------|:----|
89
-| uwsgi.worker_transmitted_data | tx | bytes/s |
90
-| uwsgi.worker_requests | requests | requests/s |
91
-| uwsgi.worker_delta_requests | delta_requests | requests/s |
92
-| uwsgi.worker_average_request_time | avg | milliseconds |
93
-| uwsgi.worker_harakiris | harakiris | harakiris/s |
94
-| uwsgi.worker_exceptions | exceptions | exceptions/s |
95
-| uwsgi.worker_status | idle, busy, cheap, pause, sig | status |
96
-| uwsgi.worker_request_handling_status | accepting, not_accepting | status |
97
-| uwsgi.worker_respawns | respawns | respawns/s |
98
-| uwsgi.worker_memory_rss | rss | bytes |
99
-| uwsgi.worker_memory_vsz | vsz | bytes |
100
-
101
-
102
-
103
-## Alerts
104
-
105
-There are no alerts configured by default for this integration.
106
-
107
-
52
## Setup
53
54
@@ -226,6 +170,62 @@ jobs:
170
171
172
173
+## Alerts
174
+
175
+There are no alerts configured by default for this integration.
176
+
177
+
178
+## Metrics
179
+
180
+Metrics grouped by *scope*.
181
+
182
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
183
+
184
+
185
+
186
+### Per uWSGI instance
187
+
188
+These metrics refer to the entire monitored application.
189
+
190
+This scope has no labels.
191
+
192
+Metrics:
193
+
194
+| Metric | Dimensions | Unit |
195
+|:------|:----------|:----|
196
+| uwsgi.transmitted_data | tx | bytes/s |
197
+| uwsgi.requests | requests | requests/s |
198
+| uwsgi.harakiris | harakiris | harakiris/s |
199
+| uwsgi.respawns | respawns | respawns/s |
200
+
201
+### Per worker
202
+
203
+These metrics refer to the Worker process.
204
+
205
+Labels:
206
+
207
+| Label | Description |
208
+|:-----------|:----------------|
209
+| worker_id | Worker ID. |
210
+
211
+Metrics:
212
+
213
+| Metric | Dimensions | Unit |
214
+|:------|:----------|:----|
215
+| uwsgi.worker_transmitted_data | tx | bytes/s |
216
+| uwsgi.worker_requests | requests | requests/s |
217
+| uwsgi.worker_delta_requests | delta_requests | requests/s |
218
+| uwsgi.worker_average_request_time | avg | milliseconds |
219
+| uwsgi.worker_harakiris | harakiris | harakiris/s |
220
+| uwsgi.worker_exceptions | exceptions | exceptions/s |
221
+| uwsgi.worker_status | idle, busy, cheap, pause, sig | status |
222
+| uwsgi.worker_request_handling_status | accepting, not_accepting | status |
223
+| uwsgi.worker_respawns | respawns | respawns/s |
224
+| uwsgi.worker_memory_rss | rss | bytes |
225
+| uwsgi.worker_memory_vsz | vsz | bytes |
226
+
227
+
228
+
229
## Troubleshooting
230
231
### Debug Mode
src/go/plugin/go.d/collector/varnish/integrations/varnish.md
+64
-64
@@ -52,70 +52,6 @@ The default configuration for this integration does not impose any limits on dat
52
53
The default configuration for this integration is not expected to impose a significant performance impact on the system.
54
55
-## Metrics
56
-
57
-Metrics grouped by *scope*.
58
-
59
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
60
-
61
-
62
-
63
-### Per Varnish instance
64
-
65
-These metrics refer to the entire monitored application.
66
-
67
-This scope has no labels.
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| varnish.client_session_connections | accepted, dropped | connections/s |
74
-| varnish.client_requests | received | requests/s |
75
-| varnish.cache_hit_ratio_total | hit, miss, hitpass, hitmiss | percent |
76
-| varnish.cache_hit_ratio_delta | hit, miss, hitpass, hitmiss | percent |
77
-| varnish.cache_expired_objects | expired | objects/s |
78
-| varnish.cache_lru_activity | nuked, moved | objects/s |
79
-| varnish.threads | threads | threads |
80
-| varnish.thread_management_activity | created, failed, destroyed, limited | threads/s |
81
-| varnish.thread_queue_len | queue_length | threads |
82
-| varnish.backends_requests | sent | requests/s |
83
-| varnish.esi_parsing_issues | errors, warnings | issues/s |
84
-| varnish.mgmt_process_uptime | uptime | seconds |
85
-| varnish.child_process_uptime | uptime | seconds |
86
-
87
-### Per Backend
88
-
89
-These metrics refer to the Backend (VBE).
90
-
91
-This scope has no labels.
92
-
93
-Metrics:
94
-
95
-| Metric | Dimensions | Unit |
96
-|:------|:----------|:----|
97
-| varnish.backend_data_transfer | req_header, req_body, resp_header, resp_body | bytes/s |
98
-
99
-### Per Storage
100
-
101
-These metrics refer to the Storage (SMA, SMF, MSE).
102
-
103
-This scope has no labels.
104
-
105
-Metrics:
106
-
107
-| Metric | Dimensions | Unit |
108
-|:------|:----------|:----|
109
-| varnish.storage_space_usage | free, used | bytes |
110
-| varnish.storage_allocated_objects | allocated | objects |
111
-
112
-
113
-
114
-## Alerts
115
-
116
-There are no alerts configured by default for this integration.
117
-
118
-
55
## Setup
56
57
@@ -208,6 +144,70 @@ jobs:
144
```
145
146
147
+## Alerts
148
+
149
+There are no alerts configured by default for this integration.
150
+
151
+
152
+## Metrics
153
+
154
+Metrics grouped by *scope*.
155
+
156
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
157
+
158
+
159
+
160
+### Per Varnish instance
161
+
162
+These metrics refer to the entire monitored application.
163
+
164
+This scope has no labels.
165
+
166
+Metrics:
167
+
168
+| Metric | Dimensions | Unit |
169
+|:------|:----------|:----|
170
+| varnish.client_session_connections | accepted, dropped | connections/s |
171
+| varnish.client_requests | received | requests/s |
172
+| varnish.cache_hit_ratio_total | hit, miss, hitpass, hitmiss | percent |
173
+| varnish.cache_hit_ratio_delta | hit, miss, hitpass, hitmiss | percent |
174
+| varnish.cache_expired_objects | expired | objects/s |
175
+| varnish.cache_lru_activity | nuked, moved | objects/s |
176
+| varnish.threads | threads | threads |
177
+| varnish.thread_management_activity | created, failed, destroyed, limited | threads/s |
178
+| varnish.thread_queue_len | queue_length | threads |
179
+| varnish.backends_requests | sent | requests/s |
180
+| varnish.esi_parsing_issues | errors, warnings | issues/s |
181
+| varnish.mgmt_process_uptime | uptime | seconds |
182
+| varnish.child_process_uptime | uptime | seconds |
183
+
184
+### Per Backend
185
+
186
+These metrics refer to the Backend (VBE).
187
+
188
+This scope has no labels.
189
+
190
+Metrics:
191
+
192
+| Metric | Dimensions | Unit |
193
+|:------|:----------|:----|
194
+| varnish.backend_data_transfer | req_header, req_body, resp_header, resp_body | bytes/s |
195
+
196
+### Per Storage
197
+
198
+These metrics refer to the Storage (SMA, SMF, MSE).
199
+
200
+This scope has no labels.
201
+
202
+Metrics:
203
+
204
+| Metric | Dimensions | Unit |
205
+|:------|:----------|:----|
206
+| varnish.storage_space_usage | free, used | bytes |
207
+| varnish.storage_allocated_objects | allocated | objects |
208
+
209
+
210
+
211
## Troubleshooting
212
213
### Debug Mode
src/go/plugin/go.d/collector/vcsa/integrations/vcenter_server_appliance.md
+89
-89
@@ -45,95 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per vCenter Server Appliance instance
57
-
58
-These metrics refer to the entire monitored application.
59
-<details>
60
-<summary>See health statuses</summary>
61
-Overall System Health:
62
-
63
-| Status | Description |
64
-|:-------:|:-------------------------------------------------------------------------------------------------------------------------|
65
-| green | All components in the appliance are healthy. |
66
-| yellow | One or more components in the appliance might become overloaded soon. |
67
-| orange | One or more components in the appliance might be degraded. |
68
-| red | One or more components in the appliance might be in an unusable status and the appliance might become unresponsive soon. |
69
-| gray | No health data is available. |
70
-| unknown | Collector failed to decode status. |
71
-
72
-Components Health:
73
-
74
-| Status | Description |
75
-|:-------:|:-------------------------------------------------------------|
76
-| green | The component is healthy. |
77
-| yellow | The component is healthy, but may have some problems. |
78
-| orange | The component is degraded, and may have serious problems. |
79
-| red | The component is unavailable, or will stop functioning soon. |
80
-| gray | No health data is available. |
81
-| unknown | Collector failed to decode status. |
82
-
83
-Software Updates Health:
84
-
85
-| Status | Description |
86
-|:-------:|:-----------------------------------------------------|
87
-| green | No updates available. |
88
-| orange | Non-security patches might be available. |
89
-| red | Security patches might be available. |
90
-| gray | An error retrieving information on software updates. |
91
-| unknown | Collector failed to decode status. |
92
-
93
-</details>
94
-
95
-
96
-This scope has no labels.
97
-
98
-Metrics:
99
-
100
-| Metric | Dimensions | Unit |
101
-|:------|:----------|:----|
102
-| vcsa.system_health_status | green, red, yellow, orange, gray, unknown | status |
103
-| vcsa.applmgmt_health_status | green, red, yellow, orange, gray, unknown | status |
104
-| vcsa.load_health_status | green, red, yellow, orange, gray, unknown | status |
105
-| vcsa.mem_health_status | green, red, yellow, orange, gray, unknown | status |
106
-| vcsa.swap_health_status | green, red, yellow, orange, gray, unknown | status |
107
-| vcsa.database_storage_health_status | green, red, yellow, orange, gray, unknown | status |
108
-| vcsa.storage_health_status | green, red, yellow, orange, gray, unknown | status |
109
-| vcsa.software_packages_health_status | green, red, orange, gray, unknown | status |
110
-
111
-
112
-
113
-## Alerts
114
-
115
-
116
-The following alerts are available:
117
-
118
-| Alert name | On metric | Description |
119
-|:------------|:----------|:------------|
120
-| [ vcsa_system_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.system_health_status | VCSA overall system status is orange. One or more components are degraded. |
121
-| [ vcsa_system_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.system_health_status | VCSA overall system status is red. One or more components are unavailable or will stop functioning soon. |
122
-| [ vcsa_applmgmt_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.applmgmt_health_status | VCSA ApplMgmt component status is orange. It is degraded, and may have serious problems. |
123
-| [ vcsa_applmgmt_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.applmgmt_health_status | VCSA ApplMgmt component status is red. It is unavailable, or will stop functioning soon. |
124
-| [ vcsa_load_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.load_health_status | VCSA Load component status is orange. It is degraded, and may have serious problems. |
125
-| [ vcsa_load_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.load_health_status | VCSA Load component status is red. It is unavailable, or will stop functioning soon. |
126
-| [ vcsa_mem_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.mem_health_status | VCSA Memory component status is orange. It is degraded, and may have serious problems. |
127
-| [ vcsa_mem_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.mem_health_status | VCSA Memory component status is red. It is unavailable, or will stop functioning soon. |
128
-| [ vcsa_swap_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.swap_health_status | VCSA Swap component status is orange. It is degraded, and may have serious problems. |
129
-| [ vcsa_swap_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.swap_health_status | VCSA Swap component status is red. It is unavailable, or will stop functioning soon. |
130
-| [ vcsa_database_storage_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.database_storage_health_status | VCSA Database Storage component status is orange. It is degraded, and may have serious problems. |
131
-| [ vcsa_database_storage_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.database_storage_health_status | VCSA Database Storage component status is red. It is unavailable, or will stop functioning soon. |
132
-| [ vcsa_storage_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.storage_health_status | VCSA Storage component status is orange. It is degraded, and may have serious problems. |
133
-| [ vcsa_storage_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.storage_health_status | VCSA Storage component status is red. It is unavailable, or will stop functioning soon. |
134
-| [ vcsa_software_packages_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.software_packages_health_status | VCSA software packages security updates are available. |
135
-
136
-
48
## Setup
49
50
@@ -272,6 +183,95 @@ jobs:
183
184
185
186
+## Alerts
187
+
188
+
189
+The following alerts are available:
190
+
191
+| Alert name | On metric | Description |
192
+|:------------|:----------|:------------|
193
+| [ vcsa_system_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.system_health_status | VCSA overall system status is orange. One or more components are degraded. |
194
+| [ vcsa_system_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.system_health_status | VCSA overall system status is red. One or more components are unavailable or will stop functioning soon. |
195
+| [ vcsa_applmgmt_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.applmgmt_health_status | VCSA ApplMgmt component status is orange. It is degraded, and may have serious problems. |
196
+| [ vcsa_applmgmt_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.applmgmt_health_status | VCSA ApplMgmt component status is red. It is unavailable, or will stop functioning soon. |
197
+| [ vcsa_load_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.load_health_status | VCSA Load component status is orange. It is degraded, and may have serious problems. |
198
+| [ vcsa_load_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.load_health_status | VCSA Load component status is red. It is unavailable, or will stop functioning soon. |
199
+| [ vcsa_mem_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.mem_health_status | VCSA Memory component status is orange. It is degraded, and may have serious problems. |
200
+| [ vcsa_mem_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.mem_health_status | VCSA Memory component status is red. It is unavailable, or will stop functioning soon. |
201
+| [ vcsa_swap_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.swap_health_status | VCSA Swap component status is orange. It is degraded, and may have serious problems. |
202
+| [ vcsa_swap_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.swap_health_status | VCSA Swap component status is red. It is unavailable, or will stop functioning soon. |
203
+| [ vcsa_database_storage_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.database_storage_health_status | VCSA Database Storage component status is orange. It is degraded, and may have serious problems. |
204
+| [ vcsa_database_storage_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.database_storage_health_status | VCSA Database Storage component status is red. It is unavailable, or will stop functioning soon. |
205
+| [ vcsa_storage_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.storage_health_status | VCSA Storage component status is orange. It is degraded, and may have serious problems. |
206
+| [ vcsa_storage_health_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.storage_health_status | VCSA Storage component status is red. It is unavailable, or will stop functioning soon. |
207
+| [ vcsa_software_packages_health_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vcsa.conf) | vcsa.software_packages_health_status | VCSA software packages security updates are available. |
208
+
209
+
210
+## Metrics
211
+
212
+Metrics grouped by *scope*.
213
+
214
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
215
+
216
+
217
+
218
+### Per vCenter Server Appliance instance
219
+
220
+These metrics refer to the entire monitored application.
221
+<details>
222
+<summary>See health statuses</summary>
223
+Overall System Health:
224
+
225
+| Status | Description |
226
+|:-------:|:-------------------------------------------------------------------------------------------------------------------------|
227
+| green | All components in the appliance are healthy. |
228
+| yellow | One or more components in the appliance might become overloaded soon. |
229
+| orange | One or more components in the appliance might be degraded. |
230
+| red | One or more components in the appliance might be in an unusable status and the appliance might become unresponsive soon. |
231
+| gray | No health data is available. |
232
+| unknown | Collector failed to decode status. |
233
+
234
+Components Health:
235
+
236
+| Status | Description |
237
+|:-------:|:-------------------------------------------------------------|
238
+| green | The component is healthy. |
239
+| yellow | The component is healthy, but may have some problems. |
240
+| orange | The component is degraded, and may have serious problems. |
241
+| red | The component is unavailable, or will stop functioning soon. |
242
+| gray | No health data is available. |
243
+| unknown | Collector failed to decode status. |
244
+
245
+Software Updates Health:
246
+
247
+| Status | Description |
248
+|:-------:|:-----------------------------------------------------|
249
+| green | No updates available. |
250
+| orange | Non-security patches might be available. |
251
+| red | Security patches might be available. |
252
+| gray | An error retrieving information on software updates. |
253
+| unknown | Collector failed to decode status. |
254
+
255
+</details>
256
+
257
+
258
+This scope has no labels.
259
+
260
+Metrics:
261
+
262
+| Metric | Dimensions | Unit |
263
+|:------|:----------|:----|
264
+| vcsa.system_health_status | green, red, yellow, orange, gray, unknown | status |
265
+| vcsa.applmgmt_health_status | green, red, yellow, orange, gray, unknown | status |
266
+| vcsa.load_health_status | green, red, yellow, orange, gray, unknown | status |
267
+| vcsa.mem_health_status | green, red, yellow, orange, gray, unknown | status |
268
+| vcsa.swap_health_status | green, red, yellow, orange, gray, unknown | status |
269
+| vcsa.database_storage_health_status | green, red, yellow, orange, gray, unknown | status |
270
+| vcsa.storage_health_status | green, red, yellow, orange, gray, unknown | status |
271
+| vcsa.software_packages_health_status | green, red, orange, gray, unknown | status |
272
+
273
+
274
+
275
## Troubleshooting
276
277
### Debug Mode
src/go/plugin/go.d/collector/vernemq/integrations/vernemq.md
+140
-140
@@ -45,146 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per node
57
-
58
-These metrics refer to the VerneMQ node.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| node | The value of this label is identical to the value of the "node" label exposed by VerneMQ. |
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| vernemq.node_socket | open | sockets |
71
-| vernemq.node_socket_operations | open, close | sockets/s |
72
-| vernemq.node_client_keepalive_expired | closed | sockets/s |
73
-| vernemq.node_socket_close_timeout | closed | sockets/s |
74
-| vernemq.node_socket_errors | errors | errors/s |
75
-| vernemq.node_queue_processes | queue_processes | queue processes |
76
-| vernemq.node_queue_processes_operations | setup, teardown | events/s |
77
-| vernemq.node_queue_process_init_from_storage | queue_processes | queue processes/s |
78
-| vernemq.node_queue_messages | received, sent | messages/s |
79
-| vernemq.node_queued_messages | queued | messages |
80
-| vernemq.node_queue_undelivered_messages | dropped, expired, unhandled | messages/s |
81
-| vernemq.node_router_subscriptions | subscriptions | subscriptions |
82
-| vernemq.node_router_matched_subscriptions | local, remote | subscriptions/s |
83
-| vernemq.node_router_memory | used | bytes |
84
-| vernemq.node_average_scheduler_utilization | utilization | percentage |
85
-| vernemq.node_system_processes | processes | processes |
86
-| vernemq.node_system_reductions | reductions | ops/s |
87
-| vernemq.node_system_context_switches | context_switches | ops/s |
88
-| vernemq.node_system_io | received, sent | bytes/s |
89
-| vernemq.node_system_run_queue | ready | processes |
90
-| vernemq.node_system_gc_count | gc | ops/s |
91
-| vernemq.node_system_gc_words_reclaimed | words_reclaimed | ops/s |
92
-| vernemq.node_system_allocated_memory | processes, system | bytes |
93
-| vernemq.node_traffic | received, sent | bytes/s |
94
-| vernemq.node_retain_messages | messages | messages |
95
-| vernemq.node_retain_memory | used | bytes |
96
-| vernemq.node_cluster_traffic | received, sent | bytes/s |
97
-| vernemq.node_cluster_dropped | dropped | bytes/s |
98
-| vernemq.node_netsplit_unresolved | unresolved | netsplits |
99
-| vernemq.node_netsplits | resolved, detected | netsplits/s |
100
-| vernemq.node_uptime | time | seconds |
101
-
102
-### Per mqtt
103
-
104
-These metrics are specific to the used MQTT protocol version.
105
-
106
-Labels:
107
-
108
-| Label | Description |
109
-|:-----------|:----------------|
110
-| node | The value of this label is identical to the value of the "node" label exposed by VerneMQ. |
111
-| mqtt_version | MQTT version. |
112
-
113
-Metrics:
114
-
115
-| Metric | Dimensions | Unit |
116
-|:------|:----------|:----|
117
-| vernemq.node_mqtt_auth | received, sent | packets/s |
118
-| vernemq.node_mqtt_auth_received_by_reason_code | success, continue_authentication, reauthenticate | packets/s |
119
-| vernemq.node_mqtt_auth_sent_by_reason_code | success, continue_authentication, reauthenticate | packets/s |
120
-| vernemq.node_mqtt_connect | connect, connack | packets/s |
121
-| vernemq.node_mqtt_connack_sent_by_return_code | success, unsupported_protocol_version, client_identifier_not_valid, server_unavailable, bad_username_or_password, not_authorized | packets/s |
122
-| vernemq.node_mqtt_connack_sent_by_reason_code | success, unspecified_error, malformed_packet, protocol_error, impl_specific_error, unsupported_protocol_version, client_identifier_not_valid, bad_username_or_password, not_authorized, server_unavailable, server_busy, banned, bad_authentication_method, topic_name_invalid, packet_too_large, quota_exceeded, payload_format_invalid, retain_not_supported, qos_not_supported, use_another_server, server_moved, connection_rate_exceeded | packets/s |
123
-| vernemq.node_mqtt_disconnect | received, sent | packets/s |
124
-| vernemq.node_mqtt_disconnect_received_by_reason_code | normal_disconnect, disconnect_with_will_msg, unspecified_error, malformed_packet, protocol_error, impl_specific_error, topic_name_invalid, receive_max_exceeded, topic_alias_invalid, packet_too_large, message_rate_too_high, quota_exceeded, administrative_action, payload_format_invalid | packets/s |
125
-| node_mqtt_disconnect_sent_by_reason_code | normal_disconnect, unspecified_error, malformed_packet, protocol_error, impl_specific_error, not_authorized, server_busy, server_shutting_down, keep_alive_timeout, session_taken_over, topic_filter_invalid, topic_name_invalid, receive_max_exceeded, topic_alias_invalid, packet_too_large, message_rate_too_high, quota_exceeded, administrative_action, payload_format_invalid, retain_not_supported, qos_not_supported, use_another_server, server_moved, shared_subs_not_supported, connection_rate_exceeded, max_connect_time, subscription_ids_not_supported, wildcard_subs_not_supported | packets/s |
126
-| vernemq.node_mqtt_subscribe | subscribe, suback | packets/s |
127
-| vernemq.node_mqtt_subscribe_error | subscribe | errors/s |
128
-| vernemq.node_mqtt_subscribe_auth_error | subscribe_auth | errors/s |
129
-| vernemq.node_mqtt_unsubscribe | unsubscribe, unsuback | packets/s |
130
-| vernemq.node_mqtt_unsubscribe_error | unsubscribe | errors/s |
131
-| vernemq.node_mqtt_publish | received, sent | packets/s |
132
-| vernemq.node_mqtt_publish_errors | publish | errors/s |
133
-| vernemq.node_mqtt_publish_auth_errors | publish_auth | errors/s |
134
-| vernemq.node_mqtt_puback | received, sent | packets/s |
135
-| vernemq.node_mqtt_puback_received_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
136
-| vernemq.node_mqtt_puback_sent_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
137
-| vernemq.node_mqtt_puback_invalid_error | unexpected | messages/s |
138
-| vernemq.node_mqtt_pubrec | received, sent | packets/s |
139
-| vernemq.node_mqtt_pubrec_received_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
140
-| vernemq.node_mqtt_pubrec_sent_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
141
-| vernemq.node_mqtt_pubrec_invalid_error | unexpected | messages/s |
142
-| vernemq.node_mqtt_pubrel | received, sent | packets/s |
143
-| vernemq.node_mqtt_pubrel_received_by_reason_code | success, packet_id_not_found | packets/s |
144
-| vernemq.node_mqtt_pubrel_sent_by_reason_code | success, packet_id_not_found | packets/s |
145
-| vernemq.node_mqtt_pubcomp | received, sent | packets/s |
146
-| vernemq.node_mqtt_pubcomp_received_by_reason_code | success, packet_id_not_found | packets/s |
147
-| vernemq.node_mqtt_pubcomp_sent_by_reason_cod | success, packet_id_not_found | packets/s |
148
-| vernemq.node_mqtt_pubcomp_invalid_error | unexpected | messages/s |
149
-| vernemq.node_mqtt_ping | pingreq, pingresp | packets/s |
150
-
151
-
152
-
153
-## Alerts
154
-
155
-
156
-The following alerts are available:
157
-
158
-| Alert name | On metric | Description |
159
-|:------------|:----------|:------------|
160
-| [ vernemq_socket_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_socket_errors | Node ${label:node} socket errors in the last minute |
161
-| [ vernemq_queue_message_drop ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_queue_undelivered_messages | Node ${label:node} dropped messages due to full queues in the last minute |
162
-| [ vernemq_queue_message_expired ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_queue_undelivered_messages | Node ${label:node} expired before delivery messages in the last minute |
163
-| [ vernemq_queue_message_unhandled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_queue_undelivered_messages | Node ${label:node} unhandled messages in the last minute |
164
-| [ vernemq_average_scheduler_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_average_scheduler_utilization | Node ${label:node} scheduler utilization over the last 10 minutes |
165
-| [ vernemq_cluster_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_cluster_dropped | Node ${label:node} traffic dropped during communication with the cluster nodes in the last minute |
166
-| [ vernemq_netsplits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_netsplits | Node ${label:node} detected netsplits (split brain) in the last minute |
167
-| [ vernemq_mqtt_connack_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_connack_sent_by_reason_code | Node ${label:node} unsuccessful sent v5 CONNACK packets in the last minute |
168
-| [ vernemq_mqtt_disconnect_received_reason_not_normal ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_disconnect_received_by_reason_code | Node ${label:node} received not normal v5 DISCONNECT packets in the last minute |
169
-| [ vernemq_mqtt_disconnect_sent_reason_not_normal ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_disconnect_sent_by_reason_code | Node ${label:node} sent not normal v5 DISCONNECT packets in the last minute |
170
-| [ vernemq_mqtt_subscribe_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_subscribe_error | Node ${label:node} mqtt v${label:mqtt_version} failed SUBSCRIBE operations in the last minute |
171
-| [ vernemq_mqtt_subscribe_auth_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_subscribe_auth_error | Node ${label:node} mqtt v${label:mqtt_version} unauthorized SUBSCRIBE attempts in the last minute |
172
-| [ vernemq_mqtt_unsubscribe_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_unsubscribe_error | Node ${label:node} mqtt v${label:mqtt_version} failed UNSUBSCRIBE operations in the last minute |
173
-| [ vernemq_mqtt_publish_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_publish_errors | Node ${label:node} mqtt v${label:mqtt_version} failed PUBLISH operations in the last minute |
174
-| [ vernemq_mqtt_publish_auth_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_publish_auth_errors | Node ${label:node} mqtt v${label:mqtt_version} unauthorized PUBLISH attempts in the last minute |
175
-| [ vernemq_mqtt_puback_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_puback_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBACK packets in the last minute |
176
-| [ vernemq_mqtt_puback_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_puback_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBACK packets in the last minute |
177
-| [ vernemq_mqtt_puback_unexpected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_puback_invalid_error | Node ${label:node} mqtt v${label:mqtt_version} received unexpected PUBACK messages in the last minute |
178
-| [ vernemq_mqtt_pubrec_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrec_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBREC packets in the last minute |
179
-| [ vernemq_mqtt_pubrec_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrec_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBREC packets in the last minute |
180
-| [ vernemq_mqtt_pubrec_invalid_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrec_invalid_error | Node ${label:node} mqtt v${label:mqtt_version} received invalid PUBREC packets in the last minute |
181
-| [ vernemq_mqtt_pubrel_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrel_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBREL packets in the last minute |
182
-| [ vernemq_mqtt_pubrel_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrel_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBREL packets in the last minute |
183
-| [ vernemq_mqtt_pubcomp_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubcomp_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBCOMP packets in the last minute |
184
-| [ vernemq_mqtt_pubcomp_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubcomp_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBCOMP packets in the last minute |
185
-| [ vernemq_mqtt_pubcomp_unexpected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubcomp_invalid_error | Node ${label:node} mqtt v${label:mqtt_version} received unexpected PUBCOMP packets in the last minute |
186
-
187
-
48
## Setup
49
50
@@ -333,6 +193,146 @@ jobs:
193
194
195
196
+## Alerts
197
+
198
+
199
+The following alerts are available:
200
+
201
+| Alert name | On metric | Description |
202
+|:------------|:----------|:------------|
203
+| [ vernemq_socket_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_socket_errors | Node ${label:node} socket errors in the last minute |
204
+| [ vernemq_queue_message_drop ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_queue_undelivered_messages | Node ${label:node} dropped messages due to full queues in the last minute |
205
+| [ vernemq_queue_message_expired ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_queue_undelivered_messages | Node ${label:node} expired before delivery messages in the last minute |
206
+| [ vernemq_queue_message_unhandled ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_queue_undelivered_messages | Node ${label:node} unhandled messages in the last minute |
207
+| [ vernemq_average_scheduler_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_average_scheduler_utilization | Node ${label:node} scheduler utilization over the last 10 minutes |
208
+| [ vernemq_cluster_dropped ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_cluster_dropped | Node ${label:node} traffic dropped during communication with the cluster nodes in the last minute |
209
+| [ vernemq_netsplits ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_netsplits | Node ${label:node} detected netsplits (split brain) in the last minute |
210
+| [ vernemq_mqtt_connack_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_connack_sent_by_reason_code | Node ${label:node} unsuccessful sent v5 CONNACK packets in the last minute |
211
+| [ vernemq_mqtt_disconnect_received_reason_not_normal ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_disconnect_received_by_reason_code | Node ${label:node} received not normal v5 DISCONNECT packets in the last minute |
212
+| [ vernemq_mqtt_disconnect_sent_reason_not_normal ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_disconnect_sent_by_reason_code | Node ${label:node} sent not normal v5 DISCONNECT packets in the last minute |
213
+| [ vernemq_mqtt_subscribe_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_subscribe_error | Node ${label:node} mqtt v${label:mqtt_version} failed SUBSCRIBE operations in the last minute |
214
+| [ vernemq_mqtt_subscribe_auth_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_subscribe_auth_error | Node ${label:node} mqtt v${label:mqtt_version} unauthorized SUBSCRIBE attempts in the last minute |
215
+| [ vernemq_mqtt_unsubscribe_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_unsubscribe_error | Node ${label:node} mqtt v${label:mqtt_version} failed UNSUBSCRIBE operations in the last minute |
216
+| [ vernemq_mqtt_publish_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_publish_errors | Node ${label:node} mqtt v${label:mqtt_version} failed PUBLISH operations in the last minute |
217
+| [ vernemq_mqtt_publish_auth_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_publish_auth_errors | Node ${label:node} mqtt v${label:mqtt_version} unauthorized PUBLISH attempts in the last minute |
218
+| [ vernemq_mqtt_puback_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_puback_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBACK packets in the last minute |
219
+| [ vernemq_mqtt_puback_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_puback_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBACK packets in the last minute |
220
+| [ vernemq_mqtt_puback_unexpected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_puback_invalid_error | Node ${label:node} mqtt v${label:mqtt_version} received unexpected PUBACK messages in the last minute |
221
+| [ vernemq_mqtt_pubrec_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrec_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBREC packets in the last minute |
222
+| [ vernemq_mqtt_pubrec_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrec_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBREC packets in the last minute |
223
+| [ vernemq_mqtt_pubrec_invalid_error ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrec_invalid_error | Node ${label:node} mqtt v${label:mqtt_version} received invalid PUBREC packets in the last minute |
224
+| [ vernemq_mqtt_pubrel_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrel_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBREL packets in the last minute |
225
+| [ vernemq_mqtt_pubrel_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubrel_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBREL packets in the last minute |
226
+| [ vernemq_mqtt_pubcomp_received_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubcomp_received_by_reason_code | Node ${label:node} mqtt v5 received unsuccessful PUBCOMP packets in the last minute |
227
+| [ vernemq_mqtt_pubcomp_sent_reason_unsuccessful ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubcomp_sent_by_reason_code | Node ${label:node} mqtt v5 unsuccessful sent PUBCOMP packets in the last minute |
228
+| [ vernemq_mqtt_pubcomp_unexpected ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vernemq.conf) | vernemq.node_mqtt_pubcomp_invalid_error | Node ${label:node} mqtt v${label:mqtt_version} received unexpected PUBCOMP packets in the last minute |
229
+
230
+
231
+## Metrics
232
+
233
+Metrics grouped by *scope*.
234
+
235
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
236
+
237
+
238
+
239
+### Per node
240
+
241
+These metrics refer to the VerneMQ node.
242
+
243
+Labels:
244
+
245
+| Label | Description |
246
+|:-----------|:----------------|
247
+| node | The value of this label is identical to the value of the "node" label exposed by VerneMQ. |
248
+
249
+Metrics:
250
+
251
+| Metric | Dimensions | Unit |
252
+|:------|:----------|:----|
253
+| vernemq.node_socket | open | sockets |
254
+| vernemq.node_socket_operations | open, close | sockets/s |
255
+| vernemq.node_client_keepalive_expired | closed | sockets/s |
256
+| vernemq.node_socket_close_timeout | closed | sockets/s |
257
+| vernemq.node_socket_errors | errors | errors/s |
258
+| vernemq.node_queue_processes | queue_processes | queue processes |
259
+| vernemq.node_queue_processes_operations | setup, teardown | events/s |
260
+| vernemq.node_queue_process_init_from_storage | queue_processes | queue processes/s |
261
+| vernemq.node_queue_messages | received, sent | messages/s |
262
+| vernemq.node_queued_messages | queued | messages |
263
+| vernemq.node_queue_undelivered_messages | dropped, expired, unhandled | messages/s |
264
+| vernemq.node_router_subscriptions | subscriptions | subscriptions |
265
+| vernemq.node_router_matched_subscriptions | local, remote | subscriptions/s |
266
+| vernemq.node_router_memory | used | bytes |
267
+| vernemq.node_average_scheduler_utilization | utilization | percentage |
268
+| vernemq.node_system_processes | processes | processes |
269
+| vernemq.node_system_reductions | reductions | ops/s |
270
+| vernemq.node_system_context_switches | context_switches | ops/s |
271
+| vernemq.node_system_io | received, sent | bytes/s |
272
+| vernemq.node_system_run_queue | ready | processes |
273
+| vernemq.node_system_gc_count | gc | ops/s |
274
+| vernemq.node_system_gc_words_reclaimed | words_reclaimed | ops/s |
275
+| vernemq.node_system_allocated_memory | processes, system | bytes |
276
+| vernemq.node_traffic | received, sent | bytes/s |
277
+| vernemq.node_retain_messages | messages | messages |
278
+| vernemq.node_retain_memory | used | bytes |
279
+| vernemq.node_cluster_traffic | received, sent | bytes/s |
280
+| vernemq.node_cluster_dropped | dropped | bytes/s |
281
+| vernemq.node_netsplit_unresolved | unresolved | netsplits |
282
+| vernemq.node_netsplits | resolved, detected | netsplits/s |
283
+| vernemq.node_uptime | time | seconds |
284
+
285
+### Per mqtt
286
+
287
+These metrics are specific to the used MQTT protocol version.
288
+
289
+Labels:
290
+
291
+| Label | Description |
292
+|:-----------|:----------------|
293
+| node | The value of this label is identical to the value of the "node" label exposed by VerneMQ. |
294
+| mqtt_version | MQTT version. |
295
+
296
+Metrics:
297
+
298
+| Metric | Dimensions | Unit |
299
+|:------|:----------|:----|
300
+| vernemq.node_mqtt_auth | received, sent | packets/s |
301
+| vernemq.node_mqtt_auth_received_by_reason_code | success, continue_authentication, reauthenticate | packets/s |
302
+| vernemq.node_mqtt_auth_sent_by_reason_code | success, continue_authentication, reauthenticate | packets/s |
303
+| vernemq.node_mqtt_connect | connect, connack | packets/s |
304
+| vernemq.node_mqtt_connack_sent_by_return_code | success, unsupported_protocol_version, client_identifier_not_valid, server_unavailable, bad_username_or_password, not_authorized | packets/s |
305
+| vernemq.node_mqtt_connack_sent_by_reason_code | success, unspecified_error, malformed_packet, protocol_error, impl_specific_error, unsupported_protocol_version, client_identifier_not_valid, bad_username_or_password, not_authorized, server_unavailable, server_busy, banned, bad_authentication_method, topic_name_invalid, packet_too_large, quota_exceeded, payload_format_invalid, retain_not_supported, qos_not_supported, use_another_server, server_moved, connection_rate_exceeded | packets/s |
306
+| vernemq.node_mqtt_disconnect | received, sent | packets/s |
307
+| vernemq.node_mqtt_disconnect_received_by_reason_code | normal_disconnect, disconnect_with_will_msg, unspecified_error, malformed_packet, protocol_error, impl_specific_error, topic_name_invalid, receive_max_exceeded, topic_alias_invalid, packet_too_large, message_rate_too_high, quota_exceeded, administrative_action, payload_format_invalid | packets/s |
308
+| node_mqtt_disconnect_sent_by_reason_code | normal_disconnect, unspecified_error, malformed_packet, protocol_error, impl_specific_error, not_authorized, server_busy, server_shutting_down, keep_alive_timeout, session_taken_over, topic_filter_invalid, topic_name_invalid, receive_max_exceeded, topic_alias_invalid, packet_too_large, message_rate_too_high, quota_exceeded, administrative_action, payload_format_invalid, retain_not_supported, qos_not_supported, use_another_server, server_moved, shared_subs_not_supported, connection_rate_exceeded, max_connect_time, subscription_ids_not_supported, wildcard_subs_not_supported | packets/s |
309
+| vernemq.node_mqtt_subscribe | subscribe, suback | packets/s |
310
+| vernemq.node_mqtt_subscribe_error | subscribe | errors/s |
311
+| vernemq.node_mqtt_subscribe_auth_error | subscribe_auth | errors/s |
312
+| vernemq.node_mqtt_unsubscribe | unsubscribe, unsuback | packets/s |
313
+| vernemq.node_mqtt_unsubscribe_error | unsubscribe | errors/s |
314
+| vernemq.node_mqtt_publish | received, sent | packets/s |
315
+| vernemq.node_mqtt_publish_errors | publish | errors/s |
316
+| vernemq.node_mqtt_publish_auth_errors | publish_auth | errors/s |
317
+| vernemq.node_mqtt_puback | received, sent | packets/s |
318
+| vernemq.node_mqtt_puback_received_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
319
+| vernemq.node_mqtt_puback_sent_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
320
+| vernemq.node_mqtt_puback_invalid_error | unexpected | messages/s |
321
+| vernemq.node_mqtt_pubrec | received, sent | packets/s |
322
+| vernemq.node_mqtt_pubrec_received_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
323
+| vernemq.node_mqtt_pubrec_sent_by_reason_code | success, no_matching_subscribers, unspecified_error, impl_specific_error, not_authorized, topic_name_invalid, packet_id_in_use, quota_exceeded, payload_format_invalid | packets/s |
324
+| vernemq.node_mqtt_pubrec_invalid_error | unexpected | messages/s |
325
+| vernemq.node_mqtt_pubrel | received, sent | packets/s |
326
+| vernemq.node_mqtt_pubrel_received_by_reason_code | success, packet_id_not_found | packets/s |
327
+| vernemq.node_mqtt_pubrel_sent_by_reason_code | success, packet_id_not_found | packets/s |
328
+| vernemq.node_mqtt_pubcomp | received, sent | packets/s |
329
+| vernemq.node_mqtt_pubcomp_received_by_reason_code | success, packet_id_not_found | packets/s |
330
+| vernemq.node_mqtt_pubcomp_sent_by_reason_cod | success, packet_id_not_found | packets/s |
331
+| vernemq.node_mqtt_pubcomp_invalid_error | unexpected | messages/s |
332
+| vernemq.node_mqtt_ping | pingreq, pingresp | packets/s |
333
+
334
+
335
+
336
## Troubleshooting
337
338
### Debug Mode
src/go/plugin/go.d/collector/vsphere/integrations/vmware_vcenter_server.md
+174
-174
@@ -91,180 +91,6 @@ There you can see that discovering took `525.614041ms`, and collecting metrics t
91
`update_every` and `timeout` parameters should be adjusted based on these numbers.
92
93
94
-## Metrics
95
-
96
-Metrics grouped by *scope*.
97
-
98
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
99
-
100
-
101
-
102
-### Per virtual machine
103
-
104
-These metrics refer to the Virtual Machine.
105
-
106
-Labels:
107
-
108
-| Label | Description |
109
-|:-----------|:----------------|
110
-| datacenter | Datacenter name |
111
-| cluster | Cluster name |
112
-| host | Host name |
113
-| vm | Virtual Machine name |
114
-
115
-Metrics:
116
-
117
-| Metric | Dimensions | Unit |
118
-|:------|:----------|:----|
119
-| vsphere.vm_cpu_utilization | used | percentage |
120
-| vsphere.vm_mem_utilization | used | percentage |
121
-| vsphere.vm_mem_usage | granted, consumed, active, shared | KiB |
122
-| vsphere.vm_mem_swap_usage | swapped | KiB |
123
-| vsphere.vm_mem_swap_io | in, out | KiB/s |
124
-| vsphere.vm_disk_io | read, write | KiB/s |
125
-| vsphere.vm_disk_max_latency | latency | milliseconds |
126
-| vsphere.vm_net_traffic | received, sent | KiB/s |
127
-| vsphere.vm_net_packets | received, sent | packets |
128
-| vsphere.vm_net_drops | received, sent | packets |
129
-| vsphere.vm_overall_status | green, red, yellow, gray | status |
130
-| vsphere.vm_system_uptime | uptime | seconds |
131
-
132
-### Per host
133
-
134
-These metrics refer to the ESXi host.
135
-
136
-Labels:
137
-
138
-| Label | Description |
139
-|:-----------|:----------------|
140
-| datacenter | Datacenter name |
141
-| cluster | Cluster name |
142
-| host | Host name |
143
-
144
-Metrics:
145
-
146
-| Metric | Dimensions | Unit |
147
-|:------|:----------|:----|
148
-| vsphere.host_cpu_utilization | used | percentage |
149
-| vsphere.host_mem_utilization | used | percentage |
150
-| vsphere.host_mem_usage | granted, consumed, active, shared, sharedcommon | KiB |
151
-| vsphere.host_mem_swap_io | in, out | KiB/s |
152
-| vsphere.host_disk_io | read, write | KiB/s |
153
-| vsphere.host_disk_max_latency | latency | milliseconds |
154
-| vsphere.host_net_traffic | received, sent | KiB/s |
155
-| vsphere.host_net_packets | received, sent | packets |
156
-| vsphere.host_net_drops | received, sent | packets |
157
-| vsphere.host_net_errors | received, sent | errors |
158
-| vsphere.host_overall_status | green, red, yellow, gray | status |
159
-| vsphere.host_system_uptime | uptime | seconds |
160
-
161
-### Per datastore
162
-
163
-These metrics refer to the Datastore.
164
-
165
-Labels:
166
-
167
-| Label | Description |
168
-|:-----------|:----------------|
169
-| datacenter | Datacenter name |
170
-| datastore | Datastore name |
171
-| type | Datastore type (VMFS, NFS, NFS41, vsan, VVOL, PMEM) |
172
-
173
-Metrics:
174
-
175
-| Metric | Dimensions | Unit |
176
-|:------|:----------|:----|
177
-| vsphere.datastore_disk_io | read, write | KiB/s |
178
-| vsphere.datastore_disk_iops | reads, writes | operations/s |
179
-| vsphere.datastore_disk_latency | read, write | milliseconds |
180
-| vsphere.datastore_space_utilization | used | percentage |
181
-| vsphere.datastore_space_usage | capacity, free, used | bytes |
182
-| vsphere.datastore_overall_status | green, red, yellow, gray | status |
183
-
184
-### Per cluster
185
-
186
-These metrics refer to the vSphere Cluster.
187
-
188
-Labels:
189
-
190
-| Label | Description |
191
-|:-----------|:----------------|
192
-| datacenter | Datacenter name |
193
-| cluster | Cluster name |
194
-
195
-Metrics:
196
-
197
-| Metric | Dimensions | Unit |
198
-|:------|:----------|:----|
199
-| vsphere.cluster_hosts | total, effective | hosts |
200
-| vsphere.cluster_cpu_capacity | total, effective | MHz |
201
-| vsphere.cluster_mem_capacity | total, effective | bytes |
202
-| vsphere.cluster_cpu_topology | cores, threads | count |
203
-| vsphere.cluster_drs_config | enabled | status |
204
-| vsphere.cluster_ha_config | enabled, admission_control | status |
205
-| vsphere.cluster_overall_status | green, red, yellow, gray | status |
206
-| vsphere.cluster_vmotions | vmotions | migrations |
207
-| vsphere.cluster_drs_score | score | percentage |
208
-| vsphere.cluster_drs_balance | current, target | score |
209
-| vsphere.cluster_vm_count | total, powered_off | VMs |
210
-| vsphere.cluster_usage_cpu | demand, entitled, reserved | MHz |
211
-| vsphere.cluster_usage_mem | demand, entitled, reserved | MB |
212
-| vsphere.cluster_cpu_utilization | used | percentage |
213
-| vsphere.cluster_cpu_usage | used, total | MHz |
214
-| vsphere.cluster_mem_utilization | used | percentage |
215
-| vsphere.cluster_mem_usage | consumed, active, granted, shared, overhead, swap_used | KiB |
216
-| vsphere.cluster_services_fairness | cpu, memory | score |
217
-| vsphere.cluster_services_effective_cpu | effective_cpu | MHz |
218
-| vsphere.cluster_services_effective_mem | effective_mem | MB |
219
-| vsphere.cluster_services_failover | failures_tolerable | failures |
220
-| vsphere.cluster_vm_migrations | vmotion, svmotion, xvmotion | operations |
221
-| vsphere.cluster_vm_lifecycle | poweron, poweroff, create, destroy, clone, deploy | operations |
222
-| vsphere.cluster_vm_management | reconfigure, reset, suspend, register, unregister | operations |
223
-| vsphere.cluster_vm_guest_ops | reboot, shutdown, standby | operations |
224
-| vsphere.cluster_vm_cold_migrations | change_ds, change_host, change_host_ds | operations |
225
-
226
-### Per resource pool
227
-
228
-These metrics refer to the vSphere Resource Pool.
229
-
230
-Labels:
231
-
232
-| Label | Description |
233
-|:-----------|:----------------|
234
-| datacenter | Datacenter name |
235
-| cluster | Cluster name |
236
-| resource_pool | Resource Pool name |
237
-
238
-Metrics:
239
-
240
-| Metric | Dimensions | Unit |
241
-|:------|:----------|:----|
242
-| vsphere.resource_pool_cpu_usage | usage, demand | MHz |
243
-| vsphere.resource_pool_cpu_entitlement | distributed | MHz |
244
-| vsphere.resource_pool_cpu_allocation | reservation_used, unreserved_for_vm, max_usage | MHz |
245
-| vsphere.resource_pool_mem_usage | host, guest | MB |
246
-| vsphere.resource_pool_mem_entitlement | distributed | MB |
247
-| vsphere.resource_pool_mem_allocation | reservation_used, unreserved_for_vm, max_usage | bytes |
248
-| vsphere.resource_pool_mem_breakdown | private, shared, swapped, ballooned, overhead, consumed_overhead, compressed | MB |
249
-| vsphere.resource_pool_cpu_config | reservation, limit | MHz |
250
-| vsphere.resource_pool_mem_config | reservation, limit | MB |
251
-| vsphere.resource_pool_overall_status | green, red, yellow, gray | status |
252
-
253
-
254
-
255
-## Alerts
256
-
257
-
258
-The following alerts are available:
259
-
260
-| Alert name | On metric | Description |
261
-|:------------|:----------|:------------|
262
-| [ vsphere_vm_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.vm_cpu_utilization | Virtual Machine CPU utilization |
263
-| [ vsphere_vm_mem_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.vm_mem_utilization | Virtual Machine memory utilization |
264
-| [ vsphere_host_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.host_cpu_utilization | ESXi Host CPU utilization |
265
-| [ vsphere_host_mem_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.host_mem_utilization | ESXi Host memory utilization |
266
-
267
-
94
## Setup
95
96
@@ -470,6 +296,180 @@ jobs:
296
297
298
299
+## Alerts
300
+
301
+
302
+The following alerts are available:
303
+
304
+| Alert name | On metric | Description |
305
+|:------------|:----------|:------------|
306
+| [ vsphere_vm_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.vm_cpu_utilization | Virtual Machine CPU utilization |
307
+| [ vsphere_vm_mem_usage ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.vm_mem_utilization | Virtual Machine memory utilization |
308
+| [ vsphere_host_cpu_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.host_cpu_utilization | ESXi Host CPU utilization |
309
+| [ vsphere_host_mem_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/vsphere.conf) | vsphere.host_mem_utilization | ESXi Host memory utilization |
310
+
311
+
312
+## Metrics
313
+
314
+Metrics grouped by *scope*.
315
+
316
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
317
+
318
+
319
+
320
+### Per virtual machine
321
+
322
+These metrics refer to the Virtual Machine.
323
+
324
+Labels:
325
+
326
+| Label | Description |
327
+|:-----------|:----------------|
328
+| datacenter | Datacenter name |
329
+| cluster | Cluster name |
330
+| host | Host name |
331
+| vm | Virtual Machine name |
332
+
333
+Metrics:
334
+
335
+| Metric | Dimensions | Unit |
336
+|:------|:----------|:----|
337
+| vsphere.vm_cpu_utilization | used | percentage |
338
+| vsphere.vm_mem_utilization | used | percentage |
339
+| vsphere.vm_mem_usage | granted, consumed, active, shared | KiB |
340
+| vsphere.vm_mem_swap_usage | swapped | KiB |
341
+| vsphere.vm_mem_swap_io | in, out | KiB/s |
342
+| vsphere.vm_disk_io | read, write | KiB/s |
343
+| vsphere.vm_disk_max_latency | latency | milliseconds |
344
+| vsphere.vm_net_traffic | received, sent | KiB/s |
345
+| vsphere.vm_net_packets | received, sent | packets |
346
+| vsphere.vm_net_drops | received, sent | packets |
347
+| vsphere.vm_overall_status | green, red, yellow, gray | status |
348
+| vsphere.vm_system_uptime | uptime | seconds |
349
+
350
+### Per host
351
+
352
+These metrics refer to the ESXi host.
353
+
354
+Labels:
355
+
356
+| Label | Description |
357
+|:-----------|:----------------|
358
+| datacenter | Datacenter name |
359
+| cluster | Cluster name |
360
+| host | Host name |
361
+
362
+Metrics:
363
+
364
+| Metric | Dimensions | Unit |
365
+|:------|:----------|:----|
366
+| vsphere.host_cpu_utilization | used | percentage |
367
+| vsphere.host_mem_utilization | used | percentage |
368
+| vsphere.host_mem_usage | granted, consumed, active, shared, sharedcommon | KiB |
369
+| vsphere.host_mem_swap_io | in, out | KiB/s |
370
+| vsphere.host_disk_io | read, write | KiB/s |
371
+| vsphere.host_disk_max_latency | latency | milliseconds |
372
+| vsphere.host_net_traffic | received, sent | KiB/s |
373
+| vsphere.host_net_packets | received, sent | packets |
374
+| vsphere.host_net_drops | received, sent | packets |
375
+| vsphere.host_net_errors | received, sent | errors |
376
+| vsphere.host_overall_status | green, red, yellow, gray | status |
377
+| vsphere.host_system_uptime | uptime | seconds |
378
+
379
+### Per datastore
380
+
381
+These metrics refer to the Datastore.
382
+
383
+Labels:
384
+
385
+| Label | Description |
386
+|:-----------|:----------------|
387
+| datacenter | Datacenter name |
388
+| datastore | Datastore name |
389
+| type | Datastore type (VMFS, NFS, NFS41, vsan, VVOL, PMEM) |
390
+
391
+Metrics:
392
+
393
+| Metric | Dimensions | Unit |
394
+|:------|:----------|:----|
395
+| vsphere.datastore_disk_io | read, write | KiB/s |
396
+| vsphere.datastore_disk_iops | reads, writes | operations/s |
397
+| vsphere.datastore_disk_latency | read, write | milliseconds |
398
+| vsphere.datastore_space_utilization | used | percentage |
399
+| vsphere.datastore_space_usage | capacity, free, used | bytes |
400
+| vsphere.datastore_overall_status | green, red, yellow, gray | status |
401
+
402
+### Per cluster
403
+
404
+These metrics refer to the vSphere Cluster.
405
+
406
+Labels:
407
+
408
+| Label | Description |
409
+|:-----------|:----------------|
410
+| datacenter | Datacenter name |
411
+| cluster | Cluster name |
412
+
413
+Metrics:
414
+
415
+| Metric | Dimensions | Unit |
416
+|:------|:----------|:----|
417
+| vsphere.cluster_hosts | total, effective | hosts |
418
+| vsphere.cluster_cpu_capacity | total, effective | MHz |
419
+| vsphere.cluster_mem_capacity | total, effective | bytes |
420
+| vsphere.cluster_cpu_topology | cores, threads | count |
421
+| vsphere.cluster_drs_config | enabled | status |
422
+| vsphere.cluster_ha_config | enabled, admission_control | status |
423
+| vsphere.cluster_overall_status | green, red, yellow, gray | status |
424
+| vsphere.cluster_vmotions | vmotions | migrations |
425
+| vsphere.cluster_drs_score | score | percentage |
426
+| vsphere.cluster_drs_balance | current, target | score |
427
+| vsphere.cluster_vm_count | total, powered_off | VMs |
428
+| vsphere.cluster_usage_cpu | demand, entitled, reserved | MHz |
429
+| vsphere.cluster_usage_mem | demand, entitled, reserved | MB |
430
+| vsphere.cluster_cpu_utilization | used | percentage |
431
+| vsphere.cluster_cpu_usage | used, total | MHz |
432
+| vsphere.cluster_mem_utilization | used | percentage |
433
+| vsphere.cluster_mem_usage | consumed, active, granted, shared, overhead, swap_used | KiB |
434
+| vsphere.cluster_services_fairness | cpu, memory | score |
435
+| vsphere.cluster_services_effective_cpu | effective_cpu | MHz |
436
+| vsphere.cluster_services_effective_mem | effective_mem | MB |
437
+| vsphere.cluster_services_failover | failures_tolerable | failures |
438
+| vsphere.cluster_vm_migrations | vmotion, svmotion, xvmotion | operations |
439
+| vsphere.cluster_vm_lifecycle | poweron, poweroff, create, destroy, clone, deploy | operations |
440
+| vsphere.cluster_vm_management | reconfigure, reset, suspend, register, unregister | operations |
441
+| vsphere.cluster_vm_guest_ops | reboot, shutdown, standby | operations |
442
+| vsphere.cluster_vm_cold_migrations | change_ds, change_host, change_host_ds | operations |
443
+
444
+### Per resource pool
445
+
446
+These metrics refer to the vSphere Resource Pool.
447
+
448
+Labels:
449
+
450
+| Label | Description |
451
+|:-----------|:----------------|
452
+| datacenter | Datacenter name |
453
+| cluster | Cluster name |
454
+| resource_pool | Resource Pool name |
455
+
456
+Metrics:
457
+
458
+| Metric | Dimensions | Unit |
459
+|:------|:----------|:----|
460
+| vsphere.resource_pool_cpu_usage | usage, demand | MHz |
461
+| vsphere.resource_pool_cpu_entitlement | distributed | MHz |
462
+| vsphere.resource_pool_cpu_allocation | reservation_used, unreserved_for_vm, max_usage | MHz |
463
+| vsphere.resource_pool_mem_usage | host, guest | MB |
464
+| vsphere.resource_pool_mem_entitlement | distributed | MB |
465
+| vsphere.resource_pool_mem_allocation | reservation_used, unreserved_for_vm, max_usage | bytes |
466
+| vsphere.resource_pool_mem_breakdown | private, shared, swapped, ballooned, overhead, consumed_overhead, compressed | MB |
467
+| vsphere.resource_pool_cpu_config | reservation, limit | MHz |
468
+| vsphere.resource_pool_mem_config | reservation, limit | MB |
469
+| vsphere.resource_pool_overall_status | green, red, yellow, gray | status |
470
+
471
+
472
+
473
## Troubleshooting
474
475
### Debug Mode
src/go/plugin/go.d/collector/w1sensor/integrations/1-wire_sensors.md
+27
-27
@@ -47,33 +47,6 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
-## Metrics
51
-
52
-Metrics grouped by *scope*.
53
-
54
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
55
-
56
-
57
-
58
-### Per sensor
59
-
60
-These metrics refer to the 1-Wire Sensor.
61
-
62
-This scope has no labels.
63
-
64
-Metrics:
65
-
66
-| Metric | Dimensions | Unit |
67
-|:------|:----------|:----|
68
-| w1sensor.temperature | temperature | Celsius |
69
-
70
-
71
-
72
-## Alerts
73
-
74
-There are no alerts configured by default for this integration.
75
-
76
-
50
## Setup
51
52
@@ -167,6 +140,33 @@ jobs:
140
```
141
142
143
+## Alerts
144
+
145
+There are no alerts configured by default for this integration.
146
+
147
+
148
+## Metrics
149
+
150
+Metrics grouped by *scope*.
151
+
152
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
153
+
154
+
155
+
156
+### Per sensor
157
+
158
+These metrics refer to the 1-Wire Sensor.
159
+
160
+This scope has no labels.
161
+
162
+Metrics:
163
+
164
+| Metric | Dimensions | Unit |
165
+|:------|:----------|:----|
166
+| w1sensor.temperature | temperature | Celsius |
167
+
168
+
169
+
170
## Troubleshooting
171
172
### Debug Mode
src/go/plugin/go.d/collector/weblog/integrations/web_server_log_files.md
+102
-102
@@ -46,108 +46,6 @@ The default configuration for this integration does not impose any limits on dat
46
47
The default configuration for this integration is not expected to impose a significant performance impact on the system.
48
49
-## Metrics
50
-
51
-Metrics grouped by *scope*.
52
-
53
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
54
-
55
-
56
-
57
-### Per Web server log files instance
58
-
59
-These metrics refer to the entire monitored application.
60
-
61
-This scope has no labels.
62
-
63
-Metrics:
64
-
65
-| Metric | Dimensions | Unit |
66
-|:------|:----------|:----|
67
-| web_log.requests | requests | requests/s |
68
-| web_log.excluded_requests | unmatched | requests/s |
69
-| web_log.type_requests | success, bad, redirect, error | requests/s |
70
-| web_log.status_code_class_responses | 1xx, 2xx, 3xx, 4xx, 5xx | responses/s |
71
-| web_log.status_code_class_1xx_responses | a dimension per 1xx code | responses/s |
72
-| web_log.status_code_class_2xx_responses | a dimension per 2xx code | responses/s |
73
-| web_log.status_code_class_3xx_responses | a dimension per 3xx code | responses/s |
74
-| web_log.status_code_class_4xx_responses | a dimension per 4xx code | responses/s |
75
-| web_log.status_code_class_5xx_responses | a dimension per 5xx code | responses/s |
76
-| web_log.bandwidth | received, sent | kilobits/s |
77
-| web_log.request_processing_time | min, max, avg | milliseconds |
78
-| web_log.requests_processing_time_histogram | a dimension per bucket | requests/s |
79
-| web_log.upstream_response_time | min, max, avg | milliseconds |
80
-| web_log.upstream_responses_time_histogram | a dimension per bucket | requests/s |
81
-| web_log.current_poll_uniq_clients | ipv4, ipv6 | clients |
82
-| web_log.vhost_requests | a dimension per vhost | requests/s |
83
-| web_log.port_requests | a dimension per port | requests/s |
84
-| web_log.scheme_requests | http, https | requests/s |
85
-| web_log.http_method_requests | a dimension per HTTP method | requests/s |
86
-| web_log.http_version_requests | a dimension per HTTP version | requests/s |
87
-| web_log.ip_proto_requests | ipv4, ipv6 | requests/s |
88
-| web_log.ssl_proto_requests | a dimension per SSL protocol | requests/s |
89
-| web_log.ssl_cipher_suite_requests | a dimension per SSL cipher suite | requests/s |
90
-| web_log.url_pattern_requests | a dimension per URL pattern | requests/s |
91
-| web_log.custom_field_pattern_requests | a dimension per custom field pattern | requests/s |
92
-
93
-### Per custom time field
94
-
95
-TBD
96
-
97
-This scope has no labels.
98
-
99
-Metrics:
100
-
101
-| Metric | Dimensions | Unit |
102
-|:------|:----------|:----|
103
-| web_log.custom_time_field_summary | min, max, avg | milliseconds |
104
-| web_log.custom_time_field_histogram | a dimension per bucket | observations |
105
-
106
-### Per custom numeric field
107
-
108
-TBD
109
-
110
-This scope has no labels.
111
-
112
-Metrics:
113
-
114
-| Metric | Dimensions | Unit |
115
-|:------|:----------|:----|
116
-| web_log.custom_numeric_field_{{field_name}}_summary | min, max, avg | {{units}} |
117
-
118
-### Per URL pattern
119
-
120
-TBD
121
-
122
-This scope has no labels.
123
-
124
-Metrics:
125
-
126
-| Metric | Dimensions | Unit |
127
-|:------|:----------|:----|
128
-| web_log.url_pattern_status_code_responses | a dimension per pattern | responses/s |
129
-| web_log.url_pattern_http_method_requests | a dimension per HTTP method | requests/s |
130
-| web_log.url_pattern_bandwidth | received, sent | kilobits/s |
131
-| web_log.url_pattern_request_processing_time | min, max, avg | milliseconds |
132
-
133
-
134
-
135
-## Alerts
136
-
137
-
138
-The following alerts are available:
139
-
140
-| Alert name | On metric | Description |
141
-|:------------|:----------|:------------|
142
-| [ web_log_1m_unmatched ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.excluded_requests | percentage of unparsed log lines over the last minute |
143
-| [ web_log_1m_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of successful HTTP requests over the last minute (1xx, 2xx, 304, 401) |
144
-| [ web_log_1m_redirects ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of redirection HTTP requests over the last minute (3xx except 304) |
145
-| [ web_log_1m_bad_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of client error HTTP requests over the last minute (4xx except 401) |
146
-| [ web_log_1m_internal_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of server error HTTP requests over the last minute (5xx) |
147
-| [ web_log_web_slow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.request_processing_time | average HTTP response time over the last 1 minute |
148
-| [ web_log_5m_requests_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of successful HTTP requests over over the last 5 minutes, compared with the previous 5 minutes |
149
-
150
-
49
## Setup
50
51
@@ -383,6 +281,108 @@ There are no configuration examples.
281
282
283
284
+## Alerts
285
+
286
+
287
+The following alerts are available:
288
+
289
+| Alert name | On metric | Description |
290
+|:------------|:----------|:------------|
291
+| [ web_log_1m_unmatched ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.excluded_requests | percentage of unparsed log lines over the last minute |
292
+| [ web_log_1m_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of successful HTTP requests over the last minute (1xx, 2xx, 304, 401) |
293
+| [ web_log_1m_redirects ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of redirection HTTP requests over the last minute (3xx except 304) |
294
+| [ web_log_1m_bad_requests ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of client error HTTP requests over the last minute (4xx except 401) |
295
+| [ web_log_1m_internal_errors ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of server error HTTP requests over the last minute (5xx) |
296
+| [ web_log_web_slow ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.request_processing_time | average HTTP response time over the last 1 minute |
297
+| [ web_log_5m_requests_ratio ](https://github.com/netdata/netdata/blob/master/src/health/health.d/web_log.conf) | web_log.type_requests | ratio of successful HTTP requests over over the last 5 minutes, compared with the previous 5 minutes |
298
+
299
+
300
+## Metrics
301
+
302
+Metrics grouped by *scope*.
303
+
304
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
305
+
306
+
307
+
308
+### Per Web server log files instance
309
+
310
+These metrics refer to the entire monitored application.
311
+
312
+This scope has no labels.
313
+
314
+Metrics:
315
+
316
+| Metric | Dimensions | Unit |
317
+|:------|:----------|:----|
318
+| web_log.requests | requests | requests/s |
319
+| web_log.excluded_requests | unmatched | requests/s |
320
+| web_log.type_requests | success, bad, redirect, error | requests/s |
321
+| web_log.status_code_class_responses | 1xx, 2xx, 3xx, 4xx, 5xx | responses/s |
322
+| web_log.status_code_class_1xx_responses | a dimension per 1xx code | responses/s |
323
+| web_log.status_code_class_2xx_responses | a dimension per 2xx code | responses/s |
324
+| web_log.status_code_class_3xx_responses | a dimension per 3xx code | responses/s |
325
+| web_log.status_code_class_4xx_responses | a dimension per 4xx code | responses/s |
326
+| web_log.status_code_class_5xx_responses | a dimension per 5xx code | responses/s |
327
+| web_log.bandwidth | received, sent | kilobits/s |
328
+| web_log.request_processing_time | min, max, avg | milliseconds |
329
+| web_log.requests_processing_time_histogram | a dimension per bucket | requests/s |
330
+| web_log.upstream_response_time | min, max, avg | milliseconds |
331
+| web_log.upstream_responses_time_histogram | a dimension per bucket | requests/s |
332
+| web_log.current_poll_uniq_clients | ipv4, ipv6 | clients |
333
+| web_log.vhost_requests | a dimension per vhost | requests/s |
334
+| web_log.port_requests | a dimension per port | requests/s |
335
+| web_log.scheme_requests | http, https | requests/s |
336
+| web_log.http_method_requests | a dimension per HTTP method | requests/s |
337
+| web_log.http_version_requests | a dimension per HTTP version | requests/s |
338
+| web_log.ip_proto_requests | ipv4, ipv6 | requests/s |
339
+| web_log.ssl_proto_requests | a dimension per SSL protocol | requests/s |
340
+| web_log.ssl_cipher_suite_requests | a dimension per SSL cipher suite | requests/s |
341
+| web_log.url_pattern_requests | a dimension per URL pattern | requests/s |
342
+| web_log.custom_field_pattern_requests | a dimension per custom field pattern | requests/s |
343
+
344
+### Per custom time field
345
+
346
+TBD
347
+
348
+This scope has no labels.
349
+
350
+Metrics:
351
+
352
+| Metric | Dimensions | Unit |
353
+|:------|:----------|:----|
354
+| web_log.custom_time_field_summary | min, max, avg | milliseconds |
355
+| web_log.custom_time_field_histogram | a dimension per bucket | observations |
356
+
357
+### Per custom numeric field
358
+
359
+TBD
360
+
361
+This scope has no labels.
362
+
363
+Metrics:
364
+
365
+| Metric | Dimensions | Unit |
366
+|:------|:----------|:----|
367
+| web_log.custom_numeric_field_{{field_name}}_summary | min, max, avg | {{units}} |
368
+
369
+### Per URL pattern
370
+
371
+TBD
372
+
373
+This scope has no labels.
374
+
375
+Metrics:
376
+
377
+| Metric | Dimensions | Unit |
378
+|:------|:----------|:----|
379
+| web_log.url_pattern_status_code_responses | a dimension per pattern | responses/s |
380
+| web_log.url_pattern_http_method_requests | a dimension per HTTP method | requests/s |
381
+| web_log.url_pattern_bandwidth | received, sent | kilobits/s |
382
+| web_log.url_pattern_request_processing_time | min, max, avg | milliseconds |
383
+
384
+
385
+
386
## Troubleshooting
387
388
### Debug Mode
src/go/plugin/go.d/collector/whoisquery/integrations/domain_expiration_date.md
+36
-36
@@ -45,42 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per domain
57
-
58
-These metrics refer to the configured source.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| domain | Configured source |
65
-
66
-Metrics:
67
-
68
-| Metric | Dimensions | Unit |
69
-|:------|:----------|:----|
70
-| whoisquery.time_until_expiration | expiry | seconds |
71
-
72
-
73
-
74
-## Alerts
75
-
76
-
77
-The following alerts are available:
78
-
79
-| Alert name | On metric | Description |
80
-|:------------|:----------|:------------|
81
-| [ whoisquery_days_until_expiration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/whoisquery.conf) | whoisquery.time_until_expiration | time until the domain name registration expires |
82
-
83
-
48
## Setup
49
50
@@ -200,6 +164,42 @@ jobs:
164
165
166
167
+## Alerts
168
+
169
+
170
+The following alerts are available:
171
+
172
+| Alert name | On metric | Description |
173
+|:------------|:----------|:------------|
174
+| [ whoisquery_days_until_expiration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/whoisquery.conf) | whoisquery.time_until_expiration | time until the domain name registration expires |
175
+
176
+
177
+## Metrics
178
+
179
+Metrics grouped by *scope*.
180
+
181
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
182
+
183
+
184
+
185
+### Per domain
186
+
187
+These metrics refer to the configured source.
188
+
189
+Labels:
190
+
191
+| Label | Description |
192
+|:-----------|:----------------|
193
+| domain | Configured source |
194
+
195
+Metrics:
196
+
197
+| Metric | Dimensions | Unit |
198
+|:------|:----------|:----|
199
+| whoisquery.time_until_expiration | expiry | seconds |
200
+
201
+
202
+
203
## Troubleshooting
204
205
### Debug Mode
src/go/plugin/go.d/collector/wireguard/integrations/wireguard.md
+50
-50
@@ -50,56 +50,6 @@ Doesn't work if Netdata or WireGuard is installed in the container.
50
51
The default configuration for this integration is not expected to impose a significant performance impact on the system.
52
53
-## Metrics
54
-
55
-Metrics grouped by *scope*.
56
-
57
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
58
-
59
-
60
-
61
-### Per device
62
-
63
-These metrics refer to the VPN network interface.
64
-
65
-Labels:
66
-
67
-| Label | Description |
68
-|:-----------|:----------------|
69
-| device | VPN network interface |
70
-
71
-Metrics:
72
-
73
-| Metric | Dimensions | Unit |
74
-|:------|:----------|:----|
75
-| wireguard.device_network_io | receive, transmit | B/s |
76
-| wireguard.device_peers | peers | peers |
77
-
78
-### Per peer
79
-
80
-These metrics refer to the VPN peer.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| device | VPN network interface |
87
-| public_key | Public key of a peer |
88
-
89
-Metrics:
90
-
91
-| Metric | Dimensions | Unit |
92
-|:------|:----------|:----|
93
-| wireguard.peer_network_io | receive, transmit | B/s |
94
-| wireguard.peer_latest_handshake_ago | time | seconds |
95
-
96
-
97
-
98
-## Alerts
99
-
100
-There are no alerts configured by default for this integration.
101
-
102
-
53
## Setup
54
55
@@ -181,6 +131,56 @@ There are no configuration examples.
131
132
133
134
+## Alerts
135
+
136
+There are no alerts configured by default for this integration.
137
+
138
+
139
+## Metrics
140
+
141
+Metrics grouped by *scope*.
142
+
143
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
144
+
145
+
146
+
147
+### Per device
148
+
149
+These metrics refer to the VPN network interface.
150
+
151
+Labels:
152
+
153
+| Label | Description |
154
+|:-----------|:----------------|
155
+| device | VPN network interface |
156
+
157
+Metrics:
158
+
159
+| Metric | Dimensions | Unit |
160
+|:------|:----------|:----|
161
+| wireguard.device_network_io | receive, transmit | B/s |
162
+| wireguard.device_peers | peers | peers |
163
+
164
+### Per peer
165
+
166
+These metrics refer to the VPN peer.
167
+
168
+Labels:
169
+
170
+| Label | Description |
171
+|:-----------|:----------------|
172
+| device | VPN network interface |
173
+| public_key | Public key of a peer |
174
+
175
+Metrics:
176
+
177
+| Metric | Dimensions | Unit |
178
+|:------|:----------|:----|
179
+| wireguard.peer_network_io | receive, transmit | B/s |
180
+| wireguard.peer_latest_handshake_ago | time | seconds |
181
+
182
+
183
+
184
## Troubleshooting
185
186
### Debug Mode
src/go/plugin/go.d/collector/x509check/integrations/x.509_certificate.md
+40
-40
@@ -45,46 +45,6 @@ The default configuration for this integration does not impose any limits on dat
45
46
The default configuration for this integration is not expected to impose a significant performance impact on the system.
47
48
-## Metrics
49
-
50
-Metrics grouped by *scope*.
51
-
52
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
53
-
54
-
55
-
56
-### Per source
57
-
58
-These metrics refer to the SSL certificate.
59
-
60
-Labels:
61
-
62
-| Label | Description |
63
-|:-----------|:----------------|
64
-| source | Same as the "source" configuration option. |
65
-| common_name | The common name (CN) extracted from the certificate. |
66
-| depth | The depth of the certificate within the certificate chain. The leaf certificate has a depth of 0, and subsequent certificates (intermediate certificates) have increasing depth values. The root certificate is at the highest depth. |
67
-
68
-Metrics:
69
-
70
-| Metric | Dimensions | Unit |
71
-|:------|:----------|:----|
72
-| x509check.time_until_expiration | expiry | seconds |
73
-| x509check.revocation_status | not_revoked, revoked | boolean |
74
-
75
-
76
-
77
-## Alerts
78
-
79
-
80
-The following alerts are available:
81
-
82
-| Alert name | On metric | Description |
83
-|:------------|:----------|:------------|
84
-| [ x509check_days_until_expiration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/x509check.conf) | x509check.time_until_expiration | SSL cert expiring soon (${label:source} cn:${label:common_name}) |
85
-| [ x509check_revocation_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/x509check.conf) | x509check.revocation_status | SSL cert revoked (${label:source}) |
86
-
87
-
48
## Setup
49
50
@@ -239,6 +199,46 @@ jobs:
199
200
201
202
+## Alerts
203
+
204
+
205
+The following alerts are available:
206
+
207
+| Alert name | On metric | Description |
208
+|:------------|:----------|:------------|
209
+| [ x509check_days_until_expiration ](https://github.com/netdata/netdata/blob/master/src/health/health.d/x509check.conf) | x509check.time_until_expiration | SSL cert expiring soon (${label:source} cn:${label:common_name}) |
210
+| [ x509check_revocation_status ](https://github.com/netdata/netdata/blob/master/src/health/health.d/x509check.conf) | x509check.revocation_status | SSL cert revoked (${label:source}) |
211
+
212
+
213
+## Metrics
214
+
215
+Metrics grouped by *scope*.
216
+
217
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
218
+
219
+
220
+
221
+### Per source
222
+
223
+These metrics refer to the SSL certificate.
224
+
225
+Labels:
226
+
227
+| Label | Description |
228
+|:-----------|:----------------|
229
+| source | Same as the "source" configuration option. |
230
+| common_name | The common name (CN) extracted from the certificate. |
231
+| depth | The depth of the certificate within the certificate chain. The leaf certificate has a depth of 0, and subsequent certificates (intermediate certificates) have increasing depth values. The root certificate is at the highest depth. |
232
+
233
+Metrics:
234
+
235
+| Metric | Dimensions | Unit |
236
+|:------|:----------|:----|
237
+| x509check.time_until_expiration | expiry | seconds |
238
+| x509check.revocation_status | not_revoked, revoked | boolean |
239
+
240
+
241
+
242
## Troubleshooting
243
244
### Debug Mode
src/go/plugin/go.d/collector/yugabytedb/integrations/yugabytedb.md
+191
-191
@@ -59,6 +59,196 @@ The default configuration for this integration does not impose any limits on dat
59
60
The default configuration for this integration is not expected to impose a significant performance impact on the system.
61
62
+## Setup
63
+
64
+
65
+You can configure the **yugabytedb** collector in two ways:
66
+
67
+| Method | Best for | How to |
68
+|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
69
+| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **yugabytedb**, then click **+** to add a job. |
70
+| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/yugabytedb.conf` and add a job. |
71
+
72
+:::important
73
+
74
+UI configuration requires paid Netdata Cloud plan.
75
+
76
+:::
77
+
78
+
79
+### Prerequisites
80
+
81
+No action required.
82
+
83
+### Configuration
84
+
85
+#### Options
86
+
87
+The following options can be defined globally: update_every, autodetection_retry.
88
+
89
+
90
+<details open><summary>Config options</summary>
91
+
92
+
93
+
94
+| Group | Option | Description | Default | Required |
95
+|:------|:-----|:------------|:--------|:---------:|
96
+| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
97
+| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
98
+| **Target** | url | Target endpoint URL. | http://127.0.0.1:7000/prometheus-metrics | yes |
99
+| | timeout | HTTP request timeout (seconds). | 1 | no |
100
+| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
101
+| | password | Password for Basic HTTP authentication. | | no |
102
+| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
103
+| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
104
+| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
105
+| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
106
+| | tls_key | Path to client TLS private key (for mTLS). | | no |
107
+| **Proxy** | proxy_url | HTTP proxy URL. | | no |
108
+| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
109
+| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
110
+| **Request** | method | HTTP method to use. | GET | no |
111
+| | body | Request body (e.g., for POST/PUT). | | no |
112
+| | headers | Additional HTTP headers (one per line as key: value). | | no |
113
+| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
114
+| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
115
+| **Functions** | functions.dsn | SQL DSN (required for query functions). | | no |
116
+| | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
117
+| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
118
+| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
119
+| | functions.running_queries.disabled | Disable the [running-queries](#running-queries) function. | no | no |
120
+| | functions.running_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
121
+| | functions.running_queries.limit | Maximum number of queries to return. | 500 | no |
122
+| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
123
+
124
+
125
+</details>
126
+
127
+
128
+#### via UI
129
+
130
+Configure the **yugabytedb** collector from the Netdata web interface:
131
+
132
+1. Go to **Nodes**.
133
+2. Select the node **where you want the yugabytedb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
134
+3. The **Collectors → Jobs** view opens by default.
135
+4. In the Search box, type _yugabytedb_ (or scroll the list) to locate the **yugabytedb** collector.
136
+5. Click the **+** next to the **yugabytedb** collector to add a new job.
137
+6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
138
+ - **Test** runs the job with the provided settings and shows whether data can be collected.
139
+ - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
140
+
141
+
142
+#### via File
143
+
144
+The configuration file name for this integration is `go.d/yugabytedb.conf`.
145
+
146
+The file format is YAML. Generally, the structure is:
147
+
148
+```yaml
149
+update_every: 1
150
+autodetection_retry: 0
151
+jobs:
152
+ - name: some_name1
153
+ - name: some_name2
154
+```
155
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
156
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
157
+
158
+```bash
159
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
+sudo ./edit-config go.d/yugabytedb.conf
161
+```
162
+
163
+##### Examples
164
+
165
+###### Basic
166
+
167
+A basic example configuration.
168
+
169
+```yaml
170
+jobs:
171
+ - name: local
172
+ url: http://127.0.0.1:7000/prometheus-metrics # Master
173
+ # url: http://127.0.0.1:9000/prometheus-metrics # Tablet Server
174
+ # url: http://127.0.0.1:12000/prometheus-metrics # YCQL
175
+ # url: http://127.0.0.1:13000/prometheus-metrics # YSQL
176
+
177
+```
178
+###### Top queries
179
+
180
+Enable SQL query functions (YSQL).
181
+
182
+<details open><summary>Config</summary>
183
+
184
+```yaml
185
+jobs:
186
+ - name: local
187
+ url: http://127.0.0.1:7000/prometheus-metrics
188
+ functions:
189
+ dsn: postgres://yugabyte@127.0.0.1:5433/yugabyte?sslmode=disable
190
+
191
+```
192
+</details>
193
+
194
+###### HTTP authentication
195
+
196
+Basic HTTP authentication.
197
+
198
+<details open><summary>Config</summary>
199
+
200
+```yaml
201
+jobs:
202
+ - name: local
203
+ url: http://127.0.0.1:7000/prometheus-metrics
204
+ username: username
205
+ password: password
206
+
207
+```
208
+</details>
209
+
210
+###### HTTPS with self-signed certificate
211
+
212
+NGINX with enabled HTTPS and self-signed certificate.
213
+
214
+<details open><summary>Config</summary>
215
+
216
+```yaml
217
+jobs:
218
+ - name: local
219
+ url: https://127.0.0.1:7000/prometheus-metrics
220
+ tls_skip_verify: yes
221
+
222
+```
223
+</details>
224
+
225
+###### Multi-instance
226
+
227
+> **Note**: When you define multiple jobs, their names must be unique.
228
+
229
+Collecting metrics from local and remote instances.
230
+
231
+
232
+<details open><summary>Config</summary>
233
+
234
+```yaml
235
+jobs:
236
+ - name: local
237
+ url: http://127.0.0.1:7000/prometheus-metrics
238
+
239
+ - name: remote
240
+ url: http://192.0.2.1:7000/prometheus-metrics
241
+
242
+```
243
+</details>
244
+
245
+
246
+
247
+## Alerts
248
+
249
+There are no alerts configured by default for this integration.
250
+
251
+
252
## Metrics
253
254
Metrics grouped by *scope*.
@@ -332,7 +522,7 @@ Metrics:
522
523
524
335
-## Functions
525
+## Live Data
526
527
This collector exposes real-time functions for interactive troubleshooting in the Live tab.
528
@@ -479,196 +669,6 @@ Currently running SQL statements from `pg_stat_activity`. Each row represents an
669
670
671
482
-## Alerts
483
-
484
-There are no alerts configured by default for this integration.
485
-
486
-
487
-## Setup
488
-
489
-
490
-You can configure the **yugabytedb** collector in two ways:
491
-
492
-| Method | Best for | How to |
493
-|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
494
-| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **yugabytedb**, then click **+** to add a job. |
495
-| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/yugabytedb.conf` and add a job. |
496
-
497
-:::important
498
-
499
-UI configuration requires paid Netdata Cloud plan.
500
-
501
-:::
502
-
503
-
504
-### Prerequisites
505
-
506
-No action required.
507
-
508
-### Configuration
509
-
510
-#### Options
511
-
512
-The following options can be defined globally: update_every, autodetection_retry.
513
-
514
-
515
-<details open><summary>Config options</summary>
516
-
517
-
518
-
519
-| Group | Option | Description | Default | Required |
520
-|:------|:-----|:------------|:--------|:---------:|
521
-| **Collection** | update_every | Data collection interval (seconds). | 5 | no |
522
-| | autodetection_retry | Autodetection retry interval (seconds). Set 0 to disable. | 0 | no |
523
-| **Target** | url | Target endpoint URL. | http://127.0.0.1:7000/prometheus-metrics | yes |
524
-| | timeout | HTTP request timeout (seconds). | 1 | no |
525
-| **HTTP Auth** | username | Username for Basic HTTP authentication. | | no |
526
-| | password | Password for Basic HTTP authentication. | | no |
527
-| | bearer_token_file | Path to a file containing a bearer token (used for `Authorization: Bearer`). | | no |
528
-| **TLS** | tls_skip_verify | Skip TLS certificate and hostname verification (insecure). | no | no |
529
-| | tls_ca | Path to CA bundle used to validate the server certificate. | | no |
530
-| | tls_cert | Path to client TLS certificate (for mTLS). | | no |
531
-| | tls_key | Path to client TLS private key (for mTLS). | | no |
532
-| **Proxy** | proxy_url | HTTP proxy URL. | | no |
533
-| | proxy_username | Username for proxy Basic HTTP authentication. | | no |
534
-| | proxy_password | Password for proxy Basic HTTP authentication. | | no |
535
-| **Request** | method | HTTP method to use. | GET | no |
536
-| | body | Request body (e.g., for POST/PUT). | | no |
537
-| | headers | Additional HTTP headers (one per line as key: value). | | no |
538
-| | not_follow_redirects | Do not follow HTTP redirects. | no | no |
539
-| | force_http2 | Force HTTP/2 (including h2c over TCP). | no | no |
540
-| **Functions** | functions.dsn | SQL DSN (required for query functions). | | no |
541
-| | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no |
542
-| | functions.top_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
543
-| | functions.top_queries.limit | Maximum number of queries to return. | 500 | no |
544
-| | functions.running_queries.disabled | Disable the [running-queries](#running-queries) function. | no | no |
545
-| | functions.running_queries.timeout | Query timeout (seconds). Uses collector timeout if not set. | | no |
546
-| | functions.running_queries.limit | Maximum number of queries to return. | 500 | no |
547
-| **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no |
548
-
549
-
550
-</details>
551
-
552
-
553
-#### via UI
554
-
555
-Configure the **yugabytedb** collector from the Netdata web interface:
556
-
557
-1. Go to **Nodes**.
558
-2. Select the node **where you want the yugabytedb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
559
-3. The **Collectors → Jobs** view opens by default.
560
-4. In the Search box, type _yugabytedb_ (or scroll the list) to locate the **yugabytedb** collector.
561
-5. Click the **+** next to the **yugabytedb** collector to add a new job.
562
-6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
563
- - **Test** runs the job with the provided settings and shows whether data can be collected.
564
- - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
565
-
566
-
567
-#### via File
568
-
569
-The configuration file name for this integration is `go.d/yugabytedb.conf`.
570
-
571
-The file format is YAML. Generally, the structure is:
572
-
573
-```yaml
574
-update_every: 1
575
-autodetection_retry: 0
576
-jobs:
577
- - name: some_name1
578
- - name: some_name2
579
-```
580
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
581
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
582
-
583
-```bash
584
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
585
-sudo ./edit-config go.d/yugabytedb.conf
586
-```
587
-
588
-##### Examples
589
-
590
-###### Basic
591
-
592
-A basic example configuration.
593
-
594
-```yaml
595
-jobs:
596
- - name: local
597
- url: http://127.0.0.1:7000/prometheus-metrics # Master
598
- # url: http://127.0.0.1:9000/prometheus-metrics # Tablet Server
599
- # url: http://127.0.0.1:12000/prometheus-metrics # YCQL
600
- # url: http://127.0.0.1:13000/prometheus-metrics # YSQL
601
-
602
-```
603
-###### Top queries
604
-
605
-Enable SQL query functions (YSQL).
606
-
607
-<details open><summary>Config</summary>
608
-
609
-```yaml
610
-jobs:
611
- - name: local
612
- url: http://127.0.0.1:7000/prometheus-metrics
613
- functions:
614
- dsn: postgres://yugabyte@127.0.0.1:5433/yugabyte?sslmode=disable
615
-
616
-```
617
-</details>
618
-
619
-###### HTTP authentication
620
-
621
-Basic HTTP authentication.
622
-
623
-<details open><summary>Config</summary>
624
-
625
-```yaml
626
-jobs:
627
- - name: local
628
- url: http://127.0.0.1:7000/prometheus-metrics
629
- username: username
630
- password: password
631
-
632
-```
633
-</details>
634
-
635
-###### HTTPS with self-signed certificate
636
-
637
-NGINX with enabled HTTPS and self-signed certificate.
638
-
639
-<details open><summary>Config</summary>
640
-
641
-```yaml
642
-jobs:
643
- - name: local
644
- url: https://127.0.0.1:7000/prometheus-metrics
645
- tls_skip_verify: yes
646
-
647
-```
648
-</details>
649
-
650
-###### Multi-instance
651
-
652
-> **Note**: When you define multiple jobs, their names must be unique.
653
-
654
-Collecting metrics from local and remote instances.
655
-
656
-
657
-<details open><summary>Config</summary>
658
-
659
-```yaml
660
-jobs:
661
- - name: local
662
- url: http://127.0.0.1:7000/prometheus-metrics
663
-
664
- - name: remote
665
- url: http://192.0.2.1:7000/prometheus-metrics
666
-
667
-```
668
-</details>
669
-
670
-
671
-
672
## Troubleshooting
673
674
### Debug Mode
src/go/plugin/go.d/collector/zfspool/integrations/zfs_pools.md
+59
-59
@@ -48,65 +48,6 @@ The default configuration for this integration does not impose any limits on dat
48
49
The default configuration for this integration is not expected to impose a significant performance impact on the system.
50
51
-## Metrics
52
-
53
-Metrics grouped by *scope*.
54
-
55
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
56
-
57
-
58
-
59
-### Per zfs pool
60
-
61
-These metrics refer to the ZFS pool.
62
-
63
-Labels:
64
-
65
-| Label | Description |
66
-|:-----------|:----------------|
67
-| pool | Zpool name |
68
-
69
-Metrics:
70
-
71
-| Metric | Dimensions | Unit |
72
-|:------|:----------|:----|
73
-| zfspool.pool_space_utilization | utilization | % |
74
-| zfspool.pool_space_usage | free, used | bytes |
75
-| zfspool.pool_fragmentation | fragmentation | % |
76
-| zfspool.pool_health_state | online, degraded, faulted, offline, unavail, removed, suspended | state |
77
-
78
-### Per zfs pool vdev
79
-
80
-These metrics refer to the ZFS pool virtual device.
81
-
82
-Labels:
83
-
84
-| Label | Description |
85
-|:-----------|:----------------|
86
-| pool | Zpool name |
87
-| vdev | Unique identifier for a virtual device (vdev) within a ZFS pool. |
88
-
89
-Metrics:
90
-
91
-| Metric | Dimensions | Unit |
92
-|:------|:----------|:----|
93
-| zfspool.vdev_health_state | online, degraded, faulted, offline, unavail, removed, suspended | state |
94
-
95
-
96
-
97
-## Alerts
98
-
99
-
100
-The following alerts are available:
101
-
102
-| Alert name | On metric | Description |
103
-|:------------|:----------|:------------|
104
-| [ zfs_pool_space_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.pool_space_utilization | ZFS pool ${label:pool} is nearing capacity. Current space usage is above the threshold. |
105
-| [ zfs_pool_health_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.pool_health_state | ZFS pool ${label:pool} state is degraded |
106
-| [ zfs_pool_health_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.pool_health_state | ZFS pool ${label:pool} state is faulted or unavail |
107
-| [ zfs_vdev_health_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.vdev_health_state | ZFS vdev ${label:vdev} state is faulted or degraded |
108
-
109
-
51
## Setup
52
53
@@ -202,6 +143,65 @@ jobs:
143
144
145
146
+## Alerts
147
+
148
+
149
+The following alerts are available:
150
+
151
+| Alert name | On metric | Description |
152
+|:------------|:----------|:------------|
153
+| [ zfs_pool_space_utilization ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.pool_space_utilization | ZFS pool ${label:pool} is nearing capacity. Current space usage is above the threshold. |
154
+| [ zfs_pool_health_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.pool_health_state | ZFS pool ${label:pool} state is degraded |
155
+| [ zfs_pool_health_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.pool_health_state | ZFS pool ${label:pool} state is faulted or unavail |
156
+| [ zfs_vdev_health_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/zfs.conf) | zfspool.vdev_health_state | ZFS vdev ${label:vdev} state is faulted or degraded |
157
+
158
+
159
+## Metrics
160
+
161
+Metrics grouped by *scope*.
162
+
163
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
164
+
165
+
166
+
167
+### Per zfs pool
168
+
169
+These metrics refer to the ZFS pool.
170
+
171
+Labels:
172
+
173
+| Label | Description |
174
+|:-----------|:----------------|
175
+| pool | Zpool name |
176
+
177
+Metrics:
178
+
179
+| Metric | Dimensions | Unit |
180
+|:------|:----------|:----|
181
+| zfspool.pool_space_utilization | utilization | % |
182
+| zfspool.pool_space_usage | free, used | bytes |
183
+| zfspool.pool_fragmentation | fragmentation | % |
184
+| zfspool.pool_health_state | online, degraded, faulted, offline, unavail, removed, suspended | state |
185
+
186
+### Per zfs pool vdev
187
+
188
+These metrics refer to the ZFS pool virtual device.
189
+
190
+Labels:
191
+
192
+| Label | Description |
193
+|:-----------|:----------------|
194
+| pool | Zpool name |
195
+| vdev | Unique identifier for a virtual device (vdev) within a ZFS pool. |
196
+
197
+Metrics:
198
+
199
+| Metric | Dimensions | Unit |
200
+|:------|:----------|:----|
201
+| zfspool.vdev_health_state | online, degraded, faulted, offline, unavail, removed, suspended | state |
202
+
203
+
204
+
205
## Troubleshooting
206
207
### Debug Mode
src/go/plugin/go.d/collector/zookeeper/integrations/zookeeper.md
+43
-43
@@ -55,49 +55,6 @@ The default configuration for this integration does not impose any limits on dat
55
56
The default configuration for this integration is not expected to impose a significant performance impact on the system.
57
58
-## Metrics
59
-
60
-Metrics grouped by *scope*.
61
-
62
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
63
-
64
-
65
-
66
-### Per ZooKeeper server
67
-
68
-These metrics refer to ZooKeeper servers.
69
-
70
-This scope has no labels.
71
-
72
-Metrics:
73
-
74
-| Metric | Dimensions | Unit |
75
-|:------|:----------|:----|
76
-| zookeeper.requests | outstanding | requests |
77
-| zookeeper.requests_latency | min, avg, max | ms |
78
-| zookeeper.stale_requests | stale | requests/s |
79
-| zookeeper.stale_requests_dropped | dropped | requests/s |
80
-| zookeeper.connections | alive | connections |
81
-| zookeeper.connections_dropped | dropped | connections/s |
82
-| zookeeper.connections_rejected | rejected | connections/s |
83
-| zookeeper.auth_fails | auth | fails/s |
84
-| zookeeper.global_sessions | global | sessions |
85
-| zookeeper.server_state | leader, follower, observer, standalone | state |
86
-| zookeeper.throttled_ops | throttled | ops/s |
87
-| zookeeper.packets | received, sent | pps |
88
-| zookeeper.file_descriptor | open | file descriptors |
89
-| zookeeper.nodes | znode, ephemerals | nodes |
90
-| zookeeper.watches | watches | watches |
91
-| zookeeper.approximate_data_size | size | KiB |
92
-| zookeeper.uptime | uptime | seconds |
93
-
94
-
95
-
96
-## Alerts
97
-
98
-There are no alerts configured by default for this integration.
99
-
100
-
58
## Setup
59
60
@@ -240,6 +197,49 @@ jobs:
197
198
199
200
+## Alerts
201
+
202
+There are no alerts configured by default for this integration.
203
+
204
+
205
+## Metrics
206
+
207
+Metrics grouped by *scope*.
208
+
209
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
210
+
211
+
212
+
213
+### Per ZooKeeper server
214
+
215
+These metrics refer to ZooKeeper servers.
216
+
217
+This scope has no labels.
218
+
219
+Metrics:
220
+
221
+| Metric | Dimensions | Unit |
222
+|:------|:----------|:----|
223
+| zookeeper.requests | outstanding | requests |
224
+| zookeeper.requests_latency | min, avg, max | ms |
225
+| zookeeper.stale_requests | stale | requests/s |
226
+| zookeeper.stale_requests_dropped | dropped | requests/s |
227
+| zookeeper.connections | alive | connections |
228
+| zookeeper.connections_dropped | dropped | connections/s |
229
+| zookeeper.connections_rejected | rejected | connections/s |
230
+| zookeeper.auth_fails | auth | fails/s |
231
+| zookeeper.global_sessions | global | sessions |
232
+| zookeeper.server_state | leader, follower, observer, standalone | state |
233
+| zookeeper.throttled_ops | throttled | ops/s |
234
+| zookeeper.packets | received, sent | pps |
235
+| zookeeper.file_descriptor | open | file descriptors |
236
+| zookeeper.nodes | znode, ephemerals | nodes |
237
+| zookeeper.watches | watches | watches |
238
+| zookeeper.approximate_data_size | size | KiB |
239
+| zookeeper.uptime | uptime | seconds |
240
+
241
+
242
+
243
## Troubleshooting
244
245
### Debug Mode
src/go/plugin/ibm.d/modules/as400/integrations/ibm_i_as-400.md
+68
-68
@@ -181,6 +181,74 @@ The default configuration for this integration does not impose any limits on dat
181
182
The default configuration for this integration is not expected to impose a significant performance impact on the system.
183
184
+## Setup
185
+
186
+
187
+### Prerequisites
188
+
189
+#### Enable monitoring interface
190
+
191
+Ensure the IBM i (AS/400) monitoring interface is accessible.
192
+
193
+
194
+
195
+### Configuration
196
+
197
+#### Options
198
+
199
+Configuration options for the as400 collector.
200
+
201
+
202
+<details open><summary>Config options</summary>
203
+
204
+
205
+
206
+| Option | Description | Default | Required |
207
+|:-----|:------------|:--------|:---------:|
208
+| update_every | Data collection frequency. | 1 | no |
209
+| endpoint | Connection endpoint. | dummy://localhost | no |
210
+
211
+
212
+</details>
213
+
214
+
215
+
216
+#### via File
217
+
218
+The configuration file name for this integration is `ibm.d/as400.conf`.
219
+
220
+
221
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
222
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
223
+
224
+```bash
225
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
226
+sudo ./edit-config ibm.d/as400.conf
227
+```
228
+
229
+##### Examples
230
+
231
+###### Basic
232
+
233
+Basic configuration example.
234
+
235
+<details open><summary>Config</summary>
236
+
237
+```yaml
238
+jobs:
239
+ - name: local
240
+ endpoint: dummy://localhost
241
+
242
+```
243
+</details>
244
+
245
+
246
+
247
+## Alerts
248
+
249
+There are no alerts configured by default for this integration.
250
+
251
+
252
## Metrics
253
254
Metrics grouped by *scope*.
@@ -454,71 +522,3 @@ Metrics:
522
| as400.temp_storage_bucket | current, peak | bytes |
523
524
457
-
458
-## Alerts
459
-
460
-There are no alerts configured by default for this integration.
461
-
462
-
463
-## Setup
464
-
465
-
466
-### Prerequisites
467
-
468
-#### Enable monitoring interface
469
-
470
-Ensure the IBM i (AS/400) monitoring interface is accessible.
471
-
472
-
473
-
474
-### Configuration
475
-
476
-#### Options
477
-
478
-Configuration options for the as400 collector.
479
-
480
-
481
-<details open><summary>Config options</summary>
482
-
483
-
484
-
485
-| Option | Description | Default | Required |
486
-|:-----|:------------|:--------|:---------:|
487
-| update_every | Data collection frequency. | 1 | no |
488
-| endpoint | Connection endpoint. | dummy://localhost | no |
489
-
490
-
491
-</details>
492
-
493
-
494
-
495
-#### via File
496
-
497
-The configuration file name for this integration is `ibm.d/as400.conf`.
498
-
499
-
500
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
501
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
502
-
503
-```bash
504
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
505
-sudo ./edit-config ibm.d/as400.conf
506
-```
507
-
508
-##### Examples
509
-
510
-###### Basic
511
-
512
-Basic configuration example.
513
-
514
-<details open><summary>Config</summary>
515
-
516
-```yaml
517
-jobs:
518
- - name: local
519
- endpoint: dummy://localhost
520
-
521
-```
522
-</details>
523
-
524
-
src/go/plugin/ibm.d/modules/db2/integrations/ibm_db2.md
+68
-68
@@ -60,6 +60,74 @@ The default configuration for this integration does not impose any limits on dat
60
61
The default configuration for this integration is not expected to impose a significant performance impact on the system.
62
63
+## Setup
64
+
65
+
66
+### Prerequisites
67
+
68
+#### Enable monitoring interface
69
+
70
+Ensure the IBM DB2 monitoring interface is accessible.
71
+
72
+
73
+
74
+### Configuration
75
+
76
+#### Options
77
+
78
+Configuration options for the db2 collector.
79
+
80
+
81
+<details open><summary>Config options</summary>
82
+
83
+
84
+
85
+| Option | Description | Default | Required |
86
+|:-----|:------------|:--------|:---------:|
87
+| update_every | Data collection frequency. | 1 | no |
88
+| endpoint | Connection endpoint. | dummy://localhost | no |
89
+
90
+
91
+</details>
92
+
93
+
94
+
95
+#### via File
96
+
97
+The configuration file name for this integration is `ibm.d/db2.conf`.
98
+
99
+
100
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
101
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
102
+
103
+```bash
104
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
105
+sudo ./edit-config ibm.d/db2.conf
106
+```
107
+
108
+##### Examples
109
+
110
+###### Basic
111
+
112
+Basic configuration example.
113
+
114
+<details open><summary>Config</summary>
115
+
116
+```yaml
117
+jobs:
118
+ - name: local
119
+ endpoint: dummy://localhost
120
+
121
+```
122
+</details>
123
+
124
+
125
+
126
+## Alerts
127
+
128
+There are no alerts configured by default for this integration.
129
+
130
+
131
## Metrics
132
133
Metrics grouped by *scope*.
@@ -412,71 +480,3 @@ Metrics:
480
| db2.tablespace_group_state | state | state |
481
482
415
-
416
-## Alerts
417
-
418
-There are no alerts configured by default for this integration.
419
-
420
-
421
-## Setup
422
-
423
-
424
-### Prerequisites
425
-
426
-#### Enable monitoring interface
427
-
428
-Ensure the IBM DB2 monitoring interface is accessible.
429
-
430
-
431
-
432
-### Configuration
433
-
434
-#### Options
435
-
436
-Configuration options for the db2 collector.
437
-
438
-
439
-<details open><summary>Config options</summary>
440
-
441
-
442
-
443
-| Option | Description | Default | Required |
444
-|:-----|:------------|:--------|:---------:|
445
-| update_every | Data collection frequency. | 1 | no |
446
-| endpoint | Connection endpoint. | dummy://localhost | no |
447
-
448
-
449
-</details>
450
-
451
-
452
-
453
-#### via File
454
-
455
-The configuration file name for this integration is `ibm.d/db2.conf`.
456
-
457
-
458
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
459
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
460
-
461
-```bash
462
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
463
-sudo ./edit-config ibm.d/db2.conf
464
-```
465
-
466
-##### Examples
467
-
468
-###### Basic
469
-
470
-Basic configuration example.
471
-
472
-<details open><summary>Config</summary>
473
-
474
-```yaml
475
-jobs:
476
- - name: local
477
- endpoint: dummy://localhost
478
-
479
-```
480
-</details>
481
-
482
-
src/go/plugin/ibm.d/modules/mq/integrations/ibm_mq.md
+68
-68
@@ -60,6 +60,74 @@ The default configuration for this integration does not impose any limits on dat
60
61
The default configuration for this integration is not expected to impose a significant performance impact on the system.
62
63
+## Setup
64
+
65
+
66
+### Prerequisites
67
+
68
+#### Enable monitoring interface
69
+
70
+Ensure the IBM MQ monitoring interface is accessible.
71
+
72
+
73
+
74
+### Configuration
75
+
76
+#### Options
77
+
78
+Configuration options for the mq collector.
79
+
80
+
81
+<details open><summary>Config options</summary>
82
+
83
+
84
+
85
+| Option | Description | Default | Required |
86
+|:-----|:------------|:--------|:---------:|
87
+| update_every | Data collection frequency. | 1 | no |
88
+| endpoint | Connection endpoint. | dummy://localhost | no |
89
+
90
+
91
+</details>
92
+
93
+
94
+
95
+#### via File
96
+
97
+The configuration file name for this integration is `ibm.d/mq.conf`.
98
+
99
+
100
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
101
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
102
+
103
+```bash
104
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
105
+sudo ./edit-config ibm.d/mq.conf
106
+```
107
+
108
+##### Examples
109
+
110
+###### Basic
111
+
112
+Basic configuration example.
113
+
114
+<details open><summary>Config</summary>
115
+
116
+```yaml
117
+jobs:
118
+ - name: local
119
+ endpoint: dummy://localhost
120
+
121
+```
122
+</details>
123
+
124
+
125
+
126
+## Alerts
127
+
128
+There are no alerts configured by default for this integration.
129
+
130
+
131
## Metrics
132
133
Metrics grouped by *scope*.
@@ -320,71 +388,3 @@ Metrics:
388
| mq.topic.time_since_last_message | time_since_last_msg | seconds |
389
390
323
-
324
-## Alerts
325
-
326
-There are no alerts configured by default for this integration.
327
-
328
-
329
-## Setup
330
-
331
-
332
-### Prerequisites
333
-
334
-#### Enable monitoring interface
335
-
336
-Ensure the IBM MQ monitoring interface is accessible.
337
-
338
-
339
-
340
-### Configuration
341
-
342
-#### Options
343
-
344
-Configuration options for the mq collector.
345
-
346
-
347
-<details open><summary>Config options</summary>
348
-
349
-
350
-
351
-| Option | Description | Default | Required |
352
-|:-----|:------------|:--------|:---------:|
353
-| update_every | Data collection frequency. | 1 | no |
354
-| endpoint | Connection endpoint. | dummy://localhost | no |
355
-
356
-
357
-</details>
358
-
359
-
360
-
361
-#### via File
362
-
363
-The configuration file name for this integration is `ibm.d/mq.conf`.
364
-
365
-
366
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
367
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
368
-
369
-```bash
370
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
371
-sudo ./edit-config ibm.d/mq.conf
372
-```
373
-
374
-##### Examples
375
-
376
-###### Basic
377
-
378
-Basic configuration example.
379
-
380
-<details open><summary>Config</summary>
381
-
382
-```yaml
383
-jobs:
384
- - name: local
385
- endpoint: dummy://localhost
386
-
387
-```
388
-</details>
389
-
390
-
src/go/plugin/ibm.d/modules/websphere/jmx/integrations/ibm_websphere_jmx.md
+68
-68
@@ -43,6 +43,74 @@ The default configuration for this integration does not impose any limits on dat
43
44
The default configuration for this integration is not expected to impose a significant performance impact on the system.
45
46
+## Setup
47
+
48
+
49
+### Prerequisites
50
+
51
+#### Enable monitoring interface
52
+
53
+Ensure the IBM WebSphere JMX monitoring interface is accessible.
54
+
55
+
56
+
57
+### Configuration
58
+
59
+#### Options
60
+
61
+Configuration options for the websphere_jmx collector.
62
+
63
+
64
+<details open><summary>Config options</summary>
65
+
66
+
67
+
68
+| Option | Description | Default | Required |
69
+|:-----|:------------|:--------|:---------:|
70
+| update_every | Data collection frequency. | 1 | no |
71
+| endpoint | Connection endpoint. | dummy://localhost | no |
72
+
73
+
74
+</details>
75
+
76
+
77
+
78
+#### via File
79
+
80
+The configuration file name for this integration is `ibm.d/websphere_jmx.conf`.
81
+
82
+
83
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
84
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
85
+
86
+```bash
87
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
88
+sudo ./edit-config ibm.d/websphere_jmx.conf
89
+```
90
+
91
+##### Examples
92
+
93
+###### Basic
94
+
95
+Basic configuration example.
96
+
97
+<details open><summary>Config</summary>
98
+
99
+```yaml
100
+jobs:
101
+ - name: local
102
+ endpoint: dummy://localhost
103
+
104
+```
105
+</details>
106
+
107
+
108
+
109
+## Alerts
110
+
111
+There are no alerts configured by default for this integration.
112
+
113
+
114
## Metrics
115
116
Metrics grouped by *scope*.
@@ -174,71 +242,3 @@ Metrics:
242
| websphere_jmx.threadpool_active | active | threads |
243
244
177
-
178
-## Alerts
179
-
180
-There are no alerts configured by default for this integration.
181
-
182
-
183
-## Setup
184
-
185
-
186
-### Prerequisites
187
-
188
-#### Enable monitoring interface
189
-
190
-Ensure the IBM WebSphere JMX monitoring interface is accessible.
191
-
192
-
193
-
194
-### Configuration
195
-
196
-#### Options
197
-
198
-Configuration options for the websphere_jmx collector.
199
-
200
-
201
-<details open><summary>Config options</summary>
202
-
203
-
204
-
205
-| Option | Description | Default | Required |
206
-|:-----|:------------|:--------|:---------:|
207
-| update_every | Data collection frequency. | 1 | no |
208
-| endpoint | Connection endpoint. | dummy://localhost | no |
209
-
210
-
211
-</details>
212
-
213
-
214
-
215
-#### via File
216
-
217
-The configuration file name for this integration is `ibm.d/websphere_jmx.conf`.
218
-
219
-
220
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
221
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
222
-
223
-```bash
224
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
225
-sudo ./edit-config ibm.d/websphere_jmx.conf
226
-```
227
-
228
-##### Examples
229
-
230
-###### Basic
231
-
232
-Basic configuration example.
233
-
234
-<details open><summary>Config</summary>
235
-
236
-```yaml
237
-jobs:
238
- - name: local
239
- endpoint: dummy://localhost
240
-
241
-```
242
-</details>
243
-
244
-
src/go/plugin/ibm.d/modules/websphere/mp/integrations/ibm_websphere_microprofile.md
+68
-68
@@ -47,6 +47,74 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
+## Setup
51
+
52
+
53
+### Prerequisites
54
+
55
+#### Enable monitoring interface
56
+
57
+Ensure the IBM WebSphere MicroProfile monitoring interface is accessible.
58
+
59
+
60
+
61
+### Configuration
62
+
63
+#### Options
64
+
65
+Configuration options for the websphere_mp collector.
66
+
67
+
68
+<details open><summary>Config options</summary>
69
+
70
+
71
+
72
+| Option | Description | Default | Required |
73
+|:-----|:------------|:--------|:---------:|
74
+| update_every | Data collection frequency. | 1 | no |
75
+| endpoint | Connection endpoint. | dummy://localhost | no |
76
+
77
+
78
+</details>
79
+
80
+
81
+
82
+#### via File
83
+
84
+The configuration file name for this integration is `ibm.d/websphere_mp.conf`.
85
+
86
+
87
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
88
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
89
+
90
+```bash
91
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
92
+sudo ./edit-config ibm.d/websphere_mp.conf
93
+```
94
+
95
+##### Examples
96
+
97
+###### Basic
98
+
99
+Basic configuration example.
100
+
101
+<details open><summary>Config</summary>
102
+
103
+```yaml
104
+jobs:
105
+ - name: local
106
+ endpoint: dummy://localhost
107
+
108
+```
109
+</details>
110
+
111
+
112
+
113
+## Alerts
114
+
115
+There are no alerts configured by default for this integration.
116
+
117
+
118
## Metrics
119
120
Metrics grouped by *scope*.
@@ -119,71 +187,3 @@ Metrics:
187
| websphere_mp.threadpool_size | size | threads |
188
189
122
-
123
-## Alerts
124
-
125
-There are no alerts configured by default for this integration.
126
-
127
-
128
-## Setup
129
-
130
-
131
-### Prerequisites
132
-
133
-#### Enable monitoring interface
134
-
135
-Ensure the IBM WebSphere MicroProfile monitoring interface is accessible.
136
-
137
-
138
-
139
-### Configuration
140
-
141
-#### Options
142
-
143
-Configuration options for the websphere_mp collector.
144
-
145
-
146
-<details open><summary>Config options</summary>
147
-
148
-
149
-
150
-| Option | Description | Default | Required |
151
-|:-----|:------------|:--------|:---------:|
152
-| update_every | Data collection frequency. | 1 | no |
153
-| endpoint | Connection endpoint. | dummy://localhost | no |
154
-
155
-
156
-</details>
157
-
158
-
159
-
160
-#### via File
161
-
162
-The configuration file name for this integration is `ibm.d/websphere_mp.conf`.
163
-
164
-
165
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
166
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
167
-
168
-```bash
169
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
170
-sudo ./edit-config ibm.d/websphere_mp.conf
171
-```
172
-
173
-##### Examples
174
-
175
-###### Basic
176
-
177
-Basic configuration example.
178
-
179
-<details open><summary>Config</summary>
180
-
181
-```yaml
182
-jobs:
183
- - name: local
184
- endpoint: dummy://localhost
185
-
186
-```
187
-</details>
188
-
189
-
src/go/plugin/ibm.d/modules/websphere/pmi/integrations/ibm_websphere_pmi.md
+68
-68
@@ -47,6 +47,74 @@ The default configuration for this integration does not impose any limits on dat
47
48
The default configuration for this integration is not expected to impose a significant performance impact on the system.
49
50
+## Setup
51
+
52
+
53
+### Prerequisites
54
+
55
+#### Enable monitoring interface
56
+
57
+Ensure the IBM WebSphere PMI monitoring interface is accessible.
58
+
59
+
60
+
61
+### Configuration
62
+
63
+#### Options
64
+
65
+Configuration options for the websphere_pmi collector.
66
+
67
+
68
+<details open><summary>Config options</summary>
69
+
70
+
71
+
72
+| Option | Description | Default | Required |
73
+|:-----|:------------|:--------|:---------:|
74
+| update_every | Data collection frequency. | 1 | no |
75
+| endpoint | Connection endpoint. | dummy://localhost | no |
76
+
77
+
78
+</details>
79
+
80
+
81
+
82
+#### via File
83
+
84
+The configuration file name for this integration is `ibm.d/websphere_pmi.conf`.
85
+
86
+
87
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
88
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
89
+
90
+```bash
91
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
92
+sudo ./edit-config ibm.d/websphere_pmi.conf
93
+```
94
+
95
+##### Examples
96
+
97
+###### Basic
98
+
99
+Basic configuration example.
100
+
101
+<details open><summary>Config</summary>
102
+
103
+```yaml
104
+jobs:
105
+ - name: local
106
+ endpoint: dummy://localhost
107
+
108
+```
109
+</details>
110
+
111
+
112
+
113
+## Alerts
114
+
115
+There are no alerts configured by default for this integration.
116
+
117
+
118
## Metrics
119
120
Metrics grouped by *scope*.
@@ -579,71 +647,3 @@ Metrics:
647
| websphere_pmi.web_services_gateway_requests | synchronous, synchronous_responses, asynchronous, asynchronous_responses | requests/s |
648
649
582
-
583
-## Alerts
584
-
585
-There are no alerts configured by default for this integration.
586
-
587
-
588
-## Setup
589
-
590
-
591
-### Prerequisites
592
-
593
-#### Enable monitoring interface
594
-
595
-Ensure the IBM WebSphere PMI monitoring interface is accessible.
596
-
597
-
598
-
599
-### Configuration
600
-
601
-#### Options
602
-
603
-Configuration options for the websphere_pmi collector.
604
-
605
-
606
-<details open><summary>Config options</summary>
607
-
608
-
609
-
610
-| Option | Description | Default | Required |
611
-|:-----|:------------|:--------|:---------:|
612
-| update_every | Data collection frequency. | 1 | no |
613
-| endpoint | Connection endpoint. | dummy://localhost | no |
614
-
615
-
616
-</details>
617
-
618
-
619
-
620
-#### via File
621
-
622
-The configuration file name for this integration is `ibm.d/websphere_pmi.conf`.
623
-
624
-
625
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-configuration-files) script from the
626
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#locate-your-config-directory).
627
-
628
-```bash
629
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
630
-sudo ./edit-config ibm.d/websphere_pmi.conf
631
-```
632
-
633
-##### Examples
634
-
635
-###### Basic
636
-
637
-Basic configuration example.
638
-
639
-<details open><summary>Config</summary>
640
-
641
-```yaml
642
-jobs:
643
- - name: local
644
- endpoint: dummy://localhost
645
-
646
-```
647
-</details>
648
-
649
-
src/go/plugin/scripts.d/collector/nagios/integrations/nagios_plugins.md
+45
-45
@@ -171,51 +171,6 @@ Each job runs one configured command. Additional charts are created only when th
171
Each job starts an external command. The impact depends mostly on how often the job runs and how expensive the check command itself is.
172
173
174
-## Metrics
175
-
176
-Metrics grouped by *scope*.
177
-
178
-The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
179
-
180
-Each configured job produces execution state and resource usage charts. When a check emits Nagios performance data, additional charts are created automatically for each metric. Non-counter perfdata with warning/critical thresholds also get threshold state charts for alerting.
181
-
182
-
183
-### Per job
184
-
185
-These metrics refer to each configured check job.
186
-
187
-Labels:
188
-
189
-| Label | Description |
190
-|:-----------|:----------------|
191
-| nagios_job | Job name as defined in the configuration. |
192
-| perfdata_value | Identifies which performance data metric a threshold state belongs to. Format is `<unit_class>_<label>`, where `<unit_class>` is derived from the UOM (`time`, `bytes`, `bits`, `percent`, or `generic`) and `<label>` is the sanitized metric label from the check output. For example, `repl_lag=5s` produces `time_repl_lag`. |
193
-
194
-Metrics:
195
-
196
-| Metric | Dimensions | Unit |
197
-|:------|:----------|:----|
198
-| nagios.job.execution_state | ok, warning, critical, unknown, timeout, paused, retry | state |
199
-| nagios.job.perfdata_threshold_state | no_threshold, ok, warning, critical, retry | state |
200
-| nagios.job.execution_duration | duration | seconds |
201
-| nagios.job.execution_cpu_total | total | seconds |
202
-| nagios.job.execution_max_rss | rss | bytes |
203
-
204
-
205
-
206
-## Alerts
207
-
208
-
209
-The following alerts are available:
210
-
211
-| Alert name | On metric | Description |
212
-|:------------|:----------|:------------|
213
-| [ nagios_job_execution_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.execution_state | Nagios job ${label:nagios_job} is in WARNING state |
214
-| [ nagios_job_execution_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.execution_state | Nagios job ${label:nagios_job} is in CRITICAL state |
215
-| [ nagios_job_perfdata_threshold_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.perfdata_threshold_state | Nagios job ${label:nagios_job} perfdata ${label:perfdata_value} is in WARNING threshold state |
216
-| [ nagios_job_perfdata_threshold_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.perfdata_threshold_state | Nagios job ${label:nagios_job} perfdata ${label:perfdata_value} is in CRITICAL threshold state |
217
-
218
-
174
## Setup
175
176
@@ -467,6 +422,51 @@ jobs:
422
423
424
425
+## Alerts
426
+
427
+
428
+The following alerts are available:
429
+
430
+| Alert name | On metric | Description |
431
+|:------------|:----------|:------------|
432
+| [ nagios_job_execution_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.execution_state | Nagios job ${label:nagios_job} is in WARNING state |
433
+| [ nagios_job_execution_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.execution_state | Nagios job ${label:nagios_job} is in CRITICAL state |
434
+| [ nagios_job_perfdata_threshold_state_warn ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.perfdata_threshold_state | Nagios job ${label:nagios_job} perfdata ${label:perfdata_value} is in WARNING threshold state |
435
+| [ nagios_job_perfdata_threshold_state_crit ](https://github.com/netdata/netdata/blob/master/src/health/health.d/nagios.conf) | nagios.job.perfdata_threshold_state | Nagios job ${label:nagios_job} perfdata ${label:perfdata_value} is in CRITICAL threshold state |
436
+
437
+
438
+## Metrics
439
+
440
+Metrics grouped by *scope*.
441
+
442
+The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
443
+
444
+Each configured job produces execution state and resource usage charts. When a check emits Nagios performance data, additional charts are created automatically for each metric. Non-counter perfdata with warning/critical thresholds also get threshold state charts for alerting.
445
+
446
+
447
+### Per job
448
+
449
+These metrics refer to each configured check job.
450
+
451
+Labels:
452
+
453
+| Label | Description |
454
+|:-----------|:----------------|
455
+| nagios_job | Job name as defined in the configuration. |
456
+| perfdata_value | Identifies which performance data metric a threshold state belongs to. Format is `<unit_class>_<label>`, where `<unit_class>` is derived from the UOM (`time`, `bytes`, `bits`, `percent`, or `generic`) and `<label>` is the sanitized metric label from the check output. For example, `repl_lag=5s` produces `time_repl_lag`. |
457
+
458
+Metrics:
459
+
460
+| Metric | Dimensions | Unit |
461
+|:------|:----------|:----|
462
+| nagios.job.execution_state | ok, warning, critical, unknown, timeout, paused, retry | state |
463
+| nagios.job.perfdata_threshold_state | no_threshold, ok, warning, critical, retry | state |
464
+| nagios.job.execution_duration | duration | seconds |
465
+| nagios.job.execution_cpu_total | total | seconds |
466
+| nagios.job.execution_max_rss | rss | bytes |
467
+
468
+
469
+
470
## Troubleshooting
471
472
### The command cannot be executed