@cryptotaxi247 / netdata-1 / commits / 37168ccc7

Regenerate integrations docs (#20978)

Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>

Netdata bot committed Sep 14, 2025 at 18:14 UTC 37168ccc7336fa127f54c619ec8ae12d361132ef
613 files changed +8669 -1618
integrations/cloud-authentication/integrations/oidc.md
+1
@@ -20,6 +20,7 @@ Integrate your organization's Authorization Servers with Netdata to better manag
20
21 ## Setup
22
23 +
24 ### Prerequisites
25 - Authorization Server with OIDC protocol supported
26 - A Netdata Cloud account
integrations/cloud-authentication/integrations/okta_sso.md
+1
@@ -20,6 +20,7 @@ Integrate your organization's Okta account with Netdata to better manage your te
20
21 ## Setup
22
23 +
24 ### Prerequisites
25 - An Okta account
26 - A Netdata Cloud account
integrations/cloud-authentication/integrations/scim.md
+1
@@ -20,6 +20,7 @@ The System for Cross-domain Identity Management (SCIM) specification is designed
20
21 ## Setup
22
23 +
24 ### Prerequisites
25 - A Netdata Cloud account
26 - Admin access to the Space
integrations/cloud-notifications/integrations/amazon_sns.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/discord.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/ilert.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/mattermost.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/microsoft_teams.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/netdata_mobile_app.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/opsgenie.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/pagerduty.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/rocketchat.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/slack.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/splunk.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/splunk_victorops.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/telegram.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
integrations/cloud-notifications/integrations/webhook.md
+1
@@ -15,6 +15,7 @@ endmeta-->
15
16 ## Setup
17
18 +
19 ### Prerequisites
20
21 - A Netdata Cloud account
src/collectors/apps.plugin/integrations/applications.md
+1
@@ -93,6 +93,7 @@ There are no alerts configured by default for this integration.
93
94 ## Setup
95
96 +
97 ### Prerequisites
98
99 No action required.
src/collectors/apps.plugin/integrations/user_groups.md
+1
@@ -93,6 +93,7 @@ There are no alerts configured by default for this integration.
93
94 ## Setup
95
96 +
97 ### Prerequisites
98
99 No action required.
src/collectors/apps.plugin/integrations/users.md
+1
@@ -93,6 +93,7 @@ There are no alerts configured by default for this integration.
93
94 ## Setup
95
96 +
97 ### Prerequisites
98
99 No action required.
src/collectors/cgroups.plugin/integrations/containers.md
+1
@@ -148,6 +148,7 @@ The following alerts are available:
148
149 ## Setup
150
151 +
152 ### Prerequisites
153
154 No action required.
src/collectors/cgroups.plugin/integrations/kubernetes_containers.md
+1
@@ -162,6 +162,7 @@ The following alerts are available:
162
163 ## Setup
164
165 +
166 ### Prerequisites
167
168 No action required.
src/collectors/cgroups.plugin/integrations/libvirt_containers.md
+1
@@ -148,6 +148,7 @@ The following alerts are available:
148
149 ## Setup
150
151 +
152 ### Prerequisites
153
154 No action required.
src/collectors/cgroups.plugin/integrations/lxc_containers.md
+1
@@ -148,6 +148,7 @@ The following alerts are available:
148
149 ## Setup
150
151 +
152 ### Prerequisites
153
154 No action required.
src/collectors/cgroups.plugin/integrations/ovirt_containers.md
+1
@@ -148,6 +148,7 @@ The following alerts are available:
148
149 ## Setup
150
151 +
152 ### Prerequisites
153
154 No action required.
src/collectors/cgroups.plugin/integrations/proxmox_containers.md
+1
@@ -148,6 +148,7 @@ The following alerts are available:
148
149 ## Setup
150
151 +
152 ### Prerequisites
153
154 No action required.
src/collectors/cgroups.plugin/integrations/systemd_services.md
+1
@@ -91,6 +91,7 @@ There are no alerts configured by default for this integration.
91
92 ## Setup
93
94 +
95 ### Prerequisites
96
97 No action required.
src/collectors/cgroups.plugin/integrations/virtual_machines.md
+1
@@ -148,6 +148,7 @@ The following alerts are available:
148
149 ## Setup
150
151 +
152 ### Prerequisites
153
154 No action required.
src/collectors/charts.d.plugin/libreswan/integrations/libreswan.md
+1
@@ -75,6 +75,7 @@ There are no alerts configured by default for this integration.
75
76 ## Setup
77
78 +
79 ### Prerequisites
80
81 #### Install charts.d plugin
src/collectors/charts.d.plugin/opensips/integrations/opensips.md
+1
@@ -92,6 +92,7 @@ There are no alerts configured by default for this integration.
92
93 ## Setup
94
95 +
96 ### Prerequisites
97
98 #### Install charts.d plugin
src/collectors/cups.plugin/integrations/cups.md
+1
@@ -91,6 +91,7 @@ There are no alerts configured by default for this integration.
91
92 ## Setup
93
94 +
95 ### Prerequisites
96
97 #### Minimum setup
src/collectors/debugfs.plugin/integrations/linux_zswap.md
+1
@@ -87,6 +87,7 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 ### Prerequisites
92
93 #### filesystem
src/collectors/debugfs.plugin/integrations/power_capping.md
+1
@@ -81,6 +81,7 @@ There are no alerts configured by default for this integration.
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 #### filesystem
src/collectors/debugfs.plugin/integrations/system_memory_fragmentation.md
+1
@@ -85,6 +85,7 @@ There are no alerts configured by default for this integration.
85
86 ## Setup
87
88 +
89 ### Prerequisites
90
91 #### filesystem
src/collectors/diskspace.plugin/integrations/disk_space.md
+1
@@ -87,6 +87,7 @@ The following alerts are available:
87
88 ## Setup
89
90 +
91 ### Prerequisites
92
93 No action required.
src/collectors/ebpf.plugin/integrations/ebpf_cachestat.md
+1
@@ -118,6 +118,7 @@ There are no alerts configured by default for this integration.
118
119 ## Setup
120
121 +
122 ### Prerequisites
123
124 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_dcstat.md
+1
@@ -116,6 +116,7 @@ There are no alerts configured by default for this integration.
116
117 ## Setup
118
119 +
120 ### Prerequisites
121
122 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_disk.md
+1
@@ -77,6 +77,7 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 ### Prerequisites
82
83 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_filedescriptor.md
+1
@@ -116,6 +116,7 @@ There are no alerts configured by default for this integration.
116
117 ## Setup
118
119 +
120 ### Prerequisites
121
122 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_filesystem.md
+1
@@ -103,6 +103,7 @@ There are no alerts configured by default for this integration.
103
104 ## Setup
105
106 +
107 ### Prerequisites
108
109 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_hardirq.md
+1
@@ -77,6 +77,7 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 ### Prerequisites
82
83 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_mdflush.md
+1
@@ -77,6 +77,7 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 ### Prerequisites
82
83 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_mount.md
+1
@@ -78,6 +78,7 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 ### Prerequisites
83
84 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_oomkill.md
+1
@@ -94,6 +94,7 @@ There are no alerts configured by default for this integration.
94
95 ## Setup
96
97 +
98 ### Prerequisites
99
100 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_process.md
+1
@@ -85,6 +85,7 @@ There are no alerts configured by default for this integration.
85
86 ## Setup
87
88 +
89 ### Prerequisites
90
91 #### Netdata flags.
src/collectors/ebpf.plugin/integrations/ebpf_processes.md
+1
@@ -121,6 +121,7 @@ There are no alerts configured by default for this integration.
121
122 ## Setup
123
124 +
125 ### Prerequisites
126
127 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_shm.md
+1
@@ -115,6 +115,7 @@ There are no alerts configured by default for this integration.
115
116 ## Setup
117
118 +
119 ### Prerequisites
120
121 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_socket.md
+1
@@ -135,6 +135,7 @@ There are no alerts configured by default for this integration.
135
136 ## Setup
137
138 +
139 ### Prerequisites
140
141 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_softirq.md
+1
@@ -77,6 +77,7 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 ### Prerequisites
82
83 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_swap.md
+1
@@ -109,6 +109,7 @@ There are no alerts configured by default for this integration.
109
110 ## Setup
111
112 +
113 ### Prerequisites
114
115 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_sync.md
+1
@@ -85,6 +85,7 @@ The following alerts are available:
85
86 ## Setup
87
88 +
89 ### Prerequisites
90
91 #### Compile kernel
src/collectors/ebpf.plugin/integrations/ebpf_vfs.md
+1
@@ -151,6 +151,7 @@ There are no alerts configured by default for this integration.
151
152 ## Setup
153
154 +
155 ### Prerequisites
156
157 #### Compile kernel
src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md
+1
@@ -74,6 +74,7 @@ There are no alerts configured by default for this integration.
74
75 ## Setup
76
77 +
78 ### Prerequisites
79
80 No action required.
src/collectors/freebsd.plugin/integrations/dev.cpu.temperature.md
+1
@@ -74,6 +74,7 @@ There are no alerts configured by default for this integration.
74
75 ## Setup
76
77 +
78 ### Prerequisites
79
80 No action required.
src/collectors/freebsd.plugin/integrations/devstat.md
+1
@@ -98,6 +98,7 @@ The following alerts are available:
98
99 ## Setup
100
101 +
102 ### Prerequisites
103
104 No action required.
src/collectors/freebsd.plugin/integrations/getifaddrs.md
+1
@@ -104,6 +104,7 @@ The following alerts are available:
104
105 ## Setup
106
107 +
108 ### Prerequisites
109
110 No action required.
src/collectors/freebsd.plugin/integrations/getmntinfo.md
+1
@@ -81,6 +81,7 @@ The following alerts are available:
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 No action required.
src/collectors/freebsd.plugin/integrations/hw.intrcnt.md
+1
@@ -75,6 +75,7 @@ There are no alerts configured by default for this integration.
75
76 ## Setup
77
78 +
79 ### Prerequisites
80
81 No action required.
src/collectors/freebsd.plugin/integrations/ipfw.md
+1
@@ -78,6 +78,7 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 ### Prerequisites
83
84 No action required.
src/collectors/freebsd.plugin/integrations/kern.cp_time.md
+1
@@ -94,6 +94,7 @@ The following alerts are available:
94
95 ## Setup
96
97 +
98 ### Prerequisites
99
100 No action required.
src/collectors/freebsd.plugin/integrations/kern.ipc.msq.md
+1
@@ -76,6 +76,7 @@ There are no alerts configured by default for this integration.
76
77 ## Setup
78
79 +
80 ### Prerequisites
81
82 No action required.
src/collectors/freebsd.plugin/integrations/kern.ipc.sem.md
+1
@@ -81,6 +81,7 @@ The following alerts are available:
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 No action required.
src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md
+1
@@ -75,6 +75,7 @@ There are no alerts configured by default for this integration.
75
76 ## Setup
77
78 +
79 ### Prerequisites
80
81 No action required.
src/collectors/freebsd.plugin/integrations/net.inet.icmp.stats.md
+1
@@ -76,6 +76,7 @@ There are no alerts configured by default for this integration.
76
77 ## Setup
78
79 +
80 ### Prerequisites
81
82 No action required.
src/collectors/freebsd.plugin/integrations/net.inet.ip.stats.md
+1
@@ -77,6 +77,7 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 ### Prerequisites
82
83 No action required.
src/collectors/freebsd.plugin/integrations/net.inet.tcp.states.md
+1
@@ -79,6 +79,7 @@ The following alerts are available:
79
80 ## Setup
81
82 +
83 ### Prerequisites
84
85 No action required.
src/collectors/freebsd.plugin/integrations/net.inet.tcp.stats.md
+1
@@ -89,6 +89,7 @@ The following alerts are available:
89
90 ## Setup
91
92 +
93 ### Prerequisites
94
95 No action required.
src/collectors/freebsd.plugin/integrations/net.inet.udp.stats.md
+1
@@ -81,6 +81,7 @@ The following alerts are available:
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 No action required.
src/collectors/freebsd.plugin/integrations/net.inet6.icmp6.stats.md
+1
@@ -80,6 +80,7 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 ### Prerequisites
85
86 No action required.
src/collectors/freebsd.plugin/integrations/net.inet6.ip6.stats.md
+1
@@ -77,6 +77,7 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 ### Prerequisites
82
83 No action required.
src/collectors/freebsd.plugin/integrations/net.isr.md
+1
@@ -93,6 +93,7 @@ The following alerts are available:
93
94 ## Setup
95
96 +
97 ### Prerequisites
98
99 No action required.
src/collectors/freebsd.plugin/integrations/system.ram.md
+1
@@ -83,6 +83,7 @@ The following alerts are available:
83
84 ## Setup
85
86 +
87 ### Prerequisites
88
89 No action required.
src/collectors/freebsd.plugin/integrations/uptime.md
+1
@@ -74,6 +74,7 @@ There are no alerts configured by default for this integration.
74
75 ## Setup
76
77 +
78 ### Prerequisites
79
80 No action required.
src/collectors/freebsd.plugin/integrations/vm.loadavg.md
+1
@@ -82,6 +82,7 @@ The following alerts are available:
82
83 ## Setup
84
85 +
86 ### Prerequisites
87
88 No action required.
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_intr.md
+1
@@ -74,6 +74,7 @@ There are no alerts configured by default for this integration.
74
75 ## Setup
76
77 +
78 ### Prerequisites
79
80 No action required.
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_soft.md
+1
@@ -74,6 +74,7 @@ There are no alerts configured by default for this integration.
74
75 ## Setup
76
77 +
78 ### Prerequisites
79
80 No action required.
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_swtch.md
+1
@@ -75,6 +75,7 @@ There are no alerts configured by default for this integration.
75
76 ## Setup
77
78 +
79 ### Prerequisites
80
81 No action required.
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_pgfaults.md
+1
@@ -74,6 +74,7 @@ There are no alerts configured by default for this integration.
74
75 ## Setup
76
77 +
78 ### Prerequisites
79
80 No action required.
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_swappgs.md
+1
@@ -79,6 +79,7 @@ The following alerts are available:
79
80 ## Setup
81
82 +
83 ### Prerequisites
84
85 No action required.
src/collectors/freebsd.plugin/integrations/vm.swap_info.md
+1
@@ -79,6 +79,7 @@ The following alerts are available:
79
80 ## Setup
81
82 +
83 ### Prerequisites
84
85 No action required.
src/collectors/freebsd.plugin/integrations/vm.vmtotal.md
+1
@@ -81,6 +81,7 @@ The following alerts are available:
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 No action required.
src/collectors/freebsd.plugin/integrations/zfs.md
+1
@@ -106,6 +106,7 @@ The following alerts are available:
106
107 ## Setup
108
109 +
110 ### Prerequisites
111
112 No action required.
src/collectors/freeipmi.plugin/integrations/intelligent_platform_management_interface_ipmi.md
+1
@@ -108,6 +108,7 @@ The following alerts are available:
108
109 ## Setup
110
111 +
112 ### Prerequisites
113
114 #### Install freeipmi.plugin
src/collectors/idlejitter.plugin/integrations/idle_os_jitter.md
+1
@@ -76,6 +76,7 @@ There are no alerts configured by default for this integration.
76
77 ## Setup
78
79 +
80 ### Prerequisites
81
82 No action required.
src/collectors/ioping.plugin/integrations/ioping.md
+1
@@ -79,6 +79,7 @@ The following alerts are available:
79
80 ## Setup
81
82 +
83 ### Prerequisites
84
85 #### Install ioping
src/collectors/macos.plugin/integrations/macos.md
+1
@@ -168,6 +168,7 @@ The following alerts are available:
168
169 ## Setup
170
171 +
172 ### Prerequisites
173
174 No action required.
src/collectors/nfacct.plugin/integrations/netfilter.md
+1
@@ -81,6 +81,7 @@ There are no alerts configured by default for this integration.
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 #### Install required packages
src/collectors/perf.plugin/integrations/cpu_performance.md
+1
@@ -93,6 +93,7 @@ There are no alerts configured by default for this integration.
93
94 ## Setup
95
96 +
97 ### Prerequisites
98
99 #### Install perf plugin
src/collectors/proc.plugin/integrations/amd_gpu.md
+1
@@ -89,6 +89,7 @@ There are no alerts configured by default for this integration.
89
90 ## Setup
91
92 +
93 ### Prerequisites
94
95 No action required.
src/collectors/proc.plugin/integrations/btrfs.md
+1
@@ -116,6 +116,7 @@ The following alerts are available:
116
117 ## Setup
118
119 +
120 ### Prerequisites
121
122 No action required.
src/collectors/proc.plugin/integrations/conntrack.md
+1
@@ -84,6 +84,7 @@ The following alerts are available:
84
85 ## Setup
86
87 +
88 ### Prerequisites
89
90 No action required.
src/collectors/proc.plugin/integrations/disk_statistics.md
+1
@@ -128,6 +128,7 @@ The following alerts are available:
128
129 ## Setup
130
131 +
132 ### Prerequisites
133
134 No action required.
src/collectors/proc.plugin/integrations/entropy.md
+1
@@ -112,6 +112,7 @@ The following alerts are available:
112
113 ## Setup
114
115 +
116 ### Prerequisites
117
118 No action required.
src/collectors/proc.plugin/integrations/infiniband.md
+1
@@ -78,6 +78,7 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 ### Prerequisites
83
84 No action required.
src/collectors/proc.plugin/integrations/inter_process_communication.md
+1
@@ -99,6 +99,7 @@ The following alerts are available:
99
100 ## Setup
101
102 +
103 ### Prerequisites
104
105 No action required.
src/collectors/proc.plugin/integrations/interrupts.md
+1
@@ -120,6 +120,7 @@ There are no alerts configured by default for this integration.
120
121 ## Setup
122
123 +
124 ### Prerequisites
125
126 No action required.
src/collectors/proc.plugin/integrations/ip_virtual_server.md
+1
@@ -76,6 +76,7 @@ There are no alerts configured by default for this integration.
76
77 ## Setup
78
79 +
80 ### Prerequisites
81
82 No action required.
src/collectors/proc.plugin/integrations/ipv6_socket_statistics.md
+1
@@ -78,6 +78,7 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 ### Prerequisites
83
84 No action required.
src/collectors/proc.plugin/integrations/kernel_same-page_merging.md
+1
@@ -82,6 +82,7 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 ### Prerequisites
87
88 No action required.
src/collectors/proc.plugin/integrations/md_raid.md
+1
@@ -104,6 +104,7 @@ The following alerts are available:
104
105 ## Setup
106
107 +
108 ### Prerequisites
109
110 No action required.
src/collectors/proc.plugin/integrations/memory_modules_dimms.md
+1
@@ -125,6 +125,7 @@ The following alerts are available:
125
126 ## Setup
127
128 +
129 ### Prerequisites
130
131 No action required.
src/collectors/proc.plugin/integrations/memory_statistics.md
+1
@@ -117,6 +117,7 @@ The following alerts are available:
117
118 ## Setup
119
120 +
121 ### Prerequisites
122
123 No action required.
src/collectors/proc.plugin/integrations/memory_usage.md
+1
@@ -114,6 +114,7 @@ The following alerts are available:
114
115 ## Setup
116
117 +
118 ### Prerequisites
119
120 No action required.
src/collectors/proc.plugin/integrations/network_interfaces.md
+1
@@ -116,6 +116,7 @@ The following alerts are available:
116
117 ## Setup
118
119 +
120 ### Prerequisites
121
122 No action required.
src/collectors/proc.plugin/integrations/network_statistics.md
+1
@@ -139,6 +139,7 @@ The following alerts are available:
139
140 ## Setup
141
142 +
143 ### Prerequisites
144
145 No action required.
src/collectors/proc.plugin/integrations/nfs_client.md
+1
@@ -78,6 +78,7 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 ### Prerequisites
83
84 No action required.
src/collectors/proc.plugin/integrations/nfs_server.md
+1
@@ -83,6 +83,7 @@ There are no alerts configured by default for this integration.
83
84 ## Setup
85
86 +
87 ### Prerequisites
88
89 No action required.
src/collectors/proc.plugin/integrations/non-uniform_memory_access.md
+1
@@ -90,6 +90,7 @@ There are no alerts configured by default for this integration.
90
91 ## Setup
92
93 +
94 ### Prerequisites
95
96 No action required.
src/collectors/proc.plugin/integrations/page_types.md
+1
@@ -92,6 +92,7 @@ There are no alerts configured by default for this integration.
92
93 ## Setup
94
95 +
96 ### Prerequisites
97
98 No action required.
src/collectors/proc.plugin/integrations/power_supply.md
+1
@@ -87,6 +87,7 @@ The following alerts are available:
87
88 ## Setup
89
90 +
91 ### Prerequisites
92
93 No action required.
src/collectors/proc.plugin/integrations/pressure_stall_information.md
+1
@@ -108,6 +108,7 @@ There are no alerts configured by default for this integration.
108
109 ## Setup
110
111 +
112 ### Prerequisites
113
114 No action required.
src/collectors/proc.plugin/integrations/sctp_statistics.md
+1
@@ -78,6 +78,7 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 ### Prerequisites
83
84 No action required.
src/collectors/proc.plugin/integrations/socket_statistics.md
+1
@@ -88,6 +88,7 @@ The following alerts are available:
88
89 ## Setup
90
91 +
92 ### Prerequisites
93
94 No action required.
src/collectors/proc.plugin/integrations/softirq_statistics.md
+1
@@ -112,6 +112,7 @@ There are no alerts configured by default for this integration.
112
113 ## Setup
114
115 +
116 ### Prerequisites
117
118 No action required.
src/collectors/proc.plugin/integrations/softnet_statistics.md
+1
@@ -114,6 +114,7 @@ The following alerts are available:
114
115 ## Setup
116
117 +
118 ### Prerequisites
119
120 No action required.
src/collectors/proc.plugin/integrations/synproxy.md
+1
@@ -76,6 +76,7 @@ There are no alerts configured by default for this integration.
76
77 ## Setup
78
79 +
80 ### Prerequisites
81
82 No action required.
src/collectors/proc.plugin/integrations/system_load_average.md
+1
@@ -107,6 +107,7 @@ The following alerts are available:
107
108 ## Setup
109
110 +
111 ### Prerequisites
112
113 No action required.
src/collectors/proc.plugin/integrations/system_statistics.md
+1
@@ -129,6 +129,7 @@ The following alerts are available:
129
130 ## Setup
131
132 +
133 ### Prerequisites
134
135 No action required.
src/collectors/proc.plugin/integrations/system_uptime.md
+1
@@ -87,6 +87,7 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 ### Prerequisites
92
93 No action required.
src/collectors/proc.plugin/integrations/wireless_network_interfaces.md
+1
@@ -79,6 +79,7 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 ### Prerequisites
84
85 No action required.
src/collectors/proc.plugin/integrations/zfs_adaptive_replacement_cache.md
+1
@@ -104,6 +104,7 @@ The following alerts are available:
104
105 ## Setup
106
107 +
108 ### Prerequisites
109
110 No action required.
src/collectors/proc.plugin/integrations/zram.md
+1
@@ -85,6 +85,7 @@ There are no alerts configured by default for this integration.
85
86 ## Setup
87
88 +
89 ### Prerequisites
90
91 No action required.
src/collectors/python.d.plugin/am2320/integrations/am2320.md
+1
@@ -75,6 +75,7 @@ There are no alerts configured by default for this integration.
75
76 ## Setup
77
78 +
79 ### Prerequisites
80
81 #### Sensor connection to a Raspberry Pi
src/collectors/python.d.plugin/go_expvar/integrations/go_applications_expvar.md
+1
@@ -80,6 +80,7 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 ### Prerequisites
85
86 #### Enable the go_expvar collector
src/collectors/python.d.plugin/pandas/integrations/pandas.md
+1
@@ -83,6 +83,7 @@ There are no alerts configured by default for this integration.
83
84 ## Setup
85
86 +
87 ### Prerequisites
88
89 #### Python Requirements
src/collectors/slabinfo.plugin/integrations/linux_kernel_slab_allocator_statistics.md
+1
@@ -82,6 +82,7 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 ### Prerequisites
87
88 #### Minimum setup
src/collectors/tc.plugin/integrations/tc_qos_classes.md
+1
@@ -87,6 +87,7 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 ### Prerequisites
92
93 #### Create `tc-qos-helper.conf`
src/collectors/timex.plugin/integrations/timex.md
+1
@@ -81,6 +81,7 @@ The following alerts are available:
81
82 ## Setup
83
84 +
85 ### Prerequisites
86
87 No action required.
src/collectors/windows.plugin/integrations/active_directory.md
+1
@@ -94,6 +94,7 @@ There are no alerts configured by default for this integration.
94
95 ## Setup
96
97 +
98 ### Prerequisites
99
100 No action required.
src/collectors/windows.plugin/integrations/active_directory_certificate_service.md
+1
@@ -98,6 +98,7 @@ There are no alerts configured by default for this integration.
98
99 ## Setup
100
101 +
102 ### Prerequisites
103
104 No action required.
src/collectors/windows.plugin/integrations/active_directory_federation_service.md
+1
@@ -109,6 +109,7 @@ There are no alerts configured by default for this integration.
109
110 ## Setup
111
112 +
113 ### Prerequisites
114
115 No action required.
src/collectors/windows.plugin/integrations/asp.net.md
+1
@@ -123,6 +123,7 @@ There are no alerts configured by default for this integration.
123
124 ## Setup
125
126 +
127 ### Prerequisites
128
129 No action required.
src/collectors/windows.plugin/integrations/hyper-v.md
+1
@@ -178,6 +178,7 @@ There are no alerts configured by default for this integration.
178
179 ## Setup
180
181 +
182 ### Prerequisites
183
184 No action required.
src/collectors/windows.plugin/integrations/iis.md
+1
@@ -145,6 +145,7 @@ There are no alerts configured by default for this integration.
145
146 ## Setup
147
148 +
149 ### Prerequisites
150
151 No action required.
src/collectors/windows.plugin/integrations/memory_statistics.md
+1
@@ -82,6 +82,7 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 ### Prerequisites
87
88 No action required.
src/collectors/windows.plugin/integrations/ms_exchange.md
+1
@@ -109,6 +109,7 @@ There are no alerts configured by default for this integration.
109
110 ## Setup
111
112 +
113 ### Prerequisites
114
115 No action required.
src/collectors/windows.plugin/integrations/ms_sql_server.md
+1
@@ -174,6 +174,7 @@ There are no alerts configured by default for this integration.
174
175 ## Setup
176
177 +
178 ### Prerequisites
179
180 #### Configure SQL Server for Monitoring
src/collectors/windows.plugin/integrations/net_framework.md
+1
@@ -113,6 +113,7 @@ There are no alerts configured by default for this integration.
113
114 ## Setup
115
116 +
117 ### Prerequisites
118
119 No action required.
src/collectors/windows.plugin/integrations/network_subsystem.md
+1
@@ -128,6 +128,7 @@ The following alerts are available:
128
129 ## Setup
130
131 +
132 ### Prerequisites
133
134 No action required.
src/collectors/windows.plugin/integrations/numa_architecture.md
+1
@@ -83,6 +83,7 @@ There are no alerts configured by default for this integration.
83
84 ## Setup
85
86 +
87 ### Prerequisites
88
89 No action required.
src/collectors/windows.plugin/integrations/physical_and_logical_disk_performance_metrics.md
+1
@@ -126,6 +126,7 @@ There are no alerts configured by default for this integration.
126
127 ## Setup
128
129 +
130 ### Prerequisites
131
132 No action required.
src/collectors/windows.plugin/integrations/power_supply.md
+1
@@ -89,6 +89,7 @@ The following alerts are available:
89
90 ## Setup
91
92 +
93 ### Prerequisites
94
95 No action required.
src/collectors/windows.plugin/integrations/processor.md
+1
@@ -100,6 +100,7 @@ The following alerts are available:
100
101 ## Setup
102
103 +
104 ### Prerequisites
105
106 No action required.
src/collectors/windows.plugin/integrations/semaphore_statistics.md
+1
@@ -83,6 +83,7 @@ There are no alerts configured by default for this integration.
83
84 ## Setup
85
86 +
87 ### Prerequisites
88
89 No action required.
src/collectors/windows.plugin/integrations/sensors.md
+1
@@ -90,6 +90,7 @@ There are no alerts configured by default for this integration.
90
91 ## Setup
92
93 +
94 ### Prerequisites
95
96 No action required.
src/collectors/windows.plugin/integrations/system_statistics.md
+1
@@ -82,6 +82,7 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 ### Prerequisites
87
88 No action required.
src/collectors/windows.plugin/integrations/system_thermal_zone.md
+1
@@ -79,6 +79,7 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 ### Prerequisites
84
85 No action required.
src/collectors/windows.plugin/integrations/windows_services.md
+1
@@ -83,6 +83,7 @@ There are no alerts configured by default for this integration.
83
84 ## Setup
85
86 +
87 ### Prerequisites
88
89 No action required.
src/collectors/xenstat.plugin/integrations/xen_xcp-ng.md
+1
@@ -122,6 +122,7 @@ There are no alerts configured by default for this integration.
122
123 ## Setup
124
125 +
126 ### Prerequisites
127
128 #### Libraries
src/exporting/aws_kinesis/integrations/aws_kinesis.md
+1
@@ -21,6 +21,7 @@ Export metrics to AWS Kinesis Data Streams
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/exporting/graphite/integrations/blueflood.md
+1
@@ -21,6 +21,7 @@ Export your Netdata metrics to Blueflood DB using the Graphite protocol, allowin
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 No action required.
src/exporting/graphite/integrations/graphite.md
+1
@@ -22,6 +22,7 @@ further analysis, or correlation with data from other sources.
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 No action required.
src/exporting/graphite/integrations/kairosdb.md
+1
@@ -21,6 +21,7 @@ Export your Netdata metrics to KairosDB using the Graphite protocol, allowing yo
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 No action required.
src/exporting/json/integrations/json.md
+1
@@ -22,6 +22,7 @@ further analysis, or correlation with data from other sources
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/exporting/mongodb/integrations/mongodb.md
+1
@@ -22,6 +22,7 @@ for long-term storage, further analysis, or correlation with data from other sou
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/exporting/opentsdb/integrations/opentsdb.md
+1
@@ -22,6 +22,7 @@ further analysis, or correlation with data from other sources.
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/exporting/prometheus/integrations/appoptics.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/azure_data_explorer.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/azure_event_hub.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/chronix.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/cortex.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/cratedb.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/elasticsearch.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/gnocchi.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/google_bigquery.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/greptimedb.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/irondb.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/kafka.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/m3db.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/metricfire.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/new_relic.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/opeansearch.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/postgresql.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/prometheus_remote_write.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/quasardb.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/splunk_signalfx.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/thanos.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/tikv.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/timescaledb.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/victoriametrics.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/vmware_aria.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/prometheus/integrations/wavefront.md
+1
@@ -25,6 +25,7 @@ The remote write exporting connector does not support buffer on failures.
25
26 ## Setup
27
28 +
29 ### Prerequisites
30
31 ####
src/exporting/pubsub/integrations/google_cloud_pub_sub.md
+1
@@ -21,6 +21,7 @@ Export metrics to Google Cloud Pub/Sub Service
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/go/plugin/go.d/collector/activemq/integrations/activemq.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **activemq** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **activemq**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/activemq.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 No action required.
@@ -122,14 +137,16 @@ The following options can be defined globally: update_every, autodetection_retry
137
138 #### via UI
139
125 -The **activemq** collector can be configured directly through the Netdata web interface:
140 +Configure the **activemq** collector from the Netdata web interface:
141
142 1. Go to **Nodes**.
128 -2. Select the node **where you want the activemq data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
143 +2. Select the node **where you want the activemq data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
144 3. The **Collectors → Jobs** view opens by default.
145 4. In the Search box, type _activemq_ (or scroll the list) to locate the **activemq** collector.
146 5. Click the **+** next to the **activemq** collector to add a new job.
132 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
147 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
148 + - **Test** runs the job with the provided settings and shows whether data can be collected.
149 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
150
151
152 #### via File
@@ -143,7 +160,7 @@ update_every: 1
160 autodetection_retry: 0
161 jobs:
162 - name: some_name1
146 - - name: some_name1
163 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
166 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/adaptecraid/integrations/adaptec_raid.md
+21 -4
@@ -118,6 +118,21 @@ The following alerts are available:
118
119 ## Setup
120
121 +
122 +You can configure the **adaptec_raid** collector in two ways:
123 +
124 +| Method | Best for | How to |
125 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
126 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **adaptec_raid**, then click **+** to add a job. |
127 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/adaptec_raid.conf` and add a job. |
128 +
129 +:::important
130 +
131 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
132 +
133 +:::
134 +
135 +
136 ### Prerequisites
137
138 No action required.
@@ -141,14 +156,16 @@ The following options can be defined globally: update_every.
156
157 #### via UI
158
144 -The **adaptec_raid** collector can be configured directly through the Netdata web interface:
159 +Configure the **adaptec_raid** collector from the Netdata web interface:
160
161 1. Go to **Nodes**.
147 -2. Select the node **where you want the adaptec_raid data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
162 +2. Select the node **where you want the adaptec_raid data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
163 3. The **Collectors → Jobs** view opens by default.
164 4. In the Search box, type _adaptec_raid_ (or scroll the list) to locate the **adaptec_raid** collector.
165 5. Click the **+** next to the **adaptec_raid** collector to add a new job.
151 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
166 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
167 + - **Test** runs the job with the provided settings and shows whether data can be collected.
168 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
169
170
171 #### via File
@@ -162,7 +179,7 @@ update_every: 1
179 autodetection_retry: 0
180 jobs:
181 - name: some_name1
165 - - name: some_name1
182 + - name: some_name2
183 ```
184 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
185 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/ap/integrations/access_points.md
+21 -4
@@ -88,6 +88,21 @@ There are no alerts configured by default for this integration.
88
89 ## Setup
90
91 +
92 +You can configure the **ap** collector in two ways:
93 +
94 +| Method | Best for | How to |
95 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
96 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **ap**, then click **+** to add a job. |
97 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ap.conf` and add a job. |
98 +
99 +:::important
100 +
101 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
102 +
103 +:::
104 +
105 +
106 ### Prerequisites
107
108 #### `iw` utility.
@@ -115,14 +130,16 @@ The following options can be defined globally: update_every.
130
131 #### via UI
132
118 -The **ap** collector can be configured directly through the Netdata web interface:
133 +Configure the **ap** collector from the Netdata web interface:
134
135 1. Go to **Nodes**.
121 -2. Select the node **where you want the ap data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
136 +2. Select the node **where you want the ap data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
137 3. The **Collectors → Jobs** view opens by default.
138 4. In the Search box, type _ap_ (or scroll the list) to locate the **ap** collector.
139 5. Click the **+** next to the **ap** collector to add a new job.
125 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
140 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
141 + - **Test** runs the job with the provided settings and shows whether data can be collected.
142 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
143
144
145 #### via File
@@ -136,7 +153,7 @@ update_every: 1
153 autodetection_retry: 0
154 jobs:
155 - name: some_name1
139 - - name: some_name1
156 + - name: some_name2
157 ```
158 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
159 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/apache/integrations/apache.md
+21 -4
@@ -92,6 +92,21 @@ There are no alerts configured by default for this integration.
92
93 ## Setup
94
95 +
96 +You can configure the **apache** collector in two ways:
97 +
98 +| Method | Best for | How to |
99 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
100 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **apache**, then click **+** to add a job. |
101 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/apache.conf` and add a job. |
102 +
103 +:::important
104 +
105 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
106 +
107 +:::
108 +
109 +
110 ### Prerequisites
111
112 #### Enable Apache status support
@@ -136,14 +151,16 @@ The following options can be defined globally: update_every, autodetection_retry
151
152 #### via UI
153
139 -The **apache** collector can be configured directly through the Netdata web interface:
154 +Configure the **apache** collector from the Netdata web interface:
155
156 1. Go to **Nodes**.
142 -2. Select the node **where you want the apache data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
157 +2. Select the node **where you want the apache data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
158 3. The **Collectors → Jobs** view opens by default.
159 4. In the Search box, type _apache_ (or scroll the list) to locate the **apache** collector.
160 5. Click the **+** next to the **apache** collector to add a new job.
146 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
161 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
162 + - **Test** runs the job with the provided settings and shows whether data can be collected.
163 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
164
165
166 #### via File
@@ -157,7 +174,7 @@ update_every: 1
174 autodetection_retry: 0
175 jobs:
176 - name: some_name1
160 - - name: some_name1
177 + - name: some_name2
178 ```
179 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
180 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/apache/integrations/httpd.md
+21 -4
@@ -92,6 +92,21 @@ There are no alerts configured by default for this integration.
92
93 ## Setup
94
95 +
96 +You can configure the **apache** collector in two ways:
97 +
98 +| Method | Best for | How to |
99 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
100 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **apache**, then click **+** to add a job. |
101 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/apache.conf` and add a job. |
102 +
103 +:::important
104 +
105 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
106 +
107 +:::
108 +
109 +
110 ### Prerequisites
111
112 #### Enable Apache status support
@@ -136,14 +151,16 @@ The following options can be defined globally: update_every, autodetection_retry
151
152 #### via UI
153
139 -The **apache** collector can be configured directly through the Netdata web interface:
154 +Configure the **apache** collector from the Netdata web interface:
155
156 1. Go to **Nodes**.
142 -2. Select the node **where you want the apache data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
157 +2. Select the node **where you want the apache data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
158 3. The **Collectors → Jobs** view opens by default.
159 4. In the Search box, type _apache_ (or scroll the list) to locate the **apache** collector.
160 5. Click the **+** next to the **apache** collector to add a new job.
146 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
161 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
162 + - **Test** runs the job with the provided settings and shows whether data can be collected.
163 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
164
165
166 #### via File
@@ -157,7 +174,7 @@ update_every: 1
174 autodetection_retry: 0
175 jobs:
176 - name: some_name1
160 - - name: some_name1
177 + - name: some_name2
178 ```
179 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
180 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/apcupsd/integrations/apc_ups.md
+21 -4
@@ -104,6 +104,21 @@ The following alerts are available:
104
105 ## Setup
106
107 +
108 +You can configure the **apcupsd** collector in two ways:
109 +
110 +| Method | Best for | How to |
111 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
112 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **apcupsd**, then click **+** to add a job. |
113 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/apcupsd.conf` and add a job. |
114 +
115 +:::important
116 +
117 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
118 +
119 +:::
120 +
121 +
122 ### Prerequisites
123
124 No action required.
@@ -129,14 +144,16 @@ The following options can be defined globally: update_every, autodetection_retry
144
145 #### via UI
146
132 -The **apcupsd** collector can be configured directly through the Netdata web interface:
147 +Configure the **apcupsd** collector from the Netdata web interface:
148
149 1. Go to **Nodes**.
135 -2. Select the node **where you want the apcupsd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
150 +2. Select the node **where you want the apcupsd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
151 3. The **Collectors → Jobs** view opens by default.
152 4. In the Search box, type _apcupsd_ (or scroll the list) to locate the **apcupsd** collector.
153 5. Click the **+** next to the **apcupsd** collector to add a new job.
139 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
154 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
155 + - **Test** runs the job with the provided settings and shows whether data can be collected.
156 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
157
158
159 #### via File
@@ -150,7 +167,7 @@ update_every: 1
167 autodetection_retry: 0
168 jobs:
169 - name: some_name1
153 - - name: some_name1
170 + - name: some_name2
171 ```
172 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
173 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/beanstalk/integrations/beanstalk.md
+21 -4
@@ -116,6 +116,21 @@ The following alerts are available:
116
117 ## Setup
118
119 +
120 +You can configure the **beanstalk** collector in two ways:
121 +
122 +| Method | Best for | How to |
123 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
124 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **beanstalk**, then click **+** to add a job. |
125 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/beanstalk.conf` and add a job. |
126 +
127 +:::important
128 +
129 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
130 +
131 +:::
132 +
133 +
134 ### Prerequisites
135
136 No action required.
@@ -142,14 +157,16 @@ The following options can be defined globally: update_every, autodetection_retry
157
158 #### via UI
159
145 -The **beanstalk** collector can be configured directly through the Netdata web interface:
160 +Configure the **beanstalk** collector from the Netdata web interface:
161
162 1. Go to **Nodes**.
148 -2. Select the node **where you want the beanstalk data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
163 +2. Select the node **where you want the beanstalk data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
164 3. The **Collectors → Jobs** view opens by default.
165 4. In the Search box, type _beanstalk_ (or scroll the list) to locate the **beanstalk** collector.
166 5. Click the **+** next to the **beanstalk** collector to add a new job.
152 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
167 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
168 + - **Test** runs the job with the provided settings and shows whether data can be collected.
169 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
170
171
172 #### via File
@@ -163,7 +180,7 @@ update_every: 1
180 autodetection_retry: 0
181 jobs:
182 - name: some_name1
166 - - name: some_name1
183 + - name: some_name2
184 ```
185 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
186 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/boinc/integrations/boinc.md
+21 -4
@@ -91,6 +91,21 @@ The following alerts are available:
91
92 ## Setup
93
94 +
95 +You can configure the **boinc** collector in two ways:
96 +
97 +| Method | Best for | How to |
98 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
99 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **boinc**, then click **+** to add a job. |
100 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/boinc.conf` and add a job. |
101 +
102 +:::important
103 +
104 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
105 +
106 +:::
107 +
108 +
109 ### Prerequisites
110
111 No action required.
@@ -117,14 +132,16 @@ The following options can be defined globally: update_every, autodetection_retry
132
133 #### via UI
134
120 -The **boinc** collector can be configured directly through the Netdata web interface:
135 +Configure the **boinc** collector from the Netdata web interface:
136
137 1. Go to **Nodes**.
123 -2. Select the node **where you want the boinc data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
138 +2. Select the node **where you want the boinc 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 _boinc_ (or scroll the list) to locate the **boinc** collector.
141 5. Click the **+** next to the **boinc** collector to add a new job.
127 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -138,7 +155,7 @@ update_every: 1
155 autodetection_retry: 0
156 jobs:
157 - name: some_name1
141 - - 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-a-configuration-file-using-edit-config) script from the
161 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/cassandra/integrations/cassandra.md
+21 -4
@@ -123,6 +123,21 @@ There are no alerts configured by default for this integration.
123
124 ## Setup
125
126 +
127 +You can configure the **cassandra** collector in two ways:
128 +
129 +| Method | Best for | How to |
130 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
131 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **cassandra**, then click **+** to add a job. |
132 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/cassandra.conf` and add a job. |
133 +
134 +:::important
135 +
136 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
137 +
138 +:::
139 +
140 +
141 ### Prerequisites
142
143 #### Configure Cassandra with Prometheus JMX Exporter
@@ -175,14 +190,16 @@ The following options can be defined globally: update_every, autodetection_retry
190
191 #### via UI
192
178 -The **cassandra** collector can be configured directly through the Netdata web interface:
193 +Configure the **cassandra** collector from the Netdata web interface:
194
195 1. Go to **Nodes**.
181 -2. Select the node **where you want the cassandra data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
196 +2. Select the node **where you want the cassandra 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 _cassandra_ (or scroll the list) to locate the **cassandra** collector.
199 5. Click the **+** next to the **cassandra** collector to add a new job.
185 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
204
205 #### via File
@@ -196,7 +213,7 @@ update_every: 1
213 autodetection_retry: 0
214 jobs:
215 - name: some_name1
199 - - 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-a-configuration-file-using-edit-config) script from the
219 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/ceph/integrations/ceph.md
+21 -4
@@ -160,6 +160,21 @@ The following alerts are available:
160
161 ## Setup
162
163 +
164 +You can configure the **ceph** collector in two ways:
165 +
166 +| Method | Best for | How to |
167 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
168 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **ceph**, then click **+** to add a job. |
169 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ceph.conf` and add a job. |
170 +
171 +:::important
172 +
173 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
174 +
175 +:::
176 +
177 +
178 ### Prerequisites
179
180 No action required.
@@ -198,14 +213,16 @@ The following options can be defined globally: update_every.
213
214 #### via UI
215
201 -The **ceph** collector can be configured directly through the Netdata web interface:
216 +Configure the **ceph** collector from the Netdata web interface:
217
218 1. Go to **Nodes**.
204 -2. Select the node **where you want the ceph data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
219 +2. Select the node **where you want the ceph data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
220 3. The **Collectors → Jobs** view opens by default.
221 4. In the Search box, type _ceph_ (or scroll the list) to locate the **ceph** collector.
222 5. Click the **+** next to the **ceph** collector to add a new job.
208 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
223 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
224 + - **Test** runs the job with the provided settings and shows whether data can be collected.
225 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
226
227
228 #### via File
@@ -219,7 +236,7 @@ update_every: 1
236 autodetection_retry: 0
237 jobs:
238 - name: some_name1
222 - - name: some_name1
239 + - name: some_name2
240 ```
241 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
242 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/chrony/integrations/chrony.md
+21 -4
@@ -95,6 +95,21 @@ There are no alerts configured by default for this integration.
95
96 ## Setup
97
98 +
99 +You can configure the **chrony** collector in two ways:
100 +
101 +| Method | Best for | How to |
102 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
103 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **chrony**, then click **+** to add a job. |
104 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/chrony.conf` and add a job. |
105 +
106 +:::important
107 +
108 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
109 +
110 +:::
111 +
112 +
113 ### Prerequisites
114
115 No action required.
@@ -120,14 +135,16 @@ The following options can be defined globally: update_every, autodetection_retry
135
136 #### via UI
137
123 -The **chrony** collector can be configured directly through the Netdata web interface:
138 +Configure the **chrony** collector from the Netdata web interface:
139
140 1. Go to **Nodes**.
126 -2. Select the node **where you want the chrony data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
141 +2. Select the node **where you want the chrony 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 _chrony_ (or scroll the list) to locate the **chrony** collector.
144 5. Click the **+** next to the **chrony** collector to add a new job.
130 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -141,7 +158,7 @@ update_every: 1
158 autodetection_retry: 0
159 jobs:
160 - name: some_name1
144 - - 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-a-configuration-file-using-edit-config) script from the
164 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/clickhouse/integrations/clickhouse.md
+21 -4
@@ -192,6 +192,21 @@ The following alerts are available:
192
193 ## Setup
194
195 +
196 +You can configure the **clickhouse** collector in two ways:
197 +
198 +| Method | Best for | How to |
199 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
200 +| [**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. |
201 +| [**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. |
202 +
203 +:::important
204 +
205 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
206 +
207 +:::
208 +
209 +
210 ### Prerequisites
211
212 No action required.
@@ -230,14 +245,16 @@ The following options can be defined globally: update_every, autodetection_retry
245
246 #### via UI
247
233 -The **clickhouse** collector can be configured directly through the Netdata web interface:
248 +Configure the **clickhouse** collector from the Netdata web interface:
249
250 1. Go to **Nodes**.
236 -2. Select the node **where you want the clickhouse data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
251 +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.
252 3. The **Collectors → Jobs** view opens by default.
253 4. In the Search box, type _clickhouse_ (or scroll the list) to locate the **clickhouse** collector.
254 5. Click the **+** next to the **clickhouse** collector to add a new job.
240 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
255 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
256 + - **Test** runs the job with the provided settings and shows whether data can be collected.
257 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
258
259
260 #### via File
@@ -251,7 +268,7 @@ update_every: 1
268 autodetection_retry: 0
269 jobs:
270 - name: some_name1
254 - - name: some_name1
271 + - name: some_name2
272 ```
273 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
274 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/cockroachdb/integrations/cockroachdb.md
+21 -4
@@ -143,6 +143,21 @@ The following alerts are available:
143
144 ## Setup
145
146 +
147 +You can configure the **cockroachdb** collector in two ways:
148 +
149 +| Method | Best for | How to |
150 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
151 +| [**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. |
152 +| [**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. |
153 +
154 +:::important
155 +
156 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
157 +
158 +:::
159 +
160 +
161 ### Prerequisites
162
163 No action required.
@@ -181,14 +196,16 @@ The following options can be defined globally: update_every, autodetection_retry
196
197 #### via UI
198
184 -The **cockroachdb** collector can be configured directly through the Netdata web interface:
199 +Configure the **cockroachdb** collector from the Netdata web interface:
200
201 1. Go to **Nodes**.
187 -2. Select the node **where you want the cockroachdb data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
202 +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.
203 3. The **Collectors → Jobs** view opens by default.
204 4. In the Search box, type _cockroachdb_ (or scroll the list) to locate the **cockroachdb** collector.
205 5. Click the **+** next to the **cockroachdb** collector to add a new job.
191 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
206 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
207 + - **Test** runs the job with the provided settings and shows whether data can be collected.
208 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
209
210
211 #### via File
@@ -202,7 +219,7 @@ update_every: 1
219 autodetection_retry: 0
220 jobs:
221 - name: some_name1
205 - - name: some_name1
222 + - name: some_name2
223 ```
224 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
225 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/consul/integrations/consul.md
+21 -4
@@ -176,6 +176,21 @@ The following alerts are available:
176
177 ## Setup
178
179 +
180 +You can configure the **consul** collector in two ways:
181 +
182 +| Method | Best for | How to |
183 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
184 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **consul**, then click **+** to add a job. |
185 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/consul.conf` and add a job. |
186 +
187 +:::important
188 +
189 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
190 +
191 +:::
192 +
193 +
194 ### Prerequisites
195
196 #### Enable Prometheus telemetry
@@ -232,14 +247,16 @@ The following options can be defined globally: update_every, autodetection_retry
247
248 #### via UI
249
235 -The **consul** collector can be configured directly through the Netdata web interface:
250 +Configure the **consul** collector from the Netdata web interface:
251
252 1. Go to **Nodes**.
238 -2. Select the node **where you want the consul data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
253 +2. Select the node **where you want the consul data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
254 3. The **Collectors → Jobs** view opens by default.
255 4. In the Search box, type _consul_ (or scroll the list) to locate the **consul** collector.
256 5. Click the **+** next to the **consul** collector to add a new job.
242 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
257 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
258 + - **Test** runs the job with the provided settings and shows whether data can be collected.
259 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
260
261
262 #### via File
@@ -253,7 +270,7 @@ update_every: 1
270 autodetection_retry: 0
271 jobs:
272 - name: some_name1
256 - - name: some_name1
273 + - name: some_name2
274 ```
275 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
276 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/coredns/integrations/coredns.md
+21 -4
@@ -126,6 +126,21 @@ There are no alerts configured by default for this integration.
126
127 ## Setup
128
129 +
130 +You can configure the **coredns** collector in two ways:
131 +
132 +| Method | Best for | How to |
133 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
134 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **coredns**, then click **+** to add a job. |
135 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/coredns.conf` and add a job. |
136 +
137 +:::important
138 +
139 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
140 +
141 +:::
142 +
143 +
144 ### Prerequisites
145
146 No action required.
@@ -202,14 +217,16 @@ per_zone_stats:
217
218 #### via UI
219
205 -The **coredns** collector can be configured directly through the Netdata web interface:
220 +Configure the **coredns** collector from the Netdata web interface:
221
222 1. Go to **Nodes**.
208 -2. Select the node **where you want the coredns data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
223 +2. Select the node **where you want the coredns data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
224 3. The **Collectors → Jobs** view opens by default.
225 4. In the Search box, type _coredns_ (or scroll the list) to locate the **coredns** collector.
226 5. Click the **+** next to the **coredns** collector to add a new job.
212 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
227 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
228 + - **Test** runs the job with the provided settings and shows whether data can be collected.
229 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
230
231
232 #### via File
@@ -223,7 +240,7 @@ update_every: 1
240 autodetection_retry: 0
241 jobs:
242 - name: some_name1
226 - - name: some_name1
243 + - name: some_name2
244 ```
245 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
246 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/couchbase/integrations/couchbase.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **couchbase** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **couchbase**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/couchbase.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 No action required.
@@ -120,14 +135,16 @@ The following options can be defined globally: update_every, autodetection_retry
135
136 #### via UI
137
123 -The **couchbase** collector can be configured directly through the Netdata web interface:
138 +Configure the **couchbase** collector from the Netdata web interface:
139
140 1. Go to **Nodes**.
126 -2. Select the node **where you want the couchbase data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
141 +2. Select the node **where you want the couchbase 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 _couchbase_ (or scroll the list) to locate the **couchbase** collector.
144 5. Click the **+** next to the **couchbase** collector to add a new job.
130 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -141,7 +158,7 @@ update_every: 1
158 autodetection_retry: 0
159 jobs:
160 - name: some_name1
144 - - 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-a-configuration-file-using-edit-config) script from the
164 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/couchdb/integrations/couchdb.md
+21 -4
@@ -90,6 +90,21 @@ There are no alerts configured by default for this integration.
90
91 ## Setup
92
93 +
94 +You can configure the **couchdb** collector in two ways:
95 +
96 +| Method | Best for | How to |
97 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
98 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **couchdb**, then click **+** to add a job. |
99 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/couchdb.conf` and add a job. |
100 +
101 +:::important
102 +
103 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
104 +
105 +:::
106 +
107 +
108 ### Prerequisites
109
110 No action required.
@@ -130,14 +145,16 @@ The following options can be defined globally: update_every, autodetection_retry
145
146 #### via UI
147
133 -The **couchdb** collector can be configured directly through the Netdata web interface:
148 +Configure the **couchdb** collector from the Netdata web interface:
149
150 1. Go to **Nodes**.
136 -2. Select the node **where you want the couchdb data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
151 +2. Select the node **where you want the couchdb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
152 3. The **Collectors → Jobs** view opens by default.
153 4. In the Search box, type _couchdb_ (or scroll the list) to locate the **couchdb** collector.
154 5. Click the **+** next to the **couchdb** collector to add a new job.
140 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
155 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
156 + - **Test** runs the job with the provided settings and shows whether data can be collected.
157 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
158
159
160 #### via File
@@ -151,7 +168,7 @@ update_every: 1
168 autodetection_retry: 0
169 jobs:
170 - name: some_name1
154 - - name: some_name1
171 + - name: some_name2
172 ```
173 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
174 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dmcache/integrations/dmcache_devices.md
+21 -4
@@ -84,6 +84,21 @@ There are no alerts configured by default for this integration.
84
85 ## Setup
86
87 +
88 +You can configure the **dmcache** collector in two ways:
89 +
90 +| Method | Best for | How to |
91 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
92 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dmcache**, then click **+** to add a job. |
93 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dmcache.conf` and add a job. |
94 +
95 +:::important
96 +
97 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
98 +
99 +:::
100 +
101 +
102 ### Prerequisites
103
104 No action required.
@@ -107,14 +122,16 @@ The following options can be defined globally: update_every.
122
123 #### via UI
124
110 -The **dmcache** collector can be configured directly through the Netdata web interface:
125 +Configure the **dmcache** collector from the Netdata web interface:
126
127 1. Go to **Nodes**.
113 -2. Select the node **where you want the dmcache data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
128 +2. Select the node **where you want the dmcache 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 _dmcache_ (or scroll the list) to locate the **dmcache** collector.
131 5. Click the **+** next to the **dmcache** collector to add a new job.
117 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -128,7 +145,7 @@ update_every: 1
145 autodetection_retry: 0
146 jobs:
147 - name: some_name1
131 - - 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-a-configuration-file-using-edit-config) script from the
151 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dnsdist/integrations/dnsdist.md
+21 -4
@@ -86,6 +86,21 @@ There are no alerts configured by default for this integration.
86
87 ## Setup
88
89 +
90 +You can configure the **dnsdist** collector in two ways:
91 +
92 +| Method | Best for | How to |
93 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
94 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dnsdist**, then click **+** to add a job. |
95 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dnsdist.conf` and add a job. |
96 +
97 +:::important
98 +
99 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
100 +
101 +:::
102 +
103 +
104 ### Prerequisites
105
106 #### Enable DNSdist built-in Webserver
@@ -128,14 +143,16 @@ The following options can be defined globally: update_every, autodetection_retry
143
144 #### via UI
145
131 -The **dnsdist** collector can be configured directly through the Netdata web interface:
146 +Configure the **dnsdist** collector from the Netdata web interface:
147
148 1. Go to **Nodes**.
134 -2. Select the node **where you want the dnsdist data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
149 +2. Select the node **where you want the dnsdist data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
150 3. The **Collectors → Jobs** view opens by default.
151 4. In the Search box, type _dnsdist_ (or scroll the list) to locate the **dnsdist** collector.
152 5. Click the **+** next to the **dnsdist** collector to add a new job.
138 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
153 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
154 + - **Test** runs the job with the provided settings and shows whether data can be collected.
155 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
156
157
158 #### via File
@@ -149,7 +166,7 @@ update_every: 1
166 autodetection_retry: 0
167 jobs:
168 - name: some_name1
152 - - name: some_name1
169 + - name: some_name2
170 ```
171 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
172 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dnsmasq/integrations/dnsmasq.md
+21 -4
@@ -78,6 +78,21 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 +You can configure the **dnsmasq** collector in two ways:
83 +
84 +| Method | Best for | How to |
85 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
86 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dnsmasq**, then click **+** to add a job. |
87 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dnsmasq.conf` and add a job. |
88 +
89 +:::important
90 +
91 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
92 +
93 +:::
94 +
95 +
96 ### Prerequisites
97
98 No action required.
@@ -104,14 +119,16 @@ The following options can be defined globally: update_every, autodetection_retry
119
120 #### via UI
121
107 -The **dnsmasq** collector can be configured directly through the Netdata web interface:
122 +Configure the **dnsmasq** collector from the Netdata web interface:
123
124 1. Go to **Nodes**.
110 -2. Select the node **where you want the dnsmasq data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
125 +2. Select the node **where you want the dnsmasq data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
126 3. The **Collectors → Jobs** view opens by default.
127 4. In the Search box, type _dnsmasq_ (or scroll the list) to locate the **dnsmasq** collector.
128 5. Click the **+** next to the **dnsmasq** collector to add a new job.
114 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
129 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
130 + - **Test** runs the job with the provided settings and shows whether data can be collected.
131 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
132
133
134 #### via File
@@ -125,7 +142,7 @@ update_every: 1
142 autodetection_retry: 0
143 jobs:
144 - name: some_name1
128 - - name: some_name1
145 + - name: some_name2
146 ```
147 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
148 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md
+21 -4
@@ -107,6 +107,21 @@ The following alerts are available:
107
108 ## Setup
109
110 +
111 +You can configure the **dnsmasq_dhcp** collector in two ways:
112 +
113 +| Method | Best for | How to |
114 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
115 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dnsmasq_dhcp**, then click **+** to add a job. |
116 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dnsmasq_dhcp.conf` and add a job. |
117 +
118 +:::important
119 +
120 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
121 +
122 +:::
123 +
124 +
125 ### Prerequisites
126
127 No action required.
@@ -133,14 +148,16 @@ The following options can be defined globally: update_every, autodetection_retry
148
149 #### via UI
150
136 -The **dnsmasq_dhcp** collector can be configured directly through the Netdata web interface:
151 +Configure the **dnsmasq_dhcp** collector from the Netdata web interface:
152
153 1. Go to **Nodes**.
139 -2. Select the node **where you want the dnsmasq_dhcp data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
154 +2. Select the node **where you want the dnsmasq_dhcp data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
155 3. The **Collectors → Jobs** view opens by default.
156 4. In the Search box, type _dnsmasq_dhcp_ (or scroll the list) to locate the **dnsmasq_dhcp** collector.
157 5. Click the **+** next to the **dnsmasq_dhcp** collector to add a new job.
143 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
158 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
159 + - **Test** runs the job with the provided settings and shows whether data can be collected.
160 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
161
162
163 #### via File
@@ -154,7 +171,7 @@ update_every: 1
171 autodetection_retry: 0
172 jobs:
173 - name: some_name1
157 - - name: some_name1
174 + - name: some_name2
175 ```
176 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
177 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dnsquery/integrations/dns_query.md
+21 -4
@@ -87,6 +87,21 @@ The following alerts are available:
87
88 ## Setup
89
90 +
91 +You can configure the **dns_query** 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 **dns_query**, 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/dns_query.conf` and add a job. |
97 +
98 +:::important
99 +
100 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
101 +
102 +:::
103 +
104 +
105 ### Prerequisites
106
107 No action required.
@@ -116,14 +131,16 @@ The following options can be defined globally: update_every, autodetection_retry
131
132 #### via UI
133
119 -The **dns_query** collector can be configured directly through the Netdata web interface:
134 +Configure the **dns_query** collector from the Netdata web interface:
135
136 1. Go to **Nodes**.
122 -2. Select the node **where you want the dns_query data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
137 +2. Select the node **where you want the dns_query data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
138 3. The **Collectors → Jobs** view opens by default.
139 4. In the Search box, type _dns_query_ (or scroll the list) to locate the **dns_query** collector.
140 5. Click the **+** next to the **dns_query** collector to add a new job.
126 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
141 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
142 + - **Test** runs the job with the provided settings and shows whether data can be collected.
143 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
144
145
146 #### via File
@@ -137,7 +154,7 @@ update_every: 1
154 autodetection_retry: 0
155 jobs:
156 - name: some_name1
140 - - name: some_name1
157 + - name: some_name2
158 ```
159 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
160 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/docker/integrations/docker.md
+21 -4
@@ -110,6 +110,21 @@ The following alerts are available:
110
111 ## Setup
112
113 +
114 +You can configure the **docker** collector in two ways:
115 +
116 +| Method | Best for | How to |
117 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
118 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **docker**, then click **+** to add a job. |
119 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/docker.conf` and add a job. |
120 +
121 +:::important
122 +
123 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
124 +
125 +:::
126 +
127 +
128 ### Prerequisites
129
130 No action required.
@@ -137,14 +152,16 @@ The following options can be defined globally: update_every, autodetection_retry
152
153 #### via UI
154
140 -The **docker** collector can be configured directly through the Netdata web interface:
155 +Configure the **docker** collector from the Netdata web interface:
156
157 1. Go to **Nodes**.
143 -2. Select the node **where you want the docker data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
158 +2. Select the node **where you want the docker data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
159 3. The **Collectors → Jobs** view opens by default.
160 4. In the Search box, type _docker_ (or scroll the list) to locate the **docker** collector.
161 5. Click the **+** next to the **docker** collector to add a new job.
147 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
162 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
163 + - **Test** runs the job with the provided settings and shows whether data can be collected.
164 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
165
166
167 #### via File
@@ -158,7 +175,7 @@ update_every: 1
175 autodetection_retry: 0
176 jobs:
177 - name: some_name1
161 - - name: some_name1
178 + - name: some_name2
179 ```
180 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
181 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/docker_engine/integrations/docker_engine.md
+21 -4
@@ -84,6 +84,21 @@ There are no alerts configured by default for this integration.
84
85 ## Setup
86
87 +
88 +You can configure the **docker_engine** collector in two ways:
89 +
90 +| Method | Best for | How to |
91 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
92 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **docker_engine**, then click **+** to add a job. |
93 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/docker_engine.conf` and add a job. |
94 +
95 +:::important
96 +
97 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
98 +
99 +:::
100 +
101 +
102 ### Prerequisites
103
104 #### Enable built-in Prometheus exporter
@@ -126,14 +141,16 @@ The following options can be defined globally: update_every, autodetection_retry
141
142 #### via UI
143
129 -The **docker_engine** collector can be configured directly through the Netdata web interface:
144 +Configure the **docker_engine** collector from the Netdata web interface:
145
146 1. Go to **Nodes**.
132 -2. Select the node **where you want the docker_engine data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
147 +2. Select the node **where you want the docker_engine data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
148 3. The **Collectors → Jobs** view opens by default.
149 4. In the Search box, type _docker_engine_ (or scroll the list) to locate the **docker_engine** collector.
150 5. Click the **+** next to the **docker_engine** collector to add a new job.
136 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
151 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
152 + - **Test** runs the job with the provided settings and shows whether data can be collected.
153 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
154
155
156 #### via File
@@ -147,7 +164,7 @@ update_every: 1
164 autodetection_retry: 0
165 jobs:
166 - name: some_name1
150 - - name: some_name1
167 + - name: some_name2
168 ```
169 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
170 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dockerhub/integrations/docker_hub_repository.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **dockerhub** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dockerhub**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dockerhub.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 No action required.
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every, autodetection_retry
134
135 #### via UI
136
122 -The **dockerhub** collector can be configured directly through the Netdata web interface:
137 +Configure the **dockerhub** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the dockerhub data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the dockerhub data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _dockerhub_ (or scroll the list) to locate the **dockerhub** collector.
143 5. Click the **+** next to the **dockerhub** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/dovecot/integrations/dovecot.md
+21 -4
@@ -90,6 +90,21 @@ There are no alerts configured by default for this integration.
90
91 ## Setup
92
93 +
94 +You can configure the **dovecot** collector in two ways:
95 +
96 +| Method | Best for | How to |
97 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
98 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **dovecot**, then click **+** to add a job. |
99 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/dovecot.conf` and add a job. |
100 +
101 +:::important
102 +
103 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
104 +
105 +:::
106 +
107 +
108 ### Prerequisites
109
110 #### Enable old_stats plugin
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every, autodetection_retry
134
135 #### via UI
136
122 -The **dovecot** collector can be configured directly through the Netdata web interface:
137 +Configure the **dovecot** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the dovecot data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the dovecot data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _dovecot_ (or scroll the list) to locate the **dovecot** collector.
143 5. Click the **+** next to the **dovecot** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/elasticsearch/integrations/elasticsearch.md
+21 -4
@@ -182,6 +182,21 @@ The following alerts are available:
182
183 ## Setup
184
185 +
186 +You can configure the **elasticsearch** collector in two ways:
187 +
188 +| Method | Best for | How to |
189 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
190 +| [**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. |
191 +| [**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. |
192 +
193 +:::important
194 +
195 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
196 +
197 +:::
198 +
199 +
200 ### Prerequisites
201
202 No action required.
@@ -225,14 +240,16 @@ The following options can be defined globally: update_every, autodetection_retry
240
241 #### via UI
242
228 -The **elasticsearch** collector can be configured directly through the Netdata web interface:
243 +Configure the **elasticsearch** collector from the Netdata web interface:
244
245 1. Go to **Nodes**.
231 -2. Select the node **where you want the elasticsearch data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
246 +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.
247 3. The **Collectors → Jobs** view opens by default.
248 4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
249 5. Click the **+** next to the **elasticsearch** collector to add a new job.
235 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
250 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
251 + - **Test** runs the job with the provided settings and shows whether data can be collected.
252 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
253
254
255 #### via File
@@ -246,7 +263,7 @@ update_every: 1
263 autodetection_retry: 0
264 jobs:
265 - name: some_name1
249 - - name: some_name1
266 + - name: some_name2
267 ```
268 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
269 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/elasticsearch/integrations/opensearch.md
+21 -4
@@ -182,6 +182,21 @@ The following alerts are available:
182
183 ## Setup
184
185 +
186 +You can configure the **elasticsearch** collector in two ways:
187 +
188 +| Method | Best for | How to |
189 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
190 +| [**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. |
191 +| [**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. |
192 +
193 +:::important
194 +
195 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
196 +
197 +:::
198 +
199 +
200 ### Prerequisites
201
202 No action required.
@@ -225,14 +240,16 @@ The following options can be defined globally: update_every, autodetection_retry
240
241 #### via UI
242
228 -The **elasticsearch** collector can be configured directly through the Netdata web interface:
243 +Configure the **elasticsearch** collector from the Netdata web interface:
244
245 1. Go to **Nodes**.
231 -2. Select the node **where you want the elasticsearch data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
246 +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.
247 3. The **Collectors → Jobs** view opens by default.
248 4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
249 5. Click the **+** next to the **elasticsearch** collector to add a new job.
235 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
250 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
251 + - **Test** runs the job with the provided settings and shows whether data can be collected.
252 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
253
254
255 #### via File
@@ -246,7 +263,7 @@ update_every: 1
263 autodetection_retry: 0
264 jobs:
265 - name: some_name1
249 - - name: some_name1
266 + - name: some_name2
267 ```
268 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
269 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/envoy/integrations/envoy.md
+21 -4
@@ -129,6 +129,21 @@ There are no alerts configured by default for this integration.
129
130 ## Setup
131
132 +
133 +You can configure the **envoy** collector in two ways:
134 +
135 +| Method | Best for | How to |
136 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
137 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **envoy**, then click **+** to add a job. |
138 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/envoy.conf` and add a job. |
139 +
140 +:::important
141 +
142 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
143 +
144 +:::
145 +
146 +
147 ### Prerequisites
148
149 No action required.
@@ -167,14 +182,16 @@ The following options can be defined globally: update_every, autodetection_retry
182
183 #### via UI
184
170 -The **envoy** collector can be configured directly through the Netdata web interface:
185 +Configure the **envoy** collector from the Netdata web interface:
186
187 1. Go to **Nodes**.
173 -2. Select the node **where you want the envoy data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
188 +2. Select the node **where you want the envoy data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
189 3. The **Collectors → Jobs** view opens by default.
190 4. In the Search box, type _envoy_ (or scroll the list) to locate the **envoy** collector.
191 5. Click the **+** next to the **envoy** collector to add a new job.
177 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
192 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
193 + - **Test** runs the job with the provided settings and shows whether data can be collected.
194 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
195
196
197 #### via File
@@ -188,7 +205,7 @@ update_every: 1
205 autodetection_retry: 0
206 jobs:
207 - name: some_name1
191 - - name: some_name1
208 + - name: some_name2
209 ```
210 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
211 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/ethtool/integrations/optical_modules.md
+21 -4
@@ -85,6 +85,21 @@ There are no alerts configured by default for this integration.
85
86 ## Setup
87
88 +
89 +You can configure the **ethtool** collector in two ways:
90 +
91 +| Method | Best for | How to |
92 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
93 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **ethtool**, then click **+** to add a job. |
94 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ethtool.conf` and add a job. |
95 +
96 +:::important
97 +
98 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
99 +
100 +:::
101 +
102 +
103 ### Prerequisites
104
105 No action required.
@@ -109,14 +124,16 @@ The following options can be defined globally: update_every.
124
125 #### via UI
126
112 -The **ethtool** collector can be configured directly through the Netdata web interface:
127 +Configure the **ethtool** collector from the Netdata web interface:
128
129 1. Go to **Nodes**.
115 -2. Select the node **where you want the ethtool data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
130 +2. Select the node **where you want the ethtool data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
131 3. The **Collectors → Jobs** view opens by default.
132 4. In the Search box, type _ethtool_ (or scroll the list) to locate the **ethtool** collector.
133 5. Click the **+** next to the **ethtool** collector to add a new job.
119 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
134 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
135 + - **Test** runs the job with the provided settings and shows whether data can be collected.
136 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
137
138
139 #### via File
@@ -130,7 +147,7 @@ update_every: 1
147 autodetection_retry: 0
148 jobs:
149 - name: some_name1
133 - - name: some_name1
150 + - name: some_name2
151 ```
152 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
153 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/exim/integrations/exim.md
+21 -4
@@ -77,6 +77,21 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 +You can configure the **exim** collector in two ways:
82 +
83 +| Method | Best for | How to |
84 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
85 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **exim**, then click **+** to add a job. |
86 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/exim.conf` and add a job. |
87 +
88 +:::important
89 +
90 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
91 +
92 +:::
93 +
94 +
95 ### Prerequisites
96
97 No action required.
@@ -100,14 +115,16 @@ The following options can be defined globally: update_every.
115
116 #### via UI
117
103 -The **exim** collector can be configured directly through the Netdata web interface:
118 +Configure the **exim** collector from the Netdata web interface:
119
120 1. Go to **Nodes**.
106 -2. Select the node **where you want the exim data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
121 +2. Select the node **where you want the exim data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
122 3. The **Collectors → Jobs** view opens by default.
123 4. In the Search box, type _exim_ (or scroll the list) to locate the **exim** collector.
124 5. Click the **+** next to the **exim** collector to add a new job.
110 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
125 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
126 + - **Test** runs the job with the provided settings and shows whether data can be collected.
127 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
128
129
130 #### via File
@@ -121,7 +138,7 @@ update_every: 1
138 autodetection_retry: 0
139 jobs:
140 - name: some_name1
124 - - name: some_name1
141 + - name: some_name2
142 ```
143 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
144 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/fail2ban/integrations/fail2ban.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **fail2ban** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **fail2ban**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/fail2ban.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 #### For Netdata running in a Docker container
@@ -115,14 +130,16 @@ The following options can be defined globally: update_every.
130
131 #### via UI
132
118 -The **fail2ban** collector can be configured directly through the Netdata web interface:
133 +Configure the **fail2ban** collector from the Netdata web interface:
134
135 1. Go to **Nodes**.
121 -2. Select the node **where you want the fail2ban data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
136 +2. Select the node **where you want the fail2ban data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
137 3. The **Collectors → Jobs** view opens by default.
138 4. In the Search box, type _fail2ban_ (or scroll the list) to locate the **fail2ban** collector.
139 5. Click the **+** next to the **fail2ban** collector to add a new job.
125 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
140 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
141 + - **Test** runs the job with the provided settings and shows whether data can be collected.
142 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
143
144
145 #### via File
@@ -136,7 +153,7 @@ update_every: 1
153 autodetection_retry: 0
154 jobs:
155 - name: some_name1
139 - - name: some_name1
156 + - name: some_name2
157 ```
158 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
159 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/filecheck/integrations/files_and_directories.md
+21 -4
@@ -102,6 +102,21 @@ There are no alerts configured by default for this integration.
102
103 ## Setup
104
105 +
106 +You can configure the **filecheck** collector in two ways:
107 +
108 +| Method | Best for | How to |
109 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
110 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **filecheck**, then click **+** to add a job. |
111 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/filecheck.conf` and add a job. |
112 +
113 +:::important
114 +
115 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
116 +
117 +:::
118 +
119 +
120 ### Prerequisites
121
122 No action required.
@@ -166,14 +181,16 @@ dirs:
181
182 #### via UI
183
169 -The **filecheck** collector can be configured directly through the Netdata web interface:
184 +Configure the **filecheck** collector from the Netdata web interface:
185
186 1. Go to **Nodes**.
172 -2. Select the node **where you want the filecheck data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
187 +2. Select the node **where you want the filecheck data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
188 3. The **Collectors → Jobs** view opens by default.
189 4. In the Search box, type _filecheck_ (or scroll the list) to locate the **filecheck** collector.
190 5. Click the **+** next to the **filecheck** collector to add a new job.
176 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
191 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
192 + - **Test** runs the job with the provided settings and shows whether data can be collected.
193 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
194
195
196 #### via File
@@ -187,7 +204,7 @@ update_every: 1
204 autodetection_retry: 0
205 jobs:
206 - name: some_name1
190 - - name: some_name1
207 + - name: some_name2
208 ```
209 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
210 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/fluentd/integrations/fluentd.md
+21 -4
@@ -77,6 +77,21 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 +You can configure the **fluentd** collector in two ways:
82 +
83 +| Method | Best for | How to |
84 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
85 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **fluentd**, then click **+** to add a job. |
86 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/fluentd.conf` and add a job. |
87 +
88 +:::important
89 +
90 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
91 +
92 +:::
93 +
94 +
95 ### Prerequisites
96
97 #### Enable monitor agent
@@ -118,14 +133,16 @@ The following options can be defined globally: update_every, autodetection_retry
133
134 #### via UI
135
121 -The **fluentd** collector can be configured directly through the Netdata web interface:
136 +Configure the **fluentd** collector from the Netdata web interface:
137
138 1. Go to **Nodes**.
124 -2. Select the node **where you want the fluentd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
139 +2. Select the node **where you want the fluentd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
140 3. The **Collectors → Jobs** view opens by default.
141 4. In the Search box, type _fluentd_ (or scroll the list) to locate the **fluentd** collector.
142 5. Click the **+** next to the **fluentd** collector to add a new job.
128 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
143 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
144 + - **Test** runs the job with the provided settings and shows whether data can be collected.
145 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
146
147
148 #### via File
@@ -139,7 +156,7 @@ update_every: 1
156 autodetection_retry: 0
157 jobs:
158 - name: some_name1
142 - - name: some_name1
159 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
162 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/freeradius/integrations/freeradius.md
+21 -4
@@ -87,6 +87,21 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 +You can configure the **freeradius** 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 **freeradius**, 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/freeradius.conf` and add a job. |
97 +
98 +:::important
99 +
100 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
101 +
102 +:::
103 +
104 +
105 ### Prerequisites
106
107 #### Enable status server
@@ -117,14 +132,16 @@ The following options can be defined globally: update_every, autodetection_retry
132
133 #### via UI
134
120 -The **freeradius** collector can be configured directly through the Netdata web interface:
135 +Configure the **freeradius** collector from the Netdata web interface:
136
137 1. Go to **Nodes**.
123 -2. Select the node **where you want the freeradius data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
138 +2. Select the node **where you want the freeradius 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 _freeradius_ (or scroll the list) to locate the **freeradius** collector.
141 5. Click the **+** next to the **freeradius** collector to add a new job.
127 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -138,7 +155,7 @@ update_every: 1
155 autodetection_retry: 0
156 jobs:
157 - name: some_name1
141 - - 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-a-configuration-file-using-edit-config) script from the
161 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/gearman/integrations/gearman.md
+21 -4
@@ -99,6 +99,21 @@ There are no alerts configured by default for this integration.
99
100 ## Setup
101
102 +
103 +You can configure the **gearman** collector in two ways:
104 +
105 +| Method | Best for | How to |
106 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
107 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **gearman**, then click **+** to add a job. |
108 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/gearman.conf` and add a job. |
109 +
110 +:::important
111 +
112 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
113 +
114 +:::
115 +
116 +
117 ### Prerequisites
118
119 No action required.
@@ -124,14 +139,16 @@ The following options can be defined globally: update_every, autodetection_retry
139
140 #### via UI
141
127 -The **gearman** collector can be configured directly through the Netdata web interface:
142 +Configure the **gearman** collector from the Netdata web interface:
143
144 1. Go to **Nodes**.
130 -2. Select the node **where you want the gearman data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
145 +2. Select the node **where you want the gearman data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
146 3. The **Collectors → Jobs** view opens by default.
147 4. In the Search box, type _gearman_ (or scroll the list) to locate the **gearman** collector.
148 5. Click the **+** next to the **gearman** collector to add a new job.
134 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
149 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
150 + - **Test** runs the job with the provided settings and shows whether data can be collected.
151 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
152
153
154 #### via File
@@ -145,7 +162,7 @@ update_every: 1
162 autodetection_retry: 0
163 jobs:
164 - name: some_name1
148 - - name: some_name1
165 + - name: some_name2
166 ```
167 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
168 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/geth/integrations/go-ethereum.md
+21 -4
@@ -91,6 +91,21 @@ There are no alerts configured by default for this integration.
91
92 ## Setup
93
94 +
95 +You can configure the **geth** collector in two ways:
96 +
97 +| Method | Best for | How to |
98 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
99 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **geth**, then click **+** to add a job. |
100 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/geth.conf` and add a job. |
101 +
102 +:::important
103 +
104 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
105 +
106 +:::
107 +
108 +
109 ### Prerequisites
110
111 No action required.
@@ -129,14 +144,16 @@ The following options can be defined globally: update_every, autodetection_retry
144
145 #### via UI
146
132 -The **geth** collector can be configured directly through the Netdata web interface:
147 +Configure the **geth** collector from the Netdata web interface:
148
149 1. Go to **Nodes**.
135 -2. Select the node **where you want the geth data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
150 +2. Select the node **where you want the geth data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
151 3. The **Collectors → Jobs** view opens by default.
152 4. In the Search box, type _geth_ (or scroll the list) to locate the **geth** collector.
153 5. Click the **+** next to the **geth** collector to add a new job.
139 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
154 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
155 + - **Test** runs the job with the provided settings and shows whether data can be collected.
156 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
157
158
159 #### via File
@@ -150,7 +167,7 @@ update_every: 1
167 autodetection_retry: 0
168 jobs:
169 - name: some_name1
153 - - name: some_name1
170 + - name: some_name2
171 ```
172 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
173 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/haproxy/integrations/haproxy.md
+21 -4
@@ -92,6 +92,21 @@ There are no alerts configured by default for this integration.
92
93 ## Setup
94
95 +
96 +You can configure the **haproxy** collector in two ways:
97 +
98 +| Method | Best for | How to |
99 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
100 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **haproxy**, then click **+** to add a job. |
101 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/haproxy.conf` and add a job. |
102 +
103 +:::important
104 +
105 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
106 +
107 +:::
108 +
109 +
110 ### Prerequisites
111
112 #### Enable PROMEX addon.
@@ -134,14 +149,16 @@ The following options can be defined globally: update_every, autodetection_retry
149
150 #### via UI
151
137 -The **haproxy** collector can be configured directly through the Netdata web interface:
152 +Configure the **haproxy** collector from the Netdata web interface:
153
154 1. Go to **Nodes**.
140 -2. Select the node **where you want the haproxy data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
155 +2. Select the node **where you want the haproxy 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 _haproxy_ (or scroll the list) to locate the **haproxy** collector.
158 5. Click the **+** next to the **haproxy** collector to add a new job.
144 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -155,7 +172,7 @@ update_every: 1
172 autodetection_retry: 0
173 jobs:
174 - name: some_name1
158 - - 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-a-configuration-file-using-edit-config) script from the
178 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/hddtemp/integrations/hdd_temperature.md
+21 -4
@@ -84,6 +84,21 @@ There are no alerts configured by default for this integration.
84
85 ## Setup
86
87 +
88 +You can configure the **hddtemp** collector in two ways:
89 +
90 +| Method | Best for | How to |
91 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
92 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **hddtemp**, then click **+** to add a job. |
93 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/hddtemp.conf` and add a job. |
94 +
95 +:::important
96 +
97 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
98 +
99 +:::
100 +
101 +
102 ### Prerequisites
103
104 #### Install hddtemp
@@ -113,14 +128,16 @@ The following options can be defined globally: update_every, autodetection_retry
128
129 #### via UI
130
116 -The **hddtemp** collector can be configured directly through the Netdata web interface:
131 +Configure the **hddtemp** collector from the Netdata web interface:
132
133 1. Go to **Nodes**.
119 -2. Select the node **where you want the hddtemp data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
134 +2. Select the node **where you want the hddtemp data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
135 3. The **Collectors → Jobs** view opens by default.
136 4. In the Search box, type _hddtemp_ (or scroll the list) to locate the **hddtemp** collector.
137 5. Click the **+** next to the **hddtemp** collector to add a new job.
123 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
138 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
139 + - **Test** runs the job with the provided settings and shows whether data can be collected.
140 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
141
142
143 #### via File
@@ -134,7 +151,7 @@ update_every: 1
151 autodetection_retry: 0
152 jobs:
153 - name: some_name1
137 - - name: some_name1
154 + - name: some_name2
155 ```
156 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
157 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/hdfs/integrations/hadoop_distributed_file_system_hdfs.md
+21 -4
@@ -109,6 +109,21 @@ The following alerts are available:
109
110 ## Setup
111
112 +
113 +You can configure the **hfs** collector in two ways:
114 +
115 +| Method | Best for | How to |
116 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
117 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **hfs**, then click **+** to add a job. |
118 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/hdfs.conf` and add a job. |
119 +
120 +:::important
121 +
122 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
123 +
124 +:::
125 +
126 +
127 ### Prerequisites
128
129 No action required.
@@ -147,14 +162,16 @@ The following options can be defined globally: update_every, autodetection_retry
162
163 #### via UI
164
150 -The **hfs** collector can be configured directly through the Netdata web interface:
165 +Configure the **hfs** collector from the Netdata web interface:
166
167 1. Go to **Nodes**.
153 -2. Select the node **where you want the hfs data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
168 +2. Select the node **where you want the hfs data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
169 3. The **Collectors → Jobs** view opens by default.
170 4. In the Search box, type _hfs_ (or scroll the list) to locate the **hfs** collector.
171 5. Click the **+** next to the **hfs** collector to add a new job.
157 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
172 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
173 + - **Test** runs the job with the provided settings and shows whether data can be collected.
174 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
175
176
177 #### via File
@@ -168,7 +185,7 @@ update_every: 1
185 autodetection_retry: 0
186 jobs:
187 - name: some_name1
171 - - name: some_name1
188 + - name: some_name2
189 ```
190 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
191 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/hpssa/integrations/hpe_smart_arrays.md
+21 -4
@@ -153,6 +153,21 @@ There are no alerts configured by default for this integration.
153
154 ## Setup
155
156 +
157 +You can configure the **hpssa** collector in two ways:
158 +
159 +| Method | Best for | How to |
160 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
161 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **hpssa**, then click **+** to add a job. |
162 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ssacli.conf` and add a job. |
163 +
164 +:::important
165 +
166 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
167 +
168 +:::
169 +
170 +
171 ### Prerequisites
172
173 #### Install ssacli
@@ -180,14 +195,16 @@ The following options can be defined globally: update_every.
195
196 #### via UI
197
183 -The **hpssa** collector can be configured directly through the Netdata web interface:
198 +Configure the **hpssa** collector from the Netdata web interface:
199
200 1. Go to **Nodes**.
186 -2. Select the node **where you want the hpssa data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
201 +2. Select the node **where you want the hpssa data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
202 3. The **Collectors → Jobs** view opens by default.
203 4. In the Search box, type _hpssa_ (or scroll the list) to locate the **hpssa** collector.
204 5. Click the **+** next to the **hpssa** collector to add a new job.
190 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
205 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
206 + - **Test** runs the job with the provided settings and shows whether data can be collected.
207 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
208
209
210 #### via File
@@ -201,7 +218,7 @@ update_every: 1
218 autodetection_retry: 0
219 jobs:
220 - name: some_name1
204 - - name: some_name1
221 + - name: some_name2
222 ```
223 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
224 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/httpcheck/integrations/http_endpoints.md
+21 -4
@@ -104,6 +104,21 @@ The following alerts are available:
104
105 ## Setup
106
107 +
108 +You can configure the **httpcheck** collector in two ways:
109 +
110 +| Method | Best for | How to |
111 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
112 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **httpcheck**, then click **+** to add a job. |
113 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/httpcheck.conf` and add a job. |
114 +
115 +:::important
116 +
117 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
118 +
119 +:::
120 +
121 +
122 ### Prerequisites
123
124 No action required.
@@ -149,14 +164,16 @@ The following options can be defined globally: update_every, autodetection_retry
164
165 #### via UI
166
152 -The **httpcheck** collector can be configured directly through the Netdata web interface:
167 +Configure the **httpcheck** collector from the Netdata web interface:
168
169 1. Go to **Nodes**.
155 -2. Select the node **where you want the httpcheck data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170 +2. Select the node **where you want the httpcheck data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
171 3. The **Collectors → Jobs** view opens by default.
172 4. In the Search box, type _httpcheck_ (or scroll the list) to locate the **httpcheck** collector.
173 5. Click the **+** next to the **httpcheck** collector to add a new job.
159 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
174 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
175 + - **Test** runs the job with the provided settings and shows whether data can be collected.
176 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
177
178
179 #### via File
@@ -170,7 +187,7 @@ update_every: 1
187 autodetection_retry: 0
188 jobs:
189 - name: some_name1
173 - - name: some_name1
190 + - name: some_name2
191 ```
192 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
193 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/icecast/integrations/icecast.md
+21 -4
@@ -78,6 +78,21 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 +You can configure the **icecast** collector in two ways:
83 +
84 +| Method | Best for | How to |
85 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
86 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **icecast**, then click **+** to add a job. |
87 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/icecast.conf` and add a job. |
88 +
89 +:::important
90 +
91 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
92 +
93 +:::
94 +
95 +
96 ### Prerequisites
97
98 #### Icecast minimum version
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every, autodetection_retry
134
135 #### via UI
136
122 -The **icecast** collector can be configured directly through the Netdata web interface:
137 +Configure the **icecast** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the icecast data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the icecast data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _icecast_ (or scroll the list) to locate the **icecast** collector.
143 5. Click the **+** next to the **icecast** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/intelgpu/integrations/intel_gpu.md
+21 -4
@@ -96,6 +96,21 @@ There are no alerts configured by default for this integration.
96
97 ## Setup
98
99 +
100 +You can configure the **intelgpu** collector in two ways:
101 +
102 +| Method | Best for | How to |
103 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
104 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **intelgpu**, then click **+** to add a job. |
105 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/intelgpu.conf` and add a job. |
106 +
107 +:::important
108 +
109 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
110 +
111 +:::
112 +
113 +
114 ### Prerequisites
115
116 #### Install intel-gpu-tools
@@ -122,14 +137,16 @@ The following options can be defined globally: update_every.
137
138 #### via UI
139
125 -The **intelgpu** collector can be configured directly through the Netdata web interface:
140 +Configure the **intelgpu** collector from the Netdata web interface:
141
142 1. Go to **Nodes**.
128 -2. Select the node **where you want the intelgpu data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
143 +2. Select the node **where you want the intelgpu data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
144 3. The **Collectors → Jobs** view opens by default.
145 4. In the Search box, type _intelgpu_ (or scroll the list) to locate the **intelgpu** collector.
146 5. Click the **+** next to the **intelgpu** collector to add a new job.
132 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
147 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
148 + - **Test** runs the job with the provided settings and shows whether data can be collected.
149 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
150
151
152 #### via File
@@ -143,7 +160,7 @@ update_every: 1
160 autodetection_retry: 0
161 jobs:
162 - name: some_name1
146 - - name: some_name1
163 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
166 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/ipfs/integrations/ipfs.md
+21 -4
@@ -99,6 +99,21 @@ The following alerts are available:
99
100 ## Setup
101
102 +
103 +You can configure the **ipfs** collector in two ways:
104 +
105 +| Method | Best for | How to |
106 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
107 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **ipfs**, then click **+** to add a job. |
108 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ipfs.conf` and add a job. |
109 +
110 +:::important
111 +
112 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
113 +
114 +:::
115 +
116 +
117 ### Prerequisites
118
119 No action required.
@@ -139,14 +154,16 @@ The following options can be defined globally: update_every, autodetection_retry
154
155 #### via UI
156
142 -The **ipfs** collector can be configured directly through the Netdata web interface:
157 +Configure the **ipfs** collector from the Netdata web interface:
158
159 1. Go to **Nodes**.
145 -2. Select the node **where you want the ipfs data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
160 +2. Select the node **where you want the ipfs data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
161 3. The **Collectors → Jobs** view opens by default.
162 4. In the Search box, type _ipfs_ (or scroll the list) to locate the **ipfs** collector.
163 5. Click the **+** next to the **ipfs** collector to add a new job.
149 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
164 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
165 + - **Test** runs the job with the provided settings and shows whether data can be collected.
166 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
167
168
169 #### via File
@@ -160,7 +177,7 @@ update_every: 1
177 autodetection_retry: 0
178 jobs:
179 - name: some_name1
163 - - name: some_name1
180 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
183 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/isc_dhcpd/integrations/isc_dhcp.md
+21 -4
@@ -95,6 +95,21 @@ There are no alerts configured by default for this integration.
95
96 ## Setup
97
98 +
99 +You can configure the **isc_dhcpd** collector in two ways:
100 +
101 +| Method | Best for | How to |
102 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
103 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **isc_dhcpd**, then click **+** to add a job. |
104 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/isc_dhcpd.conf` and add a job. |
105 +
106 +:::important
107 +
108 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
109 +
110 +:::
111 +
112 +
113 ### Prerequisites
114
115 No action required.
@@ -136,14 +151,16 @@ pools:
151
152 #### via UI
153
139 -The **isc_dhcpd** collector can be configured directly through the Netdata web interface:
154 +Configure the **isc_dhcpd** collector from the Netdata web interface:
155
156 1. Go to **Nodes**.
142 -2. Select the node **where you want the isc_dhcpd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
157 +2. Select the node **where you want the isc_dhcpd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
158 3. The **Collectors → Jobs** view opens by default.
159 4. In the Search box, type _isc_dhcpd_ (or scroll the list) to locate the **isc_dhcpd** collector.
160 5. Click the **+** next to the **isc_dhcpd** collector to add a new job.
146 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
161 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
162 + - **Test** runs the job with the provided settings and shows whether data can be collected.
163 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
164
165
166 #### via File
@@ -157,7 +174,7 @@ update_every: 1
174 autodetection_retry: 0
175 jobs:
176 - name: some_name1
160 - - name: some_name1
177 + - name: some_name2
178 ```
179 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
180 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/k8s_kubelet/integrations/kubelet.md
+21 -4
@@ -113,6 +113,21 @@ The following alerts are available:
113
114 ## Setup
115
116 +
117 +You can configure the **k8s_kubelet** collector in two ways:
118 +
119 +| Method | Best for | How to |
120 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
121 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **k8s_kubelet**, then click **+** to add a job. |
122 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/k8s_kubelet.conf` and add a job. |
123 +
124 +:::important
125 +
126 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
127 +
128 +:::
129 +
130 +
131 ### Prerequisites
132
133 No action required.
@@ -151,14 +166,16 @@ The following options can be defined globally: update_every, autodetection_retry
166
167 #### via UI
168
154 -The **k8s_kubelet** collector can be configured directly through the Netdata web interface:
169 +Configure the **k8s_kubelet** collector from the Netdata web interface:
170
171 1. Go to **Nodes**.
157 -2. Select the node **where you want the k8s_kubelet data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
172 +2. Select the node **where you want the k8s_kubelet data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
173 3. The **Collectors → Jobs** view opens by default.
174 4. In the Search box, type _k8s_kubelet_ (or scroll the list) to locate the **k8s_kubelet** collector.
175 5. Click the **+** next to the **k8s_kubelet** collector to add a new job.
161 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
176 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
177 + - **Test** runs the job with the provided settings and shows whether data can be collected.
178 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
179
180
181 #### via File
@@ -172,7 +189,7 @@ update_every: 1
189 autodetection_retry: 0
190 jobs:
191 - name: some_name1
175 - - name: some_name1
192 + - name: some_name2
193 ```
194 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
195 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/k8s_kubeproxy/integrations/kubeproxy.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **k8s_kubeproxy** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **k8s_kubeproxy**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/k8s_kubeproxy.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 No action required.
@@ -118,14 +133,16 @@ The following options can be defined globally: update_every, autodetection_retry
133
134 #### via UI
135
121 -The **k8s_kubeproxy** collector can be configured directly through the Netdata web interface:
136 +Configure the **k8s_kubeproxy** collector from the Netdata web interface:
137
138 1. Go to **Nodes**.
124 -2. Select the node **where you want the k8s_kubeproxy data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
139 +2. Select the node **where you want the k8s_kubeproxy data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
140 3. The **Collectors → Jobs** view opens by default.
141 4. In the Search box, type _k8s_kubeproxy_ (or scroll the list) to locate the **k8s_kubeproxy** collector.
142 5. Click the **+** next to the **k8s_kubeproxy** collector to add a new job.
128 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
143 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
144 + - **Test** runs the job with the provided settings and shows whether data can be collected.
145 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
146
147
148 #### via File
@@ -139,7 +156,7 @@ update_every: 1
156 autodetection_retry: 0
157 jobs:
158 - name: some_name1
142 - - name: some_name1
159 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
162 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/k8s_state/integrations/kubernetes_cluster_state.md
+21 -4
@@ -214,6 +214,21 @@ The following alerts are available:
214
215 ## Setup
216
217 +
218 +You can configure the **k8s_state** collector in two ways:
219 +
220 +| Method | Best for | How to |
221 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
222 +| [**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. |
223 +| [**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. |
224 +
225 +:::important
226 +
227 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
228 +
229 +:::
230 +
231 +
232 ### Prerequisites
233
234 No action required.
@@ -229,14 +244,16 @@ There are no configuration options.
244
245 #### via UI
246
232 -The **k8s_state** collector can be configured directly through the Netdata web interface:
247 +Configure the **k8s_state** collector from the Netdata web interface:
248
249 1. Go to **Nodes**.
235 -2. Select the node **where you want the k8s_state data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
250 +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.
251 3. The **Collectors → Jobs** view opens by default.
252 4. In the Search box, type _k8s_state_ (or scroll the list) to locate the **k8s_state** collector.
253 5. Click the **+** next to the **k8s_state** collector to add a new job.
239 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
254 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
255 + - **Test** runs the job with the provided settings and shows whether data can be collected.
256 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
257
258
259 #### via File
@@ -250,7 +267,7 @@ update_every: 1
267 autodetection_retry: 0
268 jobs:
269 - name: some_name1
253 - - name: some_name1
270 + - name: some_name2
271 ```
272 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
273 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/lighttpd/integrations/lighttpd.md
+21 -4
@@ -86,6 +86,21 @@ There are no alerts configured by default for this integration.
86
87 ## Setup
88
89 +
90 +You can configure the **lighttpd** collector in two ways:
91 +
92 +| Method | Best for | How to |
93 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
94 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **lighttpd**, then click **+** to add a job. |
95 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/lighttpd.conf` and add a job. |
96 +
97 +:::important
98 +
99 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
100 +
101 +:::
102 +
103 +
104 ### Prerequisites
105
106 #### Enable Lighttpd status support
@@ -128,14 +143,16 @@ The following options can be defined globally: update_every, autodetection_retry
143
144 #### via UI
145
131 -The **lighttpd** collector can be configured directly through the Netdata web interface:
146 +Configure the **lighttpd** collector from the Netdata web interface:
147
148 1. Go to **Nodes**.
134 -2. Select the node **where you want the lighttpd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
149 +2. Select the node **where you want the lighttpd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
150 3. The **Collectors → Jobs** view opens by default.
151 4. In the Search box, type _lighttpd_ (or scroll the list) to locate the **lighttpd** collector.
152 5. Click the **+** next to the **lighttpd** collector to add a new job.
138 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
153 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
154 + - **Test** runs the job with the provided settings and shows whether data can be collected.
155 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
156
157
158 #### via File
@@ -149,7 +166,7 @@ update_every: 1
166 autodetection_retry: 0
167 jobs:
168 - name: some_name1
152 - - name: some_name1
169 + - name: some_name2
170 ```
171 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
172 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/litespeed/integrations/litespeed.md
+21 -4
@@ -85,6 +85,21 @@ There are no alerts configured by default for this integration.
85
86 ## Setup
87
88 +
89 +You can configure the **litespeed** collector in two ways:
90 +
91 +| Method | Best for | How to |
92 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
93 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **litespeed**, then click **+** to add a job. |
94 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/litespeed.conf` and add a job. |
95 +
96 +:::important
97 +
98 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
99 +
100 +:::
101 +
102 +
103 ### Prerequisites
104
105 No action required.
@@ -109,14 +124,16 @@ The following options can be defined globally: update_every, autodetection_retry
124
125 #### via UI
126
112 -The **litespeed** collector can be configured directly through the Netdata web interface:
127 +Configure the **litespeed** collector from the Netdata web interface:
128
129 1. Go to **Nodes**.
115 -2. Select the node **where you want the litespeed data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
130 +2. Select the node **where you want the litespeed data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
131 3. The **Collectors → Jobs** view opens by default.
132 4. In the Search box, type _litespeed_ (or scroll the list) to locate the **litespeed** collector.
133 5. Click the **+** next to the **litespeed** collector to add a new job.
119 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
134 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
135 + - **Test** runs the job with the provided settings and shows whether data can be collected.
136 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
137
138
139 #### via File
@@ -130,7 +147,7 @@ update_every: 1
147 autodetection_retry: 0
148 jobs:
149 - name: some_name1
133 - - name: some_name1
150 + - name: some_name2
151 ```
152 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
153 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/logind/integrations/systemd-logind_users.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **logind** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **logind**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/logind.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 No action required.
@@ -94,14 +109,16 @@ The following options can be defined globally: update_every, autodetection_retry
109
110 #### via UI
111
97 -The **logind** collector can be configured directly through the Netdata web interface:
112 +Configure the **logind** collector from the Netdata web interface:
113
114 1. Go to **Nodes**.
100 -2. Select the node **where you want the logind data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
115 +2. Select the node **where you want the logind data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
116 3. The **Collectors → Jobs** view opens by default.
117 4. In the Search box, type _logind_ (or scroll the list) to locate the **logind** collector.
118 5. Click the **+** next to the **logind** collector to add a new job.
104 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
119 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
120 + - **Test** runs the job with the provided settings and shows whether data can be collected.
121 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
122
123
124 #### via File
@@ -115,7 +132,7 @@ update_every: 1
132 autodetection_retry: 0
133 jobs:
134 - name: some_name1
118 - - name: some_name1
135 + - name: some_name2
136 ```
137 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
138 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/logstash/integrations/logstash.md
+21 -4
@@ -103,6 +103,21 @@ There are no alerts configured by default for this integration.
103
104 ## Setup
105
106 +
107 +You can configure the **logstash** collector in two ways:
108 +
109 +| Method | Best for | How to |
110 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
111 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **logstash**, then click **+** to add a job. |
112 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/logstatsh.conf` and add a job. |
113 +
114 +:::important
115 +
116 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
117 +
118 +:::
119 +
120 +
121 ### Prerequisites
122
123 No action required.
@@ -141,14 +156,16 @@ The following options can be defined globally: update_every, autodetection_retry
156
157 #### via UI
158
144 -The **logstash** collector can be configured directly through the Netdata web interface:
159 +Configure the **logstash** collector from the Netdata web interface:
160
161 1. Go to **Nodes**.
147 -2. Select the node **where you want the logstash data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
162 +2. Select the node **where you want the logstash data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
163 3. The **Collectors → Jobs** view opens by default.
164 4. In the Search box, type _logstash_ (or scroll the list) to locate the **logstash** collector.
165 5. Click the **+** next to the **logstash** collector to add a new job.
151 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
166 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
167 + - **Test** runs the job with the provided settings and shows whether data can be collected.
168 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
169
170
171 #### via File
@@ -162,7 +179,7 @@ update_every: 1
179 autodetection_retry: 0
180 jobs:
181 - name: some_name1
165 - - name: some_name1
182 + - name: some_name2
183 ```
184 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
185 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/lvm/integrations/lvm_logical_volumes.md
+21 -4
@@ -91,6 +91,21 @@ The following alerts are available:
91
92 ## Setup
93
94 +
95 +You can configure the **lvm** collector in two ways:
96 +
97 +| Method | Best for | How to |
98 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
99 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **lvm**, then click **+** to add a job. |
100 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/lvm.conf` and add a job. |
101 +
102 +:::important
103 +
104 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
105 +
106 +:::
107 +
108 +
109 ### Prerequisites
110
111 No action required.
@@ -114,14 +129,16 @@ The following options can be defined globally: update_every.
129
130 #### via UI
131
117 -The **lvm** collector can be configured directly through the Netdata web interface:
132 +Configure the **lvm** collector from the Netdata web interface:
133
134 1. Go to **Nodes**.
120 -2. Select the node **where you want the lvm data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
135 +2. Select the node **where you want the lvm data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
136 3. The **Collectors → Jobs** view opens by default.
137 4. In the Search box, type _lvm_ (or scroll the list) to locate the **lvm** collector.
138 5. Click the **+** next to the **lvm** collector to add a new job.
124 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
139 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
140 + - **Test** runs the job with the provided settings and shows whether data can be collected.
141 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
142
143
144 #### via File
@@ -135,7 +152,7 @@ update_every: 1
152 autodetection_retry: 0
153 jobs:
154 - name: some_name1
138 - - name: some_name1
155 + - name: some_name2
156 ```
157 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
158 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/maxscale/integrations/maxscale.md
+21 -4
@@ -108,6 +108,21 @@ There are no alerts configured by default for this integration.
108
109 ## Setup
110
111 +
112 +You can configure the **maxscale** collector in two ways:
113 +
114 +| Method | Best for | How to |
115 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
116 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **maxscale**, then click **+** to add a job. |
117 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/maxscale.conf` and add a job. |
118 +
119 +:::important
120 +
121 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
122 +
123 +:::
124 +
125 +
126 ### Prerequisites
127
128 No action required.
@@ -146,14 +161,16 @@ The following options can be defined globally: update_every, autodetection_retry
161
162 #### via UI
163
149 -The **maxscale** collector can be configured directly through the Netdata web interface:
164 +Configure the **maxscale** collector from the Netdata web interface:
165
166 1. Go to **Nodes**.
152 -2. Select the node **where you want the maxscale data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
167 +2. Select the node **where you want the maxscale data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
168 3. The **Collectors → Jobs** view opens by default.
169 4. In the Search box, type _maxscale_ (or scroll the list) to locate the **maxscale** collector.
170 5. Click the **+** next to the **maxscale** collector to add a new job.
156 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
171 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
172 + - **Test** runs the job with the provided settings and shows whether data can be collected.
173 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
174
175
176 #### via File
@@ -167,7 +184,7 @@ update_every: 1
184 autodetection_retry: 0
185 jobs:
186 - name: some_name1
170 - - name: some_name1
187 + - name: some_name2
188 ```
189 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
190 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/megacli/integrations/megacli_megaraid.md
+21 -4
@@ -139,6 +139,21 @@ The following alerts are available:
139
140 ## Setup
141
142 +
143 +You can configure the **megacli** collector in two ways:
144 +
145 +| Method | Best for | How to |
146 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
147 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **megacli**, then click **+** to add a job. |
148 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/megacli.conf` and add a job. |
149 +
150 +:::important
151 +
152 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
153 +
154 +:::
155 +
156 +
157 ### Prerequisites
158
159 No action required.
@@ -162,14 +177,16 @@ The following options can be defined globally: update_every.
177
178 #### via UI
179
165 -The **megacli** collector can be configured directly through the Netdata web interface:
180 +Configure the **megacli** collector from the Netdata web interface:
181
182 1. Go to **Nodes**.
168 -2. Select the node **where you want the megacli data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
183 +2. Select the node **where you want the megacli data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
184 3. The **Collectors → Jobs** view opens by default.
185 4. In the Search box, type _megacli_ (or scroll the list) to locate the **megacli** collector.
186 5. Click the **+** next to the **megacli** collector to add a new job.
172 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
187 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
188 + - **Test** runs the job with the provided settings and shows whether data can be collected.
189 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
190
191
192 #### via File
@@ -183,7 +200,7 @@ update_every: 1
200 autodetection_retry: 0
201 jobs:
202 - name: some_name1
186 - - name: some_name1
203 + - name: some_name2
204 ```
205 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
206 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/memcached/integrations/memcached.md
+21 -4
@@ -95,6 +95,21 @@ The following alerts are available:
95
96 ## Setup
97
98 +
99 +You can configure the **memcached** collector in two ways:
100 +
101 +| Method | Best for | How to |
102 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
103 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **memcached**, then click **+** to add a job. |
104 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/memcached.conf` and add a job. |
105 +
106 +:::important
107 +
108 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
109 +
110 +:::
111 +
112 +
113 ### Prerequisites
114
115 #### UNIX socket access
@@ -133,14 +148,16 @@ The following options can be defined globally: update_every, autodetection_retry
148
149 #### via UI
150
136 -The **memcached** collector can be configured directly through the Netdata web interface:
151 +Configure the **memcached** collector from the Netdata web interface:
152
153 1. Go to **Nodes**.
139 -2. Select the node **where you want the memcached data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
154 +2. Select the node **where you want the memcached data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
155 3. The **Collectors → Jobs** view opens by default.
156 4. In the Search box, type _memcached_ (or scroll the list) to locate the **memcached** collector.
157 5. Click the **+** next to the **memcached** collector to add a new job.
143 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
158 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
159 + - **Test** runs the job with the provided settings and shows whether data can be collected.
160 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
161
162
163 #### via File
@@ -154,7 +171,7 @@ update_every: 1
171 autodetection_retry: 0
172 jobs:
173 - name: some_name1
157 - - name: some_name1
174 + - name: some_name2
175 ```
176 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
177 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/mongodb/integrations/mongodb.md
+21 -4
@@ -212,6 +212,21 @@ There are no alerts configured by default for this integration.
212
213 ## Setup
214
215 +
216 +You can configure the **mongodb** collector in two ways:
217 +
218 +| Method | Best for | How to |
219 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
220 +| [**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. |
221 +| [**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. |
222 +
223 +:::important
224 +
225 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
226 +
227 +:::
228 +
229 +
230 ### Prerequisites
231
232 #### Create a read-only user
@@ -263,14 +278,16 @@ The following options can be defined globally: update_every, autodetection_retry
278
279 #### via UI
280
266 -The **mongodb** collector can be configured directly through the Netdata web interface:
281 +Configure the **mongodb** collector from the Netdata web interface:
282
283 1. Go to **Nodes**.
269 -2. Select the node **where you want the mongodb data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
284 +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.
285 3. The **Collectors → Jobs** view opens by default.
286 4. In the Search box, type _mongodb_ (or scroll the list) to locate the **mongodb** collector.
287 5. Click the **+** next to the **mongodb** collector to add a new job.
273 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
288 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
289 + - **Test** runs the job with the provided settings and shows whether data can be collected.
290 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
291
292
293 #### via File
@@ -284,7 +301,7 @@ update_every: 1
301 autodetection_retry: 0
302 jobs:
303 - name: some_name1
287 - - name: some_name1
304 + - name: some_name2
305 ```
306 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
307 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/monit/integrations/monit.md
+21 -4
@@ -86,6 +86,21 @@ There are no alerts configured by default for this integration.
86
87 ## Setup
88
89 +
90 +You can configure the **monit** collector in two ways:
91 +
92 +| Method | Best for | How to |
93 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
94 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **monit**, then click **+** to add a job. |
95 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/monit.conf` and add a job. |
96 +
97 +:::important
98 +
99 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
100 +
101 +:::
102 +
103 +
104 ### Prerequisites
105
106 #### Enable TCP PORT
@@ -127,14 +142,16 @@ The following options can be defined globally: update_every, autodetection_retry
142
143 #### via UI
144
130 -The **monit** collector can be configured directly through the Netdata web interface:
145 +Configure the **monit** collector from the Netdata web interface:
146
147 1. Go to **Nodes**.
133 -2. Select the node **where you want the monit data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
148 +2. Select the node **where you want the monit data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
149 3. The **Collectors → Jobs** view opens by default.
150 4. In the Search box, type _monit_ (or scroll the list) to locate the **monit** collector.
151 5. Click the **+** next to the **monit** collector to add a new job.
137 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
152 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
153 + - **Test** runs the job with the provided settings and shows whether data can be collected.
154 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
155
156
157 #### via File
@@ -148,7 +165,7 @@ update_every: 1
165 autodetection_retry: 0
166 jobs:
167 - name: some_name1
151 - - name: some_name1
168 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
171 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/mysql/integrations/mariadb.md
+21 -4
@@ -202,6 +202,21 @@ The following alerts are available:
202
203 ## Setup
204
205 +
206 +You can configure the **mysql** collector in two ways:
207 +
208 +| Method | Best for | How to |
209 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
210 +| [**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. |
211 +| [**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. |
212 +
213 +:::important
214 +
215 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
216 +
217 +:::
218 +
219 +
220 ### Prerequisites
221
222 #### Create netdata user
@@ -259,14 +274,16 @@ The following options can be defined globally: update_every, autodetection_retry
274
275 #### via UI
276
262 -The **mysql** collector can be configured directly through the Netdata web interface:
277 +Configure the **mysql** collector from the Netdata web interface:
278
279 1. Go to **Nodes**.
265 -2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
280 +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.
281 3. The **Collectors → Jobs** view opens by default.
282 4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
283 5. Click the **+** next to the **mysql** collector to add a new job.
269 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
284 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
285 + - **Test** runs the job with the provided settings and shows whether data can be collected.
286 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
287
288
289 #### via File
@@ -280,7 +297,7 @@ update_every: 1
297 autodetection_retry: 0
298 jobs:
299 - name: some_name1
283 - - name: some_name1
300 + - name: some_name2
301 ```
302 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
303 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/mysql/integrations/mysql.md
+21 -4
@@ -202,6 +202,21 @@ The following alerts are available:
202
203 ## Setup
204
205 +
206 +You can configure the **mysql** collector in two ways:
207 +
208 +| Method | Best for | How to |
209 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
210 +| [**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. |
211 +| [**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. |
212 +
213 +:::important
214 +
215 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
216 +
217 +:::
218 +
219 +
220 ### Prerequisites
221
222 #### Create netdata user
@@ -259,14 +274,16 @@ The following options can be defined globally: update_every, autodetection_retry
274
275 #### via UI
276
262 -The **mysql** collector can be configured directly through the Netdata web interface:
277 +Configure the **mysql** collector from the Netdata web interface:
278
279 1. Go to **Nodes**.
265 -2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
280 +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.
281 3. The **Collectors → Jobs** view opens by default.
282 4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
283 5. Click the **+** next to the **mysql** collector to add a new job.
269 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
284 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
285 + - **Test** runs the job with the provided settings and shows whether data can be collected.
286 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
287
288
289 #### via File
@@ -280,7 +297,7 @@ update_every: 1
297 autodetection_retry: 0
298 jobs:
299 - name: some_name1
283 - - name: some_name1
300 + - name: some_name2
301 ```
302 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
303 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/mysql/integrations/percona_mysql.md
+21 -4
@@ -202,6 +202,21 @@ The following alerts are available:
202
203 ## Setup
204
205 +
206 +You can configure the **mysql** collector in two ways:
207 +
208 +| Method | Best for | How to |
209 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
210 +| [**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. |
211 +| [**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. |
212 +
213 +:::important
214 +
215 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
216 +
217 +:::
218 +
219 +
220 ### Prerequisites
221
222 #### Create netdata user
@@ -259,14 +274,16 @@ The following options can be defined globally: update_every, autodetection_retry
274
275 #### via UI
276
262 -The **mysql** collector can be configured directly through the Netdata web interface:
277 +Configure the **mysql** collector from the Netdata web interface:
278
279 1. Go to **Nodes**.
265 -2. Select the node **where you want the mysql data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
280 +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.
281 3. The **Collectors → Jobs** view opens by default.
282 4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
283 5. Click the **+** next to the **mysql** collector to add a new job.
269 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
284 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
285 + - **Test** runs the job with the provided settings and shows whether data can be collected.
286 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
287
288
289 #### via File
@@ -280,7 +297,7 @@ update_every: 1
297 autodetection_retry: 0
298 jobs:
299 - name: some_name1
283 - - name: some_name1
300 + - name: some_name2
301 ```
302 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
303 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nats/integrations/nats.md
+21 -4
@@ -241,6 +241,21 @@ There are no alerts configured by default for this integration.
241
242 ## Setup
243
244 +
245 +You can configure the **nats** collector in two ways:
246 +
247 +| Method | Best for | How to |
248 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
249 +| [**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. |
250 +| [**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. |
251 +
252 +:::important
253 +
254 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
255 +
256 +:::
257 +
258 +
259 ### Prerequisites
260
261 #### Enable NATS monitoring
@@ -284,14 +299,16 @@ The following options can be defined globally: update_every, autodetection_retry
299
300 #### via UI
301
287 -The **nats** collector can be configured directly through the Netdata web interface:
302 +Configure the **nats** collector from the Netdata web interface:
303
304 1. Go to **Nodes**.
290 -2. Select the node **where you want the nats data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
305 +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.
306 3. The **Collectors → Jobs** view opens by default.
307 4. In the Search box, type _nats_ (or scroll the list) to locate the **nats** collector.
308 5. Click the **+** next to the **nats** collector to add a new job.
294 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
309 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
310 + - **Test** runs the job with the provided settings and shows whether data can be collected.
311 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
312
313
314 #### via File
@@ -305,7 +322,7 @@ update_every: 1
322 autodetection_retry: 0
323 jobs:
324 - name: some_name1
308 - - name: some_name1
325 + - name: some_name2
326 ```
327 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
328 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nginx/integrations/nginx.md
+21 -4
@@ -87,6 +87,21 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 +You can configure the **nginx** 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 **nginx**, 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/nginx.conf` and add a job. |
97 +
98 +:::important
99 +
100 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
101 +
102 +:::
103 +
104 +
105 ### Prerequisites
106
107 #### Enable status support
@@ -167,14 +182,16 @@ The following options can be defined globally: update_every, autodetection_retry
182
183 #### via UI
184
170 -The **nginx** collector can be configured directly through the Netdata web interface:
185 +Configure the **nginx** collector from the Netdata web interface:
186
187 1. Go to **Nodes**.
173 -2. Select the node **where you want the nginx data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
188 +2. Select the node **where you want the nginx data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
189 3. The **Collectors → Jobs** view opens by default.
190 4. In the Search box, type _nginx_ (or scroll the list) to locate the **nginx** collector.
191 5. Click the **+** next to the **nginx** collector to add a new job.
177 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
192 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
193 + - **Test** runs the job with the provided settings and shows whether data can be collected.
194 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
195
196
197 #### via File
@@ -188,7 +205,7 @@ update_every: 1
205 autodetection_retry: 0
206 jobs:
207 - name: some_name1
191 - - name: some_name1
208 + - name: some_name2
209 ```
210 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
211 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nginxplus/integrations/nginx_plus.md
+21 -4
@@ -264,6 +264,21 @@ There are no alerts configured by default for this integration.
264
265 ## Setup
266
267 +
268 +You can configure the **nginxplus** collector in two ways:
269 +
270 +| Method | Best for | How to |
271 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
272 +| [**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. |
273 +| [**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. |
274 +
275 +:::important
276 +
277 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
278 +
279 +:::
280 +
281 +
282 ### Prerequisites
283
284 #### Config API
@@ -306,14 +321,16 @@ The following options can be defined globally: update_every, autodetection_retry
321
322 #### via UI
323
309 -The **nginxplus** collector can be configured directly through the Netdata web interface:
324 +Configure the **nginxplus** collector from the Netdata web interface:
325
326 1. Go to **Nodes**.
312 -2. Select the node **where you want the nginxplus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
327 +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.
328 3. The **Collectors → Jobs** view opens by default.
329 4. In the Search box, type _nginxplus_ (or scroll the list) to locate the **nginxplus** collector.
330 5. Click the **+** next to the **nginxplus** collector to add a new job.
316 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
331 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
332 + - **Test** runs the job with the provided settings and shows whether data can be collected.
333 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
334
335
336 #### via File
@@ -327,7 +344,7 @@ update_every: 1
344 autodetection_retry: 0
345 jobs:
346 - name: some_name1
330 - - name: some_name1
347 + - name: some_name2
348 ```
349 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
350 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nginxunit/integrations/nginx_unit.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **nginxunit** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nginxunit**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nginxunit.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 #### Enable HTTP Control API
@@ -124,14 +139,16 @@ The following options can be defined globally: update_every, autodetection_retry
139
140 #### via UI
141
127 -The **nginxunit** collector can be configured directly through the Netdata web interface:
142 +Configure the **nginxunit** collector from the Netdata web interface:
143
144 1. Go to **Nodes**.
130 -2. Select the node **where you want the nginxunit data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
145 +2. Select the node **where you want the nginxunit data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
146 3. The **Collectors → Jobs** view opens by default.
147 4. In the Search box, type _nginxunit_ (or scroll the list) to locate the **nginxunit** collector.
148 5. Click the **+** next to the **nginxunit** collector to add a new job.
134 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
149 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
150 + - **Test** runs the job with the provided settings and shows whether data can be collected.
151 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
152
153
154 #### via File
@@ -145,7 +162,7 @@ update_every: 1
162 autodetection_retry: 0
163 jobs:
164 - name: some_name1
148 - - name: some_name1
165 + - name: some_name2
166 ```
167 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
168 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nginxvts/integrations/nginx_vts.md
+21 -4
@@ -87,6 +87,21 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 +You can configure the **nginxvts** 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 **nginxvts**, 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/nginxvts.conf` and add a job. |
97 +
98 +:::important
99 +
100 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
101 +
102 +:::
103 +
104 +
105 ### Prerequisites
106
107 #### Configure nginx-vts module
@@ -129,14 +144,16 @@ The following options can be defined globally: update_every, autodetection_retry
144
145 #### via UI
146
132 -The **nginxvts** collector can be configured directly through the Netdata web interface:
147 +Configure the **nginxvts** collector from the Netdata web interface:
148
149 1. Go to **Nodes**.
135 -2. Select the node **where you want the nginxvts data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
150 +2. Select the node **where you want the nginxvts data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
151 3. The **Collectors → Jobs** view opens by default.
152 4. In the Search box, type _nginxvts_ (or scroll the list) to locate the **nginxvts** collector.
153 5. Click the **+** next to the **nginxvts** collector to add a new job.
139 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
154 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
155 + - **Test** runs the job with the provided settings and shows whether data can be collected.
156 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
157
158
159 #### via File
@@ -150,7 +167,7 @@ update_every: 1
167 autodetection_retry: 0
168 jobs:
169 - name: some_name1
153 - - name: some_name1
170 + - name: some_name2
171 ```
172 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
173 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nsd/integrations/nsd.md
+21 -4
@@ -93,6 +93,21 @@ There are no alerts configured by default for this integration.
93
94 ## Setup
95
96 +
97 +You can configure the **nsd** collector in two ways:
98 +
99 +| Method | Best for | How to |
100 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
101 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nsd**, then click **+** to add a job. |
102 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nsd.conf` and add a job. |
103 +
104 +:::important
105 +
106 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
107 +
108 +:::
109 +
110 +
111 ### Prerequisites
112
113 No action required.
@@ -116,14 +131,16 @@ The following options can be defined globally: update_every.
131
132 #### via UI
133
119 -The **nsd** collector can be configured directly through the Netdata web interface:
134 +Configure the **nsd** collector from the Netdata web interface:
135
136 1. Go to **Nodes**.
122 -2. Select the node **where you want the nsd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
137 +2. Select the node **where you want the nsd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
138 3. The **Collectors → Jobs** view opens by default.
139 4. In the Search box, type _nsd_ (or scroll the list) to locate the **nsd** collector.
140 5. Click the **+** next to the **nsd** collector to add a new job.
126 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
141 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
142 + - **Test** runs the job with the provided settings and shows whether data can be collected.
143 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
144
145
146 #### via File
@@ -137,7 +154,7 @@ update_every: 1
154 autodetection_retry: 0
155 jobs:
156 - name: some_name1
140 - - name: some_name1
157 + - name: some_name2
158 ```
159 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
160 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/ntpd/integrations/ntpd.md
+21 -4
@@ -111,6 +111,21 @@ There are no alerts configured by default for this integration.
111
112 ## Setup
113
114 +
115 +You can configure the **ntpd** collector in two ways:
116 +
117 +| Method | Best for | How to |
118 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
119 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **ntpd**, then click **+** to add a job. |
120 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ntpd.conf` and add a job. |
121 +
122 +:::important
123 +
124 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
125 +
126 +:::
127 +
128 +
129 ### Prerequisites
130
131 No action required.
@@ -137,14 +152,16 @@ The following options can be defined globally: update_every, autodetection_retry
152
153 #### via UI
154
140 -The **ntpd** collector can be configured directly through the Netdata web interface:
155 +Configure the **ntpd** collector from the Netdata web interface:
156
157 1. Go to **Nodes**.
143 -2. Select the node **where you want the ntpd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
158 +2. Select the node **where you want the ntpd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
159 3. The **Collectors → Jobs** view opens by default.
160 4. In the Search box, type _ntpd_ (or scroll the list) to locate the **ntpd** collector.
161 5. Click the **+** next to the **ntpd** collector to add a new job.
147 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
162 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
163 + - **Test** runs the job with the provided settings and shows whether data can be collected.
164 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
165
166
167 #### via File
@@ -158,7 +175,7 @@ update_every: 1
175 autodetection_retry: 0
176 jobs:
177 - name: some_name1
161 - - name: some_name1
178 + - name: some_name2
179 ```
180 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
181 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nvidia_smi/integrations/nvidia_gpu.md
+21 -4
@@ -116,6 +116,21 @@ There are no alerts configured by default for this integration.
116
117 ## Setup
118
119 +
120 +You can configure the **nvidia_smi** collector in two ways:
121 +
122 +| Method | Best for | How to |
123 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
124 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nvidia_smi**, then click **+** to add a job. |
125 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nvidia_smi.conf` and add a job. |
126 +
127 +:::important
128 +
129 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
130 +
131 +:::
132 +
133 +
134 ### Prerequisites
135
136 No action required.
@@ -142,14 +157,16 @@ The following options can be defined globally: update_every, autodetection_retry
157
158 #### via UI
159
145 -The **nvidia_smi** collector can be configured directly through the Netdata web interface:
160 +Configure the **nvidia_smi** collector from the Netdata web interface:
161
162 1. Go to **Nodes**.
148 -2. Select the node **where you want the nvidia_smi data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
163 +2. Select the node **where you want the nvidia_smi data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
164 3. The **Collectors → Jobs** view opens by default.
165 4. In the Search box, type _nvidia_smi_ (or scroll the list) to locate the **nvidia_smi** collector.
166 5. Click the **+** next to the **nvidia_smi** collector to add a new job.
152 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
167 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
168 + - **Test** runs the job with the provided settings and shows whether data can be collected.
169 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
170
171
172 #### via File
@@ -163,7 +180,7 @@ update_every: 1
180 autodetection_retry: 0
181 jobs:
182 - name: some_name1
166 - - name: some_name1
183 + - name: some_name2
184 ```
185 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
186 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/nvme/integrations/nvme_devices.md
+21 -4
@@ -103,6 +103,21 @@ The following alerts are available:
103
104 ## Setup
105
106 +
107 +You can configure the **nvme** collector in two ways:
108 +
109 +| Method | Best for | How to |
110 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
111 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **nvme**, then click **+** to add a job. |
112 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/nvme.conf` and add a job. |
113 +
114 +:::important
115 +
116 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
117 +
118 +:::
119 +
120 +
121 ### Prerequisites
122
123 #### Install nvme-cli
@@ -155,14 +170,16 @@ The following options can be defined globally: update_every, autodetection_retry
170
171 #### via UI
172
158 -The **nvme** collector can be configured directly through the Netdata web interface:
173 +Configure the **nvme** collector from the Netdata web interface:
174
175 1. Go to **Nodes**.
161 -2. Select the node **where you want the nvme data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
176 +2. Select the node **where you want the nvme data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
177 3. The **Collectors → Jobs** view opens by default.
178 4. In the Search box, type _nvme_ (or scroll the list) to locate the **nvme** collector.
179 5. Click the **+** next to the **nvme** collector to add a new job.
165 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
180 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
181 + - **Test** runs the job with the provided settings and shows whether data can be collected.
182 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
183
184
185 #### via File
@@ -176,7 +193,7 @@ update_every: 1
193 autodetection_retry: 0
194 jobs:
195 - name: some_name1
179 - - name: some_name1
196 + - name: some_name2
197 ```
198 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
199 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/openldap/integrations/openldap.md
+21 -4
@@ -85,6 +85,21 @@ There are no alerts configured by default for this integration.
85
86 ## Setup
87
88 +
89 +You can configure the **openldap** collector in two ways:
90 +
91 +| Method | Best for | How to |
92 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
93 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **openldap**, then click **+** to add a job. |
94 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/openldap.conf` and add a job. |
95 +
96 +:::important
97 +
98 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
99 +
100 +:::
101 +
102 +
103 ### Prerequisites
104
105 #### Enable the openLDAP Monitor Backend.
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every.
134
135 #### via UI
136
122 -The **openldap** collector can be configured directly through the Netdata web interface:
137 +Configure the **openldap** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the openldap data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the openldap data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _openldap_ (or scroll the list) to locate the **openldap** collector.
143 5. Click the **+** next to the **openldap** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/openvpn/integrations/openvpn.md
+21 -4
@@ -95,6 +95,21 @@ There are no alerts configured by default for this integration.
95
96 ## Setup
97
98 +
99 +You can configure the **openvpn** collector in two ways:
100 +
101 +| Method | Best for | How to |
102 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
103 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **openvpn**, then click **+** to add a job. |
104 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/openvpn.conf` and add a job. |
105 +
106 +:::important
107 +
108 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
109 +
110 +:::
111 +
112 +
113 ### Prerequisites
114
115 #### Enable in go.d.conf.
@@ -130,14 +145,16 @@ The following options can be defined globally: update_every, autodetection_retry
145
146 #### via UI
147
133 -The **openvpn** collector can be configured directly through the Netdata web interface:
148 +Configure the **openvpn** collector from the Netdata web interface:
149
150 1. Go to **Nodes**.
136 -2. Select the node **where you want the openvpn data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
151 +2. Select the node **where you want the openvpn data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
152 3. The **Collectors → Jobs** view opens by default.
153 4. In the Search box, type _openvpn_ (or scroll the list) to locate the **openvpn** collector.
154 5. Click the **+** next to the **openvpn** collector to add a new job.
140 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
155 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
156 + - **Test** runs the job with the provided settings and shows whether data can be collected.
157 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
158
159
160 #### via File
@@ -151,7 +168,7 @@ update_every: 1
168 autodetection_retry: 0
169 jobs:
170 - name: some_name1
154 - - name: some_name1
171 + - name: some_name2
172 ```
173 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
174 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/openvpn_status_log/integrations/openvpn_status_log.md
+21 -4
@@ -95,6 +95,21 @@ There are no alerts configured by default for this integration.
95
96 ## Setup
97
98 +
99 +You can configure the **openvpn_status_log** collector in two ways:
100 +
101 +| Method | Best for | How to |
102 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
103 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **openvpn_status_log**, then click **+** to add a job. |
104 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/openvpn_status_log.conf` and add a job. |
105 +
106 +:::important
107 +
108 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
109 +
110 +:::
111 +
112 +
113 ### Prerequisites
114
115 No action required.
@@ -120,14 +135,16 @@ The following options can be defined globally: update_every, autodetection_retry
135
136 #### via UI
137
123 -The **openvpn_status_log** collector can be configured directly through the Netdata web interface:
138 +Configure the **openvpn_status_log** collector from the Netdata web interface:
139
140 1. Go to **Nodes**.
126 -2. Select the node **where you want the openvpn_status_log data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
141 +2. Select the node **where you want the openvpn_status_log 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 _openvpn_status_log_ (or scroll the list) to locate the **openvpn_status_log** collector.
144 5. Click the **+** next to the **openvpn_status_log** collector to add a new job.
130 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -141,7 +158,7 @@ update_every: 1
158 autodetection_retry: 0
159 jobs:
160 - name: some_name1
144 - - 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-a-configuration-file-using-edit-config) script from the
164 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/oracledb/integrations/oracle_db.md
+21 -4
@@ -141,6 +141,21 @@ There are no alerts configured by default for this integration.
141
142 ## Setup
143
144 +
145 +You can configure the **oracledb** collector in two ways:
146 +
147 +| Method | Best for | How to |
148 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
149 +| [**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. |
150 +| [**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. |
151 +
152 +:::important
153 +
154 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
155 +
156 +:::
157 +
158 +
159 ### Prerequisites
160
161 #### Create a read only user for netdata
@@ -179,14 +194,16 @@ The following options can be defined globally: update_every, autodetection_retry
194
195 #### via UI
196
182 -The **oracledb** collector can be configured directly through the Netdata web interface:
197 +Configure the **oracledb** collector from the Netdata web interface:
198
199 1. Go to **Nodes**.
185 -2. Select the node **where you want the oracledb data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
200 +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.
201 3. The **Collectors → Jobs** view opens by default.
202 4. In the Search box, type _oracledb_ (or scroll the list) to locate the **oracledb** collector.
203 5. Click the **+** next to the **oracledb** collector to add a new job.
189 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
204 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
205 + - **Test** runs the job with the provided settings and shows whether data can be collected.
206 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
207
208
209 #### via File
@@ -200,7 +217,7 @@ update_every: 1
217 autodetection_retry: 0
218 jobs:
219 - name: some_name1
203 - - name: some_name1
220 + - name: some_name2
221 ```
222 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
223 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/pgbouncer/integrations/pgbouncer.md
+21 -4
@@ -113,6 +113,21 @@ There are no alerts configured by default for this integration.
113
114 ## Setup
115
116 +
117 +You can configure the **pgbouncer** collector in two ways:
118 +
119 +| Method | Best for | How to |
120 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
121 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **pgbouncer**, then click **+** to add a job. |
122 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/pgbouncer.conf` and add a job. |
123 +
124 +:::important
125 +
126 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
127 +
128 +:::
129 +
130 +
131 ### Prerequisites
132
133 #### Create netdata user
@@ -164,14 +179,16 @@ The following options can be defined globally: update_every, autodetection_retry
179
180 #### via UI
181
167 -The **pgbouncer** collector can be configured directly through the Netdata web interface:
182 +Configure the **pgbouncer** collector from the Netdata web interface:
183
184 1. Go to **Nodes**.
170 -2. Select the node **where you want the pgbouncer data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
185 +2. Select the node **where you want the pgbouncer data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
186 3. The **Collectors → Jobs** view opens by default.
187 4. In the Search box, type _pgbouncer_ (or scroll the list) to locate the **pgbouncer** collector.
188 5. Click the **+** next to the **pgbouncer** collector to add a new job.
174 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
189 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
190 + - **Test** runs the job with the provided settings and shows whether data can be collected.
191 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
192
193
194 #### via File
@@ -185,7 +202,7 @@ update_every: 1
202 autodetection_retry: 0
203 jobs:
204 - name: some_name1
188 - - name: some_name1
205 + - name: some_name2
206 ```
207 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
208 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/phpdaemon/integrations/phpdaemon.md
+21 -4
@@ -78,6 +78,21 @@ There are no alerts configured by default for this integration.
78
79 ## Setup
80
81 +
82 +You can configure the **phpdaemon** collector in two ways:
83 +
84 +| Method | Best for | How to |
85 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
86 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **phpdaemon**, then click **+** to add a job. |
87 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/phpdaemon.conf` and add a job. |
88 +
89 +:::important
90 +
91 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
92 +
93 +:::
94 +
95 +
96 ### Prerequisites
97
98 #### Enable phpDaemon's HTTP server
@@ -191,14 +206,16 @@ The following options can be defined globally: update_every, autodetection_retry
206
207 #### via UI
208
194 -The **phpdaemon** collector can be configured directly through the Netdata web interface:
209 +Configure the **phpdaemon** collector from the Netdata web interface:
210
211 1. Go to **Nodes**.
197 -2. Select the node **where you want the phpdaemon data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
212 +2. Select the node **where you want the phpdaemon data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
213 3. The **Collectors → Jobs** view opens by default.
214 4. In the Search box, type _phpdaemon_ (or scroll the list) to locate the **phpdaemon** collector.
215 5. Click the **+** next to the **phpdaemon** collector to add a new job.
201 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
216 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
217 + - **Test** runs the job with the provided settings and shows whether data can be collected.
218 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
219
220
221 #### via File
@@ -212,7 +229,7 @@ update_every: 1
229 autodetection_retry: 0
230 jobs:
231 - name: some_name1
215 - - name: some_name1
232 + - name: some_name2
233 ```
234 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
235 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/phpfpm/integrations/php-fpm.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **phpfpm** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **phpfpm**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/phpfpm.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 #### Enable status page
@@ -125,14 +140,16 @@ The following options can be defined globally: update_every, autodetection_retry
140
141 #### via UI
142
128 -The **phpfpm** collector can be configured directly through the Netdata web interface:
143 +Configure the **phpfpm** collector from the Netdata web interface:
144
145 1. Go to **Nodes**.
131 -2. Select the node **where you want the phpfpm data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
146 +2. Select the node **where you want the phpfpm data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
147 3. The **Collectors → Jobs** view opens by default.
148 4. In the Search box, type _phpfpm_ (or scroll the list) to locate the **phpfpm** collector.
149 5. Click the **+** next to the **phpfpm** collector to add a new job.
135 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
150 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
151 + - **Test** runs the job with the provided settings and shows whether data can be collected.
152 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
153
154
155 #### via File
@@ -146,7 +163,7 @@ update_every: 1
163 autodetection_retry: 0
164 jobs:
165 - name: some_name1
149 - - name: some_name1
166 + - name: some_name2
167 ```
168 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
169 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/pihole/integrations/pi-hole.md
+21 -4
@@ -99,6 +99,21 @@ The following alerts are available:
99
100 ## Setup
101
102 +
103 +You can configure the **pihole** collector in two ways:
104 +
105 +| Method | Best for | How to |
106 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
107 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **pihole**, then click **+** to add a job. |
108 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/pihole.conf` and add a job. |
109 +
110 +:::important
111 +
112 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
113 +
114 +:::
115 +
116 +
117 ### Prerequisites
118
119 #### Pi-hole v6.0 or newer
@@ -146,14 +161,16 @@ The following options can be defined globally: update_every, autodetection_retry
161
162 #### via UI
163
149 -The **pihole** collector can be configured directly through the Netdata web interface:
164 +Configure the **pihole** collector from the Netdata web interface:
165
166 1. Go to **Nodes**.
152 -2. Select the node **where you want the pihole data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
167 +2. Select the node **where you want the pihole data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
168 3. The **Collectors → Jobs** view opens by default.
169 4. In the Search box, type _pihole_ (or scroll the list) to locate the **pihole** collector.
170 5. Click the **+** next to the **pihole** collector to add a new job.
156 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
171 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
172 + - **Test** runs the job with the provided settings and shows whether data can be collected.
173 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
174
175
176 #### via File
@@ -167,7 +184,7 @@ update_every: 1
184 autodetection_retry: 0
185 jobs:
186 - name: some_name1
170 - - name: some_name1
187 + - name: some_name2
188 ```
189 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
190 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/pika/integrations/pika.md
+21 -4
@@ -100,6 +100,21 @@ There are no alerts configured by default for this integration.
100
101 ## Setup
102
103 +
104 +You can configure the **pika** collector in two ways:
105 +
106 +| Method | Best for | How to |
107 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
108 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **pika**, then click **+** to add a job. |
109 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/pika.conf` and add a job. |
110 +
111 +:::important
112 +
113 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
114 +
115 +:::
116 +
117 +
118 ### Prerequisites
119
120 No action required.
@@ -131,14 +146,16 @@ The following options can be defined globally: update_every, autodetection_retry
146
147 #### via UI
148
134 -The **pika** collector can be configured directly through the Netdata web interface:
149 +Configure the **pika** collector from the Netdata web interface:
150
151 1. Go to **Nodes**.
137 -2. Select the node **where you want the pika data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
152 +2. Select the node **where you want the pika data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
153 3. The **Collectors → Jobs** view opens by default.
154 4. In the Search box, type _pika_ (or scroll the list) to locate the **pika** collector.
155 5. Click the **+** next to the **pika** collector to add a new job.
141 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
156 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
157 + - **Test** runs the job with the provided settings and shows whether data can be collected.
158 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
159
160
161 #### via File
@@ -152,7 +169,7 @@ update_every: 1
169 autodetection_retry: 0
170 jobs:
171 - name: some_name1
155 - - name: some_name1
172 + - name: some_name2
173 ```
174 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
175 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/ping/integrations/ping.md
+21 -4
@@ -113,6 +113,21 @@ The following alerts are available:
113
114 ## Setup
115
116 +
117 +You can configure the **ping** collector in two ways:
118 +
119 +| Method | Best for | How to |
120 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
121 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **ping**, then click **+** to add a job. |
122 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/ping.conf` and add a job. |
123 +
124 +:::important
125 +
126 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
127 +
128 +:::
129 +
130 +
131 ### Prerequisites
132
133 No action required.
@@ -142,14 +157,16 @@ The following options can be defined globally: update_every, autodetection_retry
157
158 #### via UI
159
145 -The **ping** collector can be configured directly through the Netdata web interface:
160 +Configure the **ping** collector from the Netdata web interface:
161
162 1. Go to **Nodes**.
148 -2. Select the node **where you want the ping data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
163 +2. Select the node **where you want the ping data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
164 3. The **Collectors → Jobs** view opens by default.
165 4. In the Search box, type _ping_ (or scroll the list) to locate the **ping** collector.
166 5. Click the **+** next to the **ping** collector to add a new job.
152 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
167 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
168 + - **Test** runs the job with the provided settings and shows whether data can be collected.
169 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
170
171
172 #### via File
@@ -163,7 +180,7 @@ update_every: 1
180 autodetection_retry: 0
181 jobs:
182 - name: some_name1
166 - - name: some_name1
183 + - name: some_name2
184 ```
185 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
186 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/portcheck/integrations/tcp-udp_endpoints.md
+21 -4
@@ -129,6 +129,21 @@ The following alerts are available:
129
130 ## Setup
131
132 +
133 +You can configure the **portcheck** collector in two ways:
134 +
135 +| Method | Best for | How to |
136 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
137 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **portcheck**, then click **+** to add a job. |
138 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/portcheck.conf` and add a job. |
139 +
140 +:::important
141 +
142 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
143 +
144 +:::
145 +
146 +
147 ### Prerequisites
148
149 No action required.
@@ -156,14 +171,16 @@ The following options can be defined globally: update_every, autodetection_retry
171
172 #### via UI
173
159 -The **portcheck** collector can be configured directly through the Netdata web interface:
174 +Configure the **portcheck** collector from the Netdata web interface:
175
176 1. Go to **Nodes**.
162 -2. Select the node **where you want the portcheck data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
177 +2. Select the node **where you want the portcheck 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 _portcheck_ (or scroll the list) to locate the **portcheck** collector.
180 5. Click the **+** next to the **portcheck** collector to add a new job.
166 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -177,7 +194,7 @@ update_every: 1
194 autodetection_retry: 0
195 jobs:
196 - name: some_name1
180 - - 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-a-configuration-file-using-edit-config) script from the
200 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/postfix/integrations/postfix.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **postfix** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **postfix**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/postfix.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 No action required.
@@ -104,14 +119,16 @@ The following options can be defined globally: update_every.
119
120 #### via UI
121
107 -The **postfix** collector can be configured directly through the Netdata web interface:
122 +Configure the **postfix** collector from the Netdata web interface:
123
124 1. Go to **Nodes**.
110 -2. Select the node **where you want the postfix data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
125 +2. Select the node **where you want the postfix data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
126 3. The **Collectors → Jobs** view opens by default.
127 4. In the Search box, type _postfix_ (or scroll the list) to locate the **postfix** collector.
128 5. Click the **+** next to the **postfix** collector to add a new job.
114 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
129 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
130 + - **Test** runs the job with the provided settings and shows whether data can be collected.
131 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
132
133
134 #### via File
@@ -125,7 +142,7 @@ update_every: 1
142 autodetection_retry: 0
143 jobs:
144 - name: some_name1
128 - - name: some_name1
145 + - name: some_name2
146 ```
147 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
148 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/postgres/integrations/postgresql.md
+21 -4
@@ -252,6 +252,21 @@ The following alerts are available:
252
253 ## Setup
254
255 +
256 +You can configure the **postgres** collector in two ways:
257 +
258 +| Method | Best for | How to |
259 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
260 +| [**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. |
261 +| [**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. |
262 +
263 +:::important
264 +
265 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
266 +
267 +:::
268 +
269 +
270 ### Prerequisites
271
272 #### Create netdata user
@@ -296,14 +311,16 @@ The following options can be defined globally: update_every, autodetection_retry
311
312 #### via UI
313
299 -The **postgres** collector can be configured directly through the Netdata web interface:
314 +Configure the **postgres** collector from the Netdata web interface:
315
316 1. Go to **Nodes**.
302 -2. Select the node **where you want the postgres data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
317 +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.
318 3. The **Collectors → Jobs** view opens by default.
319 4. In the Search box, type _postgres_ (or scroll the list) to locate the **postgres** collector.
320 5. Click the **+** next to the **postgres** collector to add a new job.
306 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
321 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
322 + - **Test** runs the job with the provided settings and shows whether data can be collected.
323 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
324
325
326 #### via File
@@ -317,7 +334,7 @@ update_every: 1
334 autodetection_retry: 0
335 jobs:
336 - name: some_name1
320 - - name: some_name1
337 + - name: some_name2
338 ```
339 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
340 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/powerdns/integrations/powerdns_authoritative_server.md
+21 -4
@@ -84,6 +84,21 @@ There are no alerts configured by default for this integration.
84
85 ## Setup
86
87 +
88 +You can configure the **powerdns** collector in two ways:
89 +
90 +| Method | Best for | How to |
91 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
92 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **powerdns**, then click **+** to add a job. |
93 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/powerdns.conf` and add a job. |
94 +
95 +:::important
96 +
97 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
98 +
99 +:::
100 +
101 +
102 ### Prerequisites
103
104 #### Enable webserver
@@ -131,14 +146,16 @@ The following options can be defined globally: update_every, autodetection_retry
146
147 #### via UI
148
134 -The **powerdns** collector can be configured directly through the Netdata web interface:
149 +Configure the **powerdns** collector from the Netdata web interface:
150
151 1. Go to **Nodes**.
137 -2. Select the node **where you want the powerdns data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
152 +2. Select the node **where you want the powerdns data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
153 3. The **Collectors → Jobs** view opens by default.
154 4. In the Search box, type _powerdns_ (or scroll the list) to locate the **powerdns** collector.
155 5. Click the **+** next to the **powerdns** collector to add a new job.
141 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
156 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
157 + - **Test** runs the job with the provided settings and shows whether data can be collected.
158 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
159
160
161 #### via File
@@ -152,7 +169,7 @@ update_every: 1
169 autodetection_retry: 0
170 jobs:
171 - name: some_name1
155 - - name: some_name1
172 + - name: some_name2
173 ```
174 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
175 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/powerdns_recursor/integrations/powerdns_recursor.md
+21 -4
@@ -87,6 +87,21 @@ There are no alerts configured by default for this integration.
87
88 ## Setup
89
90 +
91 +You can configure the **powerdns_recursor** 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 **powerdns_recursor**, 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/powerdns_recursor.conf` and add a job. |
97 +
98 +:::important
99 +
100 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
101 +
102 +:::
103 +
104 +
105 ### Prerequisites
106
107 #### Enable webserver
@@ -134,14 +149,16 @@ The following options can be defined globally: update_every, autodetection_retry
149
150 #### via UI
151
137 -The **powerdns_recursor** collector can be configured directly through the Netdata web interface:
152 +Configure the **powerdns_recursor** collector from the Netdata web interface:
153
154 1. Go to **Nodes**.
140 -2. Select the node **where you want the powerdns_recursor data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
155 +2. Select the node **where you want the powerdns_recursor 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 _powerdns_recursor_ (or scroll the list) to locate the **powerdns_recursor** collector.
158 5. Click the **+** next to the **powerdns_recursor** collector to add a new job.
144 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -155,7 +172,7 @@ update_every: 1
172 autodetection_retry: 0
173 jobs:
174 - name: some_name1
158 - - 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-a-configuration-file-using-edit-config) script from the
178 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/4d_server.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/8430ft_modem.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/a10_acos_network_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/airthings_waveplus_air_sensor.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/akamai_edge_dns_traffic.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/akamai_global_traffic_management.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/akami_cloudmonitor.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/alamos_fe2_server.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/alibaba_cloud.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/altaro_backup.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/amd_cpu_&_gpu.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/andrews_&_arnold_line_status.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/apache_airflow.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/apache_flink.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/apicast.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/apple_time_machine.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/arm_hwcpipe.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aruba_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/arvancloud_cdn.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/audisto.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/authlog.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_compute_instances.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_spot_instance.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_ecs.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_health_events.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_instance_health.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_quota.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_rds.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_s3_buckets.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/aws_sqs.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/azure_ad_app_passwords.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/azure_application.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/azure_elastic_pool_sql.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/azure_resources.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/azure_service_bus.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/azure_sql.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/bigquery.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/bird_routing_daemon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/blackbox.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/bobcat_miner_300.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/borg_backup.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/bosh.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/bpftrace_variables.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/bungeecord.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cadvisor.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/celery.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/certificate_transparency.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **prometheus** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 #### Install Exporter
@@ -164,14 +179,16 @@ fallback_type:
179
180 #### via UI
181
167 -The **prometheus** collector can be configured directly through the Netdata web interface:
182 +Configure the **prometheus** collector from the Netdata web interface:
183
184 1. Go to **Nodes**.
170 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
185 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
186 3. The **Collectors → Jobs** view opens by default.
187 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
188 5. Click the **+** next to the **prometheus** collector to add a new job.
174 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
189 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
190 + - **Test** runs the job with the provided settings and shows whether data can be collected.
191 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
192
193
194 #### via File
@@ -185,7 +202,7 @@ update_every: 1
202 autodetection_retry: 0
203 jobs:
204 - name: some_name1
188 - - name: some_name1
205 + - name: some_name2
206 ```
207 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
208 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/checkpoint_device.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/chia.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cilium_agent.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cilium_operator.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cilium_proxy.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cisco_aci.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/citrix_netscaler.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/clamav_daemon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/clamscan_results.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/clash.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry_firehose.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cloudflare_pcap.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cloudwatch.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/clustercontrol_cmon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/collectd.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/concourse.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Configure built-in Prometheus exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/craftbeerpi.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/crowdsec.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Configure built-in Prometheus exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/crypto_exchanges.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cryptowatch.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/custom_exporter.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/cvmfs_clients.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ddwrt_routers.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_ecs_cluster.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_isilon_cluster.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_xtremio_cluster.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dell_powermax.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dependency-track.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/digitalocean.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/discourse.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dmarc.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dnsbl.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dutch_electricity_smart_meter.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/dynatrace.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/eaton_ups.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/elgato_key_light_devices..md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/energomera_smart_power_meters.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/eos.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/etcd.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 No action required.
@@ -159,14 +174,16 @@ fallback_type:
174
175 #### via UI
176
162 -The **prometheus** collector can be configured directly through the Netdata web interface:
177 +Configure the **prometheus** collector from the Netdata web interface:
178
179 1. Go to **Nodes**.
165 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
180 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
181 3. The **Collectors → Jobs** view opens by default.
182 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
183 5. Click the **+** next to the **prometheus** collector to add a new job.
169 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
184 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
185 + - **Test** runs the job with the provided settings and shows whether data can be collected.
186 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
187
188
189 #### via File
@@ -180,7 +197,7 @@ update_every: 1
197 autodetection_retry: 0
198 jobs:
199 - name: some_name1
183 - - name: some_name1
200 + - name: some_name2
201 ```
202 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
203 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/excel_spreadsheet.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/fastd.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/fortigate_firewall.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/freebsd_nfs.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/freebsd_rctl-racct.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/freifunk_network.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/fritzbox_network_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/frrouting.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/gcp_gce.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/gcp_quota.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/generic_command_line_output.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/generic_storage_enclosure_tool.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/github_api_rate_limit.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **prometheus** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 #### Install Exporter
@@ -164,14 +179,16 @@ fallback_type:
179
180 #### via UI
181
167 -The **prometheus** collector can be configured directly through the Netdata web interface:
182 +Configure the **prometheus** collector from the Netdata web interface:
183
184 1. Go to **Nodes**.
170 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
185 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
186 3. The **Collectors → Jobs** view opens by default.
187 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
188 5. Click the **+** next to the **prometheus** collector to add a new job.
174 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
189 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
190 + - **Test** runs the job with the provided settings and shows whether data can be collected.
191 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
192
193
194 #### via File
@@ -185,7 +202,7 @@ update_every: 1
202 autodetection_retry: 0
203 jobs:
204 - name: some_name1
188 - - name: some_name1
205 + - name: some_name2
206 ```
207 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
208 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/github_repository.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/gitlab_runner.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Configure built-in Prometheus exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/gobetween.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 No action required.
@@ -159,14 +174,16 @@ fallback_type:
174
175 #### via UI
176
162 -The **prometheus** collector can be configured directly through the Netdata web interface:
177 +Configure the **prometheus** collector from the Netdata web interface:
178
179 1. Go to **Nodes**.
165 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
180 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
181 3. The **Collectors → Jobs** view opens by default.
182 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
183 5. Click the **+** next to the **prometheus** collector to add a new job.
169 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
184 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
185 + - **Test** runs the job with the provided settings and shows whether data can be collected.
186 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
187
188
189 #### via File
@@ -180,7 +197,7 @@ update_every: 1
197 autodetection_retry: 0
198 jobs:
199 - name: some_name1
183 - - name: some_name1
200 + - name: some_name2
201 ```
202 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
203 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/google_cloud_platform.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/google_pagespeed.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/google_stackdriver.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/gpsd.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/grafana.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 No action required.
@@ -159,14 +174,16 @@ fallback_type:
174
175 #### via UI
176
162 -The **prometheus** collector can be configured directly through the Netdata web interface:
177 +Configure the **prometheus** collector from the Netdata web interface:
178
179 1. Go to **Nodes**.
165 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
180 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
181 3. The **Collectors → Jobs** view opens by default.
182 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
183 5. Click the **+** next to the **prometheus** collector to add a new job.
169 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
184 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
185 + - **Test** runs the job with the provided settings and shows whether data can be collected.
186 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
187
188
189 #### via File
@@ -180,7 +197,7 @@ update_every: 1
197 autodetection_retry: 0
198 jobs:
199 - name: some_name1
183 - - name: some_name1
200 + - name: some_name2
201 ```
202 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
203 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/graylog_server.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Configure built-in Prometheus exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/gtp.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/halon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hana.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hashicorp_vault_secrets.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hasura_graphql_server.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **prometheus** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 #### Install Exporter
@@ -164,14 +179,16 @@ fallback_type:
179
180 #### via UI
181
167 -The **prometheus** collector can be configured directly through the Netdata web interface:
182 +Configure the **prometheus** collector from the Netdata web interface:
183
184 1. Go to **Nodes**.
170 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
185 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
186 3. The **Collectors → Jobs** view opens by default.
187 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
188 5. Click the **+** next to the **prometheus** collector to add a new job.
174 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
189 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
190 + - **Test** runs the job with the provided settings and shows whether data can be collected.
191 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
192
193
194 #### via File
@@ -185,7 +202,7 @@ update_every: 1
202 autodetection_retry: 0
203 jobs:
204 - name: some_name1
188 - - name: some_name1
205 + - name: some_name2
206 ```
207 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
208 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hdsentinel.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/helium_hotspot.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/helium_miner_validator.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hhvm.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **prometheus** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 #### Install Exporter
@@ -164,14 +179,16 @@ fallback_type:
179
180 #### via UI
181
167 -The **prometheus** collector can be configured directly through the Netdata web interface:
182 +Configure the **prometheus** collector from the Netdata web interface:
183
184 1. Go to **Nodes**.
170 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
185 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
186 3. The **Collectors → Jobs** view opens by default.
187 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
188 5. Click the **+** next to the **prometheus** collector to add a new job.
174 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
189 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
190 + - **Test** runs the job with the provided settings and shows whether data can be collected.
191 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
192
193
194 #### via File
@@ -185,7 +202,7 @@ update_every: 1
202 autodetection_retry: 0
203 jobs:
204 - name: some_name1
188 - - name: some_name1
205 + - name: some_name2
206 ```
207 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
208 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hitron_cgn_series_cpe.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hitron_coda_cable_modem.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/homebridge.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/homey.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/honeypot.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hp_ilo.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/huawei_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/hubble.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Configure built-in Prometheus exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ibm_aix_systems_njmon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ibm_cryptoexpress_cex_cards.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ibm_mq.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum_virtualize.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ibm_z_hardware_management_console.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/influxdb.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/iota_full_node.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ipmi_by_soundcloud.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/iqair_airvisual_air_quality_monitors.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/jarvis_standing_desk.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/jenkins.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/jetbrains_floating_license_server.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/jmx.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/jolokia.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/journald.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/kafka.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/kafka_connect.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/kafka_consumer_lag.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/kafka_zookeeper.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/kannel.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/keepalived.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/kubernetes_cluster_cloud_cost.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/lagerist_disk_latency.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ldap.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/linode.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/loki.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Loki
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/lustre_metadata.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/lynis_audit_reports.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/machbase.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/maildir.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/meilisearch.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/memcached_community.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/meraki_dashboard.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mesos.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mikrotik_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mikrotik_routeros_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/minecraft.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/modbus_protocol.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mogilefs.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/monnit_sensors_mqtt.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mosquitto.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mp707_usb_thermometer.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mqtt_blackbox.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/mtail.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/naemon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nagios.md
+21 -4
@@ -80,6 +80,21 @@ There are no alerts configured by default for this integration.
80
81 ## Setup
82
83 +
84 +You can configure the **prometheus** collector in two ways:
85 +
86 +| Method | Best for | How to |
87 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
88 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
89 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
90 +
91 +:::important
92 +
93 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
94 +
95 +:::
96 +
97 +
98 ### Prerequisites
99
100 #### Install Exporter
@@ -164,14 +179,16 @@ fallback_type:
179
180 #### via UI
181
167 -The **prometheus** collector can be configured directly through the Netdata web interface:
182 +Configure the **prometheus** collector from the Netdata web interface:
183
184 1. Go to **Nodes**.
170 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
185 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
186 3. The **Collectors → Jobs** view opens by default.
187 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
188 5. Click the **+** next to the **prometheus** collector to add a new job.
174 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
189 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
190 + - **Test** runs the job with the provided settings and shows whether data can be collected.
191 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
192
193
194 #### via File
@@ -185,7 +202,7 @@ update_every: 1
202 autodetection_retry: 0
203 jobs:
204 - name: some_name1
188 - - name: some_name1
205 + - name: some_name2
206 ```
207 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
208 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nature_remo_e_lite_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/netapp_ontap_api.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/netapp_solidfire.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/netatmo_sensors.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/netflow.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/netmeter.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/new_relic.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nextcloud_servers.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nextdns.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nftables.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nrpe_daemon.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nsx-t.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/nvml.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/obs_studio.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/odbc.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/open_vswitch.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openhab.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openldap_community.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openrc.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openrct2.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openroadm_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openstack.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openvas.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/openweathermap.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/oracle_db_community.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/otrs.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/patroni.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/personal_weather_station.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/pgbackrest.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/pgpool-ii.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/philips_hue.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/pimoroni_enviro+.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/pingdom.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/podman.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/powerpal_devices.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/proftpd.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/prometheus_endpoint.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 No action required.
@@ -159,14 +174,16 @@ fallback_type:
174
175 #### via UI
176
162 -The **prometheus** collector can be configured directly through the Netdata web interface:
177 +Configure the **prometheus** collector from the Netdata web interface:
178
179 1. Go to **Nodes**.
165 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
180 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
181 3. The **Collectors → Jobs** view opens by default.
182 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
183 5. Click the **+** next to the **prometheus** collector to add a new job.
169 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
184 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
185 + - **Test** runs the job with the provided settings and shows whether data can be collected.
186 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
187
188
189 #### via File
@@ -180,7 +197,7 @@ update_every: 1
197 autodetection_retry: 0
198 jobs:
199 - name: some_name1
183 - - name: some_name1
200 + - name: some_name2
201 ```
202 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
203 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/proxmox_ve.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/radio_thermostat.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/radius.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/rancher.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/raritan_pdu.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/redis_queue.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ripe_atlas.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sabnzbd.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/salicru_eqx_inverter.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sense_energy.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sentry.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/servertech.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/shell_command.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/shelly_humidity_sensor.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sia.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/siemens_s7_plc.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/site_24x7.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/slurm.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sma_inverters.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/smart_meters_sml.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/smartrg_808ac_cable_modem.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/softether_vpn_server.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/solar_logging_stick.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/solaredge_inverters.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/solis_ginlong_5g_inverters.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sonic_nos.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/spacelift.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/speedify_cli.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sphinx.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sql_database_agnostic.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ssh.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ssl_certificate.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/starlink_spacex.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/starwind_vsan_vsphere_edition.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/statuspage.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/steam.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/storidge.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/stream.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/strongswan.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sunspec_solar_energy.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/suricata.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/synology_activebackup.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/sysload.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/t-rex_nvidia_gpu_miner.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tacacs.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tado_smart_heating_solution.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tankerkoenig_api.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tesla_powerwall.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tesla_vehicle.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tesla_wall_connector.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/tp-link_p110.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/traceroute.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/twincat_ads_web_service.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/twitch.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/ubiquiti_ufiber_olt.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/uptimerobot.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/vault_pki.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/vertica.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/vscode.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/warp10.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/xiaomi_mi_flora.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/xmpp_server.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/yourls_url_shortener.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/zerto.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/zulip.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/prometheus/integrations/zyxel_gs1200-8.md
+21 -4
@@ -79,6 +79,21 @@ There are no alerts configured by default for this integration.
79
80 ## Setup
81
82 +
83 +You can configure the **prometheus** collector in two ways:
84 +
85 +| Method | Best for | How to |
86 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
87 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **prometheus**, then click **+** to add a job. |
88 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/prometheus.conf` and add a job. |
89 +
90 +:::important
91 +
92 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
93 +
94 +:::
95 +
96 +
97 ### Prerequisites
98
99 #### Install Exporter
@@ -163,14 +178,16 @@ fallback_type:
178
179 #### via UI
180
166 -The **prometheus** collector can be configured directly through the Netdata web interface:
181 +Configure the **prometheus** collector from the Netdata web interface:
182
183 1. Go to **Nodes**.
169 -2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
184 +2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
185 3. The **Collectors → Jobs** view opens by default.
186 4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
187 5. Click the **+** next to the **prometheus** collector to add a new job.
173 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
188 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
189 + - **Test** runs the job with the provided settings and shows whether data can be collected.
190 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
191
192
193 #### via File
@@ -184,7 +201,7 @@ update_every: 1
201 autodetection_retry: 0
202 jobs:
203 - name: some_name1
187 - - name: some_name1
204 + - name: some_name2
205 ```
206 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/proxysql/integrations/proxysql.md
+21 -4
@@ -159,6 +159,21 @@ There are no alerts configured by default for this integration.
159
160 ## Setup
161
162 +
163 +You can configure the **proxysql** collector in two ways:
164 +
165 +| Method | Best for | How to |
166 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
167 +| [**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. |
168 +| [**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. |
169 +
170 +:::important
171 +
172 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
173 +
174 +:::
175 +
176 +
177 ### Prerequisites
178
179 No action required.
@@ -184,14 +199,16 @@ The following options can be defined globally: update_every, autodetection_retry
199
200 #### via UI
201
187 -The **proxysql** collector can be configured directly through the Netdata web interface:
202 +Configure the **proxysql** collector from the Netdata web interface:
203
204 1. Go to **Nodes**.
190 -2. Select the node **where you want the proxysql data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
205 +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.
206 3. The **Collectors → Jobs** view opens by default.
207 4. In the Search box, type _proxysql_ (or scroll the list) to locate the **proxysql** collector.
208 5. Click the **+** next to the **proxysql** collector to add a new job.
194 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
209 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
210 + - **Test** runs the job with the provided settings and shows whether data can be collected.
211 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
212
213
214 #### via File
@@ -205,7 +222,7 @@ update_every: 1
222 autodetection_retry: 0
223 jobs:
224 - name: some_name1
208 - - name: some_name1
225 + - name: some_name2
226 ```
227 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
228 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/pulsar/integrations/apache_pulsar.md
+21 -4
@@ -137,6 +137,21 @@ There are no alerts configured by default for this integration.
137
138 ## Setup
139
140 +
141 +You can configure the **pulsar** collector in two ways:
142 +
143 +| Method | Best for | How to |
144 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
145 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **pulsar**, then click **+** to add a job. |
146 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/pulsar.conf` and add a job. |
147 +
148 +:::important
149 +
150 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
151 +
152 +:::
153 +
154 +
155 ### Prerequisites
156
157 No action required.
@@ -175,14 +190,16 @@ The following options can be defined globally: update_every, autodetection_retry
190
191 #### via UI
192
178 -The **pulsar** collector can be configured directly through the Netdata web interface:
193 +Configure the **pulsar** collector from the Netdata web interface:
194
195 1. Go to **Nodes**.
181 -2. Select the node **where you want the pulsar data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
196 +2. Select the node **where you want the pulsar 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 _pulsar_ (or scroll the list) to locate the **pulsar** collector.
199 5. Click the **+** next to the **pulsar** collector to add a new job.
185 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
204
205 #### via File
@@ -196,7 +213,7 @@ update_every: 1
213 autodetection_retry: 0
214 jobs:
215 - name: some_name1
199 - - 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-a-configuration-file-using-edit-config) script from the
219 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/puppet/integrations/puppet.md
+21 -4
@@ -83,6 +83,21 @@ There are no alerts configured by default for this integration.
83
84 ## Setup
85
86 +
87 +You can configure the **puppet** collector in two ways:
88 +
89 +| Method | Best for | How to |
90 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
91 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **puppet**, then click **+** to add a job. |
92 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/puppet.conf` and add a job. |
93 +
94 +:::important
95 +
96 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
97 +
98 +:::
99 +
100 +
101 ### Prerequisites
102
103 No action required.
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every, autodetection_retry
134
135 #### via UI
136
122 -The **puppet** collector can be configured directly through the Netdata web interface:
137 +Configure the **puppet** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the puppet data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the puppet data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _puppet_ (or scroll the list) to locate the **puppet** collector.
143 5. Click the **+** next to the **puppet** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/rabbitmq/integrations/rabbitmq.md
+21 -4
@@ -194,6 +194,21 @@ The following alerts are available:
194
195 ## Setup
196
197 +
198 +You can configure the **rabbitmq** collector in two ways:
199 +
200 +| Method | Best for | How to |
201 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
202 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **rabbitmq**, then click **+** to add a job. |
203 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/rabbitmq.conf` and add a job. |
204 +
205 +:::important
206 +
207 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
208 +
209 +:::
210 +
211 +
212 ### Prerequisites
213
214 #### Enable management plugin.
@@ -238,14 +253,16 @@ The following options can be defined globally: update_every, autodetection_retry
253
254 #### via UI
255
241 -The **rabbitmq** collector can be configured directly through the Netdata web interface:
256 +Configure the **rabbitmq** collector from the Netdata web interface:
257
258 1. Go to **Nodes**.
244 -2. Select the node **where you want the rabbitmq data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
259 +2. Select the node **where you want the rabbitmq data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
260 3. The **Collectors → Jobs** view opens by default.
261 4. In the Search box, type _rabbitmq_ (or scroll the list) to locate the **rabbitmq** collector.
262 5. Click the **+** next to the **rabbitmq** collector to add a new job.
248 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
263 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
264 + - **Test** runs the job with the provided settings and shows whether data can be collected.
265 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
266
267
268 #### via File
@@ -259,7 +276,7 @@ update_every: 1
276 autodetection_retry: 0
277 jobs:
278 - name: some_name1
262 - - name: some_name1
279 + - name: some_name2
280 ```
281 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
282 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/redis/integrations/redis.md
+21 -4
@@ -117,6 +117,21 @@ The following alerts are available:
117
118 ## Setup
119
120 +
121 +You can configure the **redis** collector in two ways:
122 +
123 +| Method | Best for | How to |
124 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
125 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **redis**, then click **+** to add a job. |
126 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/redis.conf` and add a job. |
127 +
128 +:::important
129 +
130 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
131 +
132 +:::
133 +
134 +
135 ### Prerequisites
136
137 No action required.
@@ -148,14 +163,16 @@ The following options can be defined globally: update_every, autodetection_retry
163
164 #### via UI
165
151 -The **redis** collector can be configured directly through the Netdata web interface:
166 +Configure the **redis** collector from the Netdata web interface:
167
168 1. Go to **Nodes**.
154 -2. Select the node **where you want the redis data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
169 +2. Select the node **where you want the redis data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
170 3. The **Collectors → Jobs** view opens by default.
171 4. In the Search box, type _redis_ (or scroll the list) to locate the **redis** collector.
172 5. Click the **+** next to the **redis** collector to add a new job.
158 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
173 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
174 + - **Test** runs the job with the provided settings and shows whether data can be collected.
175 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
176
177
178 #### via File
@@ -169,7 +186,7 @@ update_every: 1
186 autodetection_retry: 0
187 jobs:
188 - name: some_name1
172 - - name: some_name1
189 + - name: some_name2
190 ```
191 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
192 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/rethinkdb/integrations/rethinkdb.md
+21 -4
@@ -103,6 +103,21 @@ There are no alerts configured by default for this integration.
103
104 ## Setup
105
106 +
107 +You can configure the **rethinkdb** collector in two ways:
108 +
109 +| Method | Best for | How to |
110 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
111 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **rethinkdb**, then click **+** to add a job. |
112 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/rethinkdb.conf` and add a job. |
113 +
114 +:::important
115 +
116 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
117 +
118 +:::
119 +
120 +
121 ### Prerequisites
122
123 No action required.
@@ -130,14 +145,16 @@ The following options can be defined globally: update_every, autodetection_retry
145
146 #### via UI
147
133 -The **rethinkdb** collector can be configured directly through the Netdata web interface:
148 +Configure the **rethinkdb** collector from the Netdata web interface:
149
150 1. Go to **Nodes**.
136 -2. Select the node **where you want the rethinkdb data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
151 +2. Select the node **where you want the rethinkdb data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
152 3. The **Collectors → Jobs** view opens by default.
153 4. In the Search box, type _rethinkdb_ (or scroll the list) to locate the **rethinkdb** collector.
154 5. Click the **+** next to the **rethinkdb** collector to add a new job.
140 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
155 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
156 + - **Test** runs the job with the provided settings and shows whether data can be collected.
157 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
158
159
160 #### via File
@@ -151,7 +168,7 @@ update_every: 1
168 autodetection_retry: 0
169 jobs:
170 - name: some_name1
154 - - name: some_name1
171 + - name: some_name2
172 ```
173 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
174 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/riakkv/integrations/riak_kv.md
+21 -4
@@ -103,6 +103,21 @@ There are no alerts configured by default for this integration.
103
104 ## Setup
105
106 +
107 +You can configure the **riakkv** collector in two ways:
108 +
109 +| Method | Best for | How to |
110 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
111 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **riakkv**, then click **+** to add a job. |
112 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/riakkv.conf` and add a job. |
113 +
114 +:::important
115 +
116 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
117 +
118 +:::
119 +
120 +
121 ### Prerequisites
122
123 #### Enable /stats endpoint
@@ -145,14 +160,16 @@ The following options can be defined globally: update_every, autodetection_retry
160
161 #### via UI
162
148 -The **riakkv** collector can be configured directly through the Netdata web interface:
163 +Configure the **riakkv** collector from the Netdata web interface:
164
165 1. Go to **Nodes**.
151 -2. Select the node **where you want the riakkv data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
166 +2. Select the node **where you want the riakkv data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
167 3. The **Collectors → Jobs** view opens by default.
168 4. In the Search box, type _riakkv_ (or scroll the list) to locate the **riakkv** collector.
169 5. Click the **+** next to the **riakkv** collector to add a new job.
155 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
170 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
171 + - **Test** runs the job with the provided settings and shows whether data can be collected.
172 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
173
174
175 #### via File
@@ -166,7 +183,7 @@ update_every: 1
183 autodetection_retry: 0
184 jobs:
185 - name: some_name1
169 - - name: some_name1
186 + - name: some_name2
187 ```
188 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
189 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/rspamd/integrations/rspamd.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **rspamd** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **rspamd**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/rspamd.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 No action required.
@@ -120,14 +135,16 @@ The following options can be defined globally: update_every, autodetection_retry
135
136 #### via UI
137
123 -The **rspamd** collector can be configured directly through the Netdata web interface:
138 +Configure the **rspamd** collector from the Netdata web interface:
139
140 1. Go to **Nodes**.
126 -2. Select the node **where you want the rspamd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
141 +2. Select the node **where you want the rspamd 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 _rspamd_ (or scroll the list) to locate the **rspamd** collector.
144 5. Click the **+** next to the **rspamd** collector to add a new job.
130 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -141,7 +158,7 @@ update_every: 1
158 autodetection_retry: 0
159 jobs:
160 - name: some_name1
144 - - 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-a-configuration-file-using-edit-config) script from the
164 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/samba/integrations/samba.md
+21 -4
@@ -99,6 +99,21 @@ There are no alerts configured by default for this integration.
99
100 ## Setup
101
102 +
103 +You can configure the **samba** collector in two ways:
104 +
105 +| Method | Best for | How to |
106 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
107 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **samba**, then click **+** to add a job. |
108 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/samba.conf` and add a job. |
109 +
110 +:::important
111 +
112 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
113 +
114 +:::
115 +
116 +
117 ### Prerequisites
118
119 #### Verifying and Enabling Profiling for SMBd
@@ -149,14 +164,16 @@ The following options can be defined globally: update_every.
164
165 #### via UI
166
152 -The **samba** collector can be configured directly through the Netdata web interface:
167 +Configure the **samba** collector from the Netdata web interface:
168
169 1. Go to **Nodes**.
155 -2. Select the node **where you want the samba data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170 +2. Select the node **where you want the samba data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
171 3. The **Collectors → Jobs** view opens by default.
172 4. In the Search box, type _samba_ (or scroll the list) to locate the **samba** collector.
173 5. Click the **+** next to the **samba** collector to add a new job.
159 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
174 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
175 + - **Test** runs the job with the provided settings and shows whether data can be collected.
176 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
177
178
179 #### via File
@@ -170,7 +187,7 @@ update_every: 1
187 autodetection_retry: 0
188 jobs:
189 - name: some_name1
173 - - name: some_name1
190 + - name: some_name2
191 ```
192 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
193 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/scaleio/integrations/dell_emc_scaleio.md
+21 -4
@@ -132,6 +132,21 @@ There are no alerts configured by default for this integration.
132
133 ## Setup
134
135 +
136 +You can configure the **scaleio** collector in two ways:
137 +
138 +| Method | Best for | How to |
139 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
140 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **scaleio**, then click **+** to add a job. |
141 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/scaleio.conf` and add a job. |
142 +
143 +:::important
144 +
145 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
146 +
147 +:::
148 +
149 +
150 ### Prerequisites
151
152 No action required.
@@ -170,14 +185,16 @@ The following options can be defined globally: update_every, autodetection_retry
185
186 #### via UI
187
173 -The **scaleio** collector can be configured directly through the Netdata web interface:
188 +Configure the **scaleio** collector from the Netdata web interface:
189
190 1. Go to **Nodes**.
176 -2. Select the node **where you want the scaleio data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
191 +2. Select the node **where you want the scaleio data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
192 3. The **Collectors → Jobs** view opens by default.
193 4. In the Search box, type _scaleio_ (or scroll the list) to locate the **scaleio** collector.
194 5. Click the **+** next to the **scaleio** collector to add a new job.
180 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
195 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
196 + - **Test** runs the job with the provided settings and shows whether data can be collected.
197 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
198
199
200 #### via File
@@ -191,7 +208,7 @@ update_every: 1
208 autodetection_retry: 0
209 jobs:
210 - name: some_name1
194 - - name: some_name1
211 + - name: some_name2
212 ```
213 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
214 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/sensors/integrations/linux_sensors.md
+21 -4
@@ -111,6 +111,21 @@ There are no alerts configured by default for this integration.
111
112 ## Setup
113
114 +
115 +You can configure the **sensors** collector in two ways:
116 +
117 +| Method | Best for | How to |
118 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
119 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **sensors**, then click **+** to add a job. |
120 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/sensors.conf` and add a job. |
121 +
122 +:::important
123 +
124 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
125 +
126 +:::
127 +
128 +
129 ### Prerequisites
130
131 No action required.
@@ -138,14 +153,16 @@ The following options can be defined globally: update_every.
153
154 #### via UI
155
141 -The **sensors** collector can be configured directly through the Netdata web interface:
156 +Configure the **sensors** collector from the Netdata web interface:
157
158 1. Go to **Nodes**.
144 -2. Select the node **where you want the sensors data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
159 +2. Select the node **where you want the sensors data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
160 3. The **Collectors → Jobs** view opens by default.
161 4. In the Search box, type _sensors_ (or scroll the list) to locate the **sensors** collector.
162 5. Click the **+** next to the **sensors** collector to add a new job.
148 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
163 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
164 + - **Test** runs the job with the provided settings and shows whether data can be collected.
165 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
166
167
168 #### via File
@@ -159,7 +176,7 @@ update_every: 1
176 autodetection_retry: 0
177 jobs:
178 - name: some_name1
162 - - name: some_name1
179 + - name: some_name2
180 ```
181 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
182 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/smartctl/integrations/s.m.a.r.t..md
+21 -4
@@ -101,6 +101,21 @@ There are no alerts configured by default for this integration.
101
102 ## Setup
103
104 +
105 +You can configure the **smartctl** collector in two ways:
106 +
107 +| Method | Best for | How to |
108 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
109 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **smartctl**, then click **+** to add a job. |
110 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/smartctl.conf` and add a job. |
111 +
112 +:::important
113 +
114 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
115 +
116 +:::
117 +
118 +
119 ### Prerequisites
120
121 #### Install smartmontools (v7.0+)
@@ -180,14 +195,16 @@ The valid arguments to this option are:
195
196 #### via UI
197
183 -The **smartctl** collector can be configured directly through the Netdata web interface:
198 +Configure the **smartctl** collector from the Netdata web interface:
199
200 1. Go to **Nodes**.
186 -2. Select the node **where you want the smartctl data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
201 +2. Select the node **where you want the smartctl data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
202 3. The **Collectors → Jobs** view opens by default.
203 4. In the Search box, type _smartctl_ (or scroll the list) to locate the **smartctl** collector.
204 5. Click the **+** next to the **smartctl** collector to add a new job.
190 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
205 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
206 + - **Test** runs the job with the provided settings and shows whether data can be collected.
207 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
208
209
210 #### via File
@@ -201,7 +218,7 @@ update_every: 1
218 autodetection_retry: 0
219 jobs:
220 - name: some_name1
204 - - name: some_name1
221 + - name: some_name2
222 ```
223 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
224 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/snmp/integrations/snmp_devices.md
+37 -14
@@ -132,9 +132,31 @@ There are no alerts configured by default for this integration.
132
133 ## Setup
134
135 +
136 +You can configure the **snmp** collector in two ways:
137 +
138 +| Method | Best for | How to |
139 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
140 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **snmp**, then click **+** to add a job. |
141 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/snmp.conf` and add a job. |
142 +
143 +:::important
144 +
145 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
146 +
147 +:::
148 +
149 +
150 ### Prerequisites
151
137 -No action required.
152 +#### Prepare the SNMP device
153 +
154 +Before configuring the collector:
155 +- Enable the SNMP service on the target device (through its management interface).
156 +- Make sure the device is reachable from the Netdata node on port 161/UDP.
157 +- Have ready the required connection details: IP address, SNMP version, and either a community string (v1/v2c) or user credentials (v3).
158 +
159 +
160
161 ### Configuration
162
@@ -149,9 +171,9 @@ The following options can be defined globally: update_every, autodetection_retry
171 |:----|:-----------|:-------|:--------:|
172 | update_every | Data collection frequency. | 10 | no |
173 | autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
152 -| hostname | Target ipv4 address. | | yes |
174 +| hostname | Target host (IP or DNS name, IPv4/IPv6). | | yes |
175 | enable_profiles | Enable collection of metrics using SNMP profiles. | true | no |
154 -| enable_profiles_table_metrics | Enable collection of SNMP table metrics from profiles. Enabling this may **increase collection time and memory usage** for devices with many network interfaces*. | true | no |
176 +| enable_profiles_table_metrics | Enable collection of SNMP table metrics from profiles. Enabling this may **increase collection time and memory usage** for devices with many network interfaces. | true | no |
177 | disable_legacy_collection | Disable the legacy SNMP collection method, forcing the collector to use only SNMP profiles (YAML-based configuration). When enabled, the collector will ignore any non-profile based collection logic. | false | no |
178 | create_vnode | If set, the collector will create a Netdata Virtual Node for this SNMP device, which will appear as a separate Node in Netdata. | true | no |
179 | vnode_device_down_threshold | Number of consecutive failed data collections before marking the device as down. | 3 | no |
@@ -168,14 +190,13 @@ The following options can be defined globally: update_every, autodetection_retry
190 | network_interface_filter.by_name | Filter interfaces by their names using [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns). | | no |
191 | network_interface_filter.by_type | Filter interfaces by their types using [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns). | | no |
192 | user.name | SNMPv3 user name. | | no |
171 -| user.name | Security level of SNMPv3 messages. | | no |
172 -| user.auth_proto | Security level of SNMPv3 messages. | | no |
173 -| user.name | Authentication protocol for SNMPv3 messages. | | no |
174 -| user.auth_key | Authentication protocol pass phrase. | | no |
193 +| user.level | Security level of SNMPv3 messages. | | no |
194 +| user.auth_proto | Authentication protocol for SNMPv3 messages. | | no |
195 +| user.auth_key | Authentication protocol pass phrase for SNMPv3 messages. | | no |
196 | user.priv_proto | Privacy protocol for SNMPv3 messages. | | no |
176 -| user.priv_key | Privacy protocol pass phrase. | | no |
197 +| user.priv_key | Privacy protocol pass phrase for SNMPv3 messages. | | no |
198
178 -##### user.auth_proto
199 +##### user.level
200
201 The security of an SNMPv3 message as per RFC 3414 (`user.level`):
202
@@ -186,7 +207,7 @@ The security of an SNMPv3 message as per RFC 3414 (`user.level`):
207 | authPriv | 3 | message authentication and encryption |
208
209
189 -##### user.name
210 +##### user.auth_proto
211
212 The digest algorithm for SNMPv3 messages that require authentication (`user.auth_proto`):
213
@@ -221,14 +242,16 @@ The encryption algorithm for SNMPv3 messages that require privacy (`user.priv_pr
242
243 #### via UI
244
224 -The **snmp** collector can be configured directly through the Netdata web interface:
245 +Configure the **snmp** collector from the Netdata web interface:
246
247 1. Go to **Nodes**.
227 -2. Select the node **where you want the snmp data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
248 +2. Select the node **where you want the snmp data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
249 3. The **Collectors → Jobs** view opens by default.
250 4. In the Search box, type _snmp_ (or scroll the list) to locate the **snmp** collector.
251 5. Click the **+** next to the **snmp** collector to add a new job.
231 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
252 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
253 + - **Test** runs the job with the provided settings and shows whether data can be collected.
254 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
255
256
257 #### via File
@@ -242,7 +265,7 @@ update_every: 1
265 autodetection_retry: 0
266 jobs:
267 - name: some_name1
245 - - name: some_name1
268 + - name: some_name2
269 ```
270 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
271 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/spigotmc/integrations/spigotmc.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **spigotmc** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **spigotmc**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/spigotmc.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 No action required.
@@ -107,14 +122,16 @@ The following options can be defined globally: update_every, autodetection_retry
122
123 #### via UI
124
110 -The **spigotmc** collector can be configured directly through the Netdata web interface:
125 +Configure the **spigotmc** collector from the Netdata web interface:
126
127 1. Go to **Nodes**.
113 -2. Select the node **where you want the spigotmc data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
128 +2. Select the node **where you want the spigotmc 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 _spigotmc_ (or scroll the list) to locate the **spigotmc** collector.
131 5. Click the **+** next to the **spigotmc** collector to add a new job.
117 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -128,7 +145,7 @@ update_every: 1
145 autodetection_retry: 0
146 jobs:
147 - name: some_name1
131 - - 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-a-configuration-file-using-edit-config) script from the
151 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/squid/integrations/squid.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **squid** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **squid**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/squid.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 No action required.
@@ -120,14 +135,16 @@ The following options can be defined globally: update_every, autodetection_retry
135
136 #### via UI
137
123 -The **squid** collector can be configured directly through the Netdata web interface:
138 +Configure the **squid** collector from the Netdata web interface:
139
140 1. Go to **Nodes**.
126 -2. Select the node **where you want the squid data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
141 +2. Select the node **where you want the squid 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 _squid_ (or scroll the list) to locate the **squid** collector.
144 5. Click the **+** next to the **squid** collector to add a new job.
130 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -141,7 +158,7 @@ update_every: 1
158 autodetection_retry: 0
159 jobs:
160 - name: some_name1
144 - - 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-a-configuration-file-using-edit-config) script from the
164 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/squidlog/integrations/squid_log_files.md
+21 -4
@@ -93,6 +93,21 @@ There are no alerts configured by default for this integration.
93
94 ## Setup
95
96 +
97 +You can configure the **squidlog** collector in two ways:
98 +
99 +| Method | Best for | How to |
100 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
101 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **squidlog**, then click **+** to add a job. |
102 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/squidlog.conf` and add a job. |
103 +
104 +:::important
105 +
106 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
107 +
108 +:::
109 +
110 +
111 ### Prerequisites
112
113 No action required.
@@ -206,14 +221,16 @@ parser:
221
222 #### via UI
223
209 -The **squidlog** collector can be configured directly through the Netdata web interface:
224 +Configure the **squidlog** collector from the Netdata web interface:
225
226 1. Go to **Nodes**.
212 -2. Select the node **where you want the squidlog data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
227 +2. Select the node **where you want the squidlog data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
228 3. The **Collectors → Jobs** view opens by default.
229 4. In the Search box, type _squidlog_ (or scroll the list) to locate the **squidlog** collector.
230 5. Click the **+** next to the **squidlog** collector to add a new job.
216 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
231 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
232 + - **Test** runs the job with the provided settings and shows whether data can be collected.
233 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
234
235
236 #### via File
@@ -227,7 +244,7 @@ update_every: 1
244 autodetection_retry: 0
245 jobs:
246 - name: some_name1
230 - - name: some_name1
247 + - name: some_name2
248 ```
249 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
250 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/storcli/integrations/storecli_raid.md
+21 -4
@@ -142,6 +142,21 @@ The following alerts are available:
142
143 ## Setup
144
145 +
146 +You can configure the **storcli** collector in two ways:
147 +
148 +| Method | Best for | How to |
149 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
150 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **storcli**, then click **+** to add a job. |
151 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/storcli.conf` and add a job. |
152 +
153 +:::important
154 +
155 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
156 +
157 +:::
158 +
159 +
160 ### Prerequisites
161
162 No action required.
@@ -165,14 +180,16 @@ The following options can be defined globally: update_every.
180
181 #### via UI
182
168 -The **storcli** collector can be configured directly through the Netdata web interface:
183 +Configure the **storcli** collector from the Netdata web interface:
184
185 1. Go to **Nodes**.
171 -2. Select the node **where you want the storcli data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
186 +2. Select the node **where you want the storcli data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
187 3. The **Collectors → Jobs** view opens by default.
188 4. In the Search box, type _storcli_ (or scroll the list) to locate the **storcli** collector.
189 5. Click the **+** next to the **storcli** collector to add a new job.
175 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
190 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
191 + - **Test** runs the job with the provided settings and shows whether data can be collected.
192 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
193
194
195 #### via File
@@ -186,7 +203,7 @@ update_every: 1
203 autodetection_retry: 0
204 jobs:
205 - name: some_name1
189 - - name: some_name1
206 + - name: some_name2
207 ```
208 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
209 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/supervisord/integrations/supervisor.md
+21 -4
@@ -100,6 +100,21 @@ There are no alerts configured by default for this integration.
100
101 ## Setup
102
103 +
104 +You can configure the **supervisord** collector in two ways:
105 +
106 +| Method | Best for | How to |
107 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
108 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **supervisord**, then click **+** to add a job. |
109 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/supervisord.conf` and add a job. |
110 +
111 +:::important
112 +
113 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
114 +
115 +:::
116 +
117 +
118 ### Prerequisites
119
120 No action required.
@@ -125,14 +140,16 @@ The following options can be defined globally: update_every, autodetection_retry
140
141 #### via UI
142
128 -The **supervisord** collector can be configured directly through the Netdata web interface:
143 +Configure the **supervisord** collector from the Netdata web interface:
144
145 1. Go to **Nodes**.
131 -2. Select the node **where you want the supervisord data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
146 +2. Select the node **where you want the supervisord data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
147 3. The **Collectors → Jobs** view opens by default.
148 4. In the Search box, type _supervisord_ (or scroll the list) to locate the **supervisord** collector.
149 5. Click the **+** next to the **supervisord** collector to add a new job.
135 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
150 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
151 + - **Test** runs the job with the provided settings and shows whether data can be collected.
152 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
153
154
155 #### via File
@@ -146,7 +163,7 @@ update_every: 1
163 autodetection_retry: 0
164 jobs:
165 - name: some_name1
149 - - name: some_name1
166 + - name: some_name2
167 ```
168 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
169 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/systemdunits/integrations/systemd_units.md
+21 -4
@@ -121,6 +121,21 @@ The following alerts are available:
121
122 ## Setup
123
124 +
125 +You can configure the **systemdunits** collector in two ways:
126 +
127 +| Method | Best for | How to |
128 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
129 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **systemdunits**, then click **+** to add a job. |
130 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/systemdunits.conf` and add a job. |
131 +
132 +:::important
133 +
134 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
135 +
136 +:::
137 +
138 +
139 ### Prerequisites
140
141 No action required.
@@ -180,14 +195,16 @@ includes:
195
196 #### via UI
197
183 -The **systemdunits** collector can be configured directly through the Netdata web interface:
198 +Configure the **systemdunits** collector from the Netdata web interface:
199
200 1. Go to **Nodes**.
186 -2. Select the node **where you want the systemdunits data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
201 +2. Select the node **where you want the systemdunits data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
202 3. The **Collectors → Jobs** view opens by default.
203 4. In the Search box, type _systemdunits_ (or scroll the list) to locate the **systemdunits** collector.
204 5. Click the **+** next to the **systemdunits** collector to add a new job.
190 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
205 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
206 + - **Test** runs the job with the provided settings and shows whether data can be collected.
207 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
208
209
210 #### via File
@@ -201,7 +218,7 @@ update_every: 1
218 autodetection_retry: 0
219 jobs:
220 - name: some_name1
204 - - name: some_name1
221 + - name: some_name2
222 ```
223 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
224 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/tengine/integrations/tengine.md
+21 -4
@@ -82,6 +82,21 @@ There are no alerts configured by default for this integration.
82
83 ## Setup
84
85 +
86 +You can configure the **tengine** collector in two ways:
87 +
88 +| Method | Best for | How to |
89 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
90 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **tengine**, then click **+** to add a job. |
91 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/tengine.conf` and add a job. |
92 +
93 +:::important
94 +
95 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
96 +
97 +:::
98 +
99 +
100 ### Prerequisites
101
102 #### Enable ngx_http_reqstat_module module.
@@ -125,14 +140,16 @@ The following options can be defined globally: update_every, autodetection_retry
140
141 #### via UI
142
128 -The **tengine** collector can be configured directly through the Netdata web interface:
143 +Configure the **tengine** collector from the Netdata web interface:
144
145 1. Go to **Nodes**.
131 -2. Select the node **where you want the tengine data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
146 +2. Select the node **where you want the tengine data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
147 3. The **Collectors → Jobs** view opens by default.
148 4. In the Search box, type _tengine_ (or scroll the list) to locate the **tengine** collector.
149 5. Click the **+** next to the **tengine** collector to add a new job.
135 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
150 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
151 + - **Test** runs the job with the provided settings and shows whether data can be collected.
152 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
153
154
155 #### via File
@@ -146,7 +163,7 @@ update_every: 1
163 autodetection_retry: 0
164 jobs:
165 - name: some_name1
149 - - name: some_name1
166 + - name: some_name2
167 ```
168 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
169 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/tomcat/integrations/tomcat.md
+21 -4
@@ -116,6 +116,21 @@ There are no alerts configured by default for this integration.
116
117 ## Setup
118
119 +
120 +You can configure the **tomcat** collector in two ways:
121 +
122 +| Method | Best for | How to |
123 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
124 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **tomcat**, then click **+** to add a job. |
125 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/tomcat.conf` and add a job. |
126 +
127 +:::important
128 +
129 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
130 +
131 +:::
132 +
133 +
134 ### Prerequisites
135
136 #### Access to Tomcat Status Endpoint
@@ -162,14 +177,16 @@ The following options can be defined globally: update_every, autodetection_retry
177
178 #### via UI
179
165 -The **tomcat** collector can be configured directly through the Netdata web interface:
180 +Configure the **tomcat** collector from the Netdata web interface:
181
182 1. Go to **Nodes**.
168 -2. Select the node **where you want the tomcat data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
183 +2. Select the node **where you want the tomcat data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
184 3. The **Collectors → Jobs** view opens by default.
185 4. In the Search box, type _tomcat_ (or scroll the list) to locate the **tomcat** collector.
186 5. Click the **+** next to the **tomcat** collector to add a new job.
172 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
187 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
188 + - **Test** runs the job with the provided settings and shows whether data can be collected.
189 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
190
191
192 #### via File
@@ -183,7 +200,7 @@ update_every: 1
200 autodetection_retry: 0
201 jobs:
202 - name: some_name1
186 - - name: some_name1
203 + - name: some_name2
204 ```
205 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
206 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/tor/integrations/tor.md
+21 -4
@@ -81,6 +81,21 @@ There are no alerts configured by default for this integration.
81
82 ## Setup
83
84 +
85 +You can configure the **tor** collector in two ways:
86 +
87 +| Method | Best for | How to |
88 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
89 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **tor**, then click **+** to add a job. |
90 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/tor.conf` and add a job. |
91 +
92 +:::important
93 +
94 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
95 +
96 +:::
97 +
98 +
99 ### Prerequisites
100
101 #### Enable Control Port
@@ -111,14 +126,16 @@ The following options can be defined globally: update_every, autodetection_retry
126
127 #### via UI
128
114 -The **tor** collector can be configured directly through the Netdata web interface:
129 +Configure the **tor** collector from the Netdata web interface:
130
131 1. Go to **Nodes**.
117 -2. Select the node **where you want the tor data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
132 +2. Select the node **where you want the tor 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 _tor_ (or scroll the list) to locate the **tor** collector.
135 5. Click the **+** next to the **tor** collector to add a new job.
121 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -132,7 +149,7 @@ update_every: 1
149 autodetection_retry: 0
150 jobs:
151 - name: some_name1
135 - - 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-a-configuration-file-using-edit-config) script from the
155 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/traefik/integrations/traefik.md
+21 -4
@@ -77,6 +77,21 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 +You can configure the **traefik** collector in two ways:
82 +
83 +| Method | Best for | How to |
84 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
85 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **traefik**, then click **+** to add a job. |
86 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/traefik.conf` and add a job. |
87 +
88 +:::important
89 +
90 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
91 +
92 +:::
93 +
94 +
95 ### Prerequisites
96
97 #### Enable built-in Prometheus exporter
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every, autodetection_retry
134
135 #### via UI
136
122 -The **traefik** collector can be configured directly through the Netdata web interface:
137 +Configure the **traefik** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the traefik data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the traefik data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _traefik_ (or scroll the list) to locate the **traefik** collector.
143 5. Click the **+** next to the **traefik** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/typesense/integrations/typesense.md
+21 -4
@@ -88,6 +88,21 @@ There are no alerts configured by default for this integration.
88
89 ## Setup
90
91 +
92 +You can configure the **typesense** collector in two ways:
93 +
94 +| Method | Best for | How to |
95 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
96 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **typesense**, then click **+** to add a job. |
97 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/typesense.conf` and add a job. |
98 +
99 +:::important
100 +
101 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
102 +
103 +:::
104 +
105 +
106 ### Prerequisites
107
108 #### API Key Configuration
@@ -135,14 +150,16 @@ The following options can be defined globally: update_every, autodetection_retry
150
151 #### via UI
152
138 -The **typesense** collector can be configured directly through the Netdata web interface:
153 +Configure the **typesense** collector from the Netdata web interface:
154
155 1. Go to **Nodes**.
141 -2. Select the node **where you want the typesense data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
156 +2. Select the node **where you want the typesense data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
157 3. The **Collectors → Jobs** view opens by default.
158 4. In the Search box, type _typesense_ (or scroll the list) to locate the **typesense** collector.
159 5. Click the **+** next to the **typesense** collector to add a new job.
145 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
160 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
161 + - **Test** runs the job with the provided settings and shows whether data can be collected.
162 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
163
164
165 #### via File
@@ -156,7 +173,7 @@ update_every: 1
173 autodetection_retry: 0
174 jobs:
175 - name: some_name1
159 - - name: some_name1
176 + - name: some_name2
177 ```
178 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
179 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/unbound/integrations/unbound.md
+21 -4
@@ -123,6 +123,21 @@ There are no alerts configured by default for this integration.
123
124 ## Setup
125
126 +
127 +You can configure the **unbound** collector in two ways:
128 +
129 +| Method | Best for | How to |
130 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
131 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **unbound**, then click **+** to add a job. |
132 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/unbound.conf` and add a job. |
133 +
134 +:::important
135 +
136 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
137 +
138 +:::
139 +
140 +
141 ### Prerequisites
142
143 #### Enable remote control interface
@@ -180,14 +195,16 @@ The following options can be defined globally: update_every, autodetection_retry
195
196 #### via UI
197
183 -The **unbound** collector can be configured directly through the Netdata web interface:
198 +Configure the **unbound** collector from the Netdata web interface:
199
200 1. Go to **Nodes**.
186 -2. Select the node **where you want the unbound data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
201 +2. Select the node **where you want the unbound data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
202 3. The **Collectors → Jobs** view opens by default.
203 4. In the Search box, type _unbound_ (or scroll the list) to locate the **unbound** collector.
204 5. Click the **+** next to the **unbound** collector to add a new job.
190 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
205 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
206 + - **Test** runs the job with the provided settings and shows whether data can be collected.
207 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
208
209
210 #### via File
@@ -201,7 +218,7 @@ update_every: 1
218 autodetection_retry: 0
219 jobs:
220 - name: some_name1
204 - - name: some_name1
221 + - name: some_name2
222 ```
223 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
224 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/upsd/integrations/ups_nut.md
+21 -4
@@ -110,6 +110,21 @@ The following alerts are available:
110
111 ## Setup
112
113 +
114 +You can configure the **upsd** collector in two ways:
115 +
116 +| Method | Best for | How to |
117 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
118 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **upsd**, then click **+** to add a job. |
119 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/upsd.conf` and add a job. |
120 +
121 +:::important
122 +
123 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
124 +
125 +:::
126 +
127 +
128 ### Prerequisites
129
130 No action required.
@@ -135,14 +150,16 @@ The following options can be defined globally: update_every, autodetection_retry
150
151 #### via UI
152
138 -The **upsd** collector can be configured directly through the Netdata web interface:
153 +Configure the **upsd** collector from the Netdata web interface:
154
155 1. Go to **Nodes**.
141 -2. Select the node **where you want the upsd data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
156 +2. Select the node **where you want the upsd data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
157 3. The **Collectors → Jobs** view opens by default.
158 4. In the Search box, type _upsd_ (or scroll the list) to locate the **upsd** collector.
159 5. Click the **+** next to the **upsd** collector to add a new job.
145 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
160 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
161 + - **Test** runs the job with the provided settings and shows whether data can be collected.
162 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
163
164
165 #### via File
@@ -156,7 +173,7 @@ update_every: 1
173 autodetection_retry: 0
174 jobs:
175 - name: some_name1
159 - - name: some_name1
176 + - name: some_name2
177 ```
178 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
179 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/uwsgi/integrations/uwsgi.md
+21 -4
@@ -108,6 +108,21 @@ There are no alerts configured by default for this integration.
108
109 ## Setup
110
111 +
112 +You can configure the **uwsgi** collector in two ways:
113 +
114 +| Method | Best for | How to |
115 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
116 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **uwsgi**, then click **+** to add a job. |
117 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/uwsgi.conf` and add a job. |
118 +
119 +:::important
120 +
121 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
122 +
123 +:::
124 +
125 +
126 ### Prerequisites
127
128 #### Enable the uWSGI Stats Server
@@ -137,14 +152,16 @@ The following options can be defined globally: update_every, autodetection_retry
152
153 #### via UI
154
140 -The **uwsgi** collector can be configured directly through the Netdata web interface:
155 +Configure the **uwsgi** collector from the Netdata web interface:
156
157 1. Go to **Nodes**.
143 -2. Select the node **where you want the uwsgi data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
158 +2. Select the node **where you want the uwsgi data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
159 3. The **Collectors → Jobs** view opens by default.
160 4. In the Search box, type _uwsgi_ (or scroll the list) to locate the **uwsgi** collector.
161 5. Click the **+** next to the **uwsgi** collector to add a new job.
147 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
162 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
163 + - **Test** runs the job with the provided settings and shows whether data can be collected.
164 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
165
166
167 #### via File
@@ -158,7 +175,7 @@ update_every: 1
175 autodetection_retry: 0
176 jobs:
177 - name: some_name1
161 - - name: some_name1
178 + - name: some_name2
179 ```
180 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
181 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/varnish/integrations/varnish.md
+21 -4
@@ -119,6 +119,21 @@ There are no alerts configured by default for this integration.
119
120 ## Setup
121
122 +
123 +You can configure the **varnish** collector in two ways:
124 +
125 +| Method | Best for | How to |
126 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
127 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **varnish**, then click **+** to add a job. |
128 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/varnish.conf` and add a job. |
129 +
130 +:::important
131 +
132 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
133 +
134 +:::
135 +
136 +
137 ### Prerequisites
138
139 No action required.
@@ -144,14 +159,16 @@ The following options can be defined globally: update_every.
159
160 #### via UI
161
147 -The **varnish** collector can be configured directly through the Netdata web interface:
162 +Configure the **varnish** collector from the Netdata web interface:
163
164 1. Go to **Nodes**.
150 -2. Select the node **where you want the varnish data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
165 +2. Select the node **where you want the varnish data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
166 3. The **Collectors → Jobs** view opens by default.
167 4. In the Search box, type _varnish_ (or scroll the list) to locate the **varnish** collector.
168 5. Click the **+** next to the **varnish** collector to add a new job.
154 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
169 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
170 + - **Test** runs the job with the provided settings and shows whether data can be collected.
171 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
172
173
174 #### via File
@@ -165,7 +182,7 @@ update_every: 1
182 autodetection_retry: 0
183 jobs:
184 - name: some_name1
168 - - name: some_name1
185 + - name: some_name2
186 ```
187 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
188 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/vcsa/integrations/vcenter_server_appliance.md
+21 -4
@@ -137,6 +137,21 @@ The following alerts are available:
137
138 ## Setup
139
140 +
141 +You can configure the **vcsa** collector in two ways:
142 +
143 +| Method | Best for | How to |
144 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
145 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **vcsa**, then click **+** to add a job. |
146 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/vcsa.conf` and add a job. |
147 +
148 +:::important
149 +
150 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
151 +
152 +:::
153 +
154 +
155 ### Prerequisites
156
157 No action required.
@@ -175,14 +190,16 @@ The following options can be defined globally: update_every, autodetection_retry
190
191 #### via UI
192
178 -The **vcsa** collector can be configured directly through the Netdata web interface:
193 +Configure the **vcsa** collector from the Netdata web interface:
194
195 1. Go to **Nodes**.
181 -2. Select the node **where you want the vcsa data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
196 +2. Select the node **where you want the vcsa 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 _vcsa_ (or scroll the list) to locate the **vcsa** collector.
199 5. Click the **+** next to the **vcsa** collector to add a new job.
185 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
204
205 #### via File
@@ -196,7 +213,7 @@ update_every: 1
213 autodetection_retry: 0
214 jobs:
215 - name: some_name1
199 - - 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-a-configuration-file-using-edit-config) script from the
219 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/vernemq/integrations/vernemq.md
+21 -4
@@ -188,6 +188,21 @@ The following alerts are available:
188
189 ## Setup
190
191 +
192 +You can configure the **vernemq** collector in two ways:
193 +
194 +| Method | Best for | How to |
195 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
196 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **vernemq**, then click **+** to add a job. |
197 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/vernemq.conf` and add a job. |
198 +
199 +:::important
200 +
201 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
202 +
203 +:::
204 +
205 +
206 ### Prerequisites
207
208 No action required.
@@ -226,14 +241,16 @@ The following options can be defined globally: update_every, autodetection_retry
241
242 #### via UI
243
229 -The **vernemq** collector can be configured directly through the Netdata web interface:
244 +Configure the **vernemq** collector from the Netdata web interface:
245
246 1. Go to **Nodes**.
232 -2. Select the node **where you want the vernemq data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
247 +2. Select the node **where you want the vernemq data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
248 3. The **Collectors → Jobs** view opens by default.
249 4. In the Search box, type _vernemq_ (or scroll the list) to locate the **vernemq** collector.
250 5. Click the **+** next to the **vernemq** collector to add a new job.
236 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
251 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
252 + - **Test** runs the job with the provided settings and shows whether data can be collected.
253 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
254
255
256 #### via File
@@ -247,7 +264,7 @@ update_every: 1
264 autodetection_retry: 0
265 jobs:
266 - name: some_name1
250 - - name: some_name1
267 + - name: some_name2
268 ```
269 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
270 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/vsphere/integrations/vmware_vcenter_server.md
+21 -4
@@ -174,6 +174,21 @@ The following alerts are available:
174
175 ## Setup
176
177 +
178 +You can configure the **vsphere** collector in two ways:
179 +
180 +| Method | Best for | How to |
181 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
182 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **vsphere**, then click **+** to add a job. |
183 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/vsphere.conf` and add a job. |
184 +
185 +:::important
186 +
187 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
188 +
189 +:::
190 +
191 +
192 ### Prerequisites
193
194 No action required.
@@ -244,14 +259,16 @@ Metrics of VMs matching the selector will be collected.
259
260 #### via UI
261
247 -The **vsphere** collector can be configured directly through the Netdata web interface:
262 +Configure the **vsphere** collector from the Netdata web interface:
263
264 1. Go to **Nodes**.
250 -2. Select the node **where you want the vsphere data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
265 +2. Select the node **where you want the vsphere data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
266 3. The **Collectors → Jobs** view opens by default.
267 4. In the Search box, type _vsphere_ (or scroll the list) to locate the **vsphere** collector.
268 5. Click the **+** next to the **vsphere** collector to add a new job.
254 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
269 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
270 + - **Test** runs the job with the provided settings and shows whether data can be collected.
271 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
272
273
274 #### via File
@@ -265,7 +282,7 @@ update_every: 1
282 autodetection_retry: 0
283 jobs:
284 - name: some_name1
268 - - name: some_name1
285 + - name: some_name2
286 ```
287 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
288 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/w1sensor/integrations/1-wire_sensors.md
+21 -4
@@ -77,6 +77,21 @@ There are no alerts configured by default for this integration.
77
78 ## Setup
79
80 +
81 +You can configure the **w1sensor** collector in two ways:
82 +
83 +| Method | Best for | How to |
84 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
85 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **w1sensor**, then click **+** to add a job. |
86 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/w1sensor.conf` and add a job. |
87 +
88 +:::important
89 +
90 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
91 +
92 +:::
93 +
94 +
95 ### Prerequisites
96
97 #### Required Linux kernel modules
@@ -103,14 +118,16 @@ The following options can be defined globally: update_every.
118
119 #### via UI
120
106 -The **w1sensor** collector can be configured directly through the Netdata web interface:
121 +Configure the **w1sensor** collector from the Netdata web interface:
122
123 1. Go to **Nodes**.
109 -2. Select the node **where you want the w1sensor data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
124 +2. Select the node **where you want the w1sensor data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
125 3. The **Collectors → Jobs** view opens by default.
126 4. In the Search box, type _w1sensor_ (or scroll the list) to locate the **w1sensor** collector.
127 5. Click the **+** next to the **w1sensor** collector to add a new job.
113 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
128 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
129 + - **Test** runs the job with the provided settings and shows whether data can be collected.
130 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
131
132
133 #### via File
@@ -124,7 +141,7 @@ update_every: 1
141 autodetection_retry: 0
142 jobs:
143 - name: some_name1
127 - - name: some_name1
144 + - name: some_name2
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-a-configuration-file-using-edit-config) script from the
147 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/weblog/integrations/web_server_log_files.md
+21 -4
@@ -151,6 +151,21 @@ The following alerts are available:
151
152 ## Setup
153
154 +
155 +You can configure the **web_log** collector in two ways:
156 +
157 +| Method | Best for | How to |
158 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
159 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **web_log**, then click **+** to add a job. |
160 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/web_log.conf` and add a job. |
161 +
162 +:::important
163 +
164 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
165 +
166 +:::
167 +
168 +
169 ### Prerequisites
170
171 No action required.
@@ -327,14 +342,16 @@ regexp_config:
342
343 #### via UI
344
330 -The **web_log** collector can be configured directly through the Netdata web interface:
345 +Configure the **web_log** collector from the Netdata web interface:
346
347 1. Go to **Nodes**.
333 -2. Select the node **where you want the web_log data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
348 +2. Select the node **where you want the web_log data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
349 3. The **Collectors → Jobs** view opens by default.
350 4. In the Search box, type _web_log_ (or scroll the list) to locate the **web_log** collector.
351 5. Click the **+** next to the **web_log** collector to add a new job.
337 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
352 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
353 + - **Test** runs the job with the provided settings and shows whether data can be collected.
354 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
355
356
357 #### via File
@@ -348,7 +365,7 @@ update_every: 1
365 autodetection_retry: 0
366 jobs:
367 - name: some_name1
351 - - name: some_name1
368 + - name: some_name2
369 ```
370 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
371 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/whoisquery/integrations/domain_expiration_date.md
+21 -4
@@ -84,6 +84,21 @@ The following alerts are available:
84
85 ## Setup
86
87 +
88 +You can configure the **whoisquery** collector in two ways:
89 +
90 +| Method | Best for | How to |
91 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
92 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **whoisquery**, then click **+** to add a job. |
93 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/whoisquery.conf` and add a job. |
94 +
95 +:::important
96 +
97 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
98 +
99 +:::
100 +
101 +
102 ### Prerequisites
103
104 No action required.
@@ -111,14 +126,16 @@ The following options can be defined globally: update_every, autodetection_retry
126
127 #### via UI
128
114 -The **whoisquery** collector can be configured directly through the Netdata web interface:
129 +Configure the **whoisquery** collector from the Netdata web interface:
130
131 1. Go to **Nodes**.
117 -2. Select the node **where you want the whoisquery data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
132 +2. Select the node **where you want the whoisquery 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 _whoisquery_ (or scroll the list) to locate the **whoisquery** collector.
135 5. Click the **+** next to the **whoisquery** collector to add a new job.
121 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -132,7 +149,7 @@ update_every: 1
149 autodetection_retry: 0
150 jobs:
151 - name: some_name1
135 - - 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-a-configuration-file-using-edit-config) script from the
155 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/wireguard/integrations/wireguard.md
+21 -4
@@ -103,6 +103,21 @@ There are no alerts configured by default for this integration.
103
104 ## Setup
105
106 +
107 +You can configure the **wireguard** collector in two ways:
108 +
109 +| Method | Best for | How to |
110 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
111 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **wireguard**, then click **+** to add a job. |
112 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/wireguard.conf` and add a job. |
113 +
114 +:::important
115 +
116 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
117 +
118 +:::
119 +
120 +
121 ### Prerequisites
122
123 No action required.
@@ -126,14 +141,16 @@ The following options can be defined globally: update_every, autodetection_retry
141
142 #### via UI
143
129 -The **wireguard** collector can be configured directly through the Netdata web interface:
144 +Configure the **wireguard** collector from the Netdata web interface:
145
146 1. Go to **Nodes**.
132 -2. Select the node **where you want the wireguard data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
147 +2. Select the node **where you want the wireguard data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
148 3. The **Collectors → Jobs** view opens by default.
149 4. In the Search box, type _wireguard_ (or scroll the list) to locate the **wireguard** collector.
150 5. Click the **+** next to the **wireguard** collector to add a new job.
136 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
151 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
152 + - **Test** runs the job with the provided settings and shows whether data can be collected.
153 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
154
155
156 #### via File
@@ -147,7 +164,7 @@ update_every: 1
164 autodetection_retry: 0
165 jobs:
166 - name: some_name1
150 - - name: some_name1
167 + - name: some_name2
168 ```
169 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
170 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/x509check/integrations/x.509_certificate.md
+21 -4
@@ -88,6 +88,21 @@ The following alerts are available:
88
89 ## Setup
90
91 +
92 +You can configure the **x509check** collector in two ways:
93 +
94 +| Method | Best for | How to |
95 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
96 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **x509check**, then click **+** to add a job. |
97 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/x509check.conf` and add a job. |
98 +
99 +:::important
100 +
101 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
102 +
103 +:::
104 +
105 +
106 ### Prerequisites
107
108 No action required.
@@ -119,14 +134,16 @@ The following options can be defined globally: update_every, autodetection_retry
134
135 #### via UI
136
122 -The **x509check** collector can be configured directly through the Netdata web interface:
137 +Configure the **x509check** collector from the Netdata web interface:
138
139 1. Go to **Nodes**.
125 -2. Select the node **where you want the x509check data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
140 +2. Select the node **where you want the x509check data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
141 3. The **Collectors → Jobs** view opens by default.
142 4. In the Search box, type _x509check_ (or scroll the list) to locate the **x509check** collector.
143 5. Click the **+** next to the **x509check** collector to add a new job.
129 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
144 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
145 + - **Test** runs the job with the provided settings and shows whether data can be collected.
146 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
147
148
149 #### via File
@@ -140,7 +157,7 @@ update_every: 1
157 autodetection_retry: 0
158 jobs:
159 - name: some_name1
143 - - name: some_name1
160 + - name: some_name2
161 ```
162 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
163 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/yugabytedb/integrations/yugabytedb.md
+21 -4
@@ -334,6 +334,21 @@ There are no alerts configured by default for this integration.
334
335 ## Setup
336
337 +
338 +You can configure the **yugabytedb** collector in two ways:
339 +
340 +| Method | Best for | How to |
341 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
342 +| [**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. |
343 +| [**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. |
344 +
345 +:::important
346 +
347 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
348 +
349 +:::
350 +
351 +
352 ### Prerequisites
353
354 No action required.
@@ -372,14 +387,16 @@ The following options can be defined globally: update_every, autodetection_retry
387
388 #### via UI
389
375 -The **yugabytedb** collector can be configured directly through the Netdata web interface:
390 +Configure the **yugabytedb** collector from the Netdata web interface:
391
392 1. Go to **Nodes**.
378 -2. Select the node **where you want the yugabytedb data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
393 +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.
394 3. The **Collectors → Jobs** view opens by default.
395 4. In the Search box, type _yugabytedb_ (or scroll the list) to locate the **yugabytedb** collector.
396 5. Click the **+** next to the **yugabytedb** collector to add a new job.
382 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
397 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
398 + - **Test** runs the job with the provided settings and shows whether data can be collected.
399 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
400
401
402 #### via File
@@ -393,7 +410,7 @@ update_every: 1
410 autodetection_retry: 0
411 jobs:
412 - name: some_name1
396 - - name: some_name1
413 + - name: some_name2
414 ```
415 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
416 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/zfspool/integrations/zfs_pools.md
+21 -4
@@ -110,6 +110,21 @@ The following alerts are available:
110
111 ## Setup
112
113 +
114 +You can configure the **zfspool** collector in two ways:
115 +
116 +| Method | Best for | How to |
117 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
118 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **zfspool**, then click **+** to add a job. |
119 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/zfspool.conf` and add a job. |
120 +
121 +:::important
122 +
123 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
124 +
125 +:::
126 +
127 +
128 ### Prerequisites
129
130 No action required.
@@ -134,14 +149,16 @@ The following options can be defined globally: update_every.
149
150 #### via UI
151
137 -The **zfspool** collector can be configured directly through the Netdata web interface:
152 +Configure the **zfspool** collector from the Netdata web interface:
153
154 1. Go to **Nodes**.
140 -2. Select the node **where you want the zfspool data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
155 +2. Select the node **where you want the zfspool 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 _zfspool_ (or scroll the list) to locate the **zfspool** collector.
158 5. Click the **+** next to the **zfspool** collector to add a new job.
144 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
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
@@ -155,7 +172,7 @@ update_every: 1
172 autodetection_retry: 0
173 jobs:
174 - name: some_name1
158 - - 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-a-configuration-file-using-edit-config) script from the
178 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/go/plugin/go.d/collector/zookeeper/integrations/zookeeper.md
+21 -4
@@ -97,6 +97,21 @@ There are no alerts configured by default for this integration.
97
98 ## Setup
99
100 +
101 +You can configure the **zookeeper** collector in two ways:
102 +
103 +| Method | Best for | How to |
104 +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
105 +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **zookeeper**, then click **+** to add a job. |
106 +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/zookeeper.conf` and add a job. |
107 +
108 +:::important
109 +
110 +UI configuration requires paid Netdata Cloud plan. File-based configuration uses the same options and is useful if you prefer configuring via file or need to automate deployments.
111 +
112 +:::
113 +
114 +
115 ### Prerequisites
116
117 #### Whitelist `mntr` command
@@ -131,14 +146,16 @@ The following options can be defined globally: update_every, autodetection_retry
146
147 #### via UI
148
134 -The **zookeeper** collector can be configured directly through the Netdata web interface:
149 +Configure the **zookeeper** collector from the Netdata web interface:
150
151 1. Go to **Nodes**.
137 -2. Select the node **where you want the zookeeper data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
152 +2. Select the node **where you want the zookeeper data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection.
153 3. The **Collectors → Jobs** view opens by default.
154 4. In the Search box, type _zookeeper_ (or scroll the list) to locate the **zookeeper** collector.
155 5. Click the **+** next to the **zookeeper** collector to add a new job.
141 -6. Fill in the job fields, then **Test** the configuration and **Submit**.
156 +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save.
157 + - **Test** runs the job with the provided settings and shows whether data can be collected.
158 + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.
159
160
161 #### via File
@@ -152,7 +169,7 @@ update_every: 1
169 autodetection_retry: 0
170 jobs:
171 - name: some_name1
155 - - name: some_name1
172 + - name: some_name2
173 ```
174 You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
175 Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
src/health/notifications/alerta/README.md
+1
@@ -22,6 +22,7 @@ You can send Netdata alerts to Alerta to see alerts coming from many Netdata hos
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/awssns/README.md
+1
@@ -37,6 +37,7 @@ You can send notifications through Amazon SNS using Netdata's Agent alert notifi
37
38 ## Setup
39
40 +
41 ### Prerequisites
42
43 ####
src/health/notifications/custom/README.md
+1
@@ -21,6 +21,7 @@ Netdata Agent's alert notification feature allows you to send custom notificatio
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/discord/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Discord using Netdata's Agent alert notification feature,
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/dynatrace/README.md
+1
@@ -22,6 +22,7 @@ You can send notifications to Dynatrace using Netdata's Agent alert notification
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/email/README.md
+1
@@ -21,6 +21,7 @@ Send notifications via Email using Netdata's Agent alert notification feature, w
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/flock/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Flock using Netdata's Agent alert notification feature, wh
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/gotify/README.md
+1
@@ -22,6 +22,7 @@ You can send alerts to your Gotify instance using Netdata's Agent alert notifica
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/ilert/README.md
+1
@@ -22,6 +22,7 @@ Sending notification to ilert via Netdata's Agent alert notification feature inc
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/irc/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to IRC using Netdata's Agent alert notification feature, whic
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/kavenegar/README.md
+1
@@ -22,6 +22,7 @@ You can send notifications to Kavenegar using Netdata's Agent alert notification
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/matrix/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Matrix network rooms using Netdata's Agent alert notificat
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/messagebird/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to MessageBird using Netdata's Agent alert notification featu
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/msteams/README.md
+1
@@ -21,6 +21,7 @@ You can send Netdata alerts to Microsoft Teams using Netdata's Agent alert notif
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/ntfy/README.md
+1
@@ -22,6 +22,7 @@ You can send alerts to an ntfy server using Netdata's Agent alert notification f
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/opsgenie/README.md
+1
@@ -22,6 +22,7 @@ You can send notifications to Opsgenie using Netdata's Agent alert notification
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/pagerduty/README.md
+1
@@ -22,6 +22,7 @@ You can send notifications to PagerDuty using Netdata's Agent alert notification
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/prowl/README.md
+1
@@ -27,6 +27,7 @@ Send notifications to Prowl using Netdata's Agent alert notification feature, wh
27
28 ## Setup
29
30 +
31 ### Prerequisites
32
33 ####
src/health/notifications/pushbullet/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Pushbullet using Netdata's Agent alert notification featur
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/pushover/README.md
+1
@@ -24,6 +24,7 @@ Send notification to Pushover using Netdata's Agent alert notification feature,
24
25 ## Setup
26
27 +
28 ### Prerequisites
29
30 ####
src/health/notifications/rocketchat/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Rocket.Chat using Netdata's Agent alert notification featu
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/signl4/README.md
+1
@@ -22,6 +22,7 @@ You can send notifications to SIGNL4 using Netdata's Agent alert notification fe
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/slack/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to a Slack workspace using Netdata's Agent alert notification
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/smseagle/README.md
+1
@@ -21,6 +21,7 @@ Forward notifications to SMSEagle device to send SMS, MMS, wake-up, or text-to-s
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/smstools3/README.md
+1
@@ -22,6 +22,7 @@ The SMS Server Tools 3 is a SMS Gateway software which can send and receive shor
22
23 ## Setup
24
25 +
26 ### Prerequisites
27
28 ####
src/health/notifications/syslog/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Syslog using Netdata's Agent alert notification feature, w
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/telegram/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Telegram using Netdata's Agent alert notification feature,
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####
src/health/notifications/twilio/README.md
+1
@@ -21,6 +21,7 @@ Send notifications to Twilio using Netdata's Agent alert notification feature, w
21
22 ## Setup
23
24 +
25 ### Prerequisites
26
27 ####