Regenerate integrations docs (#20976)
Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>
Netdata bot committed
Sep 14, 2025 at 12:21 UTC
a30308e8a034db91e26c91b770c5046a8d55878d
596 files changed
+18502
-12292
src/collectors/apps.plugin/integrations/applications.md
+7
-4
@@ -99,16 +99,19 @@ No action required.
99
100
### Configuration
101
102
-#### File
103
-
104
-There is no configuration file.
102
#### Options
103
104
105
106
There are no configuration options.
107
111
-#### Examples
108
+
109
+
110
+#### via File
111
+
112
+There is no configuration file.
113
+
114
+##### Examples
115
There are no configuration examples.
116
117
src/collectors/apps.plugin/integrations/user_groups.md
+7
-4
@@ -99,16 +99,19 @@ No action required.
99
100
### Configuration
101
102
-#### File
103
-
104
-There is no configuration file.
102
#### Options
103
104
105
106
There are no configuration options.
107
111
-#### Examples
108
+
109
+
110
+#### via File
111
+
112
+There is no configuration file.
113
+
114
+##### Examples
115
There are no configuration examples.
116
117
src/collectors/apps.plugin/integrations/users.md
+7
-4
@@ -99,16 +99,19 @@ No action required.
99
100
### Configuration
101
102
-#### File
103
-
104
-There is no configuration file.
102
#### Options
103
104
105
106
There are no configuration options.
107
111
-#### Examples
108
+
109
+
110
+#### via File
111
+
112
+There is no configuration file.
113
+
114
+##### Examples
115
There are no configuration examples.
116
117
src/collectors/cgroups.plugin/integrations/containers.md
+7
-4
@@ -154,16 +154,19 @@ No action required.
154
155
### Configuration
156
157
-#### File
158
-
159
-There is no configuration file.
157
#### Options
158
159
160
161
There are no configuration options.
162
166
-#### Examples
163
+
164
+
165
+#### via File
166
+
167
+There is no configuration file.
168
+
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/cgroups.plugin/integrations/kubernetes_containers.md
+7
-4
@@ -168,16 +168,19 @@ No action required.
168
169
### Configuration
170
171
-#### File
172
-
173
-There is no configuration file.
171
#### Options
172
173
174
175
There are no configuration options.
176
180
-#### Examples
177
+
178
+
179
+#### via File
180
+
181
+There is no configuration file.
182
+
183
+##### Examples
184
There are no configuration examples.
185
186
src/collectors/cgroups.plugin/integrations/libvirt_containers.md
+7
-4
@@ -154,16 +154,19 @@ No action required.
154
155
### Configuration
156
157
-#### File
158
-
159
-There is no configuration file.
157
#### Options
158
159
160
161
There are no configuration options.
162
166
-#### Examples
163
+
164
+
165
+#### via File
166
+
167
+There is no configuration file.
168
+
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/cgroups.plugin/integrations/lxc_containers.md
+7
-4
@@ -154,16 +154,19 @@ No action required.
154
155
### Configuration
156
157
-#### File
158
-
159
-There is no configuration file.
157
#### Options
158
159
160
161
There are no configuration options.
162
166
-#### Examples
163
+
164
+
165
+#### via File
166
+
167
+There is no configuration file.
168
+
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/cgroups.plugin/integrations/ovirt_containers.md
+7
-4
@@ -154,16 +154,19 @@ No action required.
154
155
### Configuration
156
157
-#### File
158
-
159
-There is no configuration file.
157
#### Options
158
159
160
161
There are no configuration options.
162
166
-#### Examples
163
+
164
+
165
+#### via File
166
+
167
+There is no configuration file.
168
+
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/cgroups.plugin/integrations/proxmox_containers.md
+7
-4
@@ -154,16 +154,19 @@ No action required.
154
155
### Configuration
156
157
-#### File
158
-
159
-There is no configuration file.
157
#### Options
158
159
160
161
There are no configuration options.
162
166
-#### Examples
163
+
164
+
165
+#### via File
166
+
167
+There is no configuration file.
168
+
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/cgroups.plugin/integrations/systemd_services.md
+7
-4
@@ -97,16 +97,19 @@ No action required.
97
98
### Configuration
99
100
-#### File
101
-
102
-There is no configuration file.
100
#### Options
101
102
103
104
There are no configuration options.
105
109
-#### Examples
106
+
107
+
108
+#### via File
109
+
110
+There is no configuration file.
111
+
112
+##### Examples
113
There are no configuration examples.
114
115
src/collectors/cgroups.plugin/integrations/virtual_machines.md
+7
-4
@@ -154,16 +154,19 @@ No action required.
154
155
### Configuration
156
157
-#### File
158
-
159
-There is no configuration file.
157
#### Options
158
159
160
161
There are no configuration options.
162
166
-#### Examples
163
+
164
+
165
+#### via File
166
+
167
+There is no configuration file.
168
+
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/charts.d.plugin/libreswan/integrations/libreswan.md
+22
-19
@@ -110,23 +110,6 @@ Make sure the path `/sbin/ipsec` matches your setup (execute `which ipsec` to fi
110
111
### Configuration
112
113
-#### File
114
-
115
-The configuration file name for this integration is `charts.d/libreswan.conf`.
116
-
117
-The file format is POSIX shell script. Generally, the structure is:
118
-
119
-```sh
120
-OPTION_1="some value"
121
-OPTION_2="some other value"
122
-```
123
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
124
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
-
126
-```bash
127
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
128
-sudo ./edit-config charts.d/libreswan.conf
129
-```
113
#### Options
114
115
The config file is sourced by the charts.d plugin. It's a standard bash file.
@@ -145,9 +128,29 @@ The following collapsed table contains all the options that can be configured fo
128
129
</details>
130
148
-#### Examples
131
150
-##### Run `ipsec` without sudo
132
+
133
+#### via File
134
+
135
+The configuration file name for this integration is `charts.d/libreswan.conf`.
136
+
137
+The file format is POSIX shell script. Generally, the structure is:
138
+
139
+```sh
140
+OPTION_1="some value"
141
+OPTION_2="some other value"
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).
145
+
146
+```bash
147
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
148
+sudo ./edit-config charts.d/libreswan.conf
149
+```
150
+
151
+##### Examples
152
+
153
+###### Run `ipsec` without sudo
154
155
Run the `ipsec` utility without sudo
156
src/collectors/charts.d.plugin/opensips/integrations/opensips.md
+22
-19
@@ -106,23 +106,6 @@ The collector requires the `opensipsctl` to be installed.
106
107
### Configuration
108
109
-#### File
110
-
111
-The configuration file name for this integration is `charts.d/opensips.conf`.
112
-
113
-The file format is POSIX shell script. Generally, the structure is:
114
-
115
-```sh
116
-OPTION_1="some value"
117
-OPTION_2="some other value"
118
-```
119
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
120
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
-
122
-```bash
123
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
124
-sudo ./edit-config charts.d/opensips.conf
125
-```
109
#### Options
110
111
The config file is sourced by the charts.d plugin. It's a standard bash file.
@@ -143,9 +126,29 @@ The following collapsed table contains all the options that can be configured fo
126
127
</details>
128
146
-#### Examples
129
148
-##### Custom `opensipsctl` command
130
+
131
+#### via File
132
+
133
+The configuration file name for this integration is `charts.d/opensips.conf`.
134
+
135
+The file format is POSIX shell script. Generally, the structure is:
136
+
137
+```sh
138
+OPTION_1="some value"
139
+OPTION_2="some other value"
140
+```
141
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
142
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
143
+
144
+```bash
145
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
146
+sudo ./edit-config charts.d/opensips.conf
147
+```
148
+
149
+##### Examples
150
+
151
+###### Custom `opensipsctl` command
152
153
Set a custom path to the `opensipsctl` command
154
src/collectors/cups.plugin/integrations/cups.md
+17
-14
@@ -100,7 +100,22 @@ The CUPS server must be installed and running. If you installed `netdata` using
100
101
### Configuration
102
103
-#### File
103
+#### Options
104
+
105
+
106
+
107
+<details open><summary>Config options</summary>
108
+
109
+| Name | Description | Default | Required |
110
+|:----|:-----------|:-------|:--------:|
111
+| update every | Data collection frequency. | 1 | no |
112
+| command options | Additional parameters for the collector | | no |
113
+
114
+</details>
115
+
116
+
117
+
118
+#### via File
119
120
The configuration file name for this integration is `netdata.conf`.
121
Configuration for this specific integration is located in the `[plugin:cups]` section within that file.
@@ -122,20 +137,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
137
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
138
sudo ./edit-config netdata.conf
139
```
125
-#### Options
126
-
127
-
128
-
129
-<details open><summary>Config options</summary>
130
-
131
-| Name | Description | Default | Required |
132
-|:----|:-----------|:-------|:--------:|
133
-| update every | Data collection frequency. | 1 | no |
134
-| command options | Additional parameters for the collector | | no |
135
-
136
-</details>
140
138
-#### Examples
141
+##### Examples
142
There are no configuration examples.
143
144
src/collectors/debugfs.plugin/integrations/linux_zswap.md
+17
-14
@@ -97,7 +97,22 @@ The debugfs filesystem must be mounted on your host for plugin to collect data.
97
98
### Configuration
99
100
-#### File
100
+#### Options
101
+
102
+
103
+
104
+<details open><summary>Config options</summary>
105
+
106
+| Name | Description | Default | Required |
107
+|:----|:-----------|:-------|:--------:|
108
+| update every | Data collection frequency. | 1 | no |
109
+| command options | Additinal parameters for collector | | no |
110
+
111
+</details>
112
+
113
+
114
+
115
+#### via File
116
117
The configuration file name for this integration is `netdata.conf`.
118
Configuration for this specific integration is located in the `[plugin:debugfs]` section within that file.
@@ -119,20 +134,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
134
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
135
sudo ./edit-config netdata.conf
136
```
122
-#### Options
123
-
124
-
125
-
126
-<details open><summary>Config options</summary>
127
-
128
-| Name | Description | Default | Required |
129
-|:----|:-----------|:-------|:--------:|
130
-| update every | Data collection frequency. | 1 | no |
131
-| command options | Additinal parameters for collector | | no |
132
-
133
-</details>
137
135
-#### Examples
138
+##### Examples
139
There are no configuration examples.
140
141
src/collectors/debugfs.plugin/integrations/power_capping.md
+17
-14
@@ -91,7 +91,22 @@ The debugfs filesystem must be mounted on your host for plugin to collect data.
91
92
### Configuration
93
94
-#### File
94
+#### Options
95
+
96
+
97
+
98
+<details open><summary>Config options</summary>
99
+
100
+| Name | Description | Default | Required |
101
+|:----|:-----------|:-------|:--------:|
102
+| update every | Data collection frequency. | 1 | no |
103
+| command options | Additinal parameters for collector | | no |
104
+
105
+</details>
106
+
107
+
108
+
109
+#### via File
110
111
The configuration file name for this integration is `netdata.conf`.
112
Configuration for this specific integration is located in the `[plugin:debugfs]` section within that file.
@@ -113,20 +128,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
128
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
129
sudo ./edit-config netdata.conf
130
```
116
-#### Options
117
-
118
-
119
-
120
-<details open><summary>Config options</summary>
121
-
122
-| Name | Description | Default | Required |
123
-|:----|:-----------|:-------|:--------:|
124
-| update every | Data collection frequency. | 1 | no |
125
-| command options | Additinal parameters for collector | | no |
126
-
127
-</details>
131
129
-#### Examples
132
+##### Examples
133
There are no configuration examples.
134
135
src/collectors/debugfs.plugin/integrations/system_memory_fragmentation.md
+17
-14
@@ -95,7 +95,22 @@ The debugfs filesystem must be mounted on your host for plugin to collect data.
95
96
### Configuration
97
98
-#### File
98
+#### Options
99
+
100
+
101
+
102
+<details open><summary>Config options</summary>
103
+
104
+| Name | Description | Default | Required |
105
+|:----|:-----------|:-------|:--------:|
106
+| update every | Data collection frequency. | 1 | no |
107
+| command options | Additinal parameters for collector | | no |
108
+
109
+</details>
110
+
111
+
112
+
113
+#### via File
114
115
The configuration file name for this integration is `netdata.conf`.
116
Configuration for this specific integration is located in the `[plugin:debugfs]` section within that file.
@@ -117,20 +132,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
132
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
133
sudo ./edit-config netdata.conf
134
```
120
-#### Options
121
-
122
-
123
-
124
-<details open><summary>Config options</summary>
125
-
126
-| Name | Description | Default | Required |
127
-|:----|:-----------|:-------|:--------:|
128
-| update every | Data collection frequency. | 1 | no |
129
-| command options | Additinal parameters for collector | | no |
130
-
131
-</details>
135
133
-#### Examples
136
+##### Examples
137
There are no configuration examples.
138
139
src/collectors/diskspace.plugin/integrations/disk_space.md
+23
-20
@@ -93,7 +93,28 @@ No action required.
93
94
### Configuration
95
96
-#### File
96
+#### Options
97
+
98
+You can also specify per mount point `[plugin:proc:diskspace:mountpoint]`
99
+
100
+<details open><summary>Config options</summary>
101
+
102
+| Name | Description | Default | Required |
103
+|:----|:-----------|:-------|:--------:|
104
+| update every | Data collection frequency. | 1 | no |
105
+| remove charts of unmounted disks | Remove chart when a device is unmounted on host. | yes | no |
106
+| check for new mount points every | Parse proc files frequency. | 15s | no |
107
+| exclude space metrics on paths | Do not show metrics (charts) for listed paths. This option accepts netdata simple pattern. | /proc/* /sys/* /var/run/user/* /run/user/* /snap/* /var/lib/docker/* | no |
108
+| exclude space metrics on filesystems | Do not show metrics (charts) for listed filesystems. This option accepts netdata simple pattern. | *gvfs *gluster* *s3fs *ipfs *davfs2 *httpfs *sshfs *gdfs *moosefs fusectl autofs | no |
109
+| exclude inode metrics on filesystems | Do not show metrics (charts) for listed filesystems. This option accepts netdata simple pattern. | msdosfs msdos vfat overlayfs aufs* *unionfs | no |
110
+| space usage for all disks | Define if plugin will show metrics for space usage. When value is set to `auto` plugin will try to access information to display if filesystem or path was not discarded with previous option. | auto | no |
111
+| inodes usage for all disks | Define if plugin will show metrics for inode usage. When value is set to `auto` plugin will try to access information to display if filesystem or path was not discarded with previous option. | auto | no |
112
+
113
+</details>
114
+
115
+
116
+
117
+#### via File
118
119
The configuration file name for this integration is `netdata.conf`.
120
Configuration for this specific integration is located in the `[plugin:proc:diskspace]` section within that file.
@@ -115,26 +136,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
136
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
137
sudo ./edit-config netdata.conf
138
```
118
-#### Options
119
-
120
-You can also specify per mount point `[plugin:proc:diskspace:mountpoint]`
121
-
122
-<details open><summary>Config options</summary>
123
-
124
-| Name | Description | Default | Required |
125
-|:----|:-----------|:-------|:--------:|
126
-| update every | Data collection frequency. | 1 | no |
127
-| remove charts of unmounted disks | Remove chart when a device is unmounted on host. | yes | no |
128
-| check for new mount points every | Parse proc files frequency. | 15s | no |
129
-| exclude space metrics on paths | Do not show metrics (charts) for listed paths. This option accepts netdata simple pattern. | /proc/* /sys/* /var/run/user/* /run/user/* /snap/* /var/lib/docker/* | no |
130
-| exclude space metrics on filesystems | Do not show metrics (charts) for listed filesystems. This option accepts netdata simple pattern. | *gvfs *gluster* *s3fs *ipfs *davfs2 *httpfs *sshfs *gdfs *moosefs fusectl autofs | no |
131
-| exclude inode metrics on filesystems | Do not show metrics (charts) for listed filesystems. This option accepts netdata simple pattern. | msdosfs msdos vfat overlayfs aufs* *unionfs | no |
132
-| space usage for all disks | Define if plugin will show metrics for space usage. When value is set to `auto` plugin will try to access information to display if filesystem or path was not discarded with previous option. | auto | no |
133
-| inodes usage for all disks | Define if plugin will show metrics for inode usage. When value is set to `auto` plugin will try to access information to display if filesystem or path was not discarded with previous option. | auto | no |
134
-
135
-</details>
139
137
-#### Examples
140
+##### Examples
141
There are no configuration examples.
142
143
src/collectors/ebpf.plugin/integrations/ebpf_cachestat.md
+25
-22
@@ -140,27 +140,6 @@ Now follow steps:
140
141
### Configuration
142
143
-#### File
144
-
145
-The configuration file name for this integration is `ebpf.d/cachestat.conf`.
146
-
147
-The file format is a modified INI syntax. The general structure is:
148
-
149
-```ini
150
-[section1]
151
- option1 = some value
152
- option2 = some other value
153
-
154
-[section2]
155
- option3 = some third value
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).
159
-
160
-```bash
161
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
162
-sudo ./edit-config ebpf.d/cachestat.conf
163
-```
143
#### Options
144
145
All options are defined inside section `[global]`.
@@ -182,7 +161,31 @@ All options are defined inside section `[global]`.
161
162
</details>
163
185
-#### Examples
164
+
165
+
166
+#### via File
167
+
168
+The configuration file name for this integration is `ebpf.d/cachestat.conf`.
169
+
170
+The file format is a modified INI syntax. The general structure is:
171
+
172
+```ini
173
+[section1]
174
+ option1 = some value
175
+ option2 = some other value
176
+
177
+[section2]
178
+ option3 = some third value
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).
182
+
183
+```bash
184
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
185
+sudo ./edit-config ebpf.d/cachestat.conf
186
+```
187
+
188
+##### Examples
189
There are no configuration examples.
190
191
src/collectors/ebpf.plugin/integrations/ebpf_dcstat.md
+25
-22
@@ -138,27 +138,6 @@ Now follow steps:
138
139
### Configuration
140
141
-#### File
142
-
143
-The configuration file name for this integration is `ebpf.d/dcstat.conf`.
144
-
145
-The file format is a modified INI syntax. The general structure is:
146
-
147
-```ini
148
-[section1]
149
- option1 = some value
150
- option2 = some other value
151
-
152
-[section2]
153
- option3 = some third value
154
-```
155
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
156
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
157
-
158
-```bash
159
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
-sudo ./edit-config ebpf.d/dcstat.conf
161
-```
141
#### Options
142
143
All options are defined inside section `[global]`.
@@ -180,7 +159,31 @@ All options are defined inside section `[global]`.
159
160
</details>
161
183
-#### Examples
162
+
163
+
164
+#### via File
165
+
166
+The configuration file name for this integration is `ebpf.d/dcstat.conf`.
167
+
168
+The file format is a modified INI syntax. The general structure is:
169
+
170
+```ini
171
+[section1]
172
+ option1 = some value
173
+ option2 = some other value
174
+
175
+[section2]
176
+ option3 = some third value
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).
180
+
181
+```bash
182
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
183
+sudo ./edit-config ebpf.d/dcstat.conf
184
+```
185
+
186
+##### Examples
187
There are no configuration examples.
188
189
src/collectors/ebpf.plugin/integrations/ebpf_disk.md
+19
-16
@@ -104,7 +104,24 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
104
105
### Configuration
106
107
-#### File
107
+#### Options
108
+
109
+All options are defined inside section `[global]`.
110
+
111
+
112
+<details open><summary>Config options</summary>
113
+
114
+| Name | Description | Default | Required |
115
+|:----|:-----------|:-------|:--------:|
116
+| update every | Data collection frequency. | 5 | no |
117
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
118
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
119
+
120
+</details>
121
+
122
+
123
+
124
+#### via File
125
126
The configuration file name for this integration is `ebpf.d/disk.conf`.
127
@@ -125,22 +142,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
142
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
143
sudo ./edit-config ebpf.d/disk.conf
144
```
128
-#### Options
129
-
130
-All options are defined inside section `[global]`.
131
-
132
-
133
-<details open><summary>Config options</summary>
134
-
135
-| Name | Description | Default | Required |
136
-|:----|:-----------|:-------|:--------:|
137
-| update every | Data collection frequency. | 5 | no |
138
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
139
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
140
-
141
-</details>
145
143
-#### Examples
146
+##### Examples
147
There are no configuration examples.
148
149
src/collectors/ebpf.plugin/integrations/ebpf_filedescriptor.md
+25
-22
@@ -138,27 +138,6 @@ Now follow steps:
138
139
### Configuration
140
141
-#### File
142
-
143
-The configuration file name for this integration is `ebpf.d/fd.conf`.
144
-
145
-The file format is a modified INI syntax. The general structure is:
146
-
147
-```ini
148
-[section1]
149
- option1 = some value
150
- option2 = some other value
151
-
152
-[section2]
153
- option3 = some third value
154
-```
155
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
156
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
157
-
158
-```bash
159
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
-sudo ./edit-config ebpf.d/fd.conf
161
-```
141
#### Options
142
143
All options are defined inside section `[global]`.
@@ -180,7 +159,31 @@ All options are defined inside section `[global]`.
159
160
</details>
161
183
-#### Examples
162
+
163
+
164
+#### via File
165
+
166
+The configuration file name for this integration is `ebpf.d/fd.conf`.
167
+
168
+The file format is a modified INI syntax. The general structure is:
169
+
170
+```ini
171
+[section1]
172
+ option1 = some value
173
+ option2 = some other value
174
+
175
+[section2]
176
+ option3 = some third value
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).
180
+
181
+```bash
182
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
183
+sudo ./edit-config ebpf.d/fd.conf
184
+```
185
+
186
+##### Examples
187
There are no configuration examples.
188
189
src/collectors/ebpf.plugin/integrations/ebpf_filesystem.md
+24
-21
@@ -125,7 +125,29 @@ Now follow steps:
125
126
### Configuration
127
128
-#### File
128
+#### Options
129
+
130
+This configuration file have two different sections. The `[global]` overwrites default options, while `[filesystem]` allow user to select the filesystems to monitor.
131
+
132
+
133
+<details open><summary>Config options</summary>
134
+
135
+| Name | Description | Default | Required |
136
+|:----|:-----------|:-------|:--------:|
137
+| update every | Data collection frequency. | 5 | no |
138
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
139
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
140
+| btrfsdist | Enable or disable latency monitoring for functions associated with btrfs filesystem. | yes | no |
141
+| ext4dist | Enable or disable latency monitoring for functions associated with ext4 filesystem. | yes | no |
142
+| nfsdist | Enable or disable latency monitoring for functions associated with nfs filesystem. | yes | no |
143
+| xfsdist | Enable or disable latency monitoring for functions associated with xfs filesystem. | yes | no |
144
+| zfsdist | Enable or disable latency monitoring for functions associated with zfs filesystem. | yes | no |
145
+
146
+</details>
147
+
148
+
149
+
150
+#### via File
151
152
The configuration file name for this integration is `ebpf.d/filesystem.conf`.
153
@@ -146,27 +168,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
168
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
169
sudo ./edit-config ebpf.d/filesystem.conf
170
```
149
-#### Options
150
-
151
-This configuration file have two different sections. The `[global]` overwrites default options, while `[filesystem]` allow user to select the filesystems to monitor.
152
-
153
-
154
-<details open><summary>Config options</summary>
155
-
156
-| Name | Description | Default | Required |
157
-|:----|:-----------|:-------|:--------:|
158
-| update every | Data collection frequency. | 5 | no |
159
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
160
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
161
-| btrfsdist | Enable or disable latency monitoring for functions associated with btrfs filesystem. | yes | no |
162
-| ext4dist | Enable or disable latency monitoring for functions associated with ext4 filesystem. | yes | no |
163
-| nfsdist | Enable or disable latency monitoring for functions associated with nfs filesystem. | yes | no |
164
-| xfsdist | Enable or disable latency monitoring for functions associated with xfs filesystem. | yes | no |
165
-| zfsdist | Enable or disable latency monitoring for functions associated with zfs filesystem. | yes | no |
166
-
167
-</details>
171
169
-#### Examples
172
+##### Examples
173
There are no configuration examples.
174
175
src/collectors/ebpf.plugin/integrations/ebpf_hardirq.md
+19
-16
@@ -104,7 +104,24 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
104
105
### Configuration
106
107
-#### File
107
+#### Options
108
+
109
+All options are defined inside section `[global]`.
110
+
111
+
112
+<details open><summary>Config options</summary>
113
+
114
+| Name | Description | Default | Required |
115
+|:----|:-----------|:-------|:--------:|
116
+| update every | Data collection frequency. | 5 | no |
117
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
118
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
119
+
120
+</details>
121
+
122
+
123
+
124
+#### via File
125
126
The configuration file name for this integration is `ebpf.d/hardirq.conf`.
127
@@ -125,22 +142,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
142
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
143
sudo ./edit-config ebpf.d/hardirq.conf
144
```
128
-#### Options
129
-
130
-All options are defined inside section `[global]`.
131
-
132
-
133
-<details open><summary>Config options</summary>
134
-
135
-| Name | Description | Default | Required |
136
-|:----|:-----------|:-------|:--------:|
137
-| update every | Data collection frequency. | 5 | no |
138
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
139
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
140
-
141
-</details>
145
143
-#### Examples
146
+##### Examples
147
There are no configuration examples.
148
149
src/collectors/ebpf.plugin/integrations/ebpf_mdflush.md
+19
-16
@@ -99,7 +99,24 @@ Now follow steps:
99
100
### Configuration
101
102
-#### File
102
+#### Options
103
+
104
+All options are defined inside section `[global]`.
105
+
106
+
107
+<details open><summary>Config options</summary>
108
+
109
+| Name | Description | Default | Required |
110
+|:----|:-----------|:-------|:--------:|
111
+| update every | Data collection frequency. | 5 | no |
112
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
113
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
114
+
115
+</details>
116
+
117
+
118
+
119
+#### via File
120
121
The configuration file name for this integration is `ebpf.d/mdflush.conf`.
122
@@ -120,22 +137,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
137
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
138
sudo ./edit-config ebpf.d/mdflush.conf
139
```
123
-#### Options
124
-
125
-All options are defined inside section `[global]`.
126
-
127
-
128
-<details open><summary>Config options</summary>
129
-
130
-| Name | Description | Default | Required |
131
-|:----|:-----------|:-------|:--------:|
132
-| update every | Data collection frequency. | 5 | no |
133
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
134
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
135
-
136
-</details>
140
138
-#### Examples
141
+##### Examples
142
There are no configuration examples.
143
144
src/collectors/ebpf.plugin/integrations/ebpf_mount.md
+21
-18
@@ -105,7 +105,26 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
105
106
### Configuration
107
108
-#### File
108
+#### Options
109
+
110
+All options are defined inside section `[global]`.
111
+
112
+
113
+<details open><summary>Config options</summary>
114
+
115
+| Name | Description | Default | Required |
116
+|:----|:-----------|:-------|:--------:|
117
+| update every | Data collection frequency. | 5 | no |
118
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
119
+| ebpf type format | Define the file type to load an eBPF program. Three options are available: `legacy` (Attach only `kprobe`), `co-re` (Plugin tries to use `trampoline` when available), and `auto` (plugin check OS configuration before to load). | auto | no |
120
+| ebpf co-re tracing | Select the attach method used by plugin when `co-re` is defined in previous option. Two options are available: `trampoline` (Option with lowest overhead), and `probe` (the same of legacy code). | trampoline | no |
121
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
122
+
123
+</details>
124
+
125
+
126
+
127
+#### via File
128
129
The configuration file name for this integration is `ebpf.d/mount.conf`.
130
@@ -126,24 +145,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
145
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
146
sudo ./edit-config ebpf.d/mount.conf
147
```
129
-#### Options
130
-
131
-All options are defined inside section `[global]`.
132
-
133
-
134
-<details open><summary>Config options</summary>
135
-
136
-| Name | Description | Default | Required |
137
-|:----|:-----------|:-------|:--------:|
138
-| update every | Data collection frequency. | 5 | no |
139
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
140
-| ebpf type format | Define the file type to load an eBPF program. Three options are available: `legacy` (Attach only `kprobe`), `co-re` (Plugin tries to use `trampoline` when available), and `auto` (plugin check OS configuration before to load). | auto | no |
141
-| ebpf co-re tracing | Select the attach method used by plugin when `co-re` is defined in previous option. Two options are available: `trampoline` (Option with lowest overhead), and `probe` (the same of legacy code). | trampoline | no |
142
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
143
-
144
-</details>
148
146
-#### Examples
149
+##### Examples
150
There are no configuration examples.
151
152
src/collectors/ebpf.plugin/integrations/ebpf_oomkill.md
+9
-6
@@ -121,7 +121,14 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
121
122
### Configuration
123
124
-#### File
124
+#### Options
125
+
126
+Overwrite default configuration reducing number of I/O events
127
+
128
+
129
+
130
+
131
+#### via File
132
133
The configuration file name for this integration is `ebpf.d/oomkill.conf`.
134
@@ -142,12 +149,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
149
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
sudo ./edit-config ebpf.d/oomkill.conf
151
```
145
-#### Options
146
-
147
-Overwrite default configuration reducing number of I/O events
148
-
152
150
-#### Examples
153
+##### Examples
154
There are no configuration examples.
155
156
src/collectors/ebpf.plugin/integrations/ebpf_process.md
+7
-4
@@ -94,16 +94,19 @@ To have these charts you need to compile netdata with flag `NETDATA_DEV_MODE`.
94
95
### Configuration
96
97
-#### File
98
-
99
-There is no configuration file.
97
#### Options
98
99
100
101
There are no configuration options.
102
106
-#### Examples
103
+
104
+
105
+#### via File
106
+
107
+There is no configuration file.
108
+
109
+##### Examples
110
There are no configuration examples.
111
112
src/collectors/ebpf.plugin/integrations/ebpf_processes.md
+25
-22
@@ -148,27 +148,6 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
148
149
### Configuration
150
151
-#### File
152
-
153
-The configuration file name for this integration is `ebpf.d/process.conf`.
154
-
155
-The file format is a modified INI syntax. The general structure is:
156
-
157
-```ini
158
-[section1]
159
- option1 = some value
160
- option2 = some other value
161
-
162
-[section2]
163
- option3 = some third value
164
-```
165
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-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).
167
-
168
-```bash
169
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
170
-sudo ./edit-config ebpf.d/process.conf
171
-```
151
#### Options
152
153
All options are defined inside section `[global]`.
@@ -190,7 +169,31 @@ All options are defined inside section `[global]`.
169
170
</details>
171
193
-#### Examples
172
+
173
+
174
+#### via File
175
+
176
+The configuration file name for this integration is `ebpf.d/process.conf`.
177
+
178
+The file format is a modified INI syntax. The general structure is:
179
+
180
+```ini
181
+[section1]
182
+ option1 = some value
183
+ option2 = some other value
184
+
185
+[section2]
186
+ option3 = some third value
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).
190
+
191
+```bash
192
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
193
+sudo ./edit-config ebpf.d/process.conf
194
+```
195
+
196
+##### Examples
197
There are no configuration examples.
198
199
src/collectors/ebpf.plugin/integrations/ebpf_shm.md
+25
-22
@@ -142,27 +142,6 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
142
143
### Configuration
144
145
-#### File
146
-
147
-The configuration file name for this integration is `ebpf.d/shm.conf`.
148
-
149
-The file format is a modified INI syntax. The general structure is:
150
-
151
-```ini
152
-[section1]
153
- option1 = some value
154
- option2 = some other value
155
-
156
-[section2]
157
- option3 = some third value
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).
161
-
162
-```bash
163
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
164
-sudo ./edit-config ebpf.d/shm.conf
165
-```
145
#### Options
146
147
This configuration file have two different sections. The `[global]` overwrites all default options, while `[syscalls]` allow user to select the syscall to monitor.
@@ -188,7 +167,31 @@ This configuration file have two different sections. The `[global]` overwrites a
167
168
</details>
169
191
-#### Examples
170
+
171
+
172
+#### via File
173
+
174
+The configuration file name for this integration is `ebpf.d/shm.conf`.
175
+
176
+The file format is a modified INI syntax. The general structure is:
177
+
178
+```ini
179
+[section1]
180
+ option1 = some value
181
+ option2 = some other value
182
+
183
+[section2]
184
+ option3 = some third value
185
+```
186
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
187
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
188
+
189
+```bash
190
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
191
+sudo ./edit-config ebpf.d/shm.conf
192
+```
193
+
194
+##### Examples
195
There are no configuration examples.
196
197
src/collectors/ebpf.plugin/integrations/ebpf_socket.md
+25
-22
@@ -157,27 +157,6 @@ Now follow steps:
157
158
### Configuration
159
160
-#### File
161
-
162
-The configuration file name for this integration is `ebpf.d/network.conf`.
163
-
164
-The file format is a modified INI syntax. The general structure is:
165
-
166
-```ini
167
-[section1]
168
- option1 = some value
169
- option2 = some other value
170
-
171
-[section2]
172
- option3 = some third value
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).
176
-
177
-```bash
178
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
179
-sudo ./edit-config ebpf.d/network.conf
180
-```
160
#### Options
161
162
All options are defined inside section `[global]`. Options inside `network connections` are ignored for while.
@@ -202,7 +181,31 @@ All options are defined inside section `[global]`. Options inside `network conne
181
182
</details>
183
205
-#### Examples
184
+
185
+
186
+#### via File
187
+
188
+The configuration file name for this integration is `ebpf.d/network.conf`.
189
+
190
+The file format is a modified INI syntax. The general structure is:
191
+
192
+```ini
193
+[section1]
194
+ option1 = some value
195
+ option2 = some other value
196
+
197
+[section2]
198
+ option3 = some third value
199
+```
200
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
201
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
202
+
203
+```bash
204
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
205
+sudo ./edit-config ebpf.d/network.conf
206
+```
207
+
208
+##### Examples
209
There are no configuration examples.
210
211
src/collectors/ebpf.plugin/integrations/ebpf_softirq.md
+19
-16
@@ -104,7 +104,24 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
104
105
### Configuration
106
107
-#### File
107
+#### Options
108
+
109
+All options are defined inside section `[global]`.
110
+
111
+
112
+<details open><summary>Config options</summary>
113
+
114
+| Name | Description | Default | Required |
115
+|:----|:-----------|:-------|:--------:|
116
+| update every | Data collection frequency. | 5 | no |
117
+| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
118
+| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
119
+
120
+</details>
121
+
122
+
123
+
124
+#### via File
125
126
The configuration file name for this integration is `ebpf.d/softirq.conf`.
127
@@ -125,22 +142,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
142
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
143
sudo ./edit-config ebpf.d/softirq.conf
144
```
128
-#### Options
129
-
130
-All options are defined inside section `[global]`.
131
-
132
-
133
-<details open><summary>Config options</summary>
134
-
135
-| Name | Description | Default | Required |
136
-|:----|:-----------|:-------|:--------:|
137
-| update every | Data collection frequency. | 5 | no |
138
-| ebpf load mode | Define whether plugin will monitor the call (`entry`) for the functions or it will also monitor the return (`return`). | entry | no |
139
-| lifetime | Set default lifetime for thread when enabled by cloud. | 300 | no |
140
-
141
-</details>
145
143
-#### Examples
146
+##### Examples
147
There are no configuration examples.
148
149
src/collectors/ebpf.plugin/integrations/ebpf_swap.md
+25
-22
@@ -131,27 +131,6 @@ Now follow steps:
131
132
### Configuration
133
134
-#### File
135
-
136
-The configuration file name for this integration is `ebpf.d/swap.conf`.
137
-
138
-The file format is a modified INI syntax. The general structure is:
139
-
140
-```ini
141
-[section1]
142
- option1 = some value
143
- option2 = some other value
144
-
145
-[section2]
146
- option3 = some third value
147
-```
148
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
149
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
150
-
151
-```bash
152
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
153
-sudo ./edit-config ebpf.d/swap.conf
154
-```
134
#### Options
135
136
All options are defined inside section `[global]`.
@@ -173,7 +152,31 @@ All options are defined inside section `[global]`.
152
153
</details>
154
176
-#### Examples
155
+
156
+
157
+#### via File
158
+
159
+The configuration file name for this integration is `ebpf.d/swap.conf`.
160
+
161
+The file format is a modified INI syntax. The general structure is:
162
+
163
+```ini
164
+[section1]
165
+ option1 = some value
166
+ option2 = some other value
167
+
168
+[section2]
169
+ option3 = some third value
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).
173
+
174
+```bash
175
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
176
+sudo ./edit-config ebpf.d/swap.conf
177
+```
178
+
179
+##### Examples
180
There are no configuration examples.
181
182
src/collectors/ebpf.plugin/integrations/ebpf_sync.md
+25
-22
@@ -112,27 +112,6 @@ This thread needs to attach a tracepoint to monitor when a process schedule an e
112
113
### Configuration
114
115
-#### File
116
-
117
-The configuration file name for this integration is `ebpf.d/sync.conf`.
118
-
119
-The file format is a modified INI syntax. The general structure is:
120
-
121
-```ini
122
-[section1]
123
- option1 = some value
124
- option2 = some other value
125
-
126
-[section2]
127
- option3 = some third value
128
-```
129
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
130
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
131
-
132
-```bash
133
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
134
-sudo ./edit-config ebpf.d/sync.conf
135
-```
115
#### Options
116
117
This configuration file have two different sections. The `[global]` overwrites all default options, while `[syscalls]` allow user to select the syscall to monitor.
@@ -160,7 +139,31 @@ This configuration file have two different sections. The `[global]` overwrites a
139
140
</details>
141
163
-#### Examples
142
+
143
+
144
+#### via File
145
+
146
+The configuration file name for this integration is `ebpf.d/sync.conf`.
147
+
148
+The file format is a modified INI syntax. The general structure is:
149
+
150
+```ini
151
+[section1]
152
+ option1 = some value
153
+ option2 = some other value
154
+
155
+[section2]
156
+ option3 = some third value
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).
160
+
161
+```bash
162
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
163
+sudo ./edit-config ebpf.d/sync.conf
164
+```
165
+
166
+##### Examples
167
There are no configuration examples.
168
169
src/collectors/ebpf.plugin/integrations/ebpf_vfs.md
+25
-22
@@ -173,27 +173,6 @@ Now follow steps:
173
174
### Configuration
175
176
-#### File
177
-
178
-The configuration file name for this integration is `ebpf.d/vfs.conf`.
179
-
180
-The file format is a modified INI syntax. The general structure is:
181
-
182
-```ini
183
-[section1]
184
- option1 = some value
185
- option2 = some other value
186
-
187
-[section2]
188
- option3 = some third value
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).
192
-
193
-```bash
194
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
-sudo ./edit-config ebpf.d/vfs.conf
196
-```
176
#### Options
177
178
All options are defined inside section `[global]`.
@@ -215,7 +194,31 @@ All options are defined inside section `[global]`.
194
195
</details>
196
218
-#### Examples
197
+
198
+
199
+#### via File
200
+
201
+The configuration file name for this integration is `ebpf.d/vfs.conf`.
202
+
203
+The file format is a modified INI syntax. The general structure is:
204
+
205
+```ini
206
+[section1]
207
+ option1 = some value
208
+ option2 = some other value
209
+
210
+[section2]
211
+ option3 = some third value
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).
215
+
216
+```bash
217
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
218
+sudo ./edit-config ebpf.d/vfs.conf
219
+```
220
+
221
+##### Examples
222
There are no configuration examples.
223
224
src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md
+16
-13
@@ -80,7 +80,21 @@ No action required.
80
81
### Configuration
82
83
-#### File
83
+#### Options
84
+
85
+
86
+
87
+<details open><summary></summary>
88
+
89
+| Name | Description | Default | Required |
90
+|:----|:-----------|:-------|:--------:|
91
+| dev.cpu.0.freq | Enable or disable CPU Scaling frequency metric. | yes | no |
92
+
93
+</details>
94
+
95
+
96
+
97
+#### via File
98
99
The configuration file name for this integration is `Config options`.
100
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -93,19 +107,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
108
sudo ./edit-config Config options
109
```
96
-#### Options
97
-
98
-
99
-
100
-<details open><summary></summary>
101
-
102
-| Name | Description | Default | Required |
103
-|:----|:-----------|:-------|:--------:|
104
-| dev.cpu.0.freq | Enable or disable CPU Scaling frequency metric. | yes | no |
105
-
106
-</details>
110
108
-#### Examples
111
+##### Examples
112
There are no configuration examples.
113
114
src/collectors/freebsd.plugin/integrations/dev.cpu.temperature.md
+16
-13
@@ -80,7 +80,21 @@ No action required.
80
81
### Configuration
82
83
-#### File
83
+#### Options
84
+
85
+
86
+
87
+<details open><summary>Config options</summary>
88
+
89
+| Name | Description | Default | Required |
90
+|:----|:-----------|:-------|:--------:|
91
+| dev.cpu.temperature | Enable or disable CPU temperature metric. | yes | no |
92
+
93
+</details>
94
+
95
+
96
+
97
+#### via File
98
99
The configuration file name for this integration is `netdata.conf`.
100
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -102,19 +116,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
sudo ./edit-config netdata.conf
118
```
105
-#### Options
106
-
107
-
108
-
109
-<details open><summary>Config options</summary>
110
-
111
-| Name | Description | Default | Required |
112
-|:----|:-----------|:-------|:--------:|
113
-| dev.cpu.temperature | Enable or disable CPU temperature metric. | yes | no |
114
-
115
-</details>
119
117
-#### Examples
120
+##### Examples
121
There are no configuration examples.
122
123
src/collectors/freebsd.plugin/integrations/devstat.md
+26
-23
@@ -104,28 +104,6 @@ No action required.
104
105
### Configuration
106
107
-#### File
108
-
109
-The configuration file name for this integration is `netdata.conf`.
110
-Configuration for this specific integration is located in the `[plugin:freebsd:kern.devstat]` section within that file.
111
-
112
-The file format is a modified INI syntax. The general structure is:
113
-
114
-```ini
115
-[section1]
116
- option1 = some value
117
- option2 = some other value
118
-
119
-[section2]
120
- option3 = some third value
121
-```
122
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
123
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
-
125
-```bash
126
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
127
-sudo ./edit-config netdata.conf
128
-```
107
#### Options
108
109
@@ -149,7 +127,32 @@ sudo ./edit-config netdata.conf
127
128
</details>
129
152
-#### Examples
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `netdata.conf`.
135
+Configuration for this specific integration is located in the `[plugin:freebsd:kern.devstat]` section within that file.
136
+
137
+The file format is a modified INI syntax. The general structure is:
138
+
139
+```ini
140
+[section1]
141
+ option1 = some value
142
+ option2 = some other value
143
+
144
+[section2]
145
+ option3 = some third value
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).
149
+
150
+```bash
151
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
152
+sudo ./edit-config netdata.conf
153
+```
154
+
155
+##### Examples
156
There are no configuration examples.
157
158
src/collectors/freebsd.plugin/integrations/getifaddrs.md
+26
-23
@@ -110,28 +110,6 @@ No action required.
110
111
### Configuration
112
113
-#### File
114
-
115
-The configuration file name for this integration is `netdata.conf`.
116
-Configuration for this specific integration is located in the `[plugin:freebsd:getifaddrs]` section within that file.
117
-
118
-The file format is a modified INI syntax. The general structure is:
119
-
120
-```ini
121
-[section1]
122
- option1 = some value
123
- option2 = some other value
124
-
125
-[section2]
126
- option3 = some third value
127
-```
128
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
129
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
130
-
131
-```bash
132
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
133
-sudo ./edit-config netdata.conf
134
-```
113
#### Options
114
115
@@ -155,7 +133,32 @@ sudo ./edit-config netdata.conf
133
134
</details>
135
158
-#### Examples
136
+
137
+
138
+#### via File
139
+
140
+The configuration file name for this integration is `netdata.conf`.
141
+Configuration for this specific integration is located in the `[plugin:freebsd:getifaddrs]` section within that file.
142
+
143
+The file format is a modified INI syntax. The general structure is:
144
+
145
+```ini
146
+[section1]
147
+ option1 = some value
148
+ option2 = some other value
149
+
150
+[section2]
151
+ option3 = some third value
152
+```
153
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
154
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
155
+
156
+```bash
157
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
158
+sudo ./edit-config netdata.conf
159
+```
160
+
161
+##### Examples
162
There are no configuration examples.
163
164
src/collectors/freebsd.plugin/integrations/getmntinfo.md
+20
-17
@@ -87,7 +87,25 @@ No action required.
87
88
### Configuration
89
90
-#### File
90
+#### Options
91
+
92
+
93
+
94
+<details open><summary>Config options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| enable new mount points detected at runtime | Cheeck new mount points during runtime. | auto | no |
99
+| space usage for all disks | Enable or disable space usage for all disks metric. | auto | no |
100
+| inodes usage for all disks | Enable or disable inodes usage for all disks metric. | auto | no |
101
+| exclude space metrics on paths | Do not show metrics for listed paths. | /proc/* | no |
102
+| exclude space metrics on filesystems | Do not monitor listed filesystems. | autofs procfs subfs devfs none | no |
103
+
104
+</details>
105
+
106
+
107
+
108
+#### via File
109
110
The configuration file name for this integration is `netdata.conf`.
111
Configuration for this specific integration is located in the `[plugin:freebsd:getmntinfo]` section within that file.
@@ -109,23 +127,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
127
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
128
sudo ./edit-config netdata.conf
129
```
112
-#### Options
113
-
114
-
115
-
116
-<details open><summary>Config options</summary>
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| enable new mount points detected at runtime | Cheeck new mount points during runtime. | auto | no |
121
-| space usage for all disks | Enable or disable space usage for all disks metric. | auto | no |
122
-| inodes usage for all disks | Enable or disable inodes usage for all disks metric. | auto | no |
123
-| exclude space metrics on paths | Do not show metrics for listed paths. | /proc/* | no |
124
-| exclude space metrics on filesystems | Do not monitor listed filesystems. | autofs procfs subfs devfs none | no |
125
-
126
-</details>
130
128
-#### Examples
131
+##### Examples
132
There are no configuration examples.
133
134
src/collectors/freebsd.plugin/integrations/hw.intrcnt.md
+16
-13
@@ -81,7 +81,21 @@ No action required.
81
82
### Configuration
83
84
-#### File
84
+#### Options
85
+
86
+
87
+
88
+<details open><summary>Config option</summary>
89
+
90
+| Name | Description | Default | Required |
91
+|:----|:-----------|:-------|:--------:|
92
+| hw.intrcnt | Enable or disable Interrupts metric. | yes | no |
93
+
94
+</details>
95
+
96
+
97
+
98
+#### via File
99
100
The configuration file name for this integration is `netdata.conf`.
101
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -103,19 +117,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
sudo ./edit-config netdata.conf
119
```
106
-#### Options
107
-
108
-
109
-
110
-<details open><summary>Config option</summary>
111
-
112
-| Name | Description | Default | Required |
113
-|:----|:-----------|:-------|:--------:|
114
-| hw.intrcnt | Enable or disable Interrupts metric. | yes | no |
115
-
116
-</details>
120
118
-#### Examples
121
+##### Examples
122
There are no configuration examples.
123
124
src/collectors/freebsd.plugin/integrations/ipfw.md
+18
-15
@@ -84,7 +84,23 @@ No action required.
84
85
### Configuration
86
87
-#### File
87
+#### Options
88
+
89
+
90
+
91
+<details open><summary>Config options</summary>
92
+
93
+| Name | Description | Default | Required |
94
+|:----|:-----------|:-------|:--------:|
95
+| counters for static rules | Enable or disable counters for static rules metric. | yes | no |
96
+| number of dynamic rules | Enable or disable number of dynamic rules metric. | yes | no |
97
+| allocated memory | Enable or disable allocated memory metric. | yes | no |
98
+
99
+</details>
100
+
101
+
102
+
103
+#### via File
104
105
The configuration file name for this integration is `netdata.conf`.
106
Configuration for this specific integration is located in the `[plugin:freebsd:ipfw]` section within that file.
@@ -106,21 +122,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
sudo ./edit-config netdata.conf
124
```
109
-#### Options
110
-
111
-
112
-
113
-<details open><summary>Config options</summary>
114
-
115
-| Name | Description | Default | Required |
116
-|:----|:-----------|:-------|:--------:|
117
-| counters for static rules | Enable or disable counters for static rules metric. | yes | no |
118
-| number of dynamic rules | Enable or disable number of dynamic rules metric. | yes | no |
119
-| allocated memory | Enable or disable allocated memory metric. | yes | no |
120
-
121
-</details>
125
123
-#### Examples
126
+##### Examples
127
There are no configuration examples.
128
129
src/collectors/freebsd.plugin/integrations/kern.cp_time.md
+16
-13
@@ -100,7 +100,21 @@ No action required.
100
101
### Configuration
102
103
-#### File
103
+#### Options
104
+
105
+The netdata main configuration file.
106
+
107
+<details open><summary>Config options</summary>
108
+
109
+| Name | Description | Default | Required |
110
+|:----|:-----------|:-------|:--------:|
111
+| kern.cp_time | Enable or disable Total CPU usage. | yes | no |
112
+
113
+</details>
114
+
115
+
116
+
117
+#### via File
118
119
The configuration file name for this integration is `netdata.conf`.
120
@@ -121,19 +135,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
135
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
136
sudo ./edit-config netdata.conf
137
```
124
-#### Options
125
-
126
-The netdata main configuration file.
127
-
128
-<details open><summary>Config options</summary>
129
-
130
-| Name | Description | Default | Required |
131
-|:----|:-----------|:-------|:--------:|
132
-| kern.cp_time | Enable or disable Total CPU usage. | yes | no |
133
-
134
-</details>
138
136
-#### Examples
139
+##### Examples
140
There are no configuration examples.
141
142
src/collectors/freebsd.plugin/integrations/kern.ipc.msq.md
+16
-13
@@ -82,7 +82,21 @@ No action required.
82
83
### Configuration
84
85
-#### File
85
+#### Options
86
+
87
+
88
+
89
+<details open><summary>Config options</summary>
90
+
91
+| Name | Description | Default | Required |
92
+|:----|:-----------|:-------|:--------:|
93
+| kern.ipc.msq | Enable or disable IPC message queue metric. | yes | no |
94
+
95
+</details>
96
+
97
+
98
+
99
+#### via File
100
101
The configuration file name for this integration is `netdata.conf`.
102
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -104,19 +118,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
118
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
119
sudo ./edit-config netdata.conf
120
```
107
-#### Options
108
-
109
-
110
-
111
-<details open><summary>Config options</summary>
112
-
113
-| Name | Description | Default | Required |
114
-|:----|:-----------|:-------|:--------:|
115
-| kern.ipc.msq | Enable or disable IPC message queue metric. | yes | no |
116
-
117
-</details>
121
119
-#### Examples
122
+##### Examples
123
There are no configuration examples.
124
125
src/collectors/freebsd.plugin/integrations/kern.ipc.sem.md
+16
-13
@@ -87,7 +87,21 @@ No action required.
87
88
### Configuration
89
90
-#### File
90
+#### Options
91
+
92
+
93
+
94
+<details open><summary>Config options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| kern.ipc.sem | Enable or disable semaphore metrics. | yes | no |
99
+
100
+</details>
101
+
102
+
103
+
104
+#### via File
105
106
The configuration file name for this integration is `netdata.conf`.
107
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -109,19 +123,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
123
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
124
sudo ./edit-config netdata.conf
125
```
112
-#### Options
113
-
114
-
115
-
116
-<details open><summary>Config options</summary>
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| kern.ipc.sem | Enable or disable semaphore metrics. | yes | no |
121
-
122
-</details>
126
124
-#### Examples
127
+##### Examples
128
There are no configuration examples.
129
130
src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md
+16
-13
@@ -81,7 +81,21 @@ No action required.
81
82
### Configuration
83
84
-#### File
84
+#### Options
85
+
86
+
87
+
88
+<details open><summary>Config options</summary>
89
+
90
+| Name | Description | Default | Required |
91
+|:----|:-----------|:-------|:--------:|
92
+| kern.ipc.shm | Enable or disable shared memory metric. | yes | no |
93
+
94
+</details>
95
+
96
+
97
+
98
+#### via File
99
100
The configuration file name for this integration is `netdata.conf`.
101
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -103,19 +117,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
sudo ./edit-config netdata.conf
119
```
106
-#### Options
107
-
108
-
109
-
110
-<details open><summary>Config options</summary>
111
-
112
-| Name | Description | Default | Required |
113
-|:----|:-----------|:-------|:--------:|
114
-| kern.ipc.shm | Enable or disable shared memory metric. | yes | no |
115
-
116
-</details>
120
118
-#### Examples
121
+##### Examples
122
There are no configuration examples.
123
124
src/collectors/freebsd.plugin/integrations/net.inet.icmp.stats.md
+18
-15
@@ -82,7 +82,23 @@ No action required.
82
83
### Configuration
84
85
-#### File
85
+#### Options
86
+
87
+
88
+
89
+<details open><summary>Config options</summary>
90
+
91
+| Name | Description | Default | Required |
92
+|:----|:-----------|:-------|:--------:|
93
+| IPv4 ICMP packets | Enable or disable IPv4 ICMP packets metric. | yes | no |
94
+| IPv4 ICMP error | Enable or disable IPv4 ICMP error metric. | yes | no |
95
+| IPv4 ICMP messages | Enable or disable IPv4 ICMP messages metric. | yes | no |
96
+
97
+</details>
98
+
99
+
100
+
101
+#### via File
102
103
The configuration file name for this integration is `netdata.conf`.
104
Configuration for this specific integration is located in the `[plugin:freebsd:net.inet.icmp.stats]` section within that file.
@@ -104,21 +120,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
120
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
121
sudo ./edit-config netdata.conf
122
```
107
-#### Options
108
-
109
-
110
-
111
-<details open><summary>Config options</summary>
112
-
113
-| Name | Description | Default | Required |
114
-|:----|:-----------|:-------|:--------:|
115
-| IPv4 ICMP packets | Enable or disable IPv4 ICMP packets metric. | yes | no |
116
-| IPv4 ICMP error | Enable or disable IPv4 ICMP error metric. | yes | no |
117
-| IPv4 ICMP messages | Enable or disable IPv4 ICMP messages metric. | yes | no |
118
-
119
-</details>
123
121
-#### Examples
124
+##### Examples
125
There are no configuration examples.
126
127
src/collectors/freebsd.plugin/integrations/net.inet.ip.stats.md
+19
-16
@@ -83,7 +83,24 @@ No action required.
83
84
### Configuration
85
86
-#### File
86
+#### Options
87
+
88
+
89
+
90
+<details open><summary>Config options</summary>
91
+
92
+| Name | Description | Default | Required |
93
+|:----|:-----------|:-------|:--------:|
94
+| ipv4 packets | Enable or disable IPv4 packets metric. | yes | no |
95
+| ipv4 fragments sent | Enable or disable IPv4 fragments sent metric. | yes | no |
96
+| ipv4 fragments assembly | Enable or disable IPv4 fragments assembly metric. | yes | no |
97
+| ipv4 errors | Enable or disable IPv4 errors metric. | yes | no |
98
+
99
+</details>
100
+
101
+
102
+
103
+#### via File
104
105
The configuration file name for this integration is `netdata.conf`.
106
Configuration for this specific integration is located in the `[plugin:freebsd:net.inet.ip.stats]` section within that file.
@@ -105,22 +122,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
sudo ./edit-config netdata.conf
124
```
108
-#### Options
109
-
110
-
111
-
112
-<details open><summary>Config options</summary>
113
-
114
-| Name | Description | Default | Required |
115
-|:----|:-----------|:-------|:--------:|
116
-| ipv4 packets | Enable or disable IPv4 packets metric. | yes | no |
117
-| ipv4 fragments sent | Enable or disable IPv4 fragments sent metric. | yes | no |
118
-| ipv4 fragments assembly | Enable or disable IPv4 fragments assembly metric. | yes | no |
119
-| ipv4 errors | Enable or disable IPv4 errors metric. | yes | no |
120
-
121
-</details>
125
123
-#### Examples
126
+##### Examples
127
There are no configuration examples.
128
129
src/collectors/freebsd.plugin/integrations/net.inet.tcp.states.md
+16
-13
@@ -85,7 +85,21 @@ No action required.
85
86
### Configuration
87
88
-#### File
88
+#### Options
89
+
90
+
91
+
92
+<details open><summary>Config options</summary>
93
+
94
+| Name | Description | Default | Required |
95
+|:----|:-----------|:-------|:--------:|
96
+| net.inet.tcp.states | Enable or disable TCP state metric. | yes | no |
97
+
98
+</details>
99
+
100
+
101
+
102
+#### via File
103
104
The configuration file name for this integration is `netdata.conf`.
105
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -107,19 +121,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
sudo ./edit-config netdata.conf
123
```
110
-#### Options
111
-
112
-
113
-
114
-<details open><summary>Config options</summary>
115
-
116
-| Name | Description | Default | Required |
117
-|:----|:-----------|:-------|:--------:|
118
-| net.inet.tcp.states | Enable or disable TCP state metric. | yes | no |
119
-
120
-</details>
124
122
-#### Examples
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/freebsd.plugin/integrations/net.inet.tcp.stats.md
+23
-20
@@ -95,7 +95,28 @@ No action required.
95
96
### Configuration
97
98
-#### File
98
+#### Options
99
+
100
+
101
+
102
+<details open><summary>Config options</summary>
103
+
104
+| Name | Description | Default | Required |
105
+|:----|:-----------|:-------|:--------:|
106
+| ipv4 TCP packets | Enable or disable ipv4 TCP packets metric. | yes | no |
107
+| ipv4 TCP errors | Enable or disable pv4 TCP errors metric. | yes | no |
108
+| ipv4 TCP handshake issues | Enable or disable ipv4 TCP handshake issue metric. | yes | no |
109
+| TCP connection aborts | Enable or disable TCP connection aborts metric. | auto | no |
110
+| TCP out-of-order queue | Enable or disable TCP out-of-order queue metric. | auto | no |
111
+| TCP SYN cookies | Enable or disable TCP SYN cookies metric. | auto | no |
112
+| TCP listen issues | Enable or disable TCP listen issues metric. | auto | no |
113
+| ECN packets | Enable or disable ECN packets metric. | auto | no |
114
+
115
+</details>
116
+
117
+
118
+
119
+#### via File
120
121
The configuration file name for this integration is `netdata.conf`.
122
Configuration for this specific integration is located in the `[plugin:freebsd:net.inet.tcp.stats]` section within that file.
@@ -117,26 +138,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
138
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
139
sudo ./edit-config netdata.conf
140
```
120
-#### Options
121
-
122
-
123
-
124
-<details open><summary>Config options</summary>
125
-
126
-| Name | Description | Default | Required |
127
-|:----|:-----------|:-------|:--------:|
128
-| ipv4 TCP packets | Enable or disable ipv4 TCP packets metric. | yes | no |
129
-| ipv4 TCP errors | Enable or disable pv4 TCP errors metric. | yes | no |
130
-| ipv4 TCP handshake issues | Enable or disable ipv4 TCP handshake issue metric. | yes | no |
131
-| TCP connection aborts | Enable or disable TCP connection aborts metric. | auto | no |
132
-| TCP out-of-order queue | Enable or disable TCP out-of-order queue metric. | auto | no |
133
-| TCP SYN cookies | Enable or disable TCP SYN cookies metric. | auto | no |
134
-| TCP listen issues | Enable or disable TCP listen issues metric. | auto | no |
135
-| ECN packets | Enable or disable ECN packets metric. | auto | no |
136
-
137
-</details>
141
139
-#### Examples
142
+##### Examples
143
There are no configuration examples.
144
145
src/collectors/freebsd.plugin/integrations/net.inet.udp.stats.md
+17
-14
@@ -87,7 +87,22 @@ No action required.
87
88
### Configuration
89
90
-#### File
90
+#### Options
91
+
92
+
93
+
94
+<details open><summary>Config options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| ipv4 UDP packets | Enable or disable ipv4 UDP packets metric. | yes | no |
99
+| ipv4 UDP errors | Enable or disable ipv4 UDP errors metric. | yes | no |
100
+
101
+</details>
102
+
103
+
104
+
105
+#### via File
106
107
The configuration file name for this integration is `netdata.conf`.
108
Configuration for this specific integration is located in the `[plugin:freebsd:net.inet.udp.stats]` section within that file.
@@ -109,20 +124,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
124
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
125
sudo ./edit-config netdata.conf
126
```
112
-#### Options
113
-
114
-
115
-
116
-<details open><summary>Config options</summary>
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| ipv4 UDP packets | Enable or disable ipv4 UDP packets metric. | yes | no |
121
-| ipv4 UDP errors | Enable or disable ipv4 UDP errors metric. | yes | no |
122
-
123
-</details>
127
125
-#### Examples
128
+##### Examples
129
There are no configuration examples.
130
131
src/collectors/freebsd.plugin/integrations/net.inet6.icmp6.stats.md
+22
-19
@@ -86,7 +86,27 @@ No action required.
86
87
### Configuration
88
89
-#### File
89
+#### Options
90
+
91
+
92
+
93
+<details open><summary>Config options</summary>
94
+
95
+| Name | Description | Default | Required |
96
+|:----|:-----------|:-------|:--------:|
97
+| icmp | Enable or disable ICMP metric. | auto | no |
98
+| icmp redirects | Enable or disable ICMP redirects metric. | auto | no |
99
+| icmp errors | Enable or disable ICMP errors metric. | auto | no |
100
+| icmp echos | Enable or disable ICMP echos metric. | auto | no |
101
+| icmp router | Enable or disable ICMP router metric. | auto | no |
102
+| icmp neighbor | Enable or disable ICMP neighbor metric. | auto | no |
103
+| icmp types | Enable or disable ICMP types metric. | auto | no |
104
+
105
+</details>
106
+
107
+
108
+
109
+#### via File
110
111
The configuration file name for this integration is `netdata.conf`.
112
Configuration for this specific integration is located in the `[plugin:freebsd:net.inet6.icmp6.stats]` section within that file.
@@ -108,25 +128,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
128
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
129
sudo ./edit-config netdata.conf
130
```
111
-#### Options
112
-
113
-
114
-
115
-<details open><summary>Config options</summary>
116
-
117
-| Name | Description | Default | Required |
118
-|:----|:-----------|:-------|:--------:|
119
-| icmp | Enable or disable ICMP metric. | auto | no |
120
-| icmp redirects | Enable or disable ICMP redirects metric. | auto | no |
121
-| icmp errors | Enable or disable ICMP errors metric. | auto | no |
122
-| icmp echos | Enable or disable ICMP echos metric. | auto | no |
123
-| icmp router | Enable or disable ICMP router metric. | auto | no |
124
-| icmp neighbor | Enable or disable ICMP neighbor metric. | auto | no |
125
-| icmp types | Enable or disable ICMP types metric. | auto | no |
126
-
127
-</details>
131
129
-#### Examples
132
+##### Examples
133
There are no configuration examples.
134
135
src/collectors/freebsd.plugin/integrations/net.inet6.ip6.stats.md
+19
-16
@@ -83,7 +83,24 @@ No action required.
83
84
### Configuration
85
86
-#### File
86
+#### Options
87
+
88
+
89
+
90
+<details open><summary>Config options</summary>
91
+
92
+| Name | Description | Default | Required |
93
+|:----|:-----------|:-------|:--------:|
94
+| ipv6 packets | Enable or disable ipv6 packet metric. | auto | no |
95
+| ipv6 fragments sent | Enable or disable ipv6 fragments sent metric. | auto | no |
96
+| ipv6 fragments assembly | Enable or disable ipv6 fragments assembly metric. | auto | no |
97
+| ipv6 errors | Enable or disable ipv6 errors metric. | auto | no |
98
+
99
+</details>
100
+
101
+
102
+
103
+#### via File
104
105
The configuration file name for this integration is `netdata.conf`.
106
Configuration for this specific integration is located in the `[plugin:freebsd:net.inet6.ip6.stats]` section within that file.
@@ -105,22 +122,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
sudo ./edit-config netdata.conf
124
```
108
-#### Options
109
-
110
-
111
-
112
-<details open><summary>Config options</summary>
113
-
114
-| Name | Description | Default | Required |
115
-|:----|:-----------|:-------|:--------:|
116
-| ipv6 packets | Enable or disable ipv6 packet metric. | auto | no |
117
-| ipv6 fragments sent | Enable or disable ipv6 fragments sent metric. | auto | no |
118
-| ipv6 fragments assembly | Enable or disable ipv6 fragments assembly metric. | auto | no |
119
-| ipv6 errors | Enable or disable ipv6 errors metric. | auto | no |
120
-
121
-</details>
125
123
-#### Examples
126
+##### Examples
127
There are no configuration examples.
128
129
src/collectors/freebsd.plugin/integrations/net.isr.md
+17
-14
@@ -99,7 +99,22 @@ No action required.
99
100
### Configuration
101
102
-#### File
102
+#### Options
103
+
104
+
105
+
106
+<details open><summary>Config options</summary>
107
+
108
+| Name | Description | Default | Required |
109
+|:----|:-----------|:-------|:--------:|
110
+| netisr | Enable or disable general vision about softnet stat metrics. | yes | no |
111
+| netisr per core | Enable or disable softnet stat metric per core. | yes | no |
112
+
113
+</details>
114
+
115
+
116
+
117
+#### via File
118
119
The configuration file name for this integration is `netdata.conf`.
120
Configuration for this specific integration is located in the `[plugin:freebsd:net.isr]` section within that file.
@@ -121,20 +136,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
136
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
137
sudo ./edit-config netdata.conf
138
```
124
-#### Options
125
-
126
-
127
-
128
-<details open><summary>Config options</summary>
129
-
130
-| Name | Description | Default | Required |
131
-|:----|:-----------|:-------|:--------:|
132
-| netisr | Enable or disable general vision about softnet stat metrics. | yes | no |
133
-| netisr per core | Enable or disable softnet stat metric per core. | yes | no |
134
-
135
-</details>
139
137
-#### Examples
140
+##### Examples
141
There are no configuration examples.
142
143
src/collectors/freebsd.plugin/integrations/system.ram.md
+16
-13
@@ -89,7 +89,21 @@ No action required.
89
90
### Configuration
91
92
-#### File
92
+#### Options
93
+
94
+
95
+
96
+<details open><summary>Config options</summary>
97
+
98
+| Name | Description | Default | Required |
99
+|:----|:-----------|:-------|:--------:|
100
+| system.ram | Enable or disable system RAM metric. | yes | no |
101
+
102
+</details>
103
+
104
+
105
+
106
+#### via File
107
108
The configuration file name for this integration is `netdata.conf`.
109
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -111,19 +125,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
125
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
126
sudo ./edit-config netdata.conf
127
```
114
-#### Options
115
-
116
-
117
-
118
-<details open><summary>Config options</summary>
119
-
120
-| Name | Description | Default | Required |
121
-|:----|:-----------|:-------|:--------:|
122
-| system.ram | Enable or disable system RAM metric. | yes | no |
123
-
124
-</details>
128
126
-#### Examples
129
+##### Examples
130
There are no configuration examples.
131
132
src/collectors/freebsd.plugin/integrations/uptime.md
+16
-13
@@ -80,7 +80,21 @@ No action required.
80
81
### Configuration
82
83
-#### File
83
+#### Options
84
+
85
+
86
+
87
+<details open><summary>Config options</summary>
88
+
89
+| Name | Description | Default | Required |
90
+|:----|:-----------|:-------|:--------:|
91
+| vm.loadavg | Enable or disable load average metric. | yes | no |
92
+
93
+</details>
94
+
95
+
96
+
97
+#### via File
98
99
The configuration file name for this integration is `netdata.conf`.
100
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -102,19 +116,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
sudo ./edit-config netdata.conf
118
```
105
-#### Options
106
-
107
-
108
-
109
-<details open><summary>Config options</summary>
110
-
111
-| Name | Description | Default | Required |
112
-|:----|:-----------|:-------|:--------:|
113
-| vm.loadavg | Enable or disable load average metric. | yes | no |
114
-
115
-</details>
119
117
-#### Examples
120
+##### Examples
121
There are no configuration examples.
122
123
src/collectors/freebsd.plugin/integrations/vm.loadavg.md
+16
-13
@@ -88,7 +88,21 @@ No action required.
88
89
### Configuration
90
91
-#### File
91
+#### Options
92
+
93
+
94
+
95
+<details open><summary>Config options</summary>
96
+
97
+| Name | Description | Default | Required |
98
+|:----|:-----------|:-------|:--------:|
99
+| vm.loadavg | Enable or disable load average metric. | yes | no |
100
+
101
+</details>
102
+
103
+
104
+
105
+#### via File
106
107
The configuration file name for this integration is `netdata.conf`.
108
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -110,19 +124,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
124
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
125
sudo ./edit-config netdata.conf
126
```
113
-#### Options
114
-
115
-
116
-
117
-<details open><summary>Config options</summary>
118
-
119
-| Name | Description | Default | Required |
120
-|:----|:-----------|:-------|:--------:|
121
-| vm.loadavg | Enable or disable load average metric. | yes | no |
122
-
123
-</details>
127
125
-#### Examples
128
+##### Examples
129
There are no configuration examples.
130
131
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_intr.md
+16
-13
@@ -80,7 +80,21 @@ No action required.
80
81
### Configuration
82
83
-#### File
83
+#### Options
84
+
85
+
86
+
87
+<details open><summary>Config option</summary>
88
+
89
+| Name | Description | Default | Required |
90
+|:----|:-----------|:-------|:--------:|
91
+| vm.stats.sys.v_intr | Enable or disable device interrupts metric. | yes | no |
92
+
93
+</details>
94
+
95
+
96
+
97
+#### via File
98
99
The configuration file name for this integration is `netdata.conf`.
100
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -102,19 +116,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
sudo ./edit-config netdata.conf
118
```
105
-#### Options
106
-
107
-
108
-
109
-<details open><summary>Config option</summary>
110
-
111
-| Name | Description | Default | Required |
112
-|:----|:-----------|:-------|:--------:|
113
-| vm.stats.sys.v_intr | Enable or disable device interrupts metric. | yes | no |
114
-
115
-</details>
119
117
-#### Examples
120
+##### Examples
121
There are no configuration examples.
122
123
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_soft.md
+16
-13
@@ -80,7 +80,21 @@ No action required.
80
81
### Configuration
82
83
-#### File
83
+#### Options
84
+
85
+
86
+
87
+<details open><summary>Config option</summary>
88
+
89
+| Name | Description | Default | Required |
90
+|:----|:-----------|:-------|:--------:|
91
+| vm.stats.sys.v_soft | Enable or disable software inerrupts metric. | yes | no |
92
+
93
+</details>
94
+
95
+
96
+
97
+#### via File
98
99
The configuration file name for this integration is `netdata.conf`.
100
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -102,19 +116,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
sudo ./edit-config netdata.conf
118
```
105
-#### Options
106
-
107
-
108
-
109
-<details open><summary>Config option</summary>
110
-
111
-| Name | Description | Default | Required |
112
-|:----|:-----------|:-------|:--------:|
113
-| vm.stats.sys.v_soft | Enable or disable software inerrupts metric. | yes | no |
114
-
115
-</details>
119
117
-#### Examples
120
+##### Examples
121
There are no configuration examples.
122
123
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_swtch.md
+16
-13
@@ -81,7 +81,21 @@ No action required.
81
82
### Configuration
83
84
-#### File
84
+#### Options
85
+
86
+
87
+
88
+<details open><summary>Config options</summary>
89
+
90
+| Name | Description | Default | Required |
91
+|:----|:-----------|:-------|:--------:|
92
+| vm.stats.sys.v_swtch | Enable or disable CPU context switch metric. | yes | no |
93
+
94
+</details>
95
+
96
+
97
+
98
+#### via File
99
100
The configuration file name for this integration is `netdata.conf`.
101
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -103,19 +117,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
sudo ./edit-config netdata.conf
119
```
106
-#### Options
107
-
108
-
109
-
110
-<details open><summary>Config options</summary>
111
-
112
-| Name | Description | Default | Required |
113
-|:----|:-----------|:-------|:--------:|
114
-| vm.stats.sys.v_swtch | Enable or disable CPU context switch metric. | yes | no |
115
-
116
-</details>
120
118
-#### Examples
121
+##### Examples
122
There are no configuration examples.
123
124
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_pgfaults.md
+16
-13
@@ -80,7 +80,21 @@ No action required.
80
81
### Configuration
82
83
-#### File
83
+#### Options
84
+
85
+
86
+
87
+<details open><summary>Config options</summary>
88
+
89
+| Name | Description | Default | Required |
90
+|:----|:-----------|:-------|:--------:|
91
+| vm.stats.vm.v_pgfaults | Enable or disable Memory page fault metric. | yes | no |
92
+
93
+</details>
94
+
95
+
96
+
97
+#### via File
98
99
The configuration file name for this integration is `netdata.conf`.
100
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -102,19 +116,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
sudo ./edit-config netdata.conf
118
```
105
-#### Options
106
-
107
-
108
-
109
-<details open><summary>Config options</summary>
110
-
111
-| Name | Description | Default | Required |
112
-|:----|:-----------|:-------|:--------:|
113
-| vm.stats.vm.v_pgfaults | Enable or disable Memory page fault metric. | yes | no |
114
-
115
-</details>
119
117
-#### Examples
120
+##### Examples
121
There are no configuration examples.
122
123
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_swappgs.md
+16
-13
@@ -85,7 +85,21 @@ No action required.
85
86
### Configuration
87
88
-#### File
88
+#### Options
89
+
90
+
91
+
92
+<details open><summary>Config options</summary>
93
+
94
+| Name | Description | Default | Required |
95
+|:----|:-----------|:-------|:--------:|
96
+| vm.stats.vm.v_swappgs | Enable or disable infoormation about SWAP I/O metric. | yes | no |
97
+
98
+</details>
99
+
100
+
101
+
102
+#### via File
103
104
The configuration file name for this integration is `netdata.conf`.
105
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -107,19 +121,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
sudo ./edit-config netdata.conf
123
```
110
-#### Options
111
-
112
-
113
-
114
-<details open><summary>Config options</summary>
115
-
116
-| Name | Description | Default | Required |
117
-|:----|:-----------|:-------|:--------:|
118
-| vm.stats.vm.v_swappgs | Enable or disable infoormation about SWAP I/O metric. | yes | no |
119
-
120
-</details>
124
122
-#### Examples
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/freebsd.plugin/integrations/vm.swap_info.md
+16
-13
@@ -85,7 +85,21 @@ No action required.
85
86
### Configuration
87
88
-#### File
88
+#### Options
89
+
90
+
91
+
92
+<details open><summary>Config options</summary>
93
+
94
+| Name | Description | Default | Required |
95
+|:----|:-----------|:-------|:--------:|
96
+| vm.swap_info | Enable or disable SWAP metrics. | yes | no |
97
+
98
+</details>
99
+
100
+
101
+
102
+#### via File
103
104
The configuration file name for this integration is `netdata.conf`.
105
Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file.
@@ -107,19 +121,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
sudo ./edit-config netdata.conf
123
```
110
-#### Options
111
-
112
-
113
-
114
-<details open><summary>Config options</summary>
115
-
116
-| Name | Description | Default | Required |
117
-|:----|:-----------|:-------|:--------:|
118
-| vm.swap_info | Enable or disable SWAP metrics. | yes | no |
119
-
120
-</details>
124
122
-#### Examples
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/freebsd.plugin/integrations/vm.vmtotal.md
+18
-15
@@ -87,7 +87,23 @@ No action required.
87
88
### Configuration
89
90
-#### File
90
+#### Options
91
+
92
+
93
+
94
+<details open><summary>Config Options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| enable total processes | Number of active processes. | yes | no |
99
+| processes running | Show number of processes running or blocked. | yes | no |
100
+| real memory | Memeory used on host. | yes | no |
101
+
102
+</details>
103
+
104
+
105
+
106
+#### via File
107
108
The configuration file name for this integration is `netdata.conf`.
109
Configuration for this specific integration is located in the `[plugin:freebsd:vm.vmtotal]` section within that file.
@@ -109,21 +125,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
125
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
126
sudo ./edit-config netdata.conf
127
```
112
-#### Options
113
-
114
-
115
-
116
-<details open><summary>Config Options</summary>
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| enable total processes | Number of active processes. | yes | no |
121
-| processes running | Show number of processes running or blocked. | yes | no |
122
-| real memory | Memeory used on host. | yes | no |
123
-
124
-</details>
128
126
-#### Examples
129
+##### Examples
130
There are no configuration examples.
131
132
src/collectors/freebsd.plugin/integrations/zfs.md
+16
-13
@@ -112,7 +112,21 @@ No action required.
112
113
### Configuration
114
115
-#### File
115
+#### Options
116
+
117
+
118
+
119
+<details open><summary>Config options</summary>
120
+
121
+| Name | Description | Default | Required |
122
+|:----|:-----------|:-------|:--------:|
123
+| show zero charts | Do not show charts with zero metrics. | no | no |
124
+
125
+</details>
126
+
127
+
128
+
129
+#### via File
130
131
The configuration file name for this integration is `netdata.conf`.
132
Configuration for this specific integration is located in the `[plugin:freebsd:zfs_arcstats]` section within that file.
@@ -134,19 +148,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
148
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
149
sudo ./edit-config netdata.conf
150
```
137
-#### Options
138
-
139
-
140
-
141
-<details open><summary>Config options</summary>
142
-
143
-| Name | Description | Default | Required |
144
-|:----|:-----------|:-------|:--------:|
145
-| show zero charts | Do not show charts with zero metrics. | no | no |
146
-
147
-</details>
151
149
-#### Examples
152
+##### Examples
153
There are no configuration examples.
154
155
src/collectors/freeipmi.plugin/integrations/intelligent_platform_management_interface_ipmi.md
+29
-26
@@ -128,28 +128,6 @@ to initialize IPMI settings so that the Netdata plugin works correctly. It shoul
128
129
### Configuration
130
131
-#### File
132
-
133
-The configuration file name for this integration is `netdata.conf`.
134
-Configuration for this specific integration is located in the `[plugin:freeipmi]` section within that file.
135
-
136
-The file format is a modified INI syntax. The general structure is:
137
-
138
-```ini
139
-[section1]
140
- option1 = some value
141
- option2 = some other value
142
-
143
-[section2]
144
- option3 = some third value
145
-```
146
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-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).
148
-
149
-```bash
150
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
-sudo ./edit-config netdata.conf
152
-```
131
#### Options
132
133
The configuration is set using command line options:
@@ -198,9 +176,34 @@ To display a help message listing the available command line options:
176
177
</details>
178
201
-#### Examples
179
203
-##### Decrease data collection frequency
180
+
181
+#### via File
182
+
183
+The configuration file name for this integration is `netdata.conf`.
184
+Configuration for this specific integration is located in the `[plugin:freeipmi]` section within that file.
185
+
186
+The file format is a modified INI syntax. The general structure is:
187
+
188
+```ini
189
+[section1]
190
+ option1 = some value
191
+ option2 = some other value
192
+
193
+[section2]
194
+ option3 = some third value
195
+```
196
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
197
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
198
+
199
+```bash
200
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
201
+sudo ./edit-config netdata.conf
202
+```
203
+
204
+##### Examples
205
+
206
+###### Decrease data collection frequency
207
208
Basic example decreasing data collection frequency. The minimum `update every` is 5 (enforced internally by the plugin). IPMI is slow and CPU hungry. So, once every 5 seconds is pretty acceptable.
209
@@ -209,7 +212,7 @@ Basic example decreasing data collection frequency. The minimum `update every` i
212
update every = 10
213
214
```
212
-##### Disable SEL collection
215
+###### Disable SEL collection
216
217
Append to `command options =` the options you need.
218
@@ -222,7 +225,7 @@ Append to `command options =` the options you need.
225
```
226
</details>
227
225
-##### Ignore specific sensors
228
+###### Ignore specific sensors
229
230
Specific sensor IDs can be excluded from freeipmi tools by editing `/etc/freeipmi/freeipmi.conf` and setting the IDs to be ignored at `ipmi-sensors-exclude-record-ids`.
231
src/collectors/idlejitter.plugin/integrations/idle_os_jitter.md
+13
-10
@@ -82,7 +82,18 @@ No action required.
82
83
### Configuration
84
85
-#### File
85
+#### Options
86
+
87
+This integration only supports a single configuration option, and most users will not need to change it.
88
+
89
+
90
+| Name | Description | Default | Required |
91
+|:----|:-----------|:-------|:--------:|
92
+| loop time | Specifies the target time for the data collection thread to sleep, measured in miliseconds. | 20ms | no |
93
+
94
+
95
+
96
+#### via File
97
98
The configuration file name for this integration is `netdata.conf`.
99
@@ -103,16 +114,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
114
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
115
sudo ./edit-config netdata.conf
116
```
106
-#### Options
107
-
108
-This integration only supports a single configuration option, and most users will not need to change it.
109
-
110
-
111
-| Name | Description | Default | Required |
112
-|:----|:-----------|:-------|:--------:|
113
-| loop time | Specifies the target time for the data collection thread to sleep, measured in miliseconds. | 20ms | no |
117
115
-#### Examples
118
+##### Examples
119
There are no configuration examples.
120
121
src/collectors/ioping.plugin/integrations/ioping.md
+20
-17
@@ -89,7 +89,24 @@ You can install the command by passing the argument `install` to the plugin (`/u
89
90
### Configuration
91
92
-#### File
92
+#### Options
93
+
94
+
95
+
96
+<details open><summary>Config options</summary>
97
+
98
+| Name | Description | Default | Required |
99
+|:----|:-----------|:-------|:--------:|
100
+| update_every | Data collection frequency. | 1s | no |
101
+| destination | The directory/file/device to ioping. | | yes |
102
+| request_size | The request size in bytes to ioping the destination (symbolic modifiers are supported) | 4k | no |
103
+| ioping_opts | Options passed to `ioping` commands. | -T 1000000 | no |
104
+
105
+</details>
106
+
107
+
108
+
109
+#### via File
110
111
The configuration file name for this integration is `ioping.conf`.
112
@@ -106,24 +123,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
123
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
124
sudo ./edit-config ioping.conf
125
```
109
-#### Options
110
-
111
-
112
-
113
-<details open><summary>Config options</summary>
114
-
115
-| Name | Description | Default | Required |
116
-|:----|:-----------|:-------|:--------:|
117
-| update_every | Data collection frequency. | 1s | no |
118
-| destination | The directory/file/device to ioping. | | yes |
119
-| request_size | The request size in bytes to ioping the destination (symbolic modifiers are supported) | 4k | no |
120
-| ioping_opts | Options passed to `ioping` commands. | -T 1000000 | no |
121
-
122
-</details>
126
124
-#### Examples
127
+##### Examples
128
126
-##### Basic Configuration
129
+###### Basic Configuration
130
131
This example has the minimum configuration necessary to have the plugin running.
132
src/collectors/macos.plugin/integrations/macos.md
+27
-24
@@ -174,27 +174,6 @@ No action required.
174
175
### Configuration
176
177
-#### File
178
-
179
-The configuration file name for this integration is `netdata.conf`.
180
-
181
-The file format is a modified INI syntax. The general structure is:
182
-
183
-```ini
184
-[section1]
185
- option1 = some value
186
- option2 = some other value
187
-
188
-[section2]
189
- option3 = some third value
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).
193
-
194
-```bash
195
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
196
-sudo ./edit-config netdata.conf
197
-```
177
#### Options
178
179
There are three sections in the file which you can configure:
@@ -249,9 +228,33 @@ There are three sections in the file which you can configure:
228
229
</details>
230
252
-#### Examples
231
254
-##### Disable swap monitoring.
232
+
233
+#### via File
234
+
235
+The configuration file name for this integration is `netdata.conf`.
236
+
237
+The file format is a modified INI syntax. The general structure is:
238
+
239
+```ini
240
+[section1]
241
+ option1 = some value
242
+ option2 = some other value
243
+
244
+[section2]
245
+ option3 = some third value
246
+```
247
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
248
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
249
+
250
+```bash
251
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
252
+sudo ./edit-config netdata.conf
253
+```
254
+
255
+##### Examples
256
+
257
+###### Disable swap monitoring.
258
259
A basic example that discards swap monitoring
260
@@ -266,7 +269,7 @@ A basic example that discards swap monitoring
269
```
270
</details>
271
269
-##### Disable complete Machine SMI section.
272
+###### Disable complete Machine SMI section.
273
274
A basic example that discards swap monitoring
275
src/collectors/nfacct.plugin/integrations/netfilter.md
+17
-14
@@ -91,7 +91,22 @@ Install `libmnl-dev` and `libnetfilter-acct-dev` using the package manager of yo
91
92
### Configuration
93
94
-#### File
94
+#### Options
95
+
96
+
97
+
98
+<details open><summary>Config options</summary>
99
+
100
+| Name | Description | Default | Required |
101
+|:----|:-----------|:-------|:--------:|
102
+| update every | Data collection frequency. | 1 | no |
103
+| command options | Additinal parameters for collector | | no |
104
+
105
+</details>
106
+
107
+
108
+
109
+#### via File
110
111
The configuration file name for this integration is `netdata.conf`.
112
Configuration for this specific integration is located in the `[plugin:nfacct]` section within that file.
@@ -113,20 +128,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
128
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
129
sudo ./edit-config netdata.conf
130
```
116
-#### Options
117
-
118
-
119
-
120
-<details open><summary>Config options</summary>
121
-
122
-| Name | Description | Default | Required |
123
-|:----|:-----------|:-------|:--------:|
124
-| update every | Data collection frequency. | 1 | no |
125
-| command options | Additinal parameters for collector | | no |
126
-
127
-</details>
131
129
-#### Examples
132
+##### Examples
133
There are no configuration examples.
134
135
src/collectors/perf.plugin/integrations/cpu_performance.md
+24
-21
@@ -117,7 +117,27 @@ Change the value of the `perf` setting to `yes` in the `[plugins]` section. Save
117
118
### Configuration
119
120
-#### File
120
+#### Options
121
+
122
+You can get the available options running:
123
+
124
+```bash
125
+/usr/libexec/netdata/plugins.d/perf.plugin --help
126
+````
127
+
128
+
129
+<details open><summary>Config options</summary>
130
+
131
+| Name | Description | Default | Required |
132
+|:----|:-----------|:-------|:--------:|
133
+| update every | Data collection frequency. | 1 | no |
134
+| command options | Command options that specify charts shown by the plugin. `cycles`, `instructions`, `branch`, `cache`, `bus`, `stalled`, `migrations`, `alignment`, `emulation`, `L1D`, `L1D-prefetch`, `L1I`, `LL`, `DTLB`, `ITLB`, `PBU`. | 1 | yes |
135
+
136
+</details>
137
+
138
+
139
+
140
+#### via File
141
142
The configuration file name for this integration is `netdata.conf`.
143
Configuration for this specific integration is located in the `[plugin:perf]` section within that file.
@@ -139,27 +159,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
159
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
sudo ./edit-config netdata.conf
161
```
142
-#### Options
143
-
144
-You can get the available options running:
145
-
146
-```bash
147
-/usr/libexec/netdata/plugins.d/perf.plugin --help
148
-````
149
-
150
-
151
-<details open><summary>Config options</summary>
152
-
153
-| Name | Description | Default | Required |
154
-|:----|:-----------|:-------|:--------:|
155
-| update every | Data collection frequency. | 1 | no |
156
-| command options | Command options that specify charts shown by the plugin. `cycles`, `instructions`, `branch`, `cache`, `bus`, `stalled`, `migrations`, `alignment`, `emulation`, `L1D`, `L1D-prefetch`, `L1I`, `LL`, `DTLB`, `ITLB`, `PBU`. | 1 | yes |
157
-
158
-</details>
162
160
-#### Examples
163
+##### Examples
164
162
-##### All metrics
165
+###### All metrics
166
167
Monitor all metrics available.
168
@@ -168,7 +171,7 @@ Monitor all metrics available.
171
command options = all
172
173
```
171
-##### CPU cycles
174
+###### CPU cycles
175
176
Monitor CPU cycles.
177
src/collectors/proc.plugin/integrations/amd_gpu.md
+7
-4
@@ -95,16 +95,19 @@ No action required.
95
96
### Configuration
97
98
-#### File
99
-
100
-There is no configuration file.
98
#### Options
99
100
101
102
There are no configuration options.
103
107
-#### Examples
104
+
105
+
106
+#### via File
107
+
108
+There is no configuration file.
109
+
110
+##### Examples
111
There are no configuration examples.
112
113
src/collectors/proc.plugin/integrations/btrfs.md
+7
-4
@@ -122,16 +122,19 @@ No action required.
122
123
### Configuration
124
125
-#### File
126
-
127
-There is no configuration file.
125
#### Options
126
127
128
129
There are no configuration options.
130
134
-#### Examples
131
+
132
+
133
+#### via File
134
+
135
+There is no configuration file.
136
+
137
+##### Examples
138
There are no configuration examples.
139
140
src/collectors/proc.plugin/integrations/conntrack.md
+7
-4
@@ -90,16 +90,19 @@ No action required.
90
91
### Configuration
92
93
-#### File
94
-
95
-There is no configuration file.
93
#### Options
94
95
96
97
There are no configuration options.
98
102
-#### Examples
99
+
100
+
101
+#### via File
102
+
103
+There is no configuration file.
104
+
105
+##### Examples
106
There are no configuration examples.
107
108
src/collectors/proc.plugin/integrations/disk_statistics.md
+7
-4
@@ -134,16 +134,19 @@ No action required.
134
135
### Configuration
136
137
-#### File
138
-
139
-There is no configuration file.
137
#### Options
138
139
140
141
There are no configuration options.
142
146
-#### Examples
143
+
144
+
145
+#### via File
146
+
147
+There is no configuration file.
148
+
149
+##### Examples
150
There are no configuration examples.
151
152
src/collectors/proc.plugin/integrations/entropy.md
+7
-4
@@ -118,16 +118,19 @@ No action required.
118
119
### Configuration
120
121
-#### File
122
-
123
-There is no configuration file.
121
#### Options
122
123
124
125
There are no configuration options.
126
130
-#### Examples
127
+
128
+
129
+#### via File
130
+
131
+There is no configuration file.
132
+
133
+##### Examples
134
There are no configuration examples.
135
136
src/collectors/proc.plugin/integrations/infiniband.md
+7
-4
@@ -84,16 +84,19 @@ No action required.
84
85
### Configuration
86
87
-#### File
88
-
89
-There is no configuration file.
87
#### Options
88
89
90
91
There are no configuration options.
92
96
-#### Examples
93
+
94
+
95
+#### via File
96
+
97
+There is no configuration file.
98
+
99
+##### Examples
100
There are no configuration examples.
101
102
src/collectors/proc.plugin/integrations/inter_process_communication.md
+7
-4
@@ -105,16 +105,19 @@ No action required.
105
106
### Configuration
107
108
-#### File
109
-
110
-There is no configuration file.
108
#### Options
109
110
111
112
There are no configuration options.
113
117
-#### Examples
114
+
115
+
116
+#### via File
117
+
118
+There is no configuration file.
119
+
120
+##### Examples
121
There are no configuration examples.
122
123
src/collectors/proc.plugin/integrations/interrupts.md
+7
-4
@@ -126,16 +126,19 @@ No action required.
126
127
### Configuration
128
129
-#### File
130
-
131
-There is no configuration file.
129
#### Options
130
131
132
133
There are no configuration options.
134
138
-#### Examples
135
+
136
+
137
+#### via File
138
+
139
+There is no configuration file.
140
+
141
+##### Examples
142
There are no configuration examples.
143
144
src/collectors/proc.plugin/integrations/ip_virtual_server.md
+7
-4
@@ -82,16 +82,19 @@ No action required.
82
83
### Configuration
84
85
-#### File
86
-
87
-There is no configuration file.
85
#### Options
86
87
88
89
There are no configuration options.
90
94
-#### Examples
91
+
92
+
93
+#### via File
94
+
95
+There is no configuration file.
96
+
97
+##### Examples
98
There are no configuration examples.
99
100
src/collectors/proc.plugin/integrations/ipv6_socket_statistics.md
+7
-4
@@ -84,16 +84,19 @@ No action required.
84
85
### Configuration
86
87
-#### File
88
-
89
-There is no configuration file.
87
#### Options
88
89
90
91
There are no configuration options.
92
96
-#### Examples
93
+
94
+
95
+#### via File
96
+
97
+There is no configuration file.
98
+
99
+##### Examples
100
There are no configuration examples.
101
102
src/collectors/proc.plugin/integrations/kernel_same-page_merging.md
+7
-4
@@ -88,16 +88,19 @@ No action required.
88
89
### Configuration
90
91
-#### File
92
-
93
-There is no configuration file.
91
#### Options
92
93
94
95
There are no configuration options.
96
100
-#### Examples
97
+
98
+
99
+#### via File
100
+
101
+There is no configuration file.
102
+
103
+##### Examples
104
There are no configuration examples.
105
106
src/collectors/proc.plugin/integrations/md_raid.md
+7
-4
@@ -110,16 +110,19 @@ No action required.
110
111
### Configuration
112
113
-#### File
114
-
115
-There is no configuration file.
113
#### Options
114
115
116
117
There are no configuration options.
118
122
-#### Examples
119
+
120
+
121
+#### via File
122
+
123
+There is no configuration file.
124
+
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/proc.plugin/integrations/memory_modules_dimms.md
+7
-4
@@ -131,16 +131,19 @@ No action required.
131
132
### Configuration
133
134
-#### File
135
-
136
-There is no configuration file.
134
#### Options
135
136
137
138
There are no configuration options.
139
143
-#### Examples
140
+
141
+
142
+#### via File
143
+
144
+There is no configuration file.
145
+
146
+##### Examples
147
There are no configuration examples.
148
149
src/collectors/proc.plugin/integrations/memory_statistics.md
+7
-4
@@ -123,16 +123,19 @@ No action required.
123
124
### Configuration
125
126
-#### File
127
-
128
-There is no configuration file.
126
#### Options
127
128
129
130
There are no configuration options.
131
135
-#### Examples
132
+
133
+
134
+#### via File
135
+
136
+There is no configuration file.
137
+
138
+##### Examples
139
There are no configuration examples.
140
141
src/collectors/proc.plugin/integrations/memory_usage.md
+7
-4
@@ -120,16 +120,19 @@ No action required.
120
121
### Configuration
122
123
-#### File
124
-
125
-There is no configuration file.
123
#### Options
124
125
126
127
There are no configuration options.
128
132
-#### Examples
129
+
130
+
131
+#### via File
132
+
133
+There is no configuration file.
134
+
135
+##### Examples
136
There are no configuration examples.
137
138
src/collectors/proc.plugin/integrations/network_interfaces.md
+7
-4
@@ -122,16 +122,19 @@ No action required.
122
123
### Configuration
124
125
-#### File
126
-
127
-There is no configuration file.
125
#### Options
126
127
128
129
There are no configuration options.
130
134
-#### Examples
131
+
132
+
133
+#### via File
134
+
135
+There is no configuration file.
136
+
137
+##### Examples
138
There are no configuration examples.
139
140
src/collectors/proc.plugin/integrations/network_statistics.md
+7
-4
@@ -145,16 +145,19 @@ No action required.
145
146
### Configuration
147
148
-#### File
149
-
150
-There is no configuration file.
148
#### Options
149
150
151
152
There are no configuration options.
153
157
-#### Examples
154
+
155
+
156
+#### via File
157
+
158
+There is no configuration file.
159
+
160
+##### Examples
161
There are no configuration examples.
162
163
src/collectors/proc.plugin/integrations/nfs_client.md
+7
-4
@@ -84,16 +84,19 @@ No action required.
84
85
### Configuration
86
87
-#### File
88
-
89
-There is no configuration file.
87
#### Options
88
89
90
91
There are no configuration options.
92
96
-#### Examples
93
+
94
+
95
+#### via File
96
+
97
+There is no configuration file.
98
+
99
+##### Examples
100
There are no configuration examples.
101
102
src/collectors/proc.plugin/integrations/nfs_server.md
+7
-4
@@ -89,16 +89,19 @@ No action required.
89
90
### Configuration
91
92
-#### File
93
-
94
-There is no configuration file.
92
#### Options
93
94
95
96
There are no configuration options.
97
101
-#### Examples
98
+
99
+
100
+#### via File
101
+
102
+There is no configuration file.
103
+
104
+##### Examples
105
There are no configuration examples.
106
107
src/collectors/proc.plugin/integrations/non-uniform_memory_access.md
+7
-4
@@ -96,16 +96,19 @@ No action required.
96
97
### Configuration
98
99
-#### File
100
-
101
-There is no configuration file.
99
#### Options
100
101
102
103
There are no configuration options.
104
108
-#### Examples
105
+
106
+
107
+#### via File
108
+
109
+There is no configuration file.
110
+
111
+##### Examples
112
There are no configuration examples.
113
114
src/collectors/proc.plugin/integrations/page_types.md
+7
-4
@@ -98,16 +98,19 @@ No action required.
98
99
### Configuration
100
101
-#### File
102
-
103
-There is no configuration file.
101
#### Options
102
103
104
105
There are no configuration options.
106
110
-#### Examples
107
+
108
+
109
+#### via File
110
+
111
+There is no configuration file.
112
+
113
+##### Examples
114
There are no configuration examples.
115
116
src/collectors/proc.plugin/integrations/power_supply.md
+7
-4
@@ -93,16 +93,19 @@ No action required.
93
94
### Configuration
95
96
-#### File
97
-
98
-There is no configuration file.
96
#### Options
97
98
99
100
There are no configuration options.
101
105
-#### Examples
102
+
103
+
104
+#### via File
105
+
106
+There is no configuration file.
107
+
108
+##### Examples
109
There are no configuration examples.
110
111
src/collectors/proc.plugin/integrations/pressure_stall_information.md
+7
-4
@@ -114,16 +114,19 @@ No action required.
114
115
### Configuration
116
117
-#### File
118
-
119
-There is no configuration file.
117
#### Options
118
119
120
121
There are no configuration options.
122
126
-#### Examples
123
+
124
+
125
+#### via File
126
+
127
+There is no configuration file.
128
+
129
+##### Examples
130
There are no configuration examples.
131
132
src/collectors/proc.plugin/integrations/sctp_statistics.md
+7
-4
@@ -84,16 +84,19 @@ No action required.
84
85
### Configuration
86
87
-#### File
88
-
89
-There is no configuration file.
87
#### Options
88
89
90
91
There are no configuration options.
92
96
-#### Examples
93
+
94
+
95
+#### via File
96
+
97
+There is no configuration file.
98
+
99
+##### Examples
100
There are no configuration examples.
101
102
src/collectors/proc.plugin/integrations/socket_statistics.md
+7
-4
@@ -94,16 +94,19 @@ No action required.
94
95
### Configuration
96
97
-#### File
98
-
99
-There is no configuration file.
97
#### Options
98
99
100
101
There are no configuration options.
102
106
-#### Examples
103
+
104
+
105
+#### via File
106
+
107
+There is no configuration file.
108
+
109
+##### Examples
110
There are no configuration examples.
111
112
src/collectors/proc.plugin/integrations/softirq_statistics.md
+7
-4
@@ -118,16 +118,19 @@ No action required.
118
119
### Configuration
120
121
-#### File
122
-
123
-There is no configuration file.
121
#### Options
122
123
124
125
There are no configuration options.
126
130
-#### Examples
127
+
128
+
129
+#### via File
130
+
131
+There is no configuration file.
132
+
133
+##### Examples
134
There are no configuration examples.
135
136
src/collectors/proc.plugin/integrations/softnet_statistics.md
+7
-4
@@ -120,16 +120,19 @@ No action required.
120
121
### Configuration
122
123
-#### File
124
-
125
-There is no configuration file.
123
#### Options
124
125
126
127
There are no configuration options.
128
132
-#### Examples
129
+
130
+
131
+#### via File
132
+
133
+There is no configuration file.
134
+
135
+##### Examples
136
There are no configuration examples.
137
138
src/collectors/proc.plugin/integrations/synproxy.md
+7
-4
@@ -82,16 +82,19 @@ No action required.
82
83
### Configuration
84
85
-#### File
86
-
87
-There is no configuration file.
85
#### Options
86
87
88
89
There are no configuration options.
90
94
-#### Examples
91
+
92
+
93
+#### via File
94
+
95
+There is no configuration file.
96
+
97
+##### Examples
98
There are no configuration examples.
99
100
src/collectors/proc.plugin/integrations/system_load_average.md
+7
-4
@@ -113,16 +113,19 @@ No action required.
113
114
### Configuration
115
116
-#### File
117
-
118
-There is no configuration file.
116
#### Options
117
118
119
120
There are no configuration options.
121
125
-#### Examples
122
+
123
+
124
+#### via File
125
+
126
+There is no configuration file.
127
+
128
+##### Examples
129
There are no configuration examples.
130
131
src/collectors/proc.plugin/integrations/system_statistics.md
+10
-7
@@ -135,7 +135,15 @@ No action required.
135
136
### Configuration
137
138
-#### File
138
+#### Options
139
+
140
+
141
+
142
+There are no configuration options.
143
+
144
+
145
+
146
+#### via File
147
148
The configuration file name for this integration is `netdata.conf`.
149
Configuration for this specific integration is located in the `plugin:proc:/proc/stat` section within that file.
@@ -157,13 +165,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
165
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
166
sudo ./edit-config netdata.conf
167
```
160
-#### Options
161
-
162
-
163
-
164
-There are no configuration options.
168
166
-#### Examples
169
+##### Examples
170
There are no configuration examples.
171
172
src/collectors/proc.plugin/integrations/system_uptime.md
+7
-4
@@ -93,16 +93,19 @@ No action required.
93
94
### Configuration
95
96
-#### File
97
-
98
-There is no configuration file.
96
#### Options
97
98
99
100
There are no configuration options.
101
105
-#### Examples
102
+
103
+
104
+#### via File
105
+
106
+There is no configuration file.
107
+
108
+##### Examples
109
There are no configuration examples.
110
111
src/collectors/proc.plugin/integrations/wireless_network_interfaces.md
+7
-4
@@ -85,16 +85,19 @@ No action required.
85
86
### Configuration
87
88
-#### File
89
-
90
-There is no configuration file.
88
#### Options
89
90
91
92
There are no configuration options.
93
97
-#### Examples
94
+
95
+
96
+#### via File
97
+
98
+There is no configuration file.
99
+
100
+##### Examples
101
There are no configuration examples.
102
103
src/collectors/proc.plugin/integrations/zfs_adaptive_replacement_cache.md
+7
-4
@@ -110,16 +110,19 @@ No action required.
110
111
### Configuration
112
113
-#### File
114
-
115
-There is no configuration file.
113
#### Options
114
115
116
117
There are no configuration options.
118
122
-#### Examples
119
+
120
+
121
+#### via File
122
+
123
+There is no configuration file.
124
+
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/proc.plugin/integrations/zram.md
+7
-4
@@ -91,16 +91,19 @@ No action required.
91
92
### Configuration
93
94
-#### File
95
-
96
-There is no configuration file.
94
#### Options
95
96
97
98
There are no configuration options.
99
103
-#### Examples
100
+
101
+
102
+#### via File
103
+
104
+There is no configuration file.
105
+
106
+##### Examples
107
There are no configuration examples.
108
109
src/collectors/python.d.plugin/am2320/integrations/am2320.md
+26
-23
@@ -101,27 +101,6 @@ Install the Adafruit Circuit Python AM2320 library:
101
102
### Configuration
103
104
-#### File
105
-
106
-The configuration file name for this integration is `python.d/am2320.conf`.
107
-
108
-The file format is YAML. Generally, the structure is:
109
-
110
-```yaml
111
-update_every: 1
112
-autodetection_retry: 0
113
-
114
-job_name:
115
- job_option1: some_value
116
- job_option2: some_other_vlaue
117
-```
118
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
-
121
-```bash
122
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
-sudo ./edit-config python.d/am2320.conf
124
-```
104
#### Options
105
106
There are 2 sections:
@@ -148,9 +127,33 @@ Every configuration JOB starts with a `job_name` value which will appear in the
127
128
</details>
129
151
-#### Examples
130
153
-##### Local sensor
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `python.d/am2320.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+
142
+job_name:
143
+ job_option1: some_value
144
+ job_option2: some_other_vlaue
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).
148
+
149
+```bash
150
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
+sudo ./edit-config python.d/am2320.conf
152
+```
153
+
154
+##### Examples
155
+
156
+###### Local sensor
157
158
A basic JOB configuration
159
src/collectors/python.d.plugin/go_expvar/integrations/go_applications_expvar.md
+26
-23
@@ -166,27 +166,6 @@ number of currently running Goroutines and updates these stats every second.
166
167
### Configuration
168
169
-#### File
170
-
171
-The configuration file name for this integration is `python.d/go_expvar.conf`.
172
-
173
-The file format is YAML. Generally, the structure is:
174
-
175
-```yaml
176
-update_every: 1
177
-autodetection_retry: 0
178
-
179
-job_name:
180
- job_option1: some_value
181
- job_option2: some_other_vlaue
182
-```
183
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
184
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
185
-
186
-```bash
187
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
188
-sudo ./edit-config python.d/go_expvar.conf
189
-```
169
#### Options
170
171
There are 2 sections:
@@ -218,9 +197,33 @@ Every configuration JOB starts with a `job_name` value which will appear in the
197
198
</details>
199
221
-#### Examples
200
223
-##### Monitor a Go app1 application
201
+
202
+#### via File
203
+
204
+The configuration file name for this integration is `python.d/go_expvar.conf`.
205
+
206
+The file format is YAML. Generally, the structure is:
207
+
208
+```yaml
209
+update_every: 1
210
+autodetection_retry: 0
211
+
212
+job_name:
213
+ job_option1: some_value
214
+ job_option2: some_other_vlaue
215
+```
216
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
217
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
218
+
219
+```bash
220
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
221
+sudo ./edit-config python.d/go_expvar.conf
222
+```
223
+
224
+##### Examples
225
+
226
+###### Monitor a Go app1 application
227
228
The example below sets a configuration for a Go application, called `app1`. Besides the `memstats`, the application also exposes two counters and the number of currently running Goroutines and updates these stats every second.
229
src/collectors/python.d.plugin/pandas/integrations/pandas.md
+30
-27
@@ -103,27 +103,6 @@ sudo pip install 'sqlalchemy<2.0' psycopg2-binary
103
104
### Configuration
105
106
-#### File
107
-
108
-The configuration file name for this integration is `python.d/pandas.conf`.
109
-
110
-The file format is YAML. Generally, the structure is:
111
-
112
-```yaml
113
-update_every: 1
114
-autodetection_retry: 0
115
-
116
-job_name:
117
- job_option1: some_value
118
- job_option2: some_other_vlaue
119
-```
120
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
121
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
122
-
123
-```bash
124
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
125
-sudo ./edit-config python.d/pandas.conf
126
-```
106
#### Options
107
108
There are 2 sections:
@@ -158,9 +137,33 @@ Every configuration JOB starts with a `job_name` value which will appear in the
137
138
</details>
139
161
-#### Examples
140
163
-##### Temperature API Example
141
+
142
+#### via File
143
+
144
+The configuration file name for this integration is `python.d/pandas.conf`.
145
+
146
+The file format is YAML. Generally, the structure is:
147
+
148
+```yaml
149
+update_every: 1
150
+autodetection_retry: 0
151
+
152
+job_name:
153
+ job_option1: some_value
154
+ job_option2: some_other_vlaue
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).
158
+
159
+```bash
160
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
161
+sudo ./edit-config python.d/pandas.conf
162
+```
163
+
164
+##### Examples
165
+
166
+###### Temperature API Example
167
168
example pulling some hourly temperature data, a chart for today forecast (mean,min,max) and another chart for current.
169
@@ -232,7 +235,7 @@ temperature:
235
```
236
</details>
237
235
-##### API CSV Example
238
+###### API CSV Example
239
240
example showing a read_csv from a url and some light pandas data wrangling.
241
@@ -260,7 +263,7 @@ example_csv:
263
```
264
</details>
265
263
-##### API JSON Example
266
+###### API JSON Example
267
268
example showing a read_json from a url and some light pandas data wrangling.
269
@@ -287,7 +290,7 @@ example_json:
290
```
291
</details>
292
290
-##### XML Example
293
+###### XML Example
294
295
example showing a read_xml from a url and some light pandas data wrangling.
296
@@ -313,7 +316,7 @@ example_xml:
316
```
317
</details>
318
316
-##### SQL Example
319
+###### SQL Example
320
321
example showing a read_sql from a postgres database using sqlalchemy.
322
src/collectors/slabinfo.plugin/integrations/linux_kernel_slab_allocator_statistics.md
+16
-13
@@ -91,7 +91,21 @@ If you installed `netdata` using a package manager, it is also necessary to inst
91
92
### Configuration
93
94
-#### File
94
+#### Options
95
+
96
+
97
+
98
+<details open><summary>The main configuration file.</summary>
99
+
100
+| Name | Description | Default | Required |
101
+|:----|:-----------|:-------|:--------:|
102
+| Enable plugin | As described above plugin is disabled by default, this option is used to enable plugin. | no | yes |
103
+
104
+</details>
105
+
106
+
107
+
108
+#### via File
109
110
The configuration file name for this integration is `netdata.conf`.
111
Configuration for this specific integration is located in the `[plugins]` section within that file.
@@ -113,19 +127,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
127
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
128
sudo ./edit-config netdata.conf
129
```
116
-#### Options
117
-
118
-
119
-
120
-<details open><summary>The main configuration file.</summary>
121
-
122
-| Name | Description | Default | Required |
123
-|:----|:-----------|:-------|:--------:|
124
-| Enable plugin | As described above plugin is disabled by default, this option is used to enable plugin. | no | yes |
125
-
126
-</details>
130
128
-#### Examples
131
+##### Examples
132
There are no configuration examples.
133
134
src/collectors/tc.plugin/integrations/tc_qos_classes.md
+18
-15
@@ -101,7 +101,22 @@ tc_show="class"
101
102
### Configuration
103
104
-#### File
104
+#### Options
105
+
106
+
107
+
108
+<details open><summary>Config option</summary>
109
+
110
+| Name | Description | Default | Required |
111
+|:----|:-----------|:-------|:--------:|
112
+| script to run to get tc values | Path to script `tc-qos-helper.sh` | usr/libexec/netdata/plugins.d/tc-qos-helper.s | no |
113
+| enable show all classes and qdiscs for all interfaces | yes/no flag to control what data is presented. | yes | no |
114
+
115
+</details>
116
+
117
+
118
+
119
+#### via File
120
121
The configuration file name for this integration is `netdata.conf`.
122
Configuration for this specific integration is located in the `[plugin:tc]` section within that file.
@@ -123,22 +138,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
138
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
139
sudo ./edit-config netdata.conf
140
```
126
-#### Options
127
-
128
-
129
-
130
-<details open><summary>Config option</summary>
131
-
132
-| Name | Description | Default | Required |
133
-|:----|:-----------|:-------|:--------:|
134
-| script to run to get tc values | Path to script `tc-qos-helper.sh` | usr/libexec/netdata/plugins.d/tc-qos-helper.s | no |
135
-| enable show all classes and qdiscs for all interfaces | yes/no flag to control what data is presented. | yes | no |
136
-
137
-</details>
141
139
-#### Examples
142
+##### Examples
143
141
-##### Basic
144
+###### Basic
145
146
A basic example configuration using classes defined in `/etc/iproute2/tc_cls`.
147
src/collectors/timex.plugin/integrations/timex.md
+19
-16
@@ -87,7 +87,23 @@ No action required.
87
88
### Configuration
89
90
-#### File
90
+#### Options
91
+
92
+At least one option ('clock synchronization state', 'time offset') needs to be enabled for this collector to run.
93
+
94
+<details open><summary>Config options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| update every | Data collection frequency. | 1 | no |
99
+| clock synchronization state | Make chart showing system clock synchronization state. | yes | yes |
100
+| time offset | Make chart showing computed time offset between local system and reference clock | yes | yes |
101
+
102
+</details>
103
+
104
+
105
+
106
+#### via File
107
108
The configuration file name for this integration is `netdata.conf`.
109
Configuration for this specific integration is located in the `[plugin:timex]` section within that file.
@@ -109,23 +125,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
125
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
126
sudo ./edit-config netdata.conf
127
```
112
-#### Options
113
-
114
-At least one option ('clock synchronization state', 'time offset') needs to be enabled for this collector to run.
115
-
116
-<details open><summary>Config options</summary>
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| update every | Data collection frequency. | 1 | no |
121
-| clock synchronization state | Make chart showing system clock synchronization state. | yes | yes |
122
-| time offset | Make chart showing computed time offset between local system and reference clock | yes | yes |
123
-
124
-</details>
128
126
-#### Examples
129
+##### Examples
130
128
-##### Basic
131
+###### Basic
132
133
A basic configuration example.
134
src/collectors/windows.plugin/integrations/active_directory.md
+12
-9
@@ -100,7 +100,17 @@ No action required.
100
101
### Configuration
102
103
-#### File
103
+#### Options
104
+
105
+
106
+
107
+| Name | Description | Default | Required |
108
+|:----|:-----------|:-------|:--------:|
109
+| update every | Data collection frequency. | 10 | no |
110
+
111
+
112
+
113
+#### via File
114
115
The configuration file name for this integration is `netdata.conf`.
116
Configuration for this specific integration is located in the `[plugin:windows:PerflibAD]` section within that file.
@@ -122,15 +132,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
132
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
133
sudo ./edit-config netdata.conf
134
```
125
-#### Options
126
-
127
-
128
-
129
-| Name | Description | Default | Required |
130
-|:----|:-----------|:-------|:--------:|
131
-| update every | Data collection frequency. | 10 | no |
135
133
-#### Examples
136
+##### Examples
137
There are no configuration examples.
138
139
src/collectors/windows.plugin/integrations/active_directory_certificate_service.md
+12
-9
@@ -104,7 +104,17 @@ No action required.
104
105
### Configuration
106
107
-#### File
107
+#### Options
108
+
109
+
110
+
111
+| Name | Description | Default | Required |
112
+|:----|:-----------|:-------|:--------:|
113
+| update every | Data collection frequency. | 10 | no |
114
+
115
+
116
+
117
+#### via File
118
119
The configuration file name for this integration is `netdata.conf`.
120
Configuration for this specific integration is located in the `[plugin:windows:PerflibADCS]` section within that file.
@@ -126,15 +136,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
136
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
137
sudo ./edit-config netdata.conf
138
```
129
-#### Options
130
-
131
-
132
-
133
-| Name | Description | Default | Required |
134
-|:----|:-----------|:-------|:--------:|
135
-| update every | Data collection frequency. | 10 | no |
139
137
-#### Examples
140
+##### Examples
141
There are no configuration examples.
142
143
src/collectors/windows.plugin/integrations/active_directory_federation_service.md
+12
-9
@@ -115,7 +115,17 @@ No action required.
115
116
### Configuration
117
118
-#### File
118
+#### Options
119
+
120
+
121
+
122
+| Name | Description | Default | Required |
123
+|:----|:-----------|:-------|:--------:|
124
+| update every | Data collection frequency. | 10 | no |
125
+
126
+
127
+
128
+#### via File
129
130
The configuration file name for this integration is `netdata.conf`.
131
Configuration for this specific integration is located in the `[plugin:windows:PerflibADFS]` section within that file.
@@ -137,15 +147,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
147
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
148
sudo ./edit-config netdata.conf
149
```
140
-#### Options
141
-
142
-
143
-
144
-| Name | Description | Default | Required |
145
-|:----|:-----------|:-------|:--------:|
146
-| update every | Data collection frequency. | 10 | no |
150
148
-#### Examples
151
+##### Examples
152
There are no configuration examples.
153
154
src/collectors/windows.plugin/integrations/asp.net.md
+12
-9
@@ -129,7 +129,17 @@ No action required.
129
130
### Configuration
131
132
-#### File
132
+#### Options
133
+
134
+
135
+
136
+| Name | Description | Default | Required |
137
+|:----|:-----------|:-------|:--------:|
138
+| PerflibASP | An option to enable or disable the data collection. | yes | no |
139
+
140
+
141
+
142
+#### via File
143
144
The configuration file name for this integration is `netdata.conf`.
145
Configuration for this specific integration is located in the `[plugin:windows]` section within that file.
@@ -151,15 +161,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
161
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
162
sudo ./edit-config netdata.conf
163
```
154
-#### Options
155
-
156
-
157
-
158
-| Name | Description | Default | Required |
159
-|:----|:-----------|:-------|:--------:|
160
-| PerflibASP | An option to enable or disable the data collection. | yes | no |
164
162
-#### Examples
165
+##### Examples
166
There are no configuration examples.
167
168
src/collectors/windows.plugin/integrations/hyper-v.md
+12
-9
@@ -184,7 +184,17 @@ No action required.
184
185
### Configuration
186
187
-#### File
187
+#### Options
188
+
189
+
190
+
191
+| Name | Description | Default | Required |
192
+|:----|:-----------|:-------|:--------:|
193
+| update every | Data collection frequency. | 5 | no |
194
+
195
+
196
+
197
+#### via File
198
199
The configuration file name for this integration is `netdata.conf`.
200
Configuration for this specific integration is located in the `[plugin:windows:PerflibHyperV]` section within that file.
@@ -206,15 +216,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
216
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
217
sudo ./edit-config netdata.conf
218
```
209
-#### Options
210
-
211
-
212
-
213
-| Name | Description | Default | Required |
214
-|:----|:-----------|:-------|:--------:|
215
-| update every | Data collection frequency. | 5 | no |
219
217
-#### Examples
220
+##### Examples
221
There are no configuration examples.
222
223
src/collectors/windows.plugin/integrations/iis.md
+12
-9
@@ -151,7 +151,17 @@ No action required.
151
152
### Configuration
153
154
-#### File
154
+#### Options
155
+
156
+
157
+
158
+| Name | Description | Default | Required |
159
+|:----|:-----------|:-------|:--------:|
160
+| update every | Data collection frequency. | 1 | no |
161
+
162
+
163
+
164
+#### via File
165
166
The configuration file name for this integration is `netdata.conf`.
167
Configuration for this specific integration is located in the `[plugin:windows:PerflibWebService]` section within that file.
@@ -173,15 +183,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
183
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
184
sudo ./edit-config netdata.conf
185
```
176
-#### Options
177
-
178
-
179
-
180
-| Name | Description | Default | Required |
181
-|:----|:-----------|:-------|:--------:|
182
-| update every | Data collection frequency. | 1 | no |
186
184
-#### Examples
187
+##### Examples
188
There are no configuration examples.
189
190
src/collectors/windows.plugin/integrations/memory_statistics.md
+12
-9
@@ -88,7 +88,17 @@ No action required.
88
89
### Configuration
90
91
-#### File
91
+#### Options
92
+
93
+
94
+
95
+| Name | Description | Default | Required |
96
+|:----|:-----------|:-------|:--------:|
97
+| update every | Data collection frequency. | 1 | no |
98
+
99
+
100
+
101
+#### via File
102
103
The configuration file name for this integration is `netdata.conf`.
104
Configuration for this specific integration is located in the `[plugin:windows:PerflibMemory]` section within that file.
@@ -110,15 +120,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
120
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
121
sudo ./edit-config netdata.conf
122
```
113
-#### Options
114
-
115
-
116
-
117
-| Name | Description | Default | Required |
118
-|:----|:-----------|:-------|:--------:|
119
-| update every | Data collection frequency. | 1 | no |
123
121
-#### Examples
124
+##### Examples
125
There are no configuration examples.
126
127
src/collectors/windows.plugin/integrations/ms_exchange.md
+12
-9
@@ -115,7 +115,17 @@ No action required.
115
116
### Configuration
117
118
-#### File
118
+#### Options
119
+
120
+
121
+
122
+| Name | Description | Default | Required |
123
+|:----|:-----------|:-------|:--------:|
124
+| update every | Data collection frequency. | 10 | no |
125
+
126
+
127
+
128
+#### via File
129
130
The configuration file name for this integration is `netdata.conf`.
131
Configuration for this specific integration is located in the `[plugin:windows:PerflibExchange]` section within that file.
@@ -137,15 +147,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
147
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
148
sudo ./edit-config netdata.conf
149
```
140
-#### Options
141
-
142
-
143
-
144
-| Name | Description | Default | Required |
145
-|:----|:-----------|:-------|:--------:|
146
-| update every | Data collection frequency. | 10 | no |
150
148
-#### Examples
151
+##### Examples
152
There are no configuration examples.
153
154
src/collectors/windows.plugin/integrations/ms_sql_server.md
+23
-20
@@ -243,7 +243,26 @@ For **each SQL Server** instance you want to monitor, complete the following ste
243
244
### Configuration
245
246
-#### File
246
+#### Options
247
+
248
+These options allow the collector to connect to your MSSQL instance and collect transaction data from it.
249
+
250
+| Name | Description | Default | Required |
251
+|:----|:-----------|:-------|:--------:|
252
+| update every | Data collection frequency. | 10 | no |
253
+| driver | ODBC driver used to connect to the SQL Server. | SQL Server | no |
254
+| instance | Instance name | empty | yes |
255
+| server | Server address or instance name. | empty | yes |
256
+| address | Alternative to `server`; supports named pipes if the server supports them. | empty | yes |
257
+| uid | SQL Server user identifier. | empty | yes |
258
+| pwd | Password for the specified user. | empty | yes |
259
+| additional instances | Number of additional SQL Server instances to monitor. | 0 | no |
260
+| windows authentication | Set to yes to use Windows credentials instead of SQL Server authentication. | no | no |
261
+| express | Set to yes when running SQL Express version. | no | no |
262
+
263
+
264
+
265
+#### via File
266
267
The configuration file name for this integration is `netdata.conf`.
268
Configuration for this specific integration is located in the `[plugin:windows:PerflibMSSQL]` section within that file.
@@ -265,26 +284,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
284
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
285
sudo ./edit-config netdata.conf
286
```
268
-#### Options
269
-
270
-These options allow the collector to connect to your MSSQL instance and collect transaction data from it.
271
-
272
-| Name | Description | Default | Required |
273
-|:----|:-----------|:-------|:--------:|
274
-| update every | Data collection frequency. | 10 | no |
275
-| driver | ODBC driver used to connect to the SQL Server. | SQL Server | no |
276
-| instance | Instance name | empty | yes |
277
-| server | Server address or instance name. | empty | yes |
278
-| address | Alternative to `server`; supports named pipes if the server supports them. | empty | yes |
279
-| uid | SQL Server user identifier. | empty | yes |
280
-| pwd | Password for the specified user. | empty | yes |
281
-| additional instances | Number of additional SQL Server instances to monitor. | 0 | no |
282
-| windows authentication | Set to yes to use Windows credentials instead of SQL Server authentication. | no | no |
283
-| express | Set to yes when running SQL Express version. | no | no |
287
285
-#### Examples
288
+##### Examples
289
287
-##### Single Instance
290
+###### Single Instance
291
292
An example configuration with one instance.
293
@@ -298,7 +301,7 @@ An example configuration with one instance.
301
express = no
302
303
```
301
-##### Multiple Instances
304
+###### Multiple Instances
305
306
An example configuration with two instances.
307
src/collectors/windows.plugin/integrations/net_framework.md
+12
-9
@@ -119,7 +119,17 @@ No action required.
119
120
### Configuration
121
122
-#### File
122
+#### Options
123
+
124
+
125
+
126
+| Name | Description | Default | Required |
127
+|:----|:-----------|:-------|:--------:|
128
+| update every | Data collection frequency. | 1 | no |
129
+
130
+
131
+
132
+#### via File
133
134
The configuration file name for this integration is `netdata.conf`.
135
Configuration for this specific integration is located in the `[plugin:windows:PerflibNetFramework]` section within that file.
@@ -141,15 +151,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
151
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
152
sudo ./edit-config netdata.conf
153
```
144
-#### Options
145
-
146
-
147
-
148
-| Name | Description | Default | Required |
149
-|:----|:-----------|:-------|:--------:|
150
-| update every | Data collection frequency. | 1 | no |
154
152
-#### Examples
155
+##### Examples
156
There are no configuration examples.
157
158
src/collectors/windows.plugin/integrations/network_subsystem.md
+12
-9
@@ -134,7 +134,17 @@ No action required.
134
135
### Configuration
136
137
-#### File
137
+#### Options
138
+
139
+
140
+
141
+| Name | Description | Default | Required |
142
+|:----|:-----------|:-------|:--------:|
143
+| update every | Data collection frequency. | 1 | no |
144
+
145
+
146
+
147
+#### via File
148
149
The configuration file name for this integration is `netdata.conf`.
150
Configuration for this specific integration is located in the `[plugin:windows:PerflibNetwork]` section within that file.
@@ -156,15 +166,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
166
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
167
sudo ./edit-config netdata.conf
168
```
159
-#### Options
160
-
161
-
162
-
163
-| Name | Description | Default | Required |
164
-|:----|:-----------|:-------|:--------:|
165
-| update every | Data collection frequency. | 1 | no |
169
167
-#### Examples
170
+##### Examples
171
There are no configuration examples.
172
173
src/collectors/windows.plugin/integrations/numa_architecture.md
+12
-9
@@ -89,7 +89,17 @@ No action required.
89
90
### Configuration
91
92
-#### File
92
+#### Options
93
+
94
+
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| update every | Data collection frequency. | 1 | no |
99
+
100
+
101
+
102
+#### via File
103
104
The configuration file name for this integration is `netdata.conf`.
105
Configuration for this specific integration is located in the `[plugin:windows:PerflibNUMA]` section within that file.
@@ -111,15 +121,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
sudo ./edit-config netdata.conf
123
```
114
-#### Options
115
-
116
-
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| update every | Data collection frequency. | 1 | no |
124
122
-#### Examples
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/windows.plugin/integrations/physical_and_logical_disk_performance_metrics.md
+12
-9
@@ -132,7 +132,17 @@ No action required.
132
133
### Configuration
134
135
-#### File
135
+#### Options
136
+
137
+
138
+
139
+| Name | Description | Default | Required |
140
+|:----|:-----------|:-------|:--------:|
141
+| update every | Data collection frequency. | 1 | no |
142
+
143
+
144
+
145
+#### via File
146
147
The configuration file name for this integration is `netdata.conf`.
148
Configuration for this specific integration is located in the `[plugin:windows:PerflibStorage]` section within that file.
@@ -154,15 +164,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
164
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
165
sudo ./edit-config netdata.conf
166
```
157
-#### Options
158
-
159
-
160
-
161
-| Name | Description | Default | Required |
162
-|:----|:-----------|:-------|:--------:|
163
-| update every | Data collection frequency. | 1 | no |
167
165
-#### Examples
168
+##### Examples
169
There are no configuration examples.
170
171
src/collectors/windows.plugin/integrations/power_supply.md
+12
-9
@@ -95,7 +95,17 @@ No action required.
95
96
### Configuration
97
98
-#### File
98
+#### Options
99
+
100
+
101
+
102
+| Name | Description | Default | Required |
103
+|:----|:-----------|:-------|:--------:|
104
+| update every | Data collection frequency. | 1 | no |
105
+
106
+
107
+
108
+#### via File
109
110
The configuration file name for this integration is `netdata.conf`.
111
Configuration for this specific integration is located in the `[plugin:windows:GetPowerSupply]` section within that file.
@@ -117,15 +127,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
127
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
128
sudo ./edit-config netdata.conf
129
```
120
-#### Options
121
-
122
-
123
-
124
-| Name | Description | Default | Required |
125
-|:----|:-----------|:-------|:--------:|
126
-| update every | Data collection frequency. | 1 | no |
130
128
-#### Examples
131
+##### Examples
132
There are no configuration examples.
133
134
src/collectors/windows.plugin/integrations/processor.md
+12
-9
@@ -106,7 +106,17 @@ No action required.
106
107
### Configuration
108
109
-#### File
109
+#### Options
110
+
111
+
112
+
113
+| Name | Description | Default | Required |
114
+|:----|:-----------|:-------|:--------:|
115
+| update every | Data collection frequency. | 1 | no |
116
+
117
+
118
+
119
+#### via File
120
121
The configuration file name for this integration is `netdata.conf`.
122
Configuration for this specific integration is located in the `[plugin:windows:PerflibProcessor]` section within that file.
@@ -128,15 +138,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
138
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
139
sudo ./edit-config netdata.conf
140
```
131
-#### Options
132
-
133
-
134
-
135
-| Name | Description | Default | Required |
136
-|:----|:-----------|:-------|:--------:|
137
-| update every | Data collection frequency. | 1 | no |
141
139
-#### Examples
142
+##### Examples
143
There are no configuration examples.
144
145
src/collectors/windows.plugin/integrations/semaphore_statistics.md
+12
-9
@@ -89,7 +89,17 @@ No action required.
89
90
### Configuration
91
92
-#### File
92
+#### Options
93
+
94
+
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| update every | Data collection frequency. | 1 | no |
99
+
100
+
101
+
102
+#### via File
103
104
The configuration file name for this integration is `netdata.conf`.
105
Configuration for this specific integration is located in the `[plugin:windows:PerflibObjects]` section within that file.
@@ -111,15 +121,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
sudo ./edit-config netdata.conf
123
```
114
-#### Options
115
-
116
-
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| update every | Data collection frequency. | 1 | no |
124
122
-#### Examples
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/windows.plugin/integrations/sensors.md
+12
-9
@@ -96,7 +96,17 @@ No action required.
96
97
### Configuration
98
99
-#### File
99
+#### Options
100
+
101
+
102
+
103
+| Name | Description | Default | Required |
104
+|:----|:-----------|:-------|:--------:|
105
+| update every | Data collection frequency. | 1 | no |
106
+
107
+
108
+
109
+#### via File
110
111
The configuration file name for this integration is `netdata.conf`.
112
Configuration for this specific integration is located in the `[plugin:windows:GetSensors]` section within that file.
@@ -118,15 +128,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
128
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
129
sudo ./edit-config netdata.conf
130
```
121
-#### Options
122
-
123
-
124
-
125
-| Name | Description | Default | Required |
126
-|:----|:-----------|:-------|:--------:|
127
-| update every | Data collection frequency. | 1 | no |
131
129
-#### Examples
132
+##### Examples
133
There are no configuration examples.
134
135
src/collectors/windows.plugin/integrations/system_statistics.md
+12
-9
@@ -88,7 +88,17 @@ No action required.
88
89
### Configuration
90
91
-#### File
91
+#### Options
92
+
93
+
94
+
95
+| Name | Description | Default | Required |
96
+|:----|:-----------|:-------|:--------:|
97
+| update every | Data collection frequency. | 1 | no |
98
+
99
+
100
+
101
+#### via File
102
103
The configuration file name for this integration is `netdata.conf`.
104
Configuration for this specific integration is located in the `[plugin:windows:PerflibProcesses]` section within that file.
@@ -110,15 +120,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
120
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
121
sudo ./edit-config netdata.conf
122
```
113
-#### Options
114
-
115
-
116
-
117
-| Name | Description | Default | Required |
118
-|:----|:-----------|:-------|:--------:|
119
-| update every | Data collection frequency. | 1 | no |
123
121
-#### Examples
124
+##### Examples
125
There are no configuration examples.
126
127
src/collectors/windows.plugin/integrations/system_thermal_zone.md
+12
-9
@@ -85,7 +85,17 @@ No action required.
85
86
### Configuration
87
88
-#### File
88
+#### Options
89
+
90
+
91
+
92
+| Name | Description | Default | Required |
93
+|:----|:-----------|:-------|:--------:|
94
+| update every | Data collection frequency. | 5 | no |
95
+
96
+
97
+
98
+#### via File
99
100
The configuration file name for this integration is `netdata.conf`.
101
Configuration for this specific integration is located in the `[plugin:windows:PerflibThermalZone]` section within that file.
@@ -107,15 +117,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
sudo ./edit-config netdata.conf
119
```
110
-#### Options
111
-
112
-
113
-
114
-| Name | Description | Default | Required |
115
-|:----|:-----------|:-------|:--------:|
116
-| update every | Data collection frequency. | 5 | no |
120
118
-#### Examples
121
+##### Examples
122
There are no configuration examples.
123
124
src/collectors/windows.plugin/integrations/windows_services.md
+12
-9
@@ -89,7 +89,17 @@ No action required.
89
90
### Configuration
91
92
-#### File
92
+#### Options
93
+
94
+
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| update every | Data collection frequency. | 30 | no |
99
+
100
+
101
+
102
+#### via File
103
104
The configuration file name for this integration is `netdata.conf`.
105
Configuration for this specific integration is located in the `[plugin:windows:PerflibServices]` section within that file.
@@ -111,15 +121,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
sudo ./edit-config netdata.conf
123
```
114
-#### Options
115
-
116
-
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| update every | Data collection frequency. | 30 | no |
124
122
-#### Examples
125
+##### Examples
126
There are no configuration examples.
127
128
src/collectors/xenstat.plugin/integrations/xen_xcp-ng.md
+16
-13
@@ -136,7 +136,21 @@ There are no alerts configured by default for this integration.
136
137
### Configuration
138
139
-#### File
139
+#### Options
140
+
141
+
142
+
143
+<details open><summary>Config options</summary>
144
+
145
+| Name | Description | Default | Required |
146
+|:----|:-----------|:-------|:--------:|
147
+| update every | Data collection frequency. | 1 | no |
148
+
149
+</details>
150
+
151
+
152
+
153
+#### via File
154
155
The configuration file name for this integration is `netdata.conf`.
156
Configuration for this specific integration is located in the `[plugin:xenstat]` section within that file.
@@ -158,19 +172,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
172
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
173
sudo ./edit-config netdata.conf
174
```
161
-#### Options
162
-
163
-
164
-
165
-<details open><summary>Config options</summary>
166
-
167
-| Name | Description | Default | Required |
168
-|:----|:-----------|:-------|:--------:|
169
-| update every | Data collection frequency. | 1 | no |
170
-
171
-</details>
175
173
-#### Examples
176
+##### Examples
177
There are no configuration examples.
178
179
src/exporting/aws_kinesis/integrations/aws_kinesis.md
+18
-15
@@ -44,18 +44,6 @@ Export metrics to AWS Kinesis Data Streams
44
45
### Configuration
46
47
-#### File
48
-
49
-The configuration file name for this integration is `exporting.conf`.
50
-
51
-
52
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
53
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
54
-
55
-```bash
56
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
57
-sudo ./edit-config exporting.conf
58
-```
47
#### Options
48
49
Netdata automatically computes a partition key for every record with the purpose to distribute records across available shards evenly.
@@ -138,9 +126,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
126
127
</details>
128
141
-#### Examples
129
143
-##### Example configuration
130
+
131
+#### via File
132
+
133
+The configuration file name for this integration is `exporting.conf`.
134
+
135
+
136
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
137
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
138
+
139
+```bash
140
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
141
+sudo ./edit-config exporting.conf
142
+```
143
+
144
+##### Examples
145
+
146
+###### Example configuration
147
148
Basic configuration
149
@@ -150,7 +153,7 @@ Basic configuration
153
destination = us-east-1
154
155
```
153
-##### Configuration with AWS credentials
156
+###### Configuration with AWS credentials
157
158
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
159
src/exporting/graphite/integrations/blueflood.md
+19
-16
@@ -27,18 +27,6 @@ No action required.
27
28
### Configuration
29
30
-#### File
31
-
32
-The configuration file name for this integration is `exporting.conf`.
33
-
34
-
35
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
36
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
37
-
38
-```bash
39
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
40
-sudo ./edit-config exporting.conf
41
-```
30
#### Options
31
32
The following options can be defined for this exporter.
@@ -119,9 +107,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
107
108
</details>
109
122
-#### Examples
110
124
-##### Example configuration
111
+
112
+#### via File
113
+
114
+The configuration file name for this integration is `exporting.conf`.
115
+
116
+
117
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
118
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
+
120
+```bash
121
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
+sudo ./edit-config exporting.conf
123
+```
124
+
125
+##### Examples
126
+
127
+###### Example configuration
128
129
Basic configuration
130
@@ -131,7 +134,7 @@ Basic configuration
134
destination = localhost:2003
135
136
```
134
-##### Configuration with HTTPS and HTTP authentication
137
+###### Configuration with HTTPS and HTTP authentication
138
139
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
140
@@ -143,7 +146,7 @@ Add `:https` modifier to the connector type if you need to use the TLS/SSL proto
146
password = my_password
147
148
```
146
-##### Detailed Configuration for a remote, secure host
149
+###### Detailed Configuration for a remote, secure host
150
151
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
152
src/exporting/graphite/integrations/graphite.md
+19
-16
@@ -28,18 +28,6 @@ No action required.
28
29
### Configuration
30
31
-#### File
32
-
33
-The configuration file name for this integration is `exporting.conf`.
34
-
35
-
36
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
37
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
38
-
39
-```bash
40
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
41
-sudo ./edit-config exporting.conf
42
-```
31
#### Options
32
33
The following options can be defined for this exporter.
@@ -120,9 +108,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
108
109
</details>
110
123
-#### Examples
111
125
-##### Example configuration
112
+
113
+#### via File
114
+
115
+The configuration file name for this integration is `exporting.conf`.
116
+
117
+
118
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
119
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
+
121
+```bash
122
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
+sudo ./edit-config exporting.conf
124
+```
125
+
126
+##### Examples
127
+
128
+###### Example configuration
129
130
Basic configuration
131
@@ -132,7 +135,7 @@ Basic configuration
135
destination = localhost:2003
136
137
```
135
-##### Configuration with HTTPS and HTTP authentication
138
+###### Configuration with HTTPS and HTTP authentication
139
140
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
141
@@ -144,7 +147,7 @@ Add `:https` modifier to the connector type if you need to use the TLS/SSL proto
147
password = my_password
148
149
```
147
-##### Detailed Configuration for a remote, secure host
150
+###### Detailed Configuration for a remote, secure host
151
152
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
153
src/exporting/graphite/integrations/kairosdb.md
+19
-16
@@ -27,18 +27,6 @@ No action required.
27
28
### Configuration
29
30
-#### File
31
-
32
-The configuration file name for this integration is `exporting.conf`.
33
-
34
-
35
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
36
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
37
-
38
-```bash
39
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
40
-sudo ./edit-config exporting.conf
41
-```
30
#### Options
31
32
The following options can be defined for this exporter.
@@ -119,9 +107,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
107
108
</details>
109
122
-#### Examples
110
124
-##### Example configuration
111
+
112
+#### via File
113
+
114
+The configuration file name for this integration is `exporting.conf`.
115
+
116
+
117
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
118
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
+
120
+```bash
121
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
+sudo ./edit-config exporting.conf
123
+```
124
+
125
+##### Examples
126
+
127
+###### Example configuration
128
129
Basic configuration
130
@@ -131,7 +134,7 @@ Basic configuration
134
destination = localhost:2003
135
136
```
134
-##### Configuration with HTTPS and HTTP authentication
137
+###### Configuration with HTTPS and HTTP authentication
138
139
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
140
@@ -143,7 +146,7 @@ Add `:https` modifier to the connector type if you need to use the TLS/SSL proto
146
password = my_password
147
148
```
146
-##### Detailed Configuration for a remote, secure host
149
+###### Detailed Configuration for a remote, secure host
150
151
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
152
src/exporting/json/integrations/json.md
+18
-15
@@ -31,18 +31,6 @@ further analysis, or correlation with data from other sources
31
32
### Configuration
33
34
-#### File
35
-
36
-The configuration file name for this integration is `exporting.conf`.
37
-
38
-
39
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
40
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
-
42
-```bash
43
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
44
-sudo ./edit-config exporting.conf
45
-```
34
#### Options
35
36
The following options can be defined for this exporter.
@@ -120,9 +108,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
108
109
</details>
110
123
-#### Examples
111
125
-##### Basic configuration
112
+
113
+#### via File
114
+
115
+The configuration file name for this integration is `exporting.conf`.
116
+
117
+
118
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
119
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
+
121
+```bash
122
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
+sudo ./edit-config exporting.conf
124
+```
125
+
126
+##### Examples
127
+
128
+###### Basic configuration
129
130
131
@@ -132,7 +135,7 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
135
destination = localhost:5448
136
137
```
135
-##### Configuration with HTTPS and HTTP authentication
138
+###### Configuration with HTTPS and HTTP authentication
139
140
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `json:https:my_json_instance`.
141
src/exporting/mongodb/integrations/mongodb.md
+17
-14
@@ -33,18 +33,6 @@ for long-term storage, further analysis, or correlation with data from other sou
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `exporting.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config exporting.conf
47
-```
36
#### Options
37
38
The following options can be defined for this exporter.
@@ -126,9 +114,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
114
115
</details>
116
129
-#### Examples
117
131
-##### Basic configuration
118
+
119
+#### via File
120
+
121
+The configuration file name for this integration is `exporting.conf`.
122
+
123
+
124
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
125
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
126
+
127
+```bash
128
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
129
+sudo ./edit-config exporting.conf
130
+```
131
+
132
+##### Examples
133
+
134
+###### Basic configuration
135
136
The default socket timeout depends on the exporting connector update interval.
137
The timeout is 500 ms shorter than the interval (but not less than 1000 ms). You can alter the timeout using the sockettimeoutms MongoDB URI option.
src/exporting/opentsdb/integrations/opentsdb.md
+20
-17
@@ -32,18 +32,6 @@ further analysis, or correlation with data from other sources.
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `exporting.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config exporting.conf
46
-```
35
#### Options
36
37
The following options can be defined for this exporter.
@@ -124,9 +112,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
112
113
</details>
114
127
-#### Examples
115
129
-##### Minimal configuration
116
+
117
+#### via File
118
+
119
+The configuration file name for this integration is `exporting.conf`.
120
+
121
+
122
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
123
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
+
125
+```bash
126
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
127
+sudo ./edit-config exporting.conf
128
+```
129
+
130
+##### Examples
131
+
132
+###### Minimal configuration
133
134
Add `:http` or `:https` modifiers to the connector type if you need to use other than a plaintext protocol.
135
For example: `opentsdb:http:my_opentsdb_instance`, `opentsdb:https:my_opentsdb_instance`.
@@ -138,7 +141,7 @@ For example: `opentsdb:http:my_opentsdb_instance`, `opentsdb:https:my_opentsdb_i
141
destination = localhost:4242
142
143
```
141
-##### HTTP authentication
144
+###### HTTP authentication
145
146
147
@@ -150,7 +153,7 @@ For example: `opentsdb:http:my_opentsdb_instance`, `opentsdb:https:my_opentsdb_i
153
password = my_password
154
155
```
153
-##### Using `send hosts matching`
156
+###### Using `send hosts matching`
157
158
159
@@ -161,7 +164,7 @@ For example: `opentsdb:http:my_opentsdb_instance`, `opentsdb:https:my_opentsdb_i
164
send hosts matching = localhost *
165
166
```
164
-##### Using `send charts matching`
167
+###### Using `send charts matching`
168
169
170
src/exporting/prometheus/integrations/appoptics.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/azure_data_explorer.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/azure_event_hub.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/chronix.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/cortex.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/cratedb.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/elasticsearch.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/gnocchi.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/google_bigquery.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/greptimedb.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/irondb.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/kafka.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/m3db.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/metricfire.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/new_relic.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/opeansearch.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/postgresql.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/prometheus_remote_write.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/quasardb.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/splunk_signalfx.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/thanos.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/tikv.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/timescaledb.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/victoriametrics.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/vmware_aria.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/prometheus/integrations/wavefront.md
+18
-15
@@ -37,18 +37,6 @@ The remote write exporting connector does not support buffer on failures.
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `exporting.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config exporting.conf
51
-```
40
#### Options
41
42
The following options can be defined for this exporter.
@@ -129,9 +117,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
117
118
</details>
119
132
-#### Examples
120
134
-##### Example configuration
121
+
122
+#### via File
123
+
124
+The configuration file name for this integration is `exporting.conf`.
125
+
126
+
127
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
128
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+
130
+```bash
131
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
132
+sudo ./edit-config exporting.conf
133
+```
134
+
135
+##### Examples
136
+
137
+###### Example configuration
138
139
Basic example configuration for Prometheus remote write.
140
@@ -142,7 +145,7 @@ Basic example configuration for Prometheus remote write.
145
remote write URL path = /receive
146
147
```
145
-##### Example configuration with HTTPS and HTTP authentication
148
+###### Example configuration with HTTPS and HTTP authentication
149
150
Add `:https` modifier to the connector type if you need to use the TLS/SSL protocol. For example: `remote_write:https:my_instance`.
151
src/exporting/pubsub/integrations/google_cloud_pub_sub.md
+17
-14
@@ -33,18 +33,6 @@ Export metrics to Google Cloud Pub/Sub Service
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `exporting.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config exporting.conf
47
-```
36
#### Options
37
38
The following options can be defined for this exporter.
@@ -122,9 +110,24 @@ different : disks with device-mapper, interrupts, QoS classes, statsd synthetic
110
111
</details>
112
125
-#### Examples
113
127
-##### Basic configuration
114
+
115
+#### via File
116
+
117
+The configuration file name for this integration is `exporting.conf`.
118
+
119
+
120
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
121
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
122
+
123
+```bash
124
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
125
+sudo ./edit-config exporting.conf
126
+```
127
+
128
+##### Examples
129
+
130
+###### Basic configuration
131
132
- Set the destination option to a Pub/Sub service endpoint. pubsub.googleapis.com is the default one.
133
- Create the credentials JSON file by following Google Cloud's authentication guide.
src/go/plugin/go.d/collector/activemq/integrations/activemq.md
+39
-25
@@ -86,26 +86,6 @@ No action required.
86
87
### Configuration
88
89
-#### File
90
-
91
-The configuration file name for this integration is `go.d/activemq.conf`.
92
-
93
-The file format is YAML. Generally, the structure is:
94
-
95
-```yaml
96
-update_every: 1
97
-autodetection_retry: 0
98
-jobs:
99
- - name: some_name1
100
- - name: some_name1
101
-```
102
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
-
105
-```bash
106
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
107
-sudo ./edit-config go.d/activemq.conf
108
-```
89
#### Options
90
91
The following options can be defined globally: update_every, autodetection_retry.
@@ -139,9 +119,43 @@ The following options can be defined globally: update_every, autodetection_retry
119
120
</details>
121
142
-#### Examples
122
144
-##### Basic
123
+#### via UI
124
+
125
+The **activemq** collector can be configured directly through the Netdata web interface:
126
+
127
+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.
129
+3. The **Collectors → Jobs** view opens by default.
130
+4. In the Search box, type _activemq_ (or scroll the list) to locate the **activemq** collector.
131
+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**.
133
+
134
+
135
+#### via File
136
+
137
+The configuration file name for this integration is `go.d/activemq.conf`.
138
+
139
+The file format is YAML. Generally, the structure is:
140
+
141
+```yaml
142
+update_every: 1
143
+autodetection_retry: 0
144
+jobs:
145
+ - name: some_name1
146
+ - name: some_name1
147
+```
148
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
149
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
150
+
151
+```bash
152
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
153
+sudo ./edit-config go.d/activemq.conf
154
+```
155
+
156
+##### Examples
157
+
158
+###### Basic
159
160
A basic example configuration.
161
@@ -152,7 +166,7 @@ jobs:
166
webadmin: admin
167
168
```
155
-##### HTTP authentication
169
+###### HTTP authentication
170
171
Basic HTTP authentication.
172
@@ -169,7 +183,7 @@ jobs:
183
```
184
</details>
185
172
-##### Filters and limits
186
+###### Filters and limits
187
188
Using filters and limits for queues and topics.
189
@@ -188,7 +202,7 @@ jobs:
202
```
203
</details>
204
191
-##### Multi-instance
205
+###### Multi-instance
206
207
> **Note**: When you define multiple jobs, their names must be unique.
208
src/go/plugin/go.d/collector/adaptecraid/integrations/adaptec_raid.md
+30
-16
@@ -124,7 +124,34 @@ No action required.
124
125
### Configuration
126
127
-#### File
127
+#### Options
128
+
129
+The following options can be defined globally: update_every.
130
+
131
+
132
+<details open><summary>Config options</summary>
133
+
134
+| Name | Description | Default | Required |
135
+|:----|:-----------|:-------|:--------:|
136
+| update_every | Data collection frequency. | 10 | no |
137
+| timeout | arcconf binary execution timeout. | 2 | no |
138
+
139
+</details>
140
+
141
+
142
+#### via UI
143
+
144
+The **adaptec_raid** collector can be configured directly through the Netdata web interface:
145
+
146
+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.
148
+3. The **Collectors → Jobs** view opens by default.
149
+4. In the Search box, type _adaptec_raid_ (or scroll the list) to locate the **adaptec_raid** collector.
150
+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**.
152
+
153
+
154
+#### via File
155
156
The configuration file name for this integration is `go.d/adaptec_raid.conf`.
157
@@ -144,23 +171,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
171
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
172
sudo ./edit-config go.d/adaptec_raid.conf
173
```
147
-#### Options
148
-
149
-The following options can be defined globally: update_every.
150
-
151
-
152
-<details open><summary>Config options</summary>
153
-
154
-| Name | Description | Default | Required |
155
-|:----|:-----------|:-------|:--------:|
156
-| update_every | Data collection frequency. | 10 | no |
157
-| timeout | arcconf binary execution timeout. | 2 | no |
158
-
159
-</details>
174
161
-#### Examples
175
+##### Examples
176
163
-##### Custom update_every
177
+###### Custom update_every
178
179
Allows you to override the default data collection interval.
180
src/go/plugin/go.d/collector/ap/integrations/access_points.md
+31
-17
@@ -97,7 +97,35 @@ Make sure the `iw` utility is installed.
97
98
### Configuration
99
100
-#### File
100
+#### Options
101
+
102
+The following options can be defined globally: update_every.
103
+
104
+
105
+<details open><summary>Config options</summary>
106
+
107
+| Name | Description | Default | Required |
108
+|:----|:-----------|:-------|:--------:|
109
+| update_every | Data collection frequency. | 10 | no |
110
+| binary_path | Path to the `iw` binary. If an absolute path is provided, the collector will use it directly; otherwise, it will search for the binary in directories specified in the PATH environment variable. | /usr/sbin/iw | yes |
111
+| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
112
+
113
+</details>
114
+
115
+
116
+#### via UI
117
+
118
+The **ap** collector can be configured directly through the Netdata web interface:
119
+
120
+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.
122
+3. The **Collectors → Jobs** view opens by default.
123
+4. In the Search box, type _ap_ (or scroll the list) to locate the **ap** collector.
124
+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**.
126
+
127
+
128
+#### via File
129
130
The configuration file name for this integration is `go.d/ap.conf`.
131
@@ -117,24 +145,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
145
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
146
sudo ./edit-config go.d/ap.conf
147
```
120
-#### Options
121
-
122
-The following options can be defined globally: update_every.
123
-
124
-
125
-<details open><summary>Config options</summary>
126
-
127
-| Name | Description | Default | Required |
128
-|:----|:-----------|:-------|:--------:|
129
-| update_every | Data collection frequency. | 10 | no |
130
-| binary_path | Path to the `iw` binary. If an absolute path is provided, the collector will use it directly; otherwise, it will search for the binary in directories specified in the PATH environment variable. | /usr/sbin/iw | yes |
131
-| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
132
-
133
-</details>
148
135
-#### Examples
149
+##### Examples
150
137
-##### Custom binary path
151
+###### Custom binary path
152
153
The executable is not in the directories specified in the PATH environment variable.
154
src/go/plugin/go.d/collector/apache/integrations/apache.md
+39
-25
@@ -103,26 +103,6 @@ There are no alerts configured by default for this integration.
103
104
### Configuration
105
106
-#### File
107
-
108
-The configuration file name for this integration is `go.d/apache.conf`.
109
-
110
-The file format is YAML. Generally, the structure is:
111
-
112
-```yaml
113
-update_every: 1
114
-autodetection_retry: 0
115
-jobs:
116
- - name: some_name1
117
- - name: some_name1
118
-```
119
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
120
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
-
122
-```bash
123
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
124
-sudo ./edit-config go.d/apache.conf
125
-```
106
#### Options
107
108
The following options can be defined globally: update_every, autodetection_retry.
@@ -153,9 +133,43 @@ The following options can be defined globally: update_every, autodetection_retry
133
134
</details>
135
156
-#### Examples
136
158
-##### Basic
137
+#### via UI
138
+
139
+The **apache** collector can be configured directly through the Netdata web interface:
140
+
141
+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.
143
+3. The **Collectors → Jobs** view opens by default.
144
+4. In the Search box, type _apache_ (or scroll the list) to locate the **apache** collector.
145
+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**.
147
+
148
+
149
+#### via File
150
+
151
+The configuration file name for this integration is `go.d/apache.conf`.
152
+
153
+The file format is YAML. Generally, the structure is:
154
+
155
+```yaml
156
+update_every: 1
157
+autodetection_retry: 0
158
+jobs:
159
+ - name: some_name1
160
+ - name: some_name1
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).
164
+
165
+```bash
166
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
167
+sudo ./edit-config go.d/apache.conf
168
+```
169
+
170
+##### Examples
171
+
172
+###### Basic
173
174
A basic example configuration.
175
@@ -165,7 +179,7 @@ jobs:
179
url: http://127.0.0.1/server-status?auto
180
181
```
168
-##### HTTP authentication
182
+###### HTTP authentication
183
184
Basic HTTP authentication.
185
@@ -181,7 +195,7 @@ jobs:
195
```
196
</details>
197
184
-##### HTTPS with self-signed certificate
198
+###### HTTPS with self-signed certificate
199
200
Apache with enabled HTTPS and self-signed certificate.
201
@@ -196,7 +210,7 @@ jobs:
210
```
211
</details>
212
199
-##### Multi-instance
213
+###### Multi-instance
214
215
> **Note**: When you define multiple jobs, their names must be unique.
216
src/go/plugin/go.d/collector/apache/integrations/httpd.md
+39
-25
@@ -103,26 +103,6 @@ There are no alerts configured by default for this integration.
103
104
### Configuration
105
106
-#### File
107
-
108
-The configuration file name for this integration is `go.d/apache.conf`.
109
-
110
-The file format is YAML. Generally, the structure is:
111
-
112
-```yaml
113
-update_every: 1
114
-autodetection_retry: 0
115
-jobs:
116
- - name: some_name1
117
- - name: some_name1
118
-```
119
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
120
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
-
122
-```bash
123
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
124
-sudo ./edit-config go.d/apache.conf
125
-```
106
#### Options
107
108
The following options can be defined globally: update_every, autodetection_retry.
@@ -153,9 +133,43 @@ The following options can be defined globally: update_every, autodetection_retry
133
134
</details>
135
156
-#### Examples
136
158
-##### Basic
137
+#### via UI
138
+
139
+The **apache** collector can be configured directly through the Netdata web interface:
140
+
141
+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.
143
+3. The **Collectors → Jobs** view opens by default.
144
+4. In the Search box, type _apache_ (or scroll the list) to locate the **apache** collector.
145
+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**.
147
+
148
+
149
+#### via File
150
+
151
+The configuration file name for this integration is `go.d/apache.conf`.
152
+
153
+The file format is YAML. Generally, the structure is:
154
+
155
+```yaml
156
+update_every: 1
157
+autodetection_retry: 0
158
+jobs:
159
+ - name: some_name1
160
+ - name: some_name1
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).
164
+
165
+```bash
166
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
167
+sudo ./edit-config go.d/apache.conf
168
+```
169
+
170
+##### Examples
171
+
172
+###### Basic
173
174
A basic example configuration.
175
@@ -165,7 +179,7 @@ jobs:
179
url: http://127.0.0.1/server-status?auto
180
181
```
168
-##### HTTP authentication
182
+###### HTTP authentication
183
184
Basic HTTP authentication.
185
@@ -181,7 +195,7 @@ jobs:
195
```
196
</details>
197
184
-##### HTTPS with self-signed certificate
198
+###### HTTPS with self-signed certificate
199
200
Apache with enabled HTTPS and self-signed certificate.
201
@@ -196,7 +210,7 @@ jobs:
210
```
211
</details>
212
199
-##### Multi-instance
213
+###### Multi-instance
214
215
> **Note**: When you define multiple jobs, their names must be unique.
216
src/go/plugin/go.d/collector/apcupsd/integrations/apc_ups.md
+33
-19
@@ -110,7 +110,36 @@ No action required.
110
111
### Configuration
112
113
-#### File
113
+#### Options
114
+
115
+The following options can be defined globally: update_every, autodetection_retry.
116
+
117
+
118
+<details open><summary>Config options</summary>
119
+
120
+| Name | Description | Default | Required |
121
+|:----|:-----------|:-------|:--------:|
122
+| update_every | Data collection frequency. | 1 | no |
123
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
124
+| address | Apcupsd daemon address in IP:PORT format. | 127.0.0.1:3551 | yes |
125
+| timeout | Connection/read/write timeout in seconds. The timeout includes name resolution, if required. | 2 | no |
126
+
127
+</details>
128
+
129
+
130
+#### via UI
131
+
132
+The **apcupsd** collector can be configured directly through the Netdata web interface:
133
+
134
+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.
136
+3. The **Collectors → Jobs** view opens by default.
137
+4. In the Search box, type _apcupsd_ (or scroll the list) to locate the **apcupsd** collector.
138
+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**.
140
+
141
+
142
+#### via File
143
144
The configuration file name for this integration is `go.d/apcupsd.conf`.
145
@@ -130,25 +159,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
159
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
sudo ./edit-config go.d/apcupsd.conf
161
```
133
-#### Options
134
-
135
-The following options can be defined globally: update_every, autodetection_retry.
136
-
137
-
138
-<details open><summary>Config options</summary>
139
-
140
-| Name | Description | Default | Required |
141
-|:----|:-----------|:-------|:--------:|
142
-| update_every | Data collection frequency. | 1 | no |
143
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
144
-| address | Apcupsd daemon address in IP:PORT format. | 127.0.0.1:3551 | yes |
145
-| timeout | Connection/read/write timeout in seconds. The timeout includes name resolution, if required. | 2 | no |
146
-
147
-</details>
162
149
-#### Examples
163
+##### Examples
164
151
-##### Basic
165
+###### Basic
166
167
A basic example configuration.
168
@@ -162,7 +176,7 @@ jobs:
176
```
177
</details>
178
165
-##### Multi-instance
179
+###### Multi-instance
180
181
> **Note**: When you define multiple jobs, their names must be unique.
182
src/go/plugin/go.d/collector/beanstalk/integrations/beanstalk.md
+34
-20
@@ -122,7 +122,37 @@ No action required.
122
123
### Configuration
124
125
-#### File
125
+#### Options
126
+
127
+The following options can be defined globally: update_every, autodetection_retry.
128
+
129
+
130
+<details open><summary>Config options</summary>
131
+
132
+| Name | Description | Default | Required |
133
+|:----|:-----------|:-------|:--------:|
134
+| update_every | Data collection frequency. | 1 | no |
135
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
136
+| address | The IP address and port where the Beanstalk service listens for connections. | 127.0.0.1:11300 | yes |
137
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
138
+| tube_selector | Specifies a [pattern](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#readme) for which Beanstalk tubes Netdata will collect statistics. | * | no |
139
+
140
+</details>
141
+
142
+
143
+#### via UI
144
+
145
+The **beanstalk** collector can be configured directly through the Netdata web interface:
146
+
147
+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.
149
+3. The **Collectors → Jobs** view opens by default.
150
+4. In the Search box, type _beanstalk_ (or scroll the list) to locate the **beanstalk** collector.
151
+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**.
153
+
154
+
155
+#### via File
156
157
The configuration file name for this integration is `go.d/beanstalk.conf`.
158
@@ -142,26 +172,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
172
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
173
sudo ./edit-config go.d/beanstalk.conf
174
```
145
-#### Options
146
-
147
-The following options can be defined globally: update_every, autodetection_retry.
148
-
149
-
150
-<details open><summary>Config options</summary>
151
-
152
-| Name | Description | Default | Required |
153
-|:----|:-----------|:-------|:--------:|
154
-| update_every | Data collection frequency. | 1 | no |
155
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
156
-| address | The IP address and port where the Beanstalk service listens for connections. | 127.0.0.1:11300 | yes |
157
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
158
-| tube_selector | Specifies a [pattern](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#readme) for which Beanstalk tubes Netdata will collect statistics. | * | no |
159
-
160
-</details>
175
162
-#### Examples
176
+##### Examples
177
164
-##### Basic
178
+###### Basic
179
180
A basic example configuration.
181
@@ -175,7 +189,7 @@ jobs:
189
```
190
</details>
191
178
-##### Multi-instance
192
+###### Multi-instance
193
194
> **Note**: When you define multiple jobs, their names must be unique.
195
src/go/plugin/go.d/collector/boinc/integrations/boinc.md
+34
-20
@@ -97,7 +97,37 @@ No action required.
97
98
### Configuration
99
100
-#### File
100
+#### Options
101
+
102
+The following options can be defined globally: update_every, autodetection_retry.
103
+
104
+
105
+<details open><summary>Config options</summary>
106
+
107
+| Name | Description | Default | Required |
108
+|:----|:-----------|:-------|:--------:|
109
+| update_every | Data collection frequency. | 1 | no |
110
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
111
+| address | The IP address and port where the BOINC client listens for connections. | 127.0.0.1:31416 | yes |
112
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
113
+| password | The GUI RPC password for authentication. | | no |
114
+
115
+</details>
116
+
117
+
118
+#### via UI
119
+
120
+The **boinc** collector can be configured directly through the Netdata web interface:
121
+
122
+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.
124
+3. The **Collectors → Jobs** view opens by default.
125
+4. In the Search box, type _boinc_ (or scroll the list) to locate the **boinc** collector.
126
+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**.
128
+
129
+
130
+#### via File
131
132
The configuration file name for this integration is `go.d/boinc.conf`.
133
@@ -117,26 +147,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
147
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
148
sudo ./edit-config go.d/boinc.conf
149
```
120
-#### Options
121
-
122
-The following options can be defined globally: update_every, autodetection_retry.
123
-
124
-
125
-<details open><summary>Config options</summary>
126
-
127
-| Name | Description | Default | Required |
128
-|:----|:-----------|:-------|:--------:|
129
-| update_every | Data collection frequency. | 1 | no |
130
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
131
-| address | The IP address and port where the BOINC client listens for connections. | 127.0.0.1:31416 | yes |
132
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
133
-| password | The GUI RPC password for authentication. | | no |
134
-
135
-</details>
150
137
-#### Examples
151
+##### Examples
152
139
-##### Basic
153
+###### Basic
154
155
A basic example configuration.
156
@@ -150,7 +164,7 @@ jobs:
164
```
165
</details>
166
153
-##### Multi-instance
167
+###### Multi-instance
168
169
> **Note**: When you define multiple jobs, their names must be unique.
170
src/go/plugin/go.d/collector/cassandra/integrations/cassandra.md
+39
-25
@@ -146,26 +146,6 @@ To configure Cassandra with the [JMX Exporter](https://github.com/prometheus/jmx
146
147
### Configuration
148
149
-#### File
150
-
151
-The configuration file name for this integration is `go.d/cassandra.conf`.
152
-
153
-The file format is YAML. Generally, the structure is:
154
-
155
-```yaml
156
-update_every: 1
157
-autodetection_retry: 0
158
-jobs:
159
- - name: some_name1
160
- - name: some_name1
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).
164
-
165
-```bash
166
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
167
-sudo ./edit-config go.d/cassandra.conf
168
-```
149
#### Options
150
151
The following options can be defined globally: update_every, autodetection_retry.
@@ -192,9 +172,43 @@ The following options can be defined globally: update_every, autodetection_retry
172
173
</details>
174
195
-#### Examples
175
197
-##### Basic
176
+#### via UI
177
+
178
+The **cassandra** collector can be configured directly through the Netdata web interface:
179
+
180
+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.
182
+3. The **Collectors → Jobs** view opens by default.
183
+4. In the Search box, type _cassandra_ (or scroll the list) to locate the **cassandra** collector.
184
+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**.
186
+
187
+
188
+#### via File
189
+
190
+The configuration file name for this integration is `go.d/cassandra.conf`.
191
+
192
+The file format is YAML. Generally, the structure is:
193
+
194
+```yaml
195
+update_every: 1
196
+autodetection_retry: 0
197
+jobs:
198
+ - name: some_name1
199
+ - name: some_name1
200
+```
201
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
202
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
203
+
204
+```bash
205
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
206
+sudo ./edit-config go.d/cassandra.conf
207
+```
208
+
209
+##### Examples
210
+
211
+###### Basic
212
213
A basic example configuration.
214
@@ -204,7 +218,7 @@ jobs:
218
url: http://127.0.0.1:7072/metrics
219
220
```
207
-##### HTTP authentication
221
+###### HTTP authentication
222
223
Local server with basic HTTP authentication.
224
@@ -220,7 +234,7 @@ jobs:
234
```
235
</details>
236
223
-##### HTTPS with self-signed certificate
237
+###### HTTPS with self-signed certificate
238
239
Local server with enabled HTTPS and self-signed certificate.
240
@@ -235,7 +249,7 @@ jobs:
249
```
250
</details>
251
238
-##### Multi-instance
252
+###### Multi-instance
253
254
> **Note**: When you define multiple jobs, their names must be unique.
255
src/go/plugin/go.d/collector/ceph/integrations/ceph.md
+37
-23
@@ -166,26 +166,6 @@ No action required.
166
167
### Configuration
168
169
-#### File
170
-
171
-The configuration file name for this integration is `go.d/ceph.conf`.
172
-
173
-The file format is YAML. Generally, the structure is:
174
-
175
-```yaml
176
-update_every: 1
177
-autodetection_retry: 0
178
-jobs:
179
- - name: some_name1
180
- - name: some_name1
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).
184
-
185
-```bash
186
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
187
-sudo ./edit-config go.d/ceph.conf
188
-```
169
#### Options
170
171
The following options can be defined globally: update_every.
@@ -215,9 +195,43 @@ The following options can be defined globally: update_every.
195
196
</details>
197
218
-#### Examples
198
220
-##### Basic
199
+#### via UI
200
+
201
+The **ceph** collector can be configured directly through the Netdata web interface:
202
+
203
+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.
205
+3. The **Collectors → Jobs** view opens by default.
206
+4. In the Search box, type _ceph_ (or scroll the list) to locate the **ceph** collector.
207
+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**.
209
+
210
+
211
+#### via File
212
+
213
+The configuration file name for this integration is `go.d/ceph.conf`.
214
+
215
+The file format is YAML. Generally, the structure is:
216
+
217
+```yaml
218
+update_every: 1
219
+autodetection_retry: 0
220
+jobs:
221
+ - name: some_name1
222
+ - name: some_name1
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).
226
+
227
+```bash
228
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
229
+sudo ./edit-config go.d/ceph.conf
230
+```
231
+
232
+##### Examples
233
+
234
+###### Basic
235
236
A basic example configuration.
237
@@ -229,7 +243,7 @@ jobs:
243
password: pass
244
245
```
232
-##### Multi-instance
246
+###### Multi-instance
247
248
> **Note**: When you define multiple jobs, their names must be unique.
249
src/go/plugin/go.d/collector/chrony/integrations/chrony.md
+33
-19
@@ -101,7 +101,36 @@ No action required.
101
102
### Configuration
103
104
-#### File
104
+#### Options
105
+
106
+The following options can be defined globally: update_every, autodetection_retry.
107
+
108
+
109
+<details open><summary>Config options</summary>
110
+
111
+| Name | Description | Default | Required |
112
+|:----|:-----------|:-------|:--------:|
113
+| update_every | Data collection frequency. | 5 | no |
114
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
115
+| address | Server address. The format is IP:PORT. | 127.0.0.1:323 | yes |
116
+| timeout | Connection timeout. Zero means no timeout. | 1 | no |
117
+
118
+</details>
119
+
120
+
121
+#### via UI
122
+
123
+The **chrony** collector can be configured directly through the Netdata web interface:
124
+
125
+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.
127
+3. The **Collectors → Jobs** view opens by default.
128
+4. In the Search box, type _chrony_ (or scroll the list) to locate the **chrony** collector.
129
+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**.
131
+
132
+
133
+#### via File
134
135
The configuration file name for this integration is `go.d/chrony.conf`.
136
@@ -121,25 +150,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
150
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
sudo ./edit-config go.d/chrony.conf
152
```
124
-#### Options
125
-
126
-The following options can be defined globally: update_every, autodetection_retry.
127
-
128
-
129
-<details open><summary>Config options</summary>
130
-
131
-| Name | Description | Default | Required |
132
-|:----|:-----------|:-------|:--------:|
133
-| update_every | Data collection frequency. | 5 | no |
134
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
135
-| address | Server address. The format is IP:PORT. | 127.0.0.1:323 | yes |
136
-| timeout | Connection timeout. Zero means no timeout. | 1 | no |
137
-
138
-</details>
153
140
-#### Examples
154
+##### Examples
155
142
-##### Basic
156
+###### Basic
157
158
A basic example configuration.
159
@@ -149,7 +163,7 @@ jobs:
163
address: 127.0.0.1:323
164
165
```
152
-##### Multi-instance
166
+###### Multi-instance
167
168
> **Note**: When you define multiple jobs, their names must be unique.
169
src/go/plugin/go.d/collector/clickhouse/integrations/clickhouse.md
+39
-25
@@ -198,26 +198,6 @@ No action required.
198
199
### Configuration
200
201
-#### File
202
-
203
-The configuration file name for this integration is `go.d/clickhouse.conf`.
204
-
205
-The file format is YAML. Generally, the structure is:
206
-
207
-```yaml
208
-update_every: 1
209
-autodetection_retry: 0
210
-jobs:
211
- - name: some_name1
212
- - name: some_name1
213
-```
214
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
215
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
216
-
217
-```bash
218
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
219
-sudo ./edit-config go.d/clickhouse.conf
220
-```
201
#### Options
202
203
The following options can be defined globally: update_every, autodetection_retry.
@@ -247,9 +227,43 @@ The following options can be defined globally: update_every, autodetection_retry
227
228
</details>
229
250
-#### Examples
230
252
-##### Basic
231
+#### via UI
232
+
233
+The **clickhouse** collector can be configured directly through the Netdata web interface:
234
+
235
+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.
237
+3. The **Collectors → Jobs** view opens by default.
238
+4. In the Search box, type _clickhouse_ (or scroll the list) to locate the **clickhouse** collector.
239
+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**.
241
+
242
+
243
+#### via File
244
+
245
+The configuration file name for this integration is `go.d/clickhouse.conf`.
246
+
247
+The file format is YAML. Generally, the structure is:
248
+
249
+```yaml
250
+update_every: 1
251
+autodetection_retry: 0
252
+jobs:
253
+ - name: some_name1
254
+ - name: some_name1
255
+```
256
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
257
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
258
+
259
+```bash
260
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
261
+sudo ./edit-config go.d/clickhouse.conf
262
+```
263
+
264
+##### Examples
265
+
266
+###### Basic
267
268
A basic example configuration.
269
@@ -259,7 +273,7 @@ jobs:
273
url: http://127.0.0.1:8123
274
275
```
262
-##### HTTP authentication
276
+###### HTTP authentication
277
278
Basic HTTP authentication.
279
@@ -275,7 +289,7 @@ jobs:
289
```
290
</details>
291
278
-##### HTTPS with self-signed certificate
292
+###### HTTPS with self-signed certificate
293
294
ClickHouse with enabled HTTPS and self-signed certificate.
295
@@ -290,7 +304,7 @@ jobs:
304
```
305
</details>
306
293
-##### Multi-instance
307
+###### Multi-instance
308
309
> **Note**: When you define multiple jobs, their names must be unique.
310
src/go/plugin/go.d/collector/cockroachdb/integrations/cockroachdb.md
+39
-25
@@ -149,26 +149,6 @@ No action required.
149
150
### Configuration
151
152
-#### File
153
-
154
-The configuration file name for this integration is `go.d/cockroachdb.conf`.
155
-
156
-The file format is YAML. Generally, the structure is:
157
-
158
-```yaml
159
-update_every: 1
160
-autodetection_retry: 0
161
-jobs:
162
- - name: some_name1
163
- - name: some_name1
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).
167
-
168
-```bash
169
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
170
-sudo ./edit-config go.d/cockroachdb.conf
171
-```
152
#### Options
153
154
The following options can be defined globally: update_every, autodetection_retry.
@@ -198,9 +178,43 @@ The following options can be defined globally: update_every, autodetection_retry
178
179
</details>
180
201
-#### Examples
181
203
-##### Basic
182
+#### via UI
183
+
184
+The **cockroachdb** collector can be configured directly through the Netdata web interface:
185
+
186
+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.
188
+3. The **Collectors → Jobs** view opens by default.
189
+4. In the Search box, type _cockroachdb_ (or scroll the list) to locate the **cockroachdb** collector.
190
+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**.
192
+
193
+
194
+#### via File
195
+
196
+The configuration file name for this integration is `go.d/cockroachdb.conf`.
197
+
198
+The file format is YAML. Generally, the structure is:
199
+
200
+```yaml
201
+update_every: 1
202
+autodetection_retry: 0
203
+jobs:
204
+ - name: some_name1
205
+ - name: some_name1
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).
209
+
210
+```bash
211
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
212
+sudo ./edit-config go.d/cockroachdb.conf
213
+```
214
+
215
+##### Examples
216
+
217
+###### Basic
218
219
An example configuration.
220
@@ -214,7 +228,7 @@ jobs:
228
```
229
</details>
230
217
-##### HTTP authentication
231
+###### HTTP authentication
232
233
Local server with basic HTTP authentication.
234
@@ -230,7 +244,7 @@ jobs:
244
```
245
</details>
246
233
-##### HTTPS with self-signed certificate
247
+###### HTTPS with self-signed certificate
248
249
CockroachDB with enabled HTTPS and self-signed certificate.
250
@@ -245,7 +259,7 @@ jobs:
259
```
260
</details>
261
248
-##### Multi-instance
262
+###### Multi-instance
263
264
> **Note**: When you define multiple jobs, their names must be unique.
265
src/go/plugin/go.d/collector/consul/integrations/consul.md
+38
-24
@@ -197,26 +197,6 @@ Required **only if authentication is enabled**.
197
198
### Configuration
199
200
-#### File
201
-
202
-The configuration file name for this integration is `go.d/consul.conf`.
203
-
204
-The file format is YAML. Generally, the structure is:
205
-
206
-```yaml
207
-update_every: 1
208
-autodetection_retry: 0
209
-jobs:
210
- - name: some_name1
211
- - name: some_name1
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).
215
-
216
-```bash
217
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
218
-sudo ./edit-config go.d/consul.conf
219
-```
200
#### Options
201
202
The following options can be defined globally: update_every, autodetection_retry.
@@ -249,9 +229,43 @@ The following options can be defined globally: update_every, autodetection_retry
229
230
</details>
231
252
-#### Examples
232
254
-##### Basic
233
+#### via UI
234
+
235
+The **consul** collector can be configured directly through the Netdata web interface:
236
+
237
+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.
239
+3. The **Collectors → Jobs** view opens by default.
240
+4. In the Search box, type _consul_ (or scroll the list) to locate the **consul** collector.
241
+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**.
243
+
244
+
245
+#### via File
246
+
247
+The configuration file name for this integration is `go.d/consul.conf`.
248
+
249
+The file format is YAML. Generally, the structure is:
250
+
251
+```yaml
252
+update_every: 1
253
+autodetection_retry: 0
254
+jobs:
255
+ - name: some_name1
256
+ - name: some_name1
257
+```
258
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
259
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
260
+
261
+```bash
262
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
263
+sudo ./edit-config go.d/consul.conf
264
+```
265
+
266
+##### Examples
267
+
268
+###### Basic
269
270
An example configuration.
271
@@ -262,7 +276,7 @@ jobs:
276
acl_token: "ec15675e-2999-d789-832e-8c4794daa8d7"
277
278
```
265
-##### Basic HTTP auth
279
+###### Basic HTTP auth
280
281
Local server with basic HTTP authentication.
282
@@ -279,7 +293,7 @@ jobs:
293
```
294
</details>
295
282
-##### Multi-instance
296
+###### Multi-instance
297
298
> **Note**: When you define multiple jobs, their names must be unique.
299
src/go/plugin/go.d/collector/coredns/integrations/coredns.md
+38
-24
@@ -132,26 +132,6 @@ No action required.
132
133
### Configuration
134
135
-#### File
136
-
137
-The configuration file name for this integration is `go.d/coredns.conf`.
138
-
139
-The file format is YAML. Generally, the structure is:
140
-
141
-```yaml
142
-update_every: 1
143
-autodetection_retry: 0
144
-jobs:
145
- - name: some_name1
146
- - name: some_name1
147
-```
148
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
149
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
150
-
151
-```bash
152
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
153
-sudo ./edit-config go.d/coredns.conf
154
-```
135
#### Options
136
137
The following options can be defined globally: update_every, autodetection_retry.
@@ -219,9 +199,43 @@ per_zone_stats:
199
200
</details>
201
222
-#### Examples
202
224
-##### Basic
203
+#### via UI
204
+
205
+The **coredns** collector can be configured directly through the Netdata web interface:
206
+
207
+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.
209
+3. The **Collectors → Jobs** view opens by default.
210
+4. In the Search box, type _coredns_ (or scroll the list) to locate the **coredns** collector.
211
+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**.
213
+
214
+
215
+#### via File
216
+
217
+The configuration file name for this integration is `go.d/coredns.conf`.
218
+
219
+The file format is YAML. Generally, the structure is:
220
+
221
+```yaml
222
+update_every: 1
223
+autodetection_retry: 0
224
+jobs:
225
+ - name: some_name1
226
+ - name: some_name1
227
+```
228
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
229
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
230
+
231
+```bash
232
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
233
+sudo ./edit-config go.d/coredns.conf
234
+```
235
+
236
+##### Examples
237
+
238
+###### Basic
239
240
An example configuration.
241
@@ -235,7 +249,7 @@ jobs:
249
```
250
</details>
251
238
-##### Basic HTTP auth
252
+###### Basic HTTP auth
253
254
Local server with basic HTTP authentication.
255
@@ -251,7 +265,7 @@ jobs:
265
```
266
</details>
267
254
-##### Multi-instance
268
+###### Multi-instance
269
270
> **Note**: When you define multiple jobs, their names must be unique.
271
src/go/plugin/go.d/collector/couchbase/integrations/couchbase.md
+38
-24
@@ -88,26 +88,6 @@ No action required.
88
89
### Configuration
90
91
-#### File
92
-
93
-The configuration file name for this integration is `go.d/couchbase.conf`.
94
-
95
-The file format is YAML. Generally, the structure is:
96
-
97
-```yaml
98
-update_every: 1
99
-autodetection_retry: 0
100
-jobs:
101
- - name: some_name1
102
- - name: some_name1
103
-```
104
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
-
107
-```bash
108
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
109
-sudo ./edit-config go.d/couchbase.conf
110
-```
91
#### Options
92
93
The following options can be defined globally: update_every, autodetection_retry.
@@ -137,9 +117,43 @@ The following options can be defined globally: update_every, autodetection_retry
117
118
</details>
119
140
-#### Examples
120
142
-##### Basic
121
+#### via UI
122
+
123
+The **couchbase** collector can be configured directly through the Netdata web interface:
124
+
125
+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.
127
+3. The **Collectors → Jobs** view opens by default.
128
+4. In the Search box, type _couchbase_ (or scroll the list) to locate the **couchbase** collector.
129
+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**.
131
+
132
+
133
+#### via File
134
+
135
+The configuration file name for this integration is `go.d/couchbase.conf`.
136
+
137
+The file format is YAML. Generally, the structure is:
138
+
139
+```yaml
140
+update_every: 1
141
+autodetection_retry: 0
142
+jobs:
143
+ - name: some_name1
144
+ - name: some_name1
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).
148
+
149
+```bash
150
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
+sudo ./edit-config go.d/couchbase.conf
152
+```
153
+
154
+##### Examples
155
+
156
+###### Basic
157
158
An example configuration.
159
@@ -153,7 +167,7 @@ jobs:
167
```
168
</details>
169
156
-##### Basic HTTP auth
170
+###### Basic HTTP auth
171
172
Local server with basic HTTP authentication.
173
@@ -169,7 +183,7 @@ jobs:
183
```
184
</details>
185
172
-##### Multi-instance
186
+###### Multi-instance
187
188
> **Note**: When you define multiple jobs, their names must be unique.
189
src/go/plugin/go.d/collector/couchdb/integrations/couchdb.md
+38
-24
@@ -96,26 +96,6 @@ No action required.
96
97
### Configuration
98
99
-#### File
100
-
101
-The configuration file name for this integration is `go.d/couchdb.conf`.
102
-
103
-The file format is YAML. Generally, the structure is:
104
-
105
-```yaml
106
-update_every: 1
107
-autodetection_retry: 0
108
-jobs:
109
- - name: some_name1
110
- - name: some_name1
111
-```
112
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
113
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
-
115
-```bash
116
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
-sudo ./edit-config go.d/couchdb.conf
118
-```
99
#### Options
100
101
The following options can be defined globally: update_every, autodetection_retry.
@@ -147,9 +127,43 @@ The following options can be defined globally: update_every, autodetection_retry
127
128
</details>
129
150
-#### Examples
130
152
-##### Basic
131
+#### via UI
132
+
133
+The **couchdb** collector can be configured directly through the Netdata web interface:
134
+
135
+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.
137
+3. The **Collectors → Jobs** view opens by default.
138
+4. In the Search box, type _couchdb_ (or scroll the list) to locate the **couchdb** collector.
139
+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**.
141
+
142
+
143
+#### via File
144
+
145
+The configuration file name for this integration is `go.d/couchdb.conf`.
146
+
147
+The file format is YAML. Generally, the structure is:
148
+
149
+```yaml
150
+update_every: 1
151
+autodetection_retry: 0
152
+jobs:
153
+ - name: some_name1
154
+ - name: some_name1
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).
158
+
159
+```bash
160
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
161
+sudo ./edit-config go.d/couchdb.conf
162
+```
163
+
164
+##### Examples
165
+
166
+###### Basic
167
168
An example configuration.
169
@@ -163,7 +177,7 @@ jobs:
177
```
178
</details>
179
166
-##### Basic HTTP auth
180
+###### Basic HTTP auth
181
182
Local server with basic HTTP authentication, node name and multiple databases defined. Make sure to match the node name with the `NODENAME` value in your CouchDB's `etc/vm.args` file. Typically, this is of the form `couchdb@fully.qualified.domain.name` in a cluster, or `couchdb@127.0.0.1` for a single-node server.
183
@@ -182,7 +196,7 @@ jobs:
196
```
197
</details>
198
185
-##### Multi-instance
199
+###### Multi-instance
200
201
> **Note**: When you define multiple jobs, their names must be unique.
202
src/go/plugin/go.d/collector/dmcache/integrations/dmcache_devices.md
+30
-16
@@ -90,7 +90,34 @@ No action required.
90
91
### Configuration
92
93
-#### File
93
+#### Options
94
+
95
+The following options can be defined globally: update_every.
96
+
97
+
98
+<details open><summary>Config options</summary>
99
+
100
+| Name | Description | Default | Required |
101
+|:----|:-----------|:-------|:--------:|
102
+| update_every | Data collection frequency. | 10 | no |
103
+| timeout | dmsetup binary execution timeout. | 2 | no |
104
+
105
+</details>
106
+
107
+
108
+#### via UI
109
+
110
+The **dmcache** collector can be configured directly through the Netdata web interface:
111
+
112
+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.
114
+3. The **Collectors → Jobs** view opens by default.
115
+4. In the Search box, type _dmcache_ (or scroll the list) to locate the **dmcache** collector.
116
+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**.
118
+
119
+
120
+#### via File
121
122
The configuration file name for this integration is `go.d/dmcache.conf`.
123
@@ -110,23 +137,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
137
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
138
sudo ./edit-config go.d/dmcache.conf
139
```
113
-#### Options
114
-
115
-The following options can be defined globally: update_every.
116
-
117
-
118
-<details open><summary>Config options</summary>
119
-
120
-| Name | Description | Default | Required |
121
-|:----|:-----------|:-------|:--------:|
122
-| update_every | Data collection frequency. | 10 | no |
123
-| timeout | dmsetup binary execution timeout. | 2 | no |
124
-
125
-</details>
140
127
-#### Examples
141
+##### Examples
142
129
-##### Custom update_every
143
+###### Custom update_every
144
145
Allows you to override the default data collection interval.
146
src/go/plugin/go.d/collector/dnsdist/integrations/dnsdist.md
+37
-23
@@ -96,26 +96,6 @@ For collecting metrics via HTTP, you need to [enable the built-in webserver](htt
96
97
### Configuration
98
99
-#### File
100
-
101
-The configuration file name for this integration is `go.d/dnsdist.conf`.
102
-
103
-The file format is YAML. Generally, the structure is:
104
-
105
-```yaml
106
-update_every: 1
107
-autodetection_retry: 0
108
-jobs:
109
- - name: some_name1
110
- - name: some_name1
111
-```
112
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
113
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
-
115
-```bash
116
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
-sudo ./edit-config go.d/dnsdist.conf
118
-```
99
#### Options
100
101
The following options can be defined globally: update_every, autodetection_retry.
@@ -145,9 +125,43 @@ The following options can be defined globally: update_every, autodetection_retry
125
126
</details>
127
148
-#### Examples
128
150
-##### Basic
129
+#### via UI
130
+
131
+The **dnsdist** collector can be configured directly through the Netdata web interface:
132
+
133
+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.
135
+3. The **Collectors → Jobs** view opens by default.
136
+4. In the Search box, type _dnsdist_ (or scroll the list) to locate the **dnsdist** collector.
137
+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**.
139
+
140
+
141
+#### via File
142
+
143
+The configuration file name for this integration is `go.d/dnsdist.conf`.
144
+
145
+The file format is YAML. Generally, the structure is:
146
+
147
+```yaml
148
+update_every: 1
149
+autodetection_retry: 0
150
+jobs:
151
+ - name: some_name1
152
+ - name: some_name1
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).
156
+
157
+```bash
158
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
159
+sudo ./edit-config go.d/dnsdist.conf
160
+```
161
+
162
+##### Examples
163
+
164
+###### Basic
165
166
An example configuration.
167
@@ -163,7 +177,7 @@ jobs:
177
```
178
</details>
179
166
-##### Multi-instance
180
+###### Multi-instance
181
182
> **Note**: When you define multiple jobs, their names must be unique.
183
src/go/plugin/go.d/collector/dnsmasq/integrations/dnsmasq.md
+35
-21
@@ -84,7 +84,37 @@ No action required.
84
85
### Configuration
86
87
-#### File
87
+#### Options
88
+
89
+The following options can be defined globally: update_every, autodetection_retry.
90
+
91
+
92
+<details open><summary>Config options</summary>
93
+
94
+| Name | Description | Default | Required |
95
+|:----|:-----------|:-------|:--------:|
96
+| update_every | Data collection frequency. | 1 | no |
97
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
98
+| address | Server address in `ip:port` format. | 127.0.0.1:53 | yes |
99
+| protocol | DNS query transport protocol. Supported protocols: udp, tcp, tcp-tls. | udp | no |
100
+| timeout | DNS query timeout (dial, write and read) in seconds. | 1 | no |
101
+
102
+</details>
103
+
104
+
105
+#### via UI
106
+
107
+The **dnsmasq** collector can be configured directly through the Netdata web interface:
108
+
109
+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.
111
+3. The **Collectors → Jobs** view opens by default.
112
+4. In the Search box, type _dnsmasq_ (or scroll the list) to locate the **dnsmasq** collector.
113
+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**.
115
+
116
+
117
+#### via File
118
119
The configuration file name for this integration is `go.d/dnsmasq.conf`.
120
@@ -104,26 +134,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
134
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
135
sudo ./edit-config go.d/dnsmasq.conf
136
```
107
-#### Options
108
-
109
-The following options can be defined globally: update_every, autodetection_retry.
110
-
111
-
112
-<details open><summary>Config options</summary>
113
-
114
-| Name | Description | Default | Required |
115
-|:----|:-----------|:-------|:--------:|
116
-| update_every | Data collection frequency. | 1 | no |
117
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
118
-| address | Server address in `ip:port` format. | 127.0.0.1:53 | yes |
119
-| protocol | DNS query transport protocol. Supported protocols: udp, tcp, tcp-tls. | udp | no |
120
-| timeout | DNS query timeout (dial, write and read) in seconds. | 1 | no |
121
-
122
-</details>
137
124
-#### Examples
138
+##### Examples
139
126
-##### Basic
140
+###### Basic
141
142
An example configuration.
143
@@ -137,7 +151,7 @@ jobs:
151
```
152
</details>
153
140
-##### Using TCP protocol
154
+###### Using TCP protocol
155
156
Local server with specific DNS query transport protocol.
157
@@ -152,7 +166,7 @@ jobs:
166
```
167
</details>
168
155
-##### Multi-instance
169
+###### Multi-instance
170
171
> **Note**: When you define multiple jobs, their names must be unique.
172
src/go/plugin/go.d/collector/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md
+34
-20
@@ -113,7 +113,37 @@ No action required.
113
114
### Configuration
115
116
-#### File
116
+#### Options
117
+
118
+The following options can be defined globally: update_every, autodetection_retry.
119
+
120
+
121
+<details open><summary>Config options</summary>
122
+
123
+| Name | Description | Default | Required |
124
+|:----|:-----------|:-------|:--------:|
125
+| update_every | Data collection frequency. | 1 | no |
126
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
127
+| leases_path | Path to dnsmasq DHCP leases file. | /var/lib/misc/dnsmasq.leases | no |
128
+| conf_path | Path to dnsmasq configuration file. | /etc/dnsmasq.conf | no |
129
+| conf_dir | Path to dnsmasq configuration directory. | /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new | no |
130
+
131
+</details>
132
+
133
+
134
+#### via UI
135
+
136
+The **dnsmasq_dhcp** collector can be configured directly through the Netdata web interface:
137
+
138
+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.
140
+3. The **Collectors → Jobs** view opens by default.
141
+4. In the Search box, type _dnsmasq_dhcp_ (or scroll the list) to locate the **dnsmasq_dhcp** collector.
142
+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**.
144
+
145
+
146
+#### via File
147
148
The configuration file name for this integration is `go.d/dnsmasq_dhcp.conf`.
149
@@ -133,26 +163,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
163
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
164
sudo ./edit-config go.d/dnsmasq_dhcp.conf
165
```
136
-#### Options
137
-
138
-The following options can be defined globally: update_every, autodetection_retry.
139
-
140
-
141
-<details open><summary>Config options</summary>
142
-
143
-| Name | Description | Default | Required |
144
-|:----|:-----------|:-------|:--------:|
145
-| update_every | Data collection frequency. | 1 | no |
146
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
147
-| leases_path | Path to dnsmasq DHCP leases file. | /var/lib/misc/dnsmasq.leases | no |
148
-| conf_path | Path to dnsmasq configuration file. | /etc/dnsmasq.conf | no |
149
-| conf_dir | Path to dnsmasq configuration directory. | /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new | no |
150
-
151
-</details>
166
153
-#### Examples
167
+##### Examples
168
155
-##### Basic
169
+###### Basic
170
171
An example configuration.
172
@@ -168,7 +182,7 @@ jobs:
182
```
183
</details>
184
171
-##### Pi-hole
185
+###### Pi-hole
186
187
Dnsmasq DHCP on Pi-hole.
188
src/go/plugin/go.d/collector/dnsquery/integrations/dns_query.md
+37
-23
@@ -93,26 +93,6 @@ No action required.
93
94
### Configuration
95
96
-#### File
97
-
98
-The configuration file name for this integration is `go.d/dns_query.conf`.
99
-
100
-The file format is YAML. Generally, the structure is:
101
-
102
-```yaml
103
-update_every: 1
104
-autodetection_retry: 0
105
-jobs:
106
- - name: some_name1
107
- - name: some_name1
108
-```
109
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
-
112
-```bash
113
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
114
-sudo ./edit-config go.d/dns_query.conf
115
-```
96
#### Options
97
98
The following options can be defined globally: update_every, autodetection_retry.
@@ -133,9 +113,43 @@ The following options can be defined globally: update_every, autodetection_retry
113
114
</details>
115
136
-#### Examples
116
138
-##### Specific DNS servers
117
+#### via UI
118
+
119
+The **dns_query** collector can be configured directly through the Netdata web interface:
120
+
121
+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.
123
+3. The **Collectors → Jobs** view opens by default.
124
+4. In the Search box, type _dns_query_ (or scroll the list) to locate the **dns_query** collector.
125
+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**.
127
+
128
+
129
+#### via File
130
+
131
+The configuration file name for this integration is `go.d/dns_query.conf`.
132
+
133
+The file format is YAML. Generally, the structure is:
134
+
135
+```yaml
136
+update_every: 1
137
+autodetection_retry: 0
138
+jobs:
139
+ - name: some_name1
140
+ - name: some_name1
141
+```
142
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
143
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
144
+
145
+```bash
146
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
147
+sudo ./edit-config go.d/dns_query.conf
148
+```
149
+
150
+##### Examples
151
+
152
+###### Specific DNS servers
153
154
An example configuration using Google's public DNS servers.
155
@@ -158,7 +172,7 @@ jobs:
172
```
173
</details>
174
161
-##### System DNS
175
+###### System DNS
176
177
An example configuration using DNS servers from `/etc/resolv.conf`.
178
src/go/plugin/go.d/collector/docker/integrations/docker.md
+35
-21
@@ -116,7 +116,38 @@ No action required.
116
117
### Configuration
118
119
-#### File
119
+#### Options
120
+
121
+The following options can be defined globally: update_every, autodetection_retry.
122
+
123
+
124
+<details open><summary>Config options</summary>
125
+
126
+| Name | Description | Default | Required |
127
+|:----|:-----------|:-------|:--------:|
128
+| update_every | Data collection frequency. | 1 | no |
129
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
130
+| address | Docker daemon's listening address. When using a TCP socket, the format is: tcp://[ip]:[port] | unix:///var/run/docker.sock | yes |
131
+| timeout | Request timeout in seconds. | 2 | no |
132
+| container_selector | [Pattern](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#readme) to specify which containers to monitor. | * | no |
133
+| collect_container_size | Whether to collect container writable layer size. | no | no |
134
+
135
+</details>
136
+
137
+
138
+#### via UI
139
+
140
+The **docker** collector can be configured directly through the Netdata web interface:
141
+
142
+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.
144
+3. The **Collectors → Jobs** view opens by default.
145
+4. In the Search box, type _docker_ (or scroll the list) to locate the **docker** collector.
146
+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**.
148
+
149
+
150
+#### via File
151
152
The configuration file name for this integration is `go.d/docker.conf`.
153
@@ -136,27 +167,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
167
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
168
sudo ./edit-config go.d/docker.conf
169
```
139
-#### Options
140
-
141
-The following options can be defined globally: update_every, autodetection_retry.
142
-
143
-
144
-<details open><summary>Config options</summary>
145
-
146
-| Name | Description | Default | Required |
147
-|:----|:-----------|:-------|:--------:|
148
-| update_every | Data collection frequency. | 1 | no |
149
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
150
-| address | Docker daemon's listening address. When using a TCP socket, the format is: tcp://[ip]:[port] | unix:///var/run/docker.sock | yes |
151
-| timeout | Request timeout in seconds. | 2 | no |
152
-| container_selector | [Pattern](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#readme) to specify which containers to monitor. | * | no |
153
-| collect_container_size | Whether to collect container writable layer size. | no | no |
154
-
155
-</details>
170
157
-#### Examples
171
+##### Examples
172
159
-##### Basic
173
+###### Basic
174
175
An example configuration.
176
@@ -166,7 +180,7 @@ jobs:
180
address: 'unix:///var/run/docker.sock'
181
182
```
169
-##### Multi-instance
183
+###### Multi-instance
184
185
> **Note**: When you define multiple jobs, their names must be unique.
186
src/go/plugin/go.d/collector/docker_engine/integrations/docker_engine.md
+39
-25
@@ -94,26 +94,6 @@ To enable built-in Prometheus exporter, follow the [official documentation](http
94
95
### Configuration
96
97
-#### File
98
-
99
-The configuration file name for this integration is `go.d/docker_engine.conf`.
100
-
101
-The file format is YAML. Generally, the structure is:
102
-
103
-```yaml
104
-update_every: 1
105
-autodetection_retry: 0
106
-jobs:
107
- - name: some_name1
108
- - name: some_name1
109
-```
110
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
111
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
-
113
-```bash
114
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
115
-sudo ./edit-config go.d/docker_engine.conf
116
-```
97
#### Options
98
99
The following options can be defined globally: update_every, autodetection_retry.
@@ -143,9 +123,43 @@ The following options can be defined globally: update_every, autodetection_retry
123
124
</details>
125
146
-#### Examples
126
148
-##### Basic
127
+#### via UI
128
+
129
+The **docker_engine** collector can be configured directly through the Netdata web interface:
130
+
131
+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.
133
+3. The **Collectors → Jobs** view opens by default.
134
+4. In the Search box, type _docker_engine_ (or scroll the list) to locate the **docker_engine** collector.
135
+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**.
137
+
138
+
139
+#### via File
140
+
141
+The configuration file name for this integration is `go.d/docker_engine.conf`.
142
+
143
+The file format is YAML. Generally, the structure is:
144
+
145
+```yaml
146
+update_every: 1
147
+autodetection_retry: 0
148
+jobs:
149
+ - name: some_name1
150
+ - name: some_name1
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).
154
+
155
+```bash
156
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
157
+sudo ./edit-config go.d/docker_engine.conf
158
+```
159
+
160
+##### Examples
161
+
162
+###### Basic
163
164
A basic example configuration.
165
@@ -155,7 +169,7 @@ jobs:
169
url: http://127.0.0.1:9323/metrics
170
171
```
158
-##### HTTP authentication
172
+###### HTTP authentication
173
174
Basic HTTP authentication.
175
@@ -171,7 +185,7 @@ jobs:
185
```
186
</details>
187
174
-##### HTTPS with self-signed certificate
188
+###### HTTPS with self-signed certificate
189
190
Configuration with enabled HTTPS and self-signed certificate.
191
@@ -186,7 +200,7 @@ jobs:
200
```
201
</details>
202
189
-##### Multi-instance
203
+###### Multi-instance
204
205
> **Note**: When you define multiple jobs, their names must be unique.
206
src/go/plugin/go.d/collector/dockerhub/integrations/docker_hub_repository.md
+36
-22
@@ -86,26 +86,6 @@ No action required.
86
87
### Configuration
88
89
-#### File
90
-
91
-The configuration file name for this integration is `go.d/dockerhub.conf`.
92
-
93
-The file format is YAML. Generally, the structure is:
94
-
95
-```yaml
96
-update_every: 1
97
-autodetection_retry: 0
98
-jobs:
99
- - name: some_name1
100
- - name: some_name1
101
-```
102
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
-
105
-```bash
106
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
107
-sudo ./edit-config go.d/dockerhub.conf
108
-```
89
#### Options
90
91
The following options can be defined globally: update_every, autodetection_retry.
@@ -136,9 +116,43 @@ The following options can be defined globally: update_every, autodetection_retry
116
117
</details>
118
139
-#### Examples
119
141
-##### Basic
120
+#### via UI
121
+
122
+The **dockerhub** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _dockerhub_ (or scroll the list) to locate the **dockerhub** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `go.d/dockerhub.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+jobs:
142
+ - name: some_name1
143
+ - name: some_name1
144
+```
145
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
146
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+
148
+```bash
149
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
+sudo ./edit-config go.d/dockerhub.conf
151
+```
152
+
153
+##### Examples
154
+
155
+###### Basic
156
157
A basic example configuration.
158
src/go/plugin/go.d/collector/dovecot/integrations/dovecot.md
+34
-20
@@ -100,7 +100,36 @@ To enable `old_stats` plugin, see [Old Statistics](https://doc.dovecot.org/confi
100
101
### Configuration
102
103
-#### File
103
+#### Options
104
+
105
+The following options can be defined globally: update_every, autodetection_retry.
106
+
107
+
108
+<details open><summary>Config options</summary>
109
+
110
+| Name | Description | Default | Required |
111
+|:----|:-----------|:-------|:--------:|
112
+| update_every | Data collection frequency. | 1 | no |
113
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
114
+| address | The Unix or TCP socket address where the Dovecot [old_stats](https://doc.dovecot.org/configuration_manual/stats/old_statistics/#old-statistics) plugin listens for connections. | 127.0.0.1:24242 | yes |
115
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
116
+
117
+</details>
118
+
119
+
120
+#### via UI
121
+
122
+The **dovecot** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _dovecot_ (or scroll the list) to locate the **dovecot** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
134
The configuration file name for this integration is `go.d/dovecot.conf`.
135
@@ -120,25 +149,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
149
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
sudo ./edit-config go.d/dovecot.conf
151
```
123
-#### Options
124
-
125
-The following options can be defined globally: update_every, autodetection_retry.
126
-
127
-
128
-<details open><summary>Config options</summary>
129
-
130
-| Name | Description | Default | Required |
131
-|:----|:-----------|:-------|:--------:|
132
-| update_every | Data collection frequency. | 1 | no |
133
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
134
-| address | The Unix or TCP socket address where the Dovecot [old_stats](https://doc.dovecot.org/configuration_manual/stats/old_statistics/#old-statistics) plugin listens for connections. | 127.0.0.1:24242 | yes |
135
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
136
-
137
-</details>
152
139
-#### Examples
153
+##### Examples
154
141
-##### Basic (TCP)
155
+###### Basic (TCP)
156
157
A basic example configuration.
158
@@ -152,7 +166,7 @@ jobs:
166
```
167
</details>
168
155
-##### Basic (UNIX)
169
+###### Basic (UNIX)
170
171
A basic example configuration using a UNIX socket.
172
@@ -166,7 +180,7 @@ jobs:
180
```
181
</details>
182
169
-##### Multi-instance
183
+###### Multi-instance
184
185
> **Note**: When you define multiple jobs, their names must be unique.
186
src/go/plugin/go.d/collector/elasticsearch/integrations/elasticsearch.md
+40
-26
@@ -188,26 +188,6 @@ No action required.
188
189
### Configuration
190
191
-#### File
192
-
193
-The configuration file name for this integration is `go.d/elasticsearch.conf`.
194
-
195
-The file format is YAML. Generally, the structure is:
196
-
197
-```yaml
198
-update_every: 1
199
-autodetection_retry: 0
200
-jobs:
201
- - name: some_name1
202
- - name: some_name1
203
-```
204
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
205
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
206
-
207
-```bash
208
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
209
-sudo ./edit-config go.d/elasticsearch.conf
210
-```
191
#### Options
192
193
The following options can be defined globally: update_every, autodetection_retry.
@@ -242,9 +222,43 @@ The following options can be defined globally: update_every, autodetection_retry
222
223
</details>
224
245
-#### Examples
225
247
-##### Basic single node mode
226
+#### via UI
227
+
228
+The **elasticsearch** collector can be configured directly through the Netdata web interface:
229
+
230
+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.
232
+3. The **Collectors → Jobs** view opens by default.
233
+4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
234
+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**.
236
+
237
+
238
+#### via File
239
+
240
+The configuration file name for this integration is `go.d/elasticsearch.conf`.
241
+
242
+The file format is YAML. Generally, the structure is:
243
+
244
+```yaml
245
+update_every: 1
246
+autodetection_retry: 0
247
+jobs:
248
+ - name: some_name1
249
+ - name: some_name1
250
+```
251
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
252
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
253
+
254
+```bash
255
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
256
+sudo ./edit-config go.d/elasticsearch.conf
257
+```
258
+
259
+##### Examples
260
+
261
+###### Basic single node mode
262
263
A basic example configuration.
264
@@ -254,7 +268,7 @@ jobs:
268
url: http://127.0.0.1:9200
269
270
```
257
-##### Cluster mode
271
+###### Cluster mode
272
273
Cluster mode example configuration.
274
@@ -269,7 +283,7 @@ jobs:
283
```
284
</details>
285
272
-##### HTTP authentication
286
+###### HTTP authentication
287
288
Basic HTTP authentication.
289
@@ -285,7 +299,7 @@ jobs:
299
```
300
</details>
301
288
-##### HTTPS with self-signed certificate
302
+###### HTTPS with self-signed certificate
303
304
Elasticsearch with enabled HTTPS and self-signed certificate.
305
@@ -300,7 +314,7 @@ jobs:
314
```
315
</details>
316
303
-##### Multi-instance
317
+###### Multi-instance
318
319
> **Note**: When you define multiple jobs, their names must be unique.
320
src/go/plugin/go.d/collector/elasticsearch/integrations/opensearch.md
+40
-26
@@ -188,26 +188,6 @@ No action required.
188
189
### Configuration
190
191
-#### File
192
-
193
-The configuration file name for this integration is `go.d/elasticsearch.conf`.
194
-
195
-The file format is YAML. Generally, the structure is:
196
-
197
-```yaml
198
-update_every: 1
199
-autodetection_retry: 0
200
-jobs:
201
- - name: some_name1
202
- - name: some_name1
203
-```
204
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
205
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
206
-
207
-```bash
208
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
209
-sudo ./edit-config go.d/elasticsearch.conf
210
-```
191
#### Options
192
193
The following options can be defined globally: update_every, autodetection_retry.
@@ -242,9 +222,43 @@ The following options can be defined globally: update_every, autodetection_retry
222
223
</details>
224
245
-#### Examples
225
247
-##### Basic single node mode
226
+#### via UI
227
+
228
+The **elasticsearch** collector can be configured directly through the Netdata web interface:
229
+
230
+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.
232
+3. The **Collectors → Jobs** view opens by default.
233
+4. In the Search box, type _elasticsearch_ (or scroll the list) to locate the **elasticsearch** collector.
234
+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**.
236
+
237
+
238
+#### via File
239
+
240
+The configuration file name for this integration is `go.d/elasticsearch.conf`.
241
+
242
+The file format is YAML. Generally, the structure is:
243
+
244
+```yaml
245
+update_every: 1
246
+autodetection_retry: 0
247
+jobs:
248
+ - name: some_name1
249
+ - name: some_name1
250
+```
251
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
252
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
253
+
254
+```bash
255
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
256
+sudo ./edit-config go.d/elasticsearch.conf
257
+```
258
+
259
+##### Examples
260
+
261
+###### Basic single node mode
262
263
A basic example configuration.
264
@@ -254,7 +268,7 @@ jobs:
268
url: http://127.0.0.1:9200
269
270
```
257
-##### Cluster mode
271
+###### Cluster mode
272
273
Cluster mode example configuration.
274
@@ -269,7 +283,7 @@ jobs:
283
```
284
</details>
285
272
-##### HTTP authentication
286
+###### HTTP authentication
287
288
Basic HTTP authentication.
289
@@ -285,7 +299,7 @@ jobs:
299
```
300
</details>
301
288
-##### HTTPS with self-signed certificate
302
+###### HTTPS with self-signed certificate
303
304
Elasticsearch with enabled HTTPS and self-signed certificate.
305
@@ -300,7 +314,7 @@ jobs:
314
```
315
</details>
316
303
-##### Multi-instance
317
+###### Multi-instance
318
319
> **Note**: When you define multiple jobs, their names must be unique.
320
src/go/plugin/go.d/collector/envoy/integrations/envoy.md
+39
-25
@@ -135,26 +135,6 @@ No action required.
135
136
### Configuration
137
138
-#### File
139
-
140
-The configuration file name for this integration is `go.d/envoy.conf`.
141
-
142
-The file format is YAML. Generally, the structure is:
143
-
144
-```yaml
145
-update_every: 1
146
-autodetection_retry: 0
147
-jobs:
148
- - name: some_name1
149
- - name: some_name1
150
-```
151
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
152
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
153
-
154
-```bash
155
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
156
-sudo ./edit-config go.d/envoy.conf
157
-```
138
#### Options
139
140
The following options can be defined globally: update_every, autodetection_retry.
@@ -184,9 +164,43 @@ The following options can be defined globally: update_every, autodetection_retry
164
165
</details>
166
187
-#### Examples
167
189
-##### Basic
168
+#### via UI
169
+
170
+The **envoy** collector can be configured directly through the Netdata web interface:
171
+
172
+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.
174
+3. The **Collectors → Jobs** view opens by default.
175
+4. In the Search box, type _envoy_ (or scroll the list) to locate the **envoy** collector.
176
+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**.
178
+
179
+
180
+#### via File
181
+
182
+The configuration file name for this integration is `go.d/envoy.conf`.
183
+
184
+The file format is YAML. Generally, the structure is:
185
+
186
+```yaml
187
+update_every: 1
188
+autodetection_retry: 0
189
+jobs:
190
+ - name: some_name1
191
+ - name: some_name1
192
+```
193
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
194
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
195
+
196
+```bash
197
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
198
+sudo ./edit-config go.d/envoy.conf
199
+```
200
+
201
+##### Examples
202
+
203
+###### Basic
204
205
A basic example configuration.
206
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1:9901/stats/prometheus
211
212
```
199
-##### HTTP authentication
213
+###### HTTP authentication
214
215
Basic HTTP authentication.
216
@@ -212,7 +226,7 @@ jobs:
226
```
227
</details>
228
215
-##### HTTPS with self-signed certificate
229
+###### HTTPS with self-signed certificate
230
231
Do not validate server certificate chain and hostname.
232
@@ -228,7 +242,7 @@ jobs:
242
```
243
</details>
244
231
-##### Multi-instance
245
+###### Multi-instance
246
247
> **Note**: When you define multiple jobs, their names must be unique.
248
src/go/plugin/go.d/collector/ethtool/integrations/optical_modules.md
+31
-17
@@ -91,7 +91,35 @@ No action required.
91
92
### Configuration
93
94
-#### File
94
+#### Options
95
+
96
+The following options can be defined globally: update_every.
97
+
98
+
99
+<details open><summary>Config options</summary>
100
+
101
+| Name | Description | Default | Required |
102
+|:----|:-----------|:-------|:--------:|
103
+| update_every | Data collection frequency. | 10 | no |
104
+| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
105
+| optical_interfaces | Space-separated list of optical interface names which must have optical transceiver modules with [DDM](https://en.wikipedia.org/wiki/Small_Form-factor_Pluggable#Digital_diagnostics_monitoring). | | yes |
106
+
107
+</details>
108
+
109
+
110
+#### via UI
111
+
112
+The **ethtool** collector can be configured directly through the Netdata web interface:
113
+
114
+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.
116
+3. The **Collectors → Jobs** view opens by default.
117
+4. In the Search box, type _ethtool_ (or scroll the list) to locate the **ethtool** collector.
118
+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**.
120
+
121
+
122
+#### via File
123
124
The configuration file name for this integration is `go.d/ethtool.conf`.
125
@@ -111,24 +139,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
139
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
140
sudo ./edit-config go.d/ethtool.conf
141
```
114
-#### Options
115
-
116
-The following options can be defined globally: update_every.
117
-
118
-
119
-<details open><summary>Config options</summary>
120
-
121
-| Name | Description | Default | Required |
122
-|:----|:-----------|:-------|:--------:|
123
-| update_every | Data collection frequency. | 10 | no |
124
-| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
125
-| optical_interfaces | Space-separated list of optical interface names which must have optical transceiver modules with [DDM](https://en.wikipedia.org/wiki/Small_Form-factor_Pluggable#Digital_diagnostics_monitoring). | | yes |
126
-
127
-</details>
142
129
-#### Examples
143
+##### Examples
144
131
-##### Custom binary path
145
+###### Custom binary path
146
147
The executable is not in the directories specified in the PATH environment variable.
148
src/go/plugin/go.d/collector/exim/integrations/exim.md
+30
-16
@@ -83,7 +83,34 @@ No action required.
83
84
### Configuration
85
86
-#### File
86
+#### Options
87
+
88
+The following options can be defined globally: update_every.
89
+
90
+
91
+<details open><summary>Config options</summary>
92
+
93
+| Name | Description | Default | Required |
94
+|:----|:-----------|:-------|:--------:|
95
+| update_every | Data collection frequency. | 10 | no |
96
+| timeout | exim binary execution timeout. | 2 | no |
97
+
98
+</details>
99
+
100
+
101
+#### via UI
102
+
103
+The **exim** collector can be configured directly through the Netdata web interface:
104
+
105
+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.
107
+3. The **Collectors → Jobs** view opens by default.
108
+4. In the Search box, type _exim_ (or scroll the list) to locate the **exim** collector.
109
+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**.
111
+
112
+
113
+#### via File
114
115
The configuration file name for this integration is `go.d/exim.conf`.
116
@@ -103,23 +130,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
130
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
131
sudo ./edit-config go.d/exim.conf
132
```
106
-#### Options
107
-
108
-The following options can be defined globally: update_every.
109
-
110
-
111
-<details open><summary>Config options</summary>
112
-
113
-| Name | Description | Default | Required |
114
-|:----|:-----------|:-------|:--------:|
115
-| update_every | Data collection frequency. | 10 | no |
116
-| timeout | exim binary execution timeout. | 2 | no |
117
-
118
-</details>
133
120
-#### Examples
134
+##### Examples
135
122
-##### Custom update_every
136
+###### Custom update_every
137
138
Allows you to override the default data collection interval.
139
src/go/plugin/go.d/collector/fail2ban/integrations/fail2ban.md
+30
-16
@@ -98,7 +98,34 @@ There are no alerts configured by default for this integration.
98
99
### Configuration
100
101
-#### File
101
+#### Options
102
+
103
+The following options can be defined globally: update_every.
104
+
105
+
106
+<details open><summary>Config options</summary>
107
+
108
+| Name | Description | Default | Required |
109
+|:----|:-----------|:-------|:--------:|
110
+| update_every | Data collection frequency. | 10 | no |
111
+| timeout | fail2ban-client binary execution timeout. | 2 | no |
112
+
113
+</details>
114
+
115
+
116
+#### via UI
117
+
118
+The **fail2ban** collector can be configured directly through the Netdata web interface:
119
+
120
+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.
122
+3. The **Collectors → Jobs** view opens by default.
123
+4. In the Search box, type _fail2ban_ (or scroll the list) to locate the **fail2ban** collector.
124
+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**.
126
+
127
+
128
+#### via File
129
130
The configuration file name for this integration is `go.d/fail2ban.conf`.
131
@@ -118,23 +145,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
145
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
146
sudo ./edit-config go.d/fail2ban.conf
147
```
121
-#### Options
122
-
123
-The following options can be defined globally: update_every.
124
-
125
-
126
-<details open><summary>Config options</summary>
127
-
128
-| Name | Description | Default | Required |
129
-|:----|:-----------|:-------|:--------:|
130
-| update_every | Data collection frequency. | 10 | no |
131
-| timeout | fail2ban-client binary execution timeout. | 2 | no |
132
-
133
-</details>
148
135
-#### Examples
149
+##### Examples
150
137
-##### Custom update_every
151
+###### Custom update_every
152
153
Allows you to override the default data collection interval.
154
src/go/plugin/go.d/collector/filecheck/integrations/files_and_directories.md
+37
-23
@@ -108,26 +108,6 @@ No action required.
108
109
### Configuration
110
111
-#### File
112
-
113
-The configuration file name for this integration is `go.d/filecheck.conf`.
114
-
115
-The file format is YAML. Generally, the structure is:
116
-
117
-```yaml
118
-update_every: 1
119
-autodetection_retry: 0
120
-jobs:
121
- - name: some_name1
122
- - name: some_name1
123
-```
124
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
125
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
126
-
127
-```bash
128
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
129
-sudo ./edit-config go.d/filecheck.conf
130
-```
111
#### Options
112
113
The following options can be defined globally: update_every, autodetection_retry.
@@ -183,9 +163,43 @@ dirs:
163
164
</details>
165
186
-#### Examples
166
188
-##### Files
167
+#### via UI
168
+
169
+The **filecheck** collector can be configured directly through the Netdata web interface:
170
+
171
+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.
173
+3. The **Collectors → Jobs** view opens by default.
174
+4. In the Search box, type _filecheck_ (or scroll the list) to locate the **filecheck** collector.
175
+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**.
177
+
178
+
179
+#### via File
180
+
181
+The configuration file name for this integration is `go.d/filecheck.conf`.
182
+
183
+The file format is YAML. Generally, the structure is:
184
+
185
+```yaml
186
+update_every: 1
187
+autodetection_retry: 0
188
+jobs:
189
+ - name: some_name1
190
+ - name: some_name1
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).
194
+
195
+```bash
196
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
197
+sudo ./edit-config go.d/filecheck.conf
198
+```
199
+
200
+##### Examples
201
+
202
+###### Files
203
204
Files monitoring example configuration.
205
@@ -203,7 +217,7 @@ jobs:
217
```
218
</details>
219
206
-##### Directories
220
+###### Directories
221
222
Directories monitoring example configuration.
223
src/go/plugin/go.d/collector/fluentd/integrations/fluentd.md
+39
-25
@@ -87,26 +87,6 @@ To enable monitor agent, follow the [official documentation](https://docs.fluent
87
88
### Configuration
89
90
-#### File
91
-
92
-The configuration file name for this integration is `go.d/fluentd.conf`.
93
-
94
-The file format is YAML. Generally, the structure is:
95
-
96
-```yaml
97
-update_every: 1
98
-autodetection_retry: 0
99
-jobs:
100
- - name: some_name1
101
- - name: some_name1
102
-```
103
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
-
106
-```bash
107
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
108
-sudo ./edit-config go.d/fluentd.conf
109
-```
90
#### Options
91
92
The following options can be defined globally: update_every, autodetection_retry.
@@ -135,9 +115,43 @@ The following options can be defined globally: update_every, autodetection_retry
115
116
</details>
117
138
-#### Examples
118
140
-##### Basic
119
+#### via UI
120
+
121
+The **fluentd** collector can be configured directly through the Netdata web interface:
122
+
123
+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.
125
+3. The **Collectors → Jobs** view opens by default.
126
+4. In the Search box, type _fluentd_ (or scroll the list) to locate the **fluentd** collector.
127
+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**.
129
+
130
+
131
+#### via File
132
+
133
+The configuration file name for this integration is `go.d/fluentd.conf`.
134
+
135
+The file format is YAML. Generally, the structure is:
136
+
137
+```yaml
138
+update_every: 1
139
+autodetection_retry: 0
140
+jobs:
141
+ - name: some_name1
142
+ - name: some_name1
143
+```
144
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
145
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
146
+
147
+```bash
148
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
149
+sudo ./edit-config go.d/fluentd.conf
150
+```
151
+
152
+##### Examples
153
+
154
+###### Basic
155
156
A basic example configuration.
157
@@ -147,7 +161,7 @@ jobs:
161
url: http://127.0.0.1:24220
162
163
```
150
-##### HTTP authentication
164
+###### HTTP authentication
165
166
Basic HTTP authentication.
167
@@ -163,7 +177,7 @@ jobs:
177
```
178
</details>
179
166
-##### HTTPS with self-signed certificate
180
+###### HTTPS with self-signed certificate
181
182
Fluentd with enabled HTTPS and self-signed certificate.
183
@@ -178,7 +192,7 @@ jobs:
192
```
193
</details>
194
181
-##### Multi-instance
195
+###### Multi-instance
196
197
> **Note**: When you define multiple jobs, their names must be unique.
198
src/go/plugin/go.d/collector/freeradius/integrations/freeradius.md
+34
-20
@@ -97,7 +97,37 @@ To enable status server, follow the [official documentation](https://wiki.freera
97
98
### Configuration
99
100
-#### File
100
+#### Options
101
+
102
+The following options can be defined globally: update_every, autodetection_retry.
103
+
104
+
105
+<details open><summary>Config options</summary>
106
+
107
+| Name | Description | Default | Required |
108
+|:----|:-----------|:-------|:--------:|
109
+| update_every | Data collection frequency. | 1 | no |
110
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
111
+| address | Server address. | 127.0.0.1 | yes |
112
+| port | Server port. | 18121 | no |
113
+| secret | FreeRADIUS secret. | adminsecret | no |
114
+
115
+</details>
116
+
117
+
118
+#### via UI
119
+
120
+The **freeradius** collector can be configured directly through the Netdata web interface:
121
+
122
+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.
124
+3. The **Collectors → Jobs** view opens by default.
125
+4. In the Search box, type _freeradius_ (or scroll the list) to locate the **freeradius** collector.
126
+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**.
128
+
129
+
130
+#### via File
131
132
The configuration file name for this integration is `go.d/freeradius.conf`.
133
@@ -117,26 +147,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
147
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
148
sudo ./edit-config go.d/freeradius.conf
149
```
120
-#### Options
121
-
122
-The following options can be defined globally: update_every, autodetection_retry.
123
-
124
-
125
-<details open><summary>Config options</summary>
126
-
127
-| Name | Description | Default | Required |
128
-|:----|:-----------|:-------|:--------:|
129
-| update_every | Data collection frequency. | 1 | no |
130
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
131
-| address | Server address. | 127.0.0.1 | yes |
132
-| port | Server port. | 18121 | no |
133
-| secret | FreeRADIUS secret. | adminsecret | no |
134
-
135
-</details>
150
137
-#### Examples
151
+##### Examples
152
139
-##### Basic
153
+###### Basic
154
155
A basic example configuration.
156
@@ -152,7 +166,7 @@ jobs:
166
```
167
</details>
168
155
-##### Multi-instance
169
+###### Multi-instance
170
171
> **Note**: When you define multiple jobs, their names must be unique.
172
src/go/plugin/go.d/collector/gearman/integrations/gearman.md
+33
-19
@@ -105,7 +105,36 @@ No action required.
105
106
### Configuration
107
108
-#### File
108
+#### Options
109
+
110
+The following options can be defined globally: update_every, autodetection_retry.
111
+
112
+
113
+<details open><summary>Config options</summary>
114
+
115
+| Name | Description | Default | Required |
116
+|:----|:-----------|:-------|:--------:|
117
+| update_every | Data collection frequency. | 1 | no |
118
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
119
+| address | The IP address and port where the Gearman service listens for connections. | 127.0.0.1:11211 | yes |
120
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
121
+
122
+</details>
123
+
124
+
125
+#### via UI
126
+
127
+The **gearman** collector can be configured directly through the Netdata web interface:
128
+
129
+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.
131
+3. The **Collectors → Jobs** view opens by default.
132
+4. In the Search box, type _gearman_ (or scroll the list) to locate the **gearman** collector.
133
+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**.
135
+
136
+
137
+#### via File
138
139
The configuration file name for this integration is `go.d/gearman.conf`.
140
@@ -125,25 +154,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
154
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
155
sudo ./edit-config go.d/gearman.conf
156
```
128
-#### Options
129
-
130
-The following options can be defined globally: update_every, autodetection_retry.
131
-
132
-
133
-<details open><summary>Config options</summary>
134
-
135
-| Name | Description | Default | Required |
136
-|:----|:-----------|:-------|:--------:|
137
-| update_every | Data collection frequency. | 1 | no |
138
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
139
-| address | The IP address and port where the Gearman service listens for connections. | 127.0.0.1:11211 | yes |
140
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
141
-
142
-</details>
157
144
-#### Examples
158
+##### Examples
159
146
-##### Basic
160
+###### Basic
161
162
A basic example configuration.
163
@@ -157,7 +171,7 @@ jobs:
171
```
172
</details>
173
160
-##### Multi-instance
174
+###### Multi-instance
175
176
> **Note**: When you define multiple jobs, their names must be unique.
177
src/go/plugin/go.d/collector/geth/integrations/go-ethereum.md
+38
-24
@@ -97,26 +97,6 @@ No action required.
97
98
### Configuration
99
100
-#### File
101
-
102
-The configuration file name for this integration is `go.d/geth.conf`.
103
-
104
-The file format is YAML. Generally, the structure is:
105
-
106
-```yaml
107
-update_every: 1
108
-autodetection_retry: 0
109
-jobs:
110
- - name: some_name1
111
- - name: some_name1
112
-```
113
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
-
116
-```bash
117
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
-sudo ./edit-config go.d/geth.conf
119
-```
100
#### Options
101
102
The following options can be defined globally: update_every, autodetection_retry.
@@ -146,9 +126,43 @@ The following options can be defined globally: update_every, autodetection_retry
126
127
</details>
128
149
-#### Examples
129
151
-##### Basic
130
+#### via UI
131
+
132
+The **geth** collector can be configured directly through the Netdata web interface:
133
+
134
+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.
136
+3. The **Collectors → Jobs** view opens by default.
137
+4. In the Search box, type _geth_ (or scroll the list) to locate the **geth** collector.
138
+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**.
140
+
141
+
142
+#### via File
143
+
144
+The configuration file name for this integration is `go.d/geth.conf`.
145
+
146
+The file format is YAML. Generally, the structure is:
147
+
148
+```yaml
149
+update_every: 1
150
+autodetection_retry: 0
151
+jobs:
152
+ - name: some_name1
153
+ - name: some_name1
154
+```
155
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
156
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
157
+
158
+```bash
159
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
+sudo ./edit-config go.d/geth.conf
161
+```
162
+
163
+##### Examples
164
+
165
+###### Basic
166
167
A basic example configuration.
168
@@ -158,7 +172,7 @@ jobs:
172
url: http://127.0.0.1:6060/debug/metrics/prometheus
173
174
```
161
-##### HTTP authentication
175
+###### HTTP authentication
176
177
Basic HTTP authentication.
178
@@ -174,7 +188,7 @@ jobs:
188
```
189
</details>
190
177
-##### Multi-instance
191
+###### Multi-instance
192
193
> **Note**: When you define multiple jobs, their names must be unique.
194
src/go/plugin/go.d/collector/haproxy/integrations/haproxy.md
+39
-25
@@ -102,26 +102,6 @@ To enable PROMEX addon, follow the [official documentation](https://github.com/h
102
103
### Configuration
104
105
-#### File
106
-
107
-The configuration file name for this integration is `go.d/haproxy.conf`.
108
-
109
-The file format is YAML. Generally, the structure is:
110
-
111
-```yaml
112
-update_every: 1
113
-autodetection_retry: 0
114
-jobs:
115
- - name: some_name1
116
- - name: some_name1
117
-```
118
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
-
121
-```bash
122
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
-sudo ./edit-config go.d/haproxy.conf
124
-```
105
#### Options
106
107
The following options can be defined globally: update_every, autodetection_retry.
@@ -151,9 +131,43 @@ The following options can be defined globally: update_every, autodetection_retry
131
132
</details>
133
154
-#### Examples
134
156
-##### Basic
135
+#### via UI
136
+
137
+The **haproxy** collector can be configured directly through the Netdata web interface:
138
+
139
+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.
141
+3. The **Collectors → Jobs** view opens by default.
142
+4. In the Search box, type _haproxy_ (or scroll the list) to locate the **haproxy** collector.
143
+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**.
145
+
146
+
147
+#### via File
148
+
149
+The configuration file name for this integration is `go.d/haproxy.conf`.
150
+
151
+The file format is YAML. Generally, the structure is:
152
+
153
+```yaml
154
+update_every: 1
155
+autodetection_retry: 0
156
+jobs:
157
+ - name: some_name1
158
+ - name: some_name1
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).
162
+
163
+```bash
164
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
165
+sudo ./edit-config go.d/haproxy.conf
166
+```
167
+
168
+##### Examples
169
+
170
+###### Basic
171
172
A basic example configuration.
173
@@ -167,7 +181,7 @@ jobs:
181
```
182
</details>
183
170
-##### HTTP authentication
184
+###### HTTP authentication
185
186
Basic HTTP authentication.
187
@@ -183,7 +197,7 @@ jobs:
197
```
198
</details>
199
186
-##### HTTPS with self-signed certificate
200
+###### HTTPS with self-signed certificate
201
202
NGINX Plus with enabled HTTPS and self-signed certificate.
203
@@ -198,7 +212,7 @@ jobs:
212
```
213
</details>
214
201
-##### Multi-instance
215
+###### Multi-instance
216
217
> **Note**: When you define multiple jobs, their names must be unique.
218
src/go/plugin/go.d/collector/hddtemp/integrations/hdd_temperature.md
+33
-19
@@ -94,7 +94,36 @@ Install `hddtemp` using your distribution's package manager.
94
95
### Configuration
96
97
-#### File
97
+#### Options
98
+
99
+The following options can be defined globally: update_every, autodetection_retry.
100
+
101
+
102
+<details open><summary>Config options</summary>
103
+
104
+| Name | Description | Default | Required |
105
+|:----|:-----------|:-------|:--------:|
106
+| update_every | Data collection frequency. | 1 | no |
107
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
108
+| address | The IP address and port where the hddtemp daemon listens for connections. | 127.0.0.1:7634 | yes |
109
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
110
+
111
+</details>
112
+
113
+
114
+#### via UI
115
+
116
+The **hddtemp** collector can be configured directly through the Netdata web interface:
117
+
118
+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.
120
+3. The **Collectors → Jobs** view opens by default.
121
+4. In the Search box, type _hddtemp_ (or scroll the list) to locate the **hddtemp** collector.
122
+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**.
124
+
125
+
126
+#### via File
127
128
The configuration file name for this integration is `go.d/hddtemp.conf`.
129
@@ -114,25 +143,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
143
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
144
sudo ./edit-config go.d/hddtemp.conf
145
```
117
-#### Options
118
-
119
-The following options can be defined globally: update_every, autodetection_retry.
120
-
121
-
122
-<details open><summary>Config options</summary>
123
-
124
-| Name | Description | Default | Required |
125
-|:----|:-----------|:-------|:--------:|
126
-| update_every | Data collection frequency. | 1 | no |
127
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
128
-| address | The IP address and port where the hddtemp daemon listens for connections. | 127.0.0.1:7634 | yes |
129
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
130
-
131
-</details>
146
133
-#### Examples
147
+##### Examples
148
135
-##### Basic
149
+###### Basic
150
151
A basic example configuration.
152
@@ -146,7 +160,7 @@ jobs:
160
```
161
</details>
162
149
-##### Multi-instance
163
+###### Multi-instance
164
165
> **Note**: When you define multiple jobs, their names must be unique.
166
src/go/plugin/go.d/collector/hdfs/integrations/hadoop_distributed_file_system_hdfs.md
+39
-25
@@ -115,26 +115,6 @@ No action required.
115
116
### Configuration
117
118
-#### File
119
-
120
-The configuration file name for this integration is `go.d/hdfs.conf`.
121
-
122
-The file format is YAML. Generally, the structure is:
123
-
124
-```yaml
125
-update_every: 1
126
-autodetection_retry: 0
127
-jobs:
128
- - name: some_name1
129
- - name: some_name1
130
-```
131
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
132
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
133
-
134
-```bash
135
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
136
-sudo ./edit-config go.d/hdfs.conf
137
-```
118
#### Options
119
120
The following options can be defined globally: update_every, autodetection_retry.
@@ -164,9 +144,43 @@ The following options can be defined globally: update_every, autodetection_retry
144
145
</details>
146
167
-#### Examples
147
169
-##### Basic
148
+#### via UI
149
+
150
+The **hfs** collector can be configured directly through the Netdata web interface:
151
+
152
+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.
154
+3. The **Collectors → Jobs** view opens by default.
155
+4. In the Search box, type _hfs_ (or scroll the list) to locate the **hfs** collector.
156
+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**.
158
+
159
+
160
+#### via File
161
+
162
+The configuration file name for this integration is `go.d/hdfs.conf`.
163
+
164
+The file format is YAML. Generally, the structure is:
165
+
166
+```yaml
167
+update_every: 1
168
+autodetection_retry: 0
169
+jobs:
170
+ - name: some_name1
171
+ - name: some_name1
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).
175
+
176
+```bash
177
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
178
+sudo ./edit-config go.d/hdfs.conf
179
+```
180
+
181
+##### Examples
182
+
183
+###### Basic
184
185
A basic example configuration.
186
@@ -176,7 +190,7 @@ jobs:
190
url: http://127.0.0.1:9870/jmx
191
192
```
179
-##### HTTP authentication
193
+###### HTTP authentication
194
195
Basic HTTP authentication.
196
@@ -192,7 +206,7 @@ jobs:
206
```
207
</details>
208
195
-##### HTTPS with self-signed certificate
209
+###### HTTPS with self-signed certificate
210
211
Do not validate server certificate chain and hostname.
212
@@ -208,7 +222,7 @@ jobs:
222
```
223
</details>
224
211
-##### Multi-instance
225
+###### Multi-instance
226
227
> **Note**: When you define multiple jobs, their names must be unique.
228
src/go/plugin/go.d/collector/hpssa/integrations/hpe_smart_arrays.md
+30
-16
@@ -163,7 +163,34 @@ See [official installation instructions](https://support.hpe.com/connect/s/softw
163
164
### Configuration
165
166
-#### File
166
+#### Options
167
+
168
+The following options can be defined globally: update_every.
169
+
170
+
171
+<details open><summary>Config options</summary>
172
+
173
+| Name | Description | Default | Required |
174
+|:----|:-----------|:-------|:--------:|
175
+| update_every | Data collection frequency. | 10 | no |
176
+| timeout | ssacli binary execution timeout. | 2 | no |
177
+
178
+</details>
179
+
180
+
181
+#### via UI
182
+
183
+The **hpssa** collector can be configured directly through the Netdata web interface:
184
+
185
+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.
187
+3. The **Collectors → Jobs** view opens by default.
188
+4. In the Search box, type _hpssa_ (or scroll the list) to locate the **hpssa** collector.
189
+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**.
191
+
192
+
193
+#### via File
194
195
The configuration file name for this integration is `go.d/ssacli.conf`.
196
@@ -183,23 +210,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
210
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
211
sudo ./edit-config go.d/ssacli.conf
212
```
186
-#### Options
187
-
188
-The following options can be defined globally: update_every.
189
-
190
-
191
-<details open><summary>Config options</summary>
192
-
193
-| Name | Description | Default | Required |
194
-|:----|:-----------|:-------|:--------:|
195
-| update_every | Data collection frequency. | 10 | no |
196
-| timeout | ssacli binary execution timeout. | 2 | no |
197
-
198
-</details>
213
200
-#### Examples
214
+##### Examples
215
202
-##### Custom update_every
216
+###### Custom update_every
217
218
Allows you to override the default data collection interval.
219
src/go/plugin/go.d/collector/httpcheck/integrations/http_endpoints.md
+42
-28
@@ -110,26 +110,6 @@ No action required.
110
111
### Configuration
112
113
-#### File
114
-
115
-The configuration file name for this integration is `go.d/httpcheck.conf`.
116
-
117
-The file format is YAML. Generally, the structure is:
118
-
119
-```yaml
120
-update_every: 1
121
-autodetection_retry: 0
122
-jobs:
123
- - name: some_name1
124
- - name: some_name1
125
-```
126
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
127
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
128
-
129
-```bash
130
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
131
-sudo ./edit-config go.d/httpcheck.conf
132
-```
113
#### Options
114
115
The following options can be defined globally: update_every, autodetection_retry.
@@ -166,9 +146,43 @@ The following options can be defined globally: update_every, autodetection_retry
146
147
</details>
148
169
-#### Examples
149
171
-##### Basic
150
+#### via UI
151
+
152
+The **httpcheck** collector can be configured directly through the Netdata web interface:
153
+
154
+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.
156
+3. The **Collectors → Jobs** view opens by default.
157
+4. In the Search box, type _httpcheck_ (or scroll the list) to locate the **httpcheck** collector.
158
+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**.
160
+
161
+
162
+#### via File
163
+
164
+The configuration file name for this integration is `go.d/httpcheck.conf`.
165
+
166
+The file format is YAML. Generally, the structure is:
167
+
168
+```yaml
169
+update_every: 1
170
+autodetection_retry: 0
171
+jobs:
172
+ - name: some_name1
173
+ - name: some_name1
174
+```
175
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
176
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
177
+
178
+```bash
179
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
180
+sudo ./edit-config go.d/httpcheck.conf
181
+```
182
+
183
+##### Examples
184
+
185
+###### Basic
186
187
A basic example configuration.
188
@@ -182,7 +196,7 @@ jobs:
196
```
197
</details>
198
185
-##### With HTTP request headers
199
+###### With HTTP request headers
200
201
Configuration with HTTP request headers that will be sent by the client.
202
@@ -200,7 +214,7 @@ jobs:
214
```
215
</details>
216
203
-##### With `status_accepted`
217
+###### With `status_accepted`
218
219
A basic example configuration with non-default status_accepted.
220
@@ -217,7 +231,7 @@ jobs:
231
```
232
</details>
233
220
-##### With `header_match`
234
+###### With `header_match`
235
236
Example configurations with `header_match`. See the value [pattern](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#supported-format) syntax.
237
@@ -264,7 +278,7 @@ jobs:
278
```
279
</details>
280
267
-##### HTTP authentication
281
+###### HTTP authentication
282
283
Basic HTTP authentication.
284
@@ -280,7 +294,7 @@ jobs:
294
```
295
</details>
296
283
-##### HTTPS with self-signed certificate
297
+###### HTTPS with self-signed certificate
298
299
Do not validate server certificate chain and hostname.
300
@@ -296,7 +310,7 @@ jobs:
310
```
311
</details>
312
299
-##### Multi-instance
313
+###### Multi-instance
314
315
> **Note**: When you define multiple jobs, their names must be unique.
316
src/go/plugin/go.d/collector/icecast/integrations/icecast.md
+37
-23
@@ -87,26 +87,6 @@ Needs at least Icecast version >= 2.4.0
87
88
### Configuration
89
90
-#### File
91
-
92
-The configuration file name for this integration is `go.d/icecast.conf`.
93
-
94
-The file format is YAML. Generally, the structure is:
95
-
96
-```yaml
97
-update_every: 1
98
-autodetection_retry: 0
99
-jobs:
100
- - name: some_name1
101
- - name: some_name1
102
-```
103
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
-
106
-```bash
107
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
108
-sudo ./edit-config go.d/icecast.conf
109
-```
90
#### Options
91
92
The following options can be defined globally: update_every, autodetection_retry.
@@ -136,9 +116,43 @@ The following options can be defined globally: update_every, autodetection_retry
116
117
</details>
118
139
-#### Examples
119
141
-##### Basic
120
+#### via UI
121
+
122
+The **icecast** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _icecast_ (or scroll the list) to locate the **icecast** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `go.d/icecast.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+jobs:
142
+ - name: some_name1
143
+ - name: some_name1
144
+```
145
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
146
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+
148
+```bash
149
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
+sudo ./edit-config go.d/icecast.conf
151
+```
152
+
153
+##### Examples
154
+
155
+###### Basic
156
157
A basic example configuration.
158
@@ -148,7 +162,7 @@ jobs:
162
url: http://127.0.0.1:8000
163
164
```
151
-##### Multi-instance
165
+###### Multi-instance
166
167
> **Note**: When you define multiple jobs, their names must be unique.
168
src/go/plugin/go.d/collector/intelgpu/integrations/intel_gpu.md
+30
-16
@@ -105,7 +105,34 @@ Install `intel-gpu-tools` using your distribution's package manager.
105
106
### Configuration
107
108
-#### File
108
+#### Options
109
+
110
+The following options can be defined globally: update_every.
111
+
112
+
113
+<details open><summary>Config options</summary>
114
+
115
+| Name | Description | Default | Required |
116
+|:----|:-----------|:-------|:--------:|
117
+| update_every | Data collection frequency. | 1 | no |
118
+| device | Select a specific GPU using [supported filter](https://manpages.debian.org/testing/intel-gpu-tools/intel_gpu_top.1.en.html#DESCRIPTION). | | no |
119
+
120
+</details>
121
+
122
+
123
+#### via UI
124
+
125
+The **intelgpu** collector can be configured directly through the Netdata web interface:
126
+
127
+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.
129
+3. The **Collectors → Jobs** view opens by default.
130
+4. In the Search box, type _intelgpu_ (or scroll the list) to locate the **intelgpu** collector.
131
+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**.
133
+
134
+
135
+#### via File
136
137
The configuration file name for this integration is `go.d/intelgpu.conf`.
138
@@ -125,23 +152,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
152
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
153
sudo ./edit-config go.d/intelgpu.conf
154
```
128
-#### Options
129
-
130
-The following options can be defined globally: update_every.
131
-
132
-
133
-<details open><summary>Config options</summary>
134
-
135
-| Name | Description | Default | Required |
136
-|:----|:-----------|:-------|:--------:|
137
-| update_every | Data collection frequency. | 1 | no |
138
-| device | Select a specific GPU using [supported filter](https://manpages.debian.org/testing/intel-gpu-tools/intel_gpu_top.1.en.html#DESCRIPTION). | | no |
139
-
140
-</details>
155
142
-#### Examples
156
+##### Examples
157
144
-##### Custom update_every
158
+###### Custom update_every
159
160
Allows you to override the default data collection interval.
161
src/go/plugin/go.d/collector/ipfs/integrations/ipfs.md
+37
-23
@@ -105,26 +105,6 @@ No action required.
105
106
### Configuration
107
108
-#### File
109
-
110
-The configuration file name for this integration is `go.d/ipfs.conf`.
111
-
112
-The file format is YAML. Generally, the structure is:
113
-
114
-```yaml
115
-update_every: 1
116
-autodetection_retry: 0
117
-jobs:
118
- - name: some_name1
119
- - name: some_name1
120
-```
121
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
122
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
123
-
124
-```bash
125
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
126
-sudo ./edit-config go.d/ipfs.conf
127
-```
108
#### Options
109
110
The following options can be defined globally: update_every, autodetection_retry.
@@ -156,9 +136,43 @@ The following options can be defined globally: update_every, autodetection_retry
136
137
</details>
138
159
-#### Examples
139
161
-##### Basic
140
+#### via UI
141
+
142
+The **ipfs** collector can be configured directly through the Netdata web interface:
143
+
144
+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.
146
+3. The **Collectors → Jobs** view opens by default.
147
+4. In the Search box, type _ipfs_ (or scroll the list) to locate the **ipfs** collector.
148
+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**.
150
+
151
+
152
+#### via File
153
+
154
+The configuration file name for this integration is `go.d/ipfs.conf`.
155
+
156
+The file format is YAML. Generally, the structure is:
157
+
158
+```yaml
159
+update_every: 1
160
+autodetection_retry: 0
161
+jobs:
162
+ - name: some_name1
163
+ - name: some_name1
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).
167
+
168
+```bash
169
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
170
+sudo ./edit-config go.d/ipfs.conf
171
+```
172
+
173
+##### Examples
174
+
175
+###### Basic
176
177
A basic example configuration.
178
@@ -168,7 +182,7 @@ jobs:
182
url: http://127.0.0.1:5001
183
184
```
171
-##### Multi-instance
185
+###### Multi-instance
186
187
> **Note**: When you define multiple jobs, their names must be unique.
188
src/go/plugin/go.d/collector/isc_dhcpd/integrations/isc_dhcp.md
+36
-22
@@ -101,26 +101,6 @@ No action required.
101
102
### Configuration
103
104
-#### File
105
-
106
-The configuration file name for this integration is `go.d/isc_dhcpd.conf`.
107
-
108
-The file format is YAML. Generally, the structure is:
109
-
110
-```yaml
111
-update_every: 1
112
-autodetection_retry: 0
113
-jobs:
114
- - name: some_name1
115
- - name: some_name1
116
-```
117
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
118
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
-
120
-```bash
121
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
122
-sudo ./edit-config go.d/isc_dhcpd.conf
123
-```
104
#### Options
105
106
The following options can be defined globally: update_every, autodetection_retry.
@@ -153,9 +133,43 @@ pools:
133
134
</details>
135
156
-#### Examples
136
158
-##### Basic
137
+#### via UI
138
+
139
+The **isc_dhcpd** collector can be configured directly through the Netdata web interface:
140
+
141
+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.
143
+3. The **Collectors → Jobs** view opens by default.
144
+4. In the Search box, type _isc_dhcpd_ (or scroll the list) to locate the **isc_dhcpd** collector.
145
+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**.
147
+
148
+
149
+#### via File
150
+
151
+The configuration file name for this integration is `go.d/isc_dhcpd.conf`.
152
+
153
+The file format is YAML. Generally, the structure is:
154
+
155
+```yaml
156
+update_every: 1
157
+autodetection_retry: 0
158
+jobs:
159
+ - name: some_name1
160
+ - name: some_name1
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).
164
+
165
+```bash
166
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
167
+sudo ./edit-config go.d/isc_dhcpd.conf
168
+```
169
+
170
+##### Examples
171
+
172
+###### Basic
173
174
A basic example configuration.
175
src/go/plugin/go.d/collector/k8s_kubelet/integrations/kubelet.md
+37
-23
@@ -119,26 +119,6 @@ No action required.
119
120
### Configuration
121
122
-#### File
123
-
124
-The configuration file name for this integration is `go.d/k8s_kubelet.conf`.
125
-
126
-The file format is YAML. Generally, the structure is:
127
-
128
-```yaml
129
-update_every: 1
130
-autodetection_retry: 0
131
-jobs:
132
- - name: some_name1
133
- - name: some_name1
134
-```
135
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
136
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
137
-
138
-```bash
139
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
140
-sudo ./edit-config go.d/k8s_kubelet.conf
141
-```
122
#### Options
123
124
The following options can be defined globally: update_every, autodetection_retry.
@@ -168,9 +148,43 @@ The following options can be defined globally: update_every, autodetection_retry
148
149
</details>
150
171
-#### Examples
151
173
-##### Basic
152
+#### via UI
153
+
154
+The **k8s_kubelet** collector can be configured directly through the Netdata web interface:
155
+
156
+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.
158
+3. The **Collectors → Jobs** view opens by default.
159
+4. In the Search box, type _k8s_kubelet_ (or scroll the list) to locate the **k8s_kubelet** collector.
160
+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**.
162
+
163
+
164
+#### via File
165
+
166
+The configuration file name for this integration is `go.d/k8s_kubelet.conf`.
167
+
168
+The file format is YAML. Generally, the structure is:
169
+
170
+```yaml
171
+update_every: 1
172
+autodetection_retry: 0
173
+jobs:
174
+ - name: some_name1
175
+ - name: some_name1
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).
179
+
180
+```bash
181
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
182
+sudo ./edit-config go.d/k8s_kubelet.conf
183
+```
184
+
185
+##### Examples
186
+
187
+###### Basic
188
189
A basic example configuration.
190
@@ -180,7 +194,7 @@ jobs:
194
url: http://127.0.0.1:10255/metrics
195
196
```
183
-##### HTTPS with self-signed certificate
197
+###### HTTPS with self-signed certificate
198
199
Do not validate server certificate chain and hostname.
200
src/go/plugin/go.d/collector/k8s_kubeproxy/integrations/kubeproxy.md
+37
-23
@@ -86,26 +86,6 @@ No action required.
86
87
### Configuration
88
89
-#### File
90
-
91
-The configuration file name for this integration is `go.d/k8s_kubeproxy.conf`.
92
-
93
-The file format is YAML. Generally, the structure is:
94
-
95
-```yaml
96
-update_every: 1
97
-autodetection_retry: 0
98
-jobs:
99
- - name: some_name1
100
- - name: some_name1
101
-```
102
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
-
105
-```bash
106
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
107
-sudo ./edit-config go.d/k8s_kubeproxy.conf
108
-```
89
#### Options
90
91
The following options can be defined globally: update_every, autodetection_retry.
@@ -135,9 +115,43 @@ The following options can be defined globally: update_every, autodetection_retry
115
116
</details>
117
138
-#### Examples
118
140
-##### Basic
119
+#### via UI
120
+
121
+The **k8s_kubeproxy** collector can be configured directly through the Netdata web interface:
122
+
123
+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.
125
+3. The **Collectors → Jobs** view opens by default.
126
+4. In the Search box, type _k8s_kubeproxy_ (or scroll the list) to locate the **k8s_kubeproxy** collector.
127
+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**.
129
+
130
+
131
+#### via File
132
+
133
+The configuration file name for this integration is `go.d/k8s_kubeproxy.conf`.
134
+
135
+The file format is YAML. Generally, the structure is:
136
+
137
+```yaml
138
+update_every: 1
139
+autodetection_retry: 0
140
+jobs:
141
+ - name: some_name1
142
+ - name: some_name1
143
+```
144
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
145
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
146
+
147
+```bash
148
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
149
+sudo ./edit-config go.d/k8s_kubeproxy.conf
150
+```
151
+
152
+##### Examples
153
+
154
+###### Basic
155
156
A basic example configuration.
157
@@ -147,7 +161,7 @@ jobs:
161
url: http://127.0.0.1:10249/metrics
162
163
```
150
-##### HTTPS with self-signed certificate
164
+###### HTTPS with self-signed certificate
165
166
Do not validate server certificate chain and hostname.
167
src/go/plugin/go.d/collector/k8s_state/integrations/kubernetes_cluster_state.md
+21
-7
@@ -220,7 +220,26 @@ No action required.
220
221
### Configuration
222
223
-#### File
223
+#### Options
224
+
225
+
226
+
227
+There are no configuration options.
228
+
229
+
230
+#### via UI
231
+
232
+The **k8s_state** collector can be configured directly through the Netdata web interface:
233
+
234
+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.
236
+3. The **Collectors → Jobs** view opens by default.
237
+4. In the Search box, type _k8s_state_ (or scroll the list) to locate the **k8s_state** collector.
238
+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**.
240
+
241
+
242
+#### via File
243
244
The configuration file name for this integration is `go.d/k8s_state.conf`.
245
@@ -240,13 +259,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
259
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
260
sudo ./edit-config go.d/k8s_state.conf
261
```
243
-#### Options
244
-
245
-
246
-
247
-There are no configuration options.
262
249
-#### Examples
263
+##### Examples
264
There are no configuration examples.
265
266
src/go/plugin/go.d/collector/lighttpd/integrations/lighttpd.md
+39
-25
@@ -96,26 +96,6 @@ To enable status support, see the [official documentation](https://redmine.light
96
97
### Configuration
98
99
-#### File
100
-
101
-The configuration file name for this integration is `go.d/lighttpd.conf`.
102
-
103
-The file format is YAML. Generally, the structure is:
104
-
105
-```yaml
106
-update_every: 1
107
-autodetection_retry: 0
108
-jobs:
109
- - name: some_name1
110
- - name: some_name1
111
-```
112
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
113
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
-
115
-```bash
116
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
117
-sudo ./edit-config go.d/lighttpd.conf
118
-```
99
#### Options
100
101
The following options can be defined globally: update_every, autodetection_retry.
@@ -145,9 +125,43 @@ The following options can be defined globally: update_every, autodetection_retry
125
126
</details>
127
148
-#### Examples
128
150
-##### Basic
129
+#### via UI
130
+
131
+The **lighttpd** collector can be configured directly through the Netdata web interface:
132
+
133
+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.
135
+3. The **Collectors → Jobs** view opens by default.
136
+4. In the Search box, type _lighttpd_ (or scroll the list) to locate the **lighttpd** collector.
137
+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**.
139
+
140
+
141
+#### via File
142
+
143
+The configuration file name for this integration is `go.d/lighttpd.conf`.
144
+
145
+The file format is YAML. Generally, the structure is:
146
+
147
+```yaml
148
+update_every: 1
149
+autodetection_retry: 0
150
+jobs:
151
+ - name: some_name1
152
+ - name: some_name1
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).
156
+
157
+```bash
158
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
159
+sudo ./edit-config go.d/lighttpd.conf
160
+```
161
+
162
+##### Examples
163
+
164
+###### Basic
165
166
A basic example configuration.
167
@@ -157,7 +171,7 @@ jobs:
171
url: http://127.0.0.1/server-status?auto
172
173
```
160
-##### HTTP authentication
174
+###### HTTP authentication
175
176
Basic HTTP authentication.
177
@@ -173,7 +187,7 @@ jobs:
187
```
188
</details>
189
176
-##### HTTPS with self-signed certificate
190
+###### HTTPS with self-signed certificate
191
192
Lighttpd with enabled HTTPS and self-signed certificate.
193
@@ -188,7 +202,7 @@ jobs:
202
```
203
</details>
204
191
-##### Multi-instance
205
+###### Multi-instance
206
207
> **Note**: When you define multiple jobs, their names must be unique.
208
src/go/plugin/go.d/collector/litespeed/integrations/litespeed.md
+31
-17
@@ -91,7 +91,35 @@ No action required.
91
92
### Configuration
93
94
-#### File
94
+#### Options
95
+
96
+The following options can be defined globally: update_every, autodetection_retry.
97
+
98
+
99
+<details open><summary>Config options</summary>
100
+
101
+| Name | Description | Default | Required |
102
+|:----|:-----------|:-------|:--------:|
103
+| update_every | Data collection frequency. | 10 | no |
104
+| autodetection_retry | Sets the job re-check interval in seconds. | 0 | no |
105
+| reports_dir | Directory containing Litespeed's real-time statistics files. | /tmp/lshttpd/ | no |
106
+
107
+</details>
108
+
109
+
110
+#### via UI
111
+
112
+The **litespeed** collector can be configured directly through the Netdata web interface:
113
+
114
+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.
116
+3. The **Collectors → Jobs** view opens by default.
117
+4. In the Search box, type _litespeed_ (or scroll the list) to locate the **litespeed** collector.
118
+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**.
120
+
121
+
122
+#### via File
123
124
The configuration file name for this integration is `go.d/litespeed.conf`.
125
@@ -111,24 +139,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
139
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
140
sudo ./edit-config go.d/litespeed.conf
141
```
114
-#### Options
115
-
116
-The following options can be defined globally: update_every, autodetection_retry.
117
-
118
-
119
-<details open><summary>Config options</summary>
120
-
121
-| Name | Description | Default | Required |
122
-|:----|:-----------|:-------|:--------:|
123
-| update_every | Data collection frequency. | 10 | no |
124
-| autodetection_retry | Sets the job re-check interval in seconds. | 0 | no |
125
-| reports_dir | Directory containing Litespeed's real-time statistics files. | /tmp/lshttpd/ | no |
126
-
127
-</details>
142
129
-#### Examples
143
+##### Examples
144
131
-##### Set the path to statistics
145
+###### Set the path to statistics
146
147
Change the path for the litespeed stats files
148
src/go/plugin/go.d/collector/logind/integrations/systemd-logind_users.md
+20
-6
@@ -86,7 +86,25 @@ No action required.
86
87
### Configuration
88
89
-#### File
89
+#### Options
90
+
91
+The following options can be defined globally: update_every, autodetection_retry.
92
+
93
+
94
+
95
+#### via UI
96
+
97
+The **logind** collector can be configured directly through the Netdata web interface:
98
+
99
+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.
101
+3. The **Collectors → Jobs** view opens by default.
102
+4. In the Search box, type _logind_ (or scroll the list) to locate the **logind** collector.
103
+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**.
105
+
106
+
107
+#### via File
108
109
The configuration file name for this integration is `go.d/logind.conf`.
110
@@ -106,12 +124,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
124
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
125
sudo ./edit-config go.d/logind.conf
126
```
109
-#### Options
110
-
111
-The following options can be defined globally: update_every, autodetection_retry.
112
-
127
114
-#### Examples
128
+##### Examples
129
There are no configuration examples.
130
131
src/go/plugin/go.d/collector/logstash/integrations/logstash.md
+39
-25
@@ -109,26 +109,6 @@ No action required.
109
110
### Configuration
111
112
-#### File
113
-
114
-The configuration file name for this integration is `go.d/logstatsh.conf`.
115
-
116
-The file format is YAML. Generally, the structure is:
117
-
118
-```yaml
119
-update_every: 1
120
-autodetection_retry: 0
121
-jobs:
122
- - name: some_name1
123
- - name: some_name1
124
-```
125
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
126
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
127
-
128
-```bash
129
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
130
-sudo ./edit-config go.d/logstatsh.conf
131
-```
112
#### Options
113
114
The following options can be defined globally: update_every, autodetection_retry.
@@ -158,9 +138,43 @@ The following options can be defined globally: update_every, autodetection_retry
138
139
</details>
140
161
-#### Examples
141
163
-##### Basic
142
+#### via UI
143
+
144
+The **logstash** collector can be configured directly through the Netdata web interface:
145
+
146
+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.
148
+3. The **Collectors → Jobs** view opens by default.
149
+4. In the Search box, type _logstash_ (or scroll the list) to locate the **logstash** collector.
150
+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**.
152
+
153
+
154
+#### via File
155
+
156
+The configuration file name for this integration is `go.d/logstatsh.conf`.
157
+
158
+The file format is YAML. Generally, the structure is:
159
+
160
+```yaml
161
+update_every: 1
162
+autodetection_retry: 0
163
+jobs:
164
+ - name: some_name1
165
+ - name: some_name1
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).
169
+
170
+```bash
171
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
172
+sudo ./edit-config go.d/logstatsh.conf
173
+```
174
+
175
+##### Examples
176
+
177
+###### Basic
178
179
A basic example configuration.
180
@@ -174,7 +188,7 @@ jobs:
188
```
189
</details>
190
177
-##### HTTP authentication
191
+###### HTTP authentication
192
193
HTTP authentication.
194
@@ -190,7 +204,7 @@ jobs:
204
```
205
</details>
206
193
-##### HTTPS with self-signed certificate
207
+###### HTTPS with self-signed certificate
208
209
HTTPS and self-signed certificate.
210
@@ -205,7 +219,7 @@ jobs:
219
```
220
</details>
221
208
-##### Multi-instance
222
+###### Multi-instance
223
224
> **Note**: When you define multiple jobs, their names must be unique.
225
src/go/plugin/go.d/collector/lvm/integrations/lvm_logical_volumes.md
+30
-16
@@ -97,7 +97,34 @@ No action required.
97
98
### Configuration
99
100
-#### File
100
+#### Options
101
+
102
+The following options can be defined globally: update_every.
103
+
104
+
105
+<details open><summary>Config options</summary>
106
+
107
+| Name | Description | Default | Required |
108
+|:----|:-----------|:-------|:--------:|
109
+| update_every | Data collection frequency. | 10 | no |
110
+| timeout | lvs binary execution timeout. | 2 | no |
111
+
112
+</details>
113
+
114
+
115
+#### via UI
116
+
117
+The **lvm** collector can be configured directly through the Netdata web interface:
118
+
119
+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.
121
+3. The **Collectors → Jobs** view opens by default.
122
+4. In the Search box, type _lvm_ (or scroll the list) to locate the **lvm** collector.
123
+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**.
125
+
126
+
127
+#### via File
128
129
The configuration file name for this integration is `go.d/lvm.conf`.
130
@@ -117,23 +144,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
144
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
145
sudo ./edit-config go.d/lvm.conf
146
```
120
-#### Options
121
-
122
-The following options can be defined globally: update_every.
123
-
124
-
125
-<details open><summary>Config options</summary>
126
-
127
-| Name | Description | Default | Required |
128
-|:----|:-----------|:-------|:--------:|
129
-| update_every | Data collection frequency. | 10 | no |
130
-| timeout | lvs binary execution timeout. | 2 | no |
131
-
132
-</details>
147
134
-#### Examples
148
+##### Examples
149
136
-##### Custom update_every
150
+###### Custom update_every
151
152
Allows you to override the default data collection interval.
153
src/go/plugin/go.d/collector/maxscale/integrations/maxscale.md
+38
-24
@@ -114,26 +114,6 @@ No action required.
114
115
### Configuration
116
117
-#### File
118
-
119
-The configuration file name for this integration is `go.d/maxscale.conf`.
120
-
121
-The file format is YAML. Generally, the structure is:
122
-
123
-```yaml
124
-update_every: 1
125
-autodetection_retry: 0
126
-jobs:
127
- - name: some_name1
128
- - name: some_name1
129
-```
130
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
131
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
132
-
133
-```bash
134
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
135
-sudo ./edit-config go.d/maxscale.conf
136
-```
117
#### Options
118
119
The following options can be defined globally: update_every, autodetection_retry.
@@ -163,9 +143,43 @@ The following options can be defined globally: update_every, autodetection_retry
143
144
</details>
145
166
-#### Examples
146
168
-##### Basic
147
+#### via UI
148
+
149
+The **maxscale** collector can be configured directly through the Netdata web interface:
150
+
151
+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.
153
+3. The **Collectors → Jobs** view opens by default.
154
+4. In the Search box, type _maxscale_ (or scroll the list) to locate the **maxscale** collector.
155
+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**.
157
+
158
+
159
+#### via File
160
+
161
+The configuration file name for this integration is `go.d/maxscale.conf`.
162
+
163
+The file format is YAML. Generally, the structure is:
164
+
165
+```yaml
166
+update_every: 1
167
+autodetection_retry: 0
168
+jobs:
169
+ - name: some_name1
170
+ - name: some_name1
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).
174
+
175
+```bash
176
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
177
+sudo ./edit-config go.d/maxscale.conf
178
+```
179
+
180
+##### Examples
181
+
182
+###### Basic
183
184
A basic example configuration.
185
@@ -177,7 +191,7 @@ jobs:
191
password: mariadb
192
193
```
180
-##### HTTPS with self-signed certificate
194
+###### HTTPS with self-signed certificate
195
196
MaxScale with enabled HTTPS and self-signed certificate.
197
@@ -194,7 +208,7 @@ jobs:
208
```
209
</details>
210
197
-##### Multi-instance
211
+###### Multi-instance
212
213
> **Note**: When you define multiple jobs, their names must be unique.
214
src/go/plugin/go.d/collector/megacli/integrations/megacli_megaraid.md
+30
-16
@@ -145,7 +145,34 @@ No action required.
145
146
### Configuration
147
148
-#### File
148
+#### Options
149
+
150
+The following options can be defined globally: update_every.
151
+
152
+
153
+<details open><summary>Config options</summary>
154
+
155
+| Name | Description | Default | Required |
156
+|:----|:-----------|:-------|:--------:|
157
+| update_every | Data collection frequency. | 10 | no |
158
+| timeout | megacli binary execution timeout. | 2 | no |
159
+
160
+</details>
161
+
162
+
163
+#### via UI
164
+
165
+The **megacli** collector can be configured directly through the Netdata web interface:
166
+
167
+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.
169
+3. The **Collectors → Jobs** view opens by default.
170
+4. In the Search box, type _megacli_ (or scroll the list) to locate the **megacli** collector.
171
+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**.
173
+
174
+
175
+#### via File
176
177
The configuration file name for this integration is `go.d/megacli.conf`.
178
@@ -165,23 +192,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
192
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
193
sudo ./edit-config go.d/megacli.conf
194
```
168
-#### Options
169
-
170
-The following options can be defined globally: update_every.
171
-
172
-
173
-<details open><summary>Config options</summary>
174
-
175
-| Name | Description | Default | Required |
176
-|:----|:-----------|:-------|:--------:|
177
-| update_every | Data collection frequency. | 10 | no |
178
-| timeout | megacli binary execution timeout. | 2 | no |
179
-
180
-</details>
195
182
-#### Examples
196
+##### Examples
197
184
-##### Custom update_every
198
+###### Custom update_every
199
200
Allows you to override the default data collection interval.
201
src/go/plugin/go.d/collector/memcached/integrations/memcached.md
+33
-19
@@ -114,7 +114,36 @@ has permission to access it. You can do this by:
114
115
### Configuration
116
117
-#### File
117
+#### Options
118
+
119
+The following options can be defined globally: update_every, autodetection_retry.
120
+
121
+
122
+<details open><summary>Config options</summary>
123
+
124
+| Name | Description | Default | Required |
125
+|:----|:-----------|:-------|:--------:|
126
+| update_every | Data collection frequency. | 1 | no |
127
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
128
+| address | The IP address and port where the memcached service listens for connections. | 127.0.0.1:11211 | yes |
129
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
130
+
131
+</details>
132
+
133
+
134
+#### via UI
135
+
136
+The **memcached** collector can be configured directly through the Netdata web interface:
137
+
138
+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.
140
+3. The **Collectors → Jobs** view opens by default.
141
+4. In the Search box, type _memcached_ (or scroll the list) to locate the **memcached** collector.
142
+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**.
144
+
145
+
146
+#### via File
147
148
The configuration file name for this integration is `go.d/memcached.conf`.
149
@@ -134,25 +163,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
163
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
164
sudo ./edit-config go.d/memcached.conf
165
```
137
-#### Options
138
-
139
-The following options can be defined globally: update_every, autodetection_retry.
140
-
141
-
142
-<details open><summary>Config options</summary>
143
-
144
-| Name | Description | Default | Required |
145
-|:----|:-----------|:-------|:--------:|
146
-| update_every | Data collection frequency. | 1 | no |
147
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
148
-| address | The IP address and port where the memcached service listens for connections. | 127.0.0.1:11211 | yes |
149
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
150
-
151
-</details>
166
153
-#### Examples
167
+##### Examples
168
155
-##### Basic
169
+###### Basic
170
171
A basic example configuration.
172
@@ -166,7 +180,7 @@ jobs:
180
```
181
</details>
182
169
-##### Multi-instance
183
+###### Multi-instance
184
185
> **Note**: When you define multiple jobs, their names must be unique.
186
src/go/plugin/go.d/collector/mongodb/integrations/mongodb.md
+35
-21
@@ -243,7 +243,37 @@ Create a read-only user for Netdata in the admin database.
243
244
### Configuration
245
246
-#### File
246
+#### Options
247
+
248
+The following options can be defined globally: update_every, autodetection_retry.
249
+
250
+
251
+<details open><summary>Config options</summary>
252
+
253
+| Name | Description | Default | Required |
254
+|:----|:-----------|:-------|:--------:|
255
+| update_every | Data collection frequency. | 5 | no |
256
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
257
+| uri | MongoDB connection string. See [URI syntax](https://www.mongodb.com/docs/manual/reference/connection-string/). | mongodb://localhost:27017 | yes |
258
+| timeout | Query timeout in seconds. | 1 | no |
259
+| databases | Databases selector. Determines which database metrics will be collected. | | no |
260
+
261
+</details>
262
+
263
+
264
+#### via UI
265
+
266
+The **mongodb** collector can be configured directly through the Netdata web interface:
267
+
268
+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.
270
+3. The **Collectors → Jobs** view opens by default.
271
+4. In the Search box, type _mongodb_ (or scroll the list) to locate the **mongodb** collector.
272
+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**.
274
+
275
+
276
+#### via File
277
278
The configuration file name for this integration is `go.d/mongodb.conf`.
279
@@ -263,26 +293,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
293
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
294
sudo ./edit-config go.d/mongodb.conf
295
```
266
-#### Options
267
-
268
-The following options can be defined globally: update_every, autodetection_retry.
269
-
270
-
271
-<details open><summary>Config options</summary>
272
-
273
-| Name | Description | Default | Required |
274
-|:----|:-----------|:-------|:--------:|
275
-| update_every | Data collection frequency. | 5 | no |
276
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
277
-| uri | MongoDB connection string. See [URI syntax](https://www.mongodb.com/docs/manual/reference/connection-string/). | mongodb://localhost:27017 | yes |
278
-| timeout | Query timeout in seconds. | 1 | no |
279
-| databases | Databases selector. Determines which database metrics will be collected. | | no |
280
-
281
-</details>
296
283
-#### Examples
297
+##### Examples
298
285
-##### TCP socket
299
+###### TCP socket
300
301
An example configuration.
302
@@ -296,7 +310,7 @@ jobs:
310
```
311
</details>
312
299
-##### With databases metrics
313
+###### With databases metrics
314
315
An example configuration.
316
@@ -313,7 +327,7 @@ jobs:
327
```
328
</details>
329
316
-##### Multi-instance
330
+###### Multi-instance
331
332
> **Note**: When you define multiple jobs, their names must be unique.
333
src/go/plugin/go.d/collector/monit/integrations/monit.md
+38
-24
@@ -95,26 +95,6 @@ See [Syntax for TCP port](https://mmonit.com/monit/documentation/monit.html#TCP-
95
96
### Configuration
97
98
-#### File
99
-
100
-The configuration file name for this integration is `go.d/monit.conf`.
101
-
102
-The file format is YAML. Generally, the structure is:
103
-
104
-```yaml
105
-update_every: 1
106
-autodetection_retry: 0
107
-jobs:
108
- - name: some_name1
109
- - name: some_name1
110
-```
111
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
112
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
-
114
-```bash
115
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
116
-sudo ./edit-config go.d/monit.conf
117
-```
98
#### Options
99
100
The following options can be defined globally: update_every, autodetection_retry.
@@ -144,9 +124,43 @@ The following options can be defined globally: update_every, autodetection_retry
124
125
</details>
126
147
-#### Examples
127
149
-##### HTTP authentication
128
+#### via UI
129
+
130
+The **monit** collector can be configured directly through the Netdata web interface:
131
+
132
+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.
134
+3. The **Collectors → Jobs** view opens by default.
135
+4. In the Search box, type _monit_ (or scroll the list) to locate the **monit** collector.
136
+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**.
138
+
139
+
140
+#### via File
141
+
142
+The configuration file name for this integration is `go.d/monit.conf`.
143
+
144
+The file format is YAML. Generally, the structure is:
145
+
146
+```yaml
147
+update_every: 1
148
+autodetection_retry: 0
149
+jobs:
150
+ - name: some_name1
151
+ - name: some_name1
152
+```
153
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
154
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
155
+
156
+```bash
157
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
158
+sudo ./edit-config go.d/monit.conf
159
+```
160
+
161
+##### Examples
162
+
163
+###### HTTP authentication
164
165
Basic HTTP authentication.
166
@@ -162,7 +176,7 @@ jobs:
176
```
177
</details>
178
165
-##### HTTPS with self-signed certificate
179
+###### HTTPS with self-signed certificate
180
181
With enabled HTTPS and self-signed certificate.
182
@@ -177,7 +191,7 @@ jobs:
191
```
192
</details>
193
180
-##### Multi-instance
194
+###### Multi-instance
195
196
> **Note**: When you define multiple jobs, their names must be unique.
197
src/go/plugin/go.d/collector/mysql/integrations/mariadb.md
+37
-23
@@ -239,7 +239,37 @@ It will only be able to gather statistics without being able to alter or affect
239
240
### Configuration
241
242
-#### File
242
+#### Options
243
+
244
+The following options can be defined globally: update_every, autodetection_retry.
245
+
246
+
247
+<details open><summary>Config options</summary>
248
+
249
+| Name | Description | Default | Required |
250
+|:----|:-----------|:-------|:--------:|
251
+| update_every | Data collection frequency. | 5 | no |
252
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
253
+| dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
254
+| my.cnf | Specifies the my.cnf file to read the connection settings from the [client] section. | | no |
255
+| timeout | Query timeout in seconds. | 1 | no |
256
+
257
+</details>
258
+
259
+
260
+#### via UI
261
+
262
+The **mysql** collector can be configured directly through the Netdata web interface:
263
+
264
+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.
266
+3. The **Collectors → Jobs** view opens by default.
267
+4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
268
+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**.
270
+
271
+
272
+#### via File
273
274
The configuration file name for this integration is `go.d/mysql.conf`.
275
@@ -259,26 +289,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
289
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
290
sudo ./edit-config go.d/mysql.conf
291
```
262
-#### Options
263
-
264
-The following options can be defined globally: update_every, autodetection_retry.
265
-
266
-
267
-<details open><summary>Config options</summary>
268
-
269
-| Name | Description | Default | Required |
270
-|:----|:-----------|:-------|:--------:|
271
-| update_every | Data collection frequency. | 5 | no |
272
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
273
-| dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
274
-| my.cnf | Specifies the my.cnf file to read the connection settings from the [client] section. | | no |
275
-| timeout | Query timeout in seconds. | 1 | no |
276
-
277
-</details>
292
279
-#### Examples
293
+##### Examples
294
281
-##### TCP socket
295
+###### TCP socket
296
297
An example configuration.
298
@@ -292,7 +306,7 @@ jobs:
306
```
307
</details>
308
295
-##### Unix socket
309
+###### Unix socket
310
311
An example configuration.
312
@@ -306,7 +320,7 @@ jobs:
320
```
321
</details>
322
309
-##### Connection with password
323
+###### Connection with password
324
325
An example configuration.
326
@@ -320,7 +334,7 @@ jobs:
334
```
335
</details>
336
323
-##### my.cnf
337
+###### my.cnf
338
339
An example configuration.
340
@@ -334,7 +348,7 @@ jobs:
348
```
349
</details>
350
337
-##### Multi-instance
351
+###### Multi-instance
352
353
> **Note**: When you define multiple jobs, their names must be unique.
354
src/go/plugin/go.d/collector/mysql/integrations/mysql.md
+37
-23
@@ -239,7 +239,37 @@ It will only be able to gather statistics without being able to alter or affect
239
240
### Configuration
241
242
-#### File
242
+#### Options
243
+
244
+The following options can be defined globally: update_every, autodetection_retry.
245
+
246
+
247
+<details open><summary>Config options</summary>
248
+
249
+| Name | Description | Default | Required |
250
+|:----|:-----------|:-------|:--------:|
251
+| update_every | Data collection frequency. | 5 | no |
252
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
253
+| dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
254
+| my.cnf | Specifies the my.cnf file to read the connection settings from the [client] section. | | no |
255
+| timeout | Query timeout in seconds. | 1 | no |
256
+
257
+</details>
258
+
259
+
260
+#### via UI
261
+
262
+The **mysql** collector can be configured directly through the Netdata web interface:
263
+
264
+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.
266
+3. The **Collectors → Jobs** view opens by default.
267
+4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
268
+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**.
270
+
271
+
272
+#### via File
273
274
The configuration file name for this integration is `go.d/mysql.conf`.
275
@@ -259,26 +289,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
289
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
290
sudo ./edit-config go.d/mysql.conf
291
```
262
-#### Options
263
-
264
-The following options can be defined globally: update_every, autodetection_retry.
265
-
266
-
267
-<details open><summary>Config options</summary>
268
-
269
-| Name | Description | Default | Required |
270
-|:----|:-----------|:-------|:--------:|
271
-| update_every | Data collection frequency. | 5 | no |
272
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
273
-| dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
274
-| my.cnf | Specifies the my.cnf file to read the connection settings from the [client] section. | | no |
275
-| timeout | Query timeout in seconds. | 1 | no |
276
-
277
-</details>
292
279
-#### Examples
293
+##### Examples
294
281
-##### TCP socket
295
+###### TCP socket
296
297
An example configuration.
298
@@ -292,7 +306,7 @@ jobs:
306
```
307
</details>
308
295
-##### Unix socket
309
+###### Unix socket
310
311
An example configuration.
312
@@ -306,7 +320,7 @@ jobs:
320
```
321
</details>
322
309
-##### Connection with password
323
+###### Connection with password
324
325
An example configuration.
326
@@ -320,7 +334,7 @@ jobs:
334
```
335
</details>
336
323
-##### my.cnf
337
+###### my.cnf
338
339
An example configuration.
340
@@ -334,7 +348,7 @@ jobs:
348
```
349
</details>
350
337
-##### Multi-instance
351
+###### Multi-instance
352
353
> **Note**: When you define multiple jobs, their names must be unique.
354
src/go/plugin/go.d/collector/mysql/integrations/percona_mysql.md
+37
-23
@@ -239,7 +239,37 @@ It will only be able to gather statistics without being able to alter or affect
239
240
### Configuration
241
242
-#### File
242
+#### Options
243
+
244
+The following options can be defined globally: update_every, autodetection_retry.
245
+
246
+
247
+<details open><summary>Config options</summary>
248
+
249
+| Name | Description | Default | Required |
250
+|:----|:-----------|:-------|:--------:|
251
+| update_every | Data collection frequency. | 5 | no |
252
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
253
+| dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
254
+| my.cnf | Specifies the my.cnf file to read the connection settings from the [client] section. | | no |
255
+| timeout | Query timeout in seconds. | 1 | no |
256
+
257
+</details>
258
+
259
+
260
+#### via UI
261
+
262
+The **mysql** collector can be configured directly through the Netdata web interface:
263
+
264
+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.
266
+3. The **Collectors → Jobs** view opens by default.
267
+4. In the Search box, type _mysql_ (or scroll the list) to locate the **mysql** collector.
268
+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**.
270
+
271
+
272
+#### via File
273
274
The configuration file name for this integration is `go.d/mysql.conf`.
275
@@ -259,26 +289,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
289
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
290
sudo ./edit-config go.d/mysql.conf
291
```
262
-#### Options
263
-
264
-The following options can be defined globally: update_every, autodetection_retry.
265
-
266
-
267
-<details open><summary>Config options</summary>
268
-
269
-| Name | Description | Default | Required |
270
-|:----|:-----------|:-------|:--------:|
271
-| update_every | Data collection frequency. | 5 | no |
272
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
273
-| dsn | MySQL server DSN (Data Source Name). See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | root@tcp(localhost:3306)/ | yes |
274
-| my.cnf | Specifies the my.cnf file to read the connection settings from the [client] section. | | no |
275
-| timeout | Query timeout in seconds. | 1 | no |
276
-
277
-</details>
292
279
-#### Examples
293
+##### Examples
294
281
-##### TCP socket
295
+###### TCP socket
296
297
An example configuration.
298
@@ -292,7 +306,7 @@ jobs:
306
```
307
</details>
308
295
-##### Unix socket
309
+###### Unix socket
310
311
An example configuration.
312
@@ -306,7 +320,7 @@ jobs:
320
```
321
</details>
322
309
-##### Connection with password
323
+###### Connection with password
324
325
An example configuration.
326
@@ -320,7 +334,7 @@ jobs:
334
```
335
</details>
336
323
-##### my.cnf
337
+###### my.cnf
338
339
An example configuration.
340
@@ -334,7 +348,7 @@ jobs:
348
```
349
</details>
350
337
-##### Multi-instance
351
+###### Multi-instance
352
353
> **Note**: When you define multiple jobs, their names must be unique.
354
src/go/plugin/go.d/collector/nats/integrations/nats.md
+39
-25
@@ -251,26 +251,6 @@ See [Enable monitoring](https://docs.nats.io/running-a-nats-service/nats_admin/m
251
252
### Configuration
253
254
-#### File
255
-
256
-The configuration file name for this integration is `go.d/nats.conf`.
257
-
258
-The file format is YAML. Generally, the structure is:
259
-
260
-```yaml
261
-update_every: 1
262
-autodetection_retry: 0
263
-jobs:
264
- - name: some_name1
265
- - name: some_name1
266
-```
267
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
268
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
269
-
270
-```bash
271
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
272
-sudo ./edit-config go.d/nats.conf
273
-```
254
#### Options
255
256
The following options can be defined globally: update_every, autodetection_retry.
@@ -301,9 +281,43 @@ The following options can be defined globally: update_every, autodetection_retry
281
282
</details>
283
304
-#### Examples
284
306
-##### Basic
285
+#### via UI
286
+
287
+The **nats** collector can be configured directly through the Netdata web interface:
288
+
289
+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.
291
+3. The **Collectors → Jobs** view opens by default.
292
+4. In the Search box, type _nats_ (or scroll the list) to locate the **nats** collector.
293
+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**.
295
+
296
+
297
+#### via File
298
+
299
+The configuration file name for this integration is `go.d/nats.conf`.
300
+
301
+The file format is YAML. Generally, the structure is:
302
+
303
+```yaml
304
+update_every: 1
305
+autodetection_retry: 0
306
+jobs:
307
+ - name: some_name1
308
+ - name: some_name1
309
+```
310
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
311
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
312
+
313
+```bash
314
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
315
+sudo ./edit-config go.d/nats.conf
316
+```
317
+
318
+##### Examples
319
+
320
+###### Basic
321
322
A basic example configuration.
323
@@ -313,7 +327,7 @@ jobs:
327
url: http://127.0.0.1:8222
328
329
```
316
-##### HTTP authentication
330
+###### HTTP authentication
331
332
Basic HTTP authentication.
333
@@ -329,7 +343,7 @@ jobs:
343
```
344
</details>
345
332
-##### HTTPS with self-signed certificate
346
+###### HTTPS with self-signed certificate
347
348
NATS with enabled HTTPS and self-signed certificate.
349
@@ -344,7 +358,7 @@ jobs:
358
```
359
</details>
360
347
-##### Multi-instance
361
+###### Multi-instance
362
363
> **Note**: When you define multiple jobs, their names must be unique.
364
src/go/plugin/go.d/collector/nginx/integrations/nginx.md
+39
-25
@@ -135,26 +135,6 @@ Configure [ngx_http_stub_status_module](https://nginx.org/en/docs/http/ngx_http_
135
136
### Configuration
137
138
-#### File
139
-
140
-The configuration file name for this integration is `go.d/nginx.conf`.
141
-
142
-The file format is YAML. Generally, the structure is:
143
-
144
-```yaml
145
-update_every: 1
146
-autodetection_retry: 0
147
-jobs:
148
- - name: some_name1
149
- - name: some_name1
150
-```
151
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
152
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
153
-
154
-```bash
155
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
156
-sudo ./edit-config go.d/nginx.conf
157
-```
138
#### Options
139
140
The following options can be defined globally: update_every, autodetection_retry.
@@ -184,9 +164,43 @@ The following options can be defined globally: update_every, autodetection_retry
164
165
</details>
166
187
-#### Examples
167
189
-##### Basic
168
+#### via UI
169
+
170
+The **nginx** collector can be configured directly through the Netdata web interface:
171
+
172
+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.
174
+3. The **Collectors → Jobs** view opens by default.
175
+4. In the Search box, type _nginx_ (or scroll the list) to locate the **nginx** collector.
176
+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**.
178
+
179
+
180
+#### via File
181
+
182
+The configuration file name for this integration is `go.d/nginx.conf`.
183
+
184
+The file format is YAML. Generally, the structure is:
185
+
186
+```yaml
187
+update_every: 1
188
+autodetection_retry: 0
189
+jobs:
190
+ - name: some_name1
191
+ - name: some_name1
192
+```
193
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
194
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
195
+
196
+```bash
197
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
198
+sudo ./edit-config go.d/nginx.conf
199
+```
200
+
201
+##### Examples
202
+
203
+###### Basic
204
205
A basic example configuration.
206
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1/stub_status
211
212
```
199
-##### HTTP authentication
213
+###### HTTP authentication
214
215
Basic HTTP authentication.
216
@@ -212,7 +226,7 @@ jobs:
226
```
227
</details>
228
215
-##### HTTPS with self-signed certificate
229
+###### HTTPS with self-signed certificate
230
231
NGINX with enabled HTTPS and self-signed certificate.
232
@@ -227,7 +241,7 @@ jobs:
241
```
242
</details>
243
230
-##### Multi-instance
244
+###### Multi-instance
245
246
> **Note**: When you define multiple jobs, their names must be unique.
247
src/go/plugin/go.d/collector/nginxplus/integrations/nginx_plus.md
+39
-25
@@ -274,26 +274,6 @@ To configure API, see the [official documentation](https://docs.nginx.com/nginx/
274
275
### Configuration
276
277
-#### File
278
-
279
-The configuration file name for this integration is `go.d/nginxplus.conf`.
280
-
281
-The file format is YAML. Generally, the structure is:
282
-
283
-```yaml
284
-update_every: 1
285
-autodetection_retry: 0
286
-jobs:
287
- - name: some_name1
288
- - name: some_name1
289
-```
290
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
291
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
292
-
293
-```bash
294
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
295
-sudo ./edit-config go.d/nginxplus.conf
296
-```
277
#### Options
278
279
The following options can be defined globally: update_every, autodetection_retry.
@@ -323,9 +303,43 @@ The following options can be defined globally: update_every, autodetection_retry
303
304
</details>
305
326
-#### Examples
306
328
-##### Basic
307
+#### via UI
308
+
309
+The **nginxplus** collector can be configured directly through the Netdata web interface:
310
+
311
+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.
313
+3. The **Collectors → Jobs** view opens by default.
314
+4. In the Search box, type _nginxplus_ (or scroll the list) to locate the **nginxplus** collector.
315
+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**.
317
+
318
+
319
+#### via File
320
+
321
+The configuration file name for this integration is `go.d/nginxplus.conf`.
322
+
323
+The file format is YAML. Generally, the structure is:
324
+
325
+```yaml
326
+update_every: 1
327
+autodetection_retry: 0
328
+jobs:
329
+ - name: some_name1
330
+ - name: some_name1
331
+```
332
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
333
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
334
+
335
+```bash
336
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
337
+sudo ./edit-config go.d/nginxplus.conf
338
+```
339
+
340
+##### Examples
341
+
342
+###### Basic
343
344
A basic example configuration.
345
@@ -339,7 +353,7 @@ jobs:
353
```
354
</details>
355
342
-##### HTTP authentication
356
+###### HTTP authentication
357
358
Basic HTTP authentication.
359
@@ -355,7 +369,7 @@ jobs:
369
```
370
</details>
371
358
-##### HTTPS with self-signed certificate
372
+###### HTTPS with self-signed certificate
373
374
NGINX Plus with enabled HTTPS and self-signed certificate.
375
@@ -370,7 +384,7 @@ jobs:
384
```
385
</details>
386
373
-##### Multi-instance
387
+###### Multi-instance
388
389
> **Note**: When you define multiple jobs, their names must be unique.
390
src/go/plugin/go.d/collector/nginxunit/integrations/nginx_unit.md
+39
-25
@@ -92,26 +92,6 @@ See [Control API](https://unit.nginx.org/controlapi/#configuration-api) document
92
93
### Configuration
94
95
-#### File
96
-
97
-The configuration file name for this integration is `go.d/nginxunit.conf`.
98
-
99
-The file format is YAML. Generally, the structure is:
100
-
101
-```yaml
102
-update_every: 1
103
-autodetection_retry: 0
104
-jobs:
105
- - name: some_name1
106
- - name: some_name1
107
-```
108
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
109
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
-
111
-```bash
112
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
113
-sudo ./edit-config go.d/nginxunit.conf
114
-```
95
#### Options
96
97
The following options can be defined globally: update_every, autodetection_retry.
@@ -141,9 +121,43 @@ The following options can be defined globally: update_every, autodetection_retry
121
122
</details>
123
144
-#### Examples
124
146
-##### Basic
125
+#### via UI
126
+
127
+The **nginxunit** collector can be configured directly through the Netdata web interface:
128
+
129
+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.
131
+3. The **Collectors → Jobs** view opens by default.
132
+4. In the Search box, type _nginxunit_ (or scroll the list) to locate the **nginxunit** collector.
133
+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**.
135
+
136
+
137
+#### via File
138
+
139
+The configuration file name for this integration is `go.d/nginxunit.conf`.
140
+
141
+The file format is YAML. Generally, the structure is:
142
+
143
+```yaml
144
+update_every: 1
145
+autodetection_retry: 0
146
+jobs:
147
+ - name: some_name1
148
+ - name: some_name1
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).
152
+
153
+```bash
154
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
155
+sudo ./edit-config go.d/nginxunit.conf
156
+```
157
+
158
+##### Examples
159
+
160
+###### Basic
161
162
A basic example configuration.
163
@@ -153,7 +167,7 @@ jobs:
167
url: http://127.0.0.1:8000
168
169
```
156
-##### HTTP authentication
170
+###### HTTP authentication
171
172
Basic HTTP authentication.
173
@@ -169,7 +183,7 @@ jobs:
183
```
184
</details>
185
172
-##### HTTPS with self-signed certificate
186
+###### HTTPS with self-signed certificate
187
188
NGINX Unit with enabled HTTPS and self-signed certificate.
189
@@ -184,7 +198,7 @@ jobs:
198
```
199
</details>
200
187
-##### Multi-instance
201
+###### Multi-instance
202
203
> **Note**: When you define multiple jobs, their names must be unique.
204
src/go/plugin/go.d/collector/nginxvts/integrations/nginx_vts.md
+39
-25
@@ -97,26 +97,6 @@ To configure nginx-vts, see the [https://github.com/vozlt/nginx-module-vts#insta
97
98
### Configuration
99
100
-#### File
101
-
102
-The configuration file name for this integration is `go.d/nginxvts.conf`.
103
-
104
-The file format is YAML. Generally, the structure is:
105
-
106
-```yaml
107
-update_every: 1
108
-autodetection_retry: 0
109
-jobs:
110
- - name: some_name1
111
- - name: some_name1
112
-```
113
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
-
116
-```bash
117
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
118
-sudo ./edit-config go.d/nginxvts.conf
119
-```
100
#### Options
101
102
The following options can be defined globally: update_every, autodetection_retry.
@@ -146,9 +126,43 @@ The following options can be defined globally: update_every, autodetection_retry
126
127
</details>
128
149
-#### Examples
129
151
-##### Basic
130
+#### via UI
131
+
132
+The **nginxvts** collector can be configured directly through the Netdata web interface:
133
+
134
+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.
136
+3. The **Collectors → Jobs** view opens by default.
137
+4. In the Search box, type _nginxvts_ (or scroll the list) to locate the **nginxvts** collector.
138
+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**.
140
+
141
+
142
+#### via File
143
+
144
+The configuration file name for this integration is `go.d/nginxvts.conf`.
145
+
146
+The file format is YAML. Generally, the structure is:
147
+
148
+```yaml
149
+update_every: 1
150
+autodetection_retry: 0
151
+jobs:
152
+ - name: some_name1
153
+ - name: some_name1
154
+```
155
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
156
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
157
+
158
+```bash
159
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
160
+sudo ./edit-config go.d/nginxvts.conf
161
+```
162
+
163
+##### Examples
164
+
165
+###### Basic
166
167
A basic example configuration.
168
@@ -158,7 +172,7 @@ jobs:
172
url: http://127.0.0.1/status/format/json
173
174
```
161
-##### HTTP authentication
175
+###### HTTP authentication
176
177
Basic HTTP authentication.
178
@@ -174,7 +188,7 @@ jobs:
188
```
189
</details>
190
177
-##### HTTPS with self-signed certificate
191
+###### HTTPS with self-signed certificate
192
193
Do not validate server certificate chain and hostname.
194
@@ -190,7 +204,7 @@ jobs:
204
```
205
</details>
206
193
-##### Multi-instance
207
+###### Multi-instance
208
209
> **Note**: When you define multiple jobs, their names must be unique.
210
src/go/plugin/go.d/collector/nsd/integrations/nsd.md
+30
-16
@@ -99,7 +99,34 @@ No action required.
99
100
### Configuration
101
102
-#### File
102
+#### Options
103
+
104
+The following options can be defined globally: update_every.
105
+
106
+
107
+<details open><summary>Config options</summary>
108
+
109
+| Name | Description | Default | Required |
110
+|:----|:-----------|:-------|:--------:|
111
+| update_every | Data collection frequency. | 10 | no |
112
+| timeout | nsd-control binary execution timeout. | 2 | no |
113
+
114
+</details>
115
+
116
+
117
+#### via UI
118
+
119
+The **nsd** collector can be configured directly through the Netdata web interface:
120
+
121
+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.
123
+3. The **Collectors → Jobs** view opens by default.
124
+4. In the Search box, type _nsd_ (or scroll the list) to locate the **nsd** collector.
125
+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**.
127
+
128
+
129
+#### via File
130
131
The configuration file name for this integration is `go.d/nsd.conf`.
132
@@ -119,23 +146,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
146
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
147
sudo ./edit-config go.d/nsd.conf
148
```
122
-#### Options
123
-
124
-The following options can be defined globally: update_every.
125
-
126
-
127
-<details open><summary>Config options</summary>
128
-
129
-| Name | Description | Default | Required |
130
-|:----|:-----------|:-------|:--------:|
131
-| update_every | Data collection frequency. | 10 | no |
132
-| timeout | nsd-control binary execution timeout. | 2 | no |
133
-
134
-</details>
149
136
-#### Examples
150
+##### Examples
151
138
-##### Custom update_every
152
+###### Custom update_every
153
154
Allows you to override the default data collection interval.
155
src/go/plugin/go.d/collector/ntpd/integrations/ntpd.md
+35
-21
@@ -117,7 +117,37 @@ No action required.
117
118
### Configuration
119
120
-#### File
120
+#### Options
121
+
122
+The following options can be defined globally: update_every, autodetection_retry.
123
+
124
+
125
+<details open><summary>Config options</summary>
126
+
127
+| Name | Description | Default | Required |
128
+|:----|:-----------|:-------|:--------:|
129
+| update_every | Data collection frequency. | 1 | no |
130
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
131
+| address | Server address in IP:PORT format. | 127.0.0.1:123 | yes |
132
+| timeout | Connection/read/write timeout. | 1 | no |
133
+| collect_peers | Determines whether peer metrics will be collected. | no | no |
134
+
135
+</details>
136
+
137
+
138
+#### via UI
139
+
140
+The **ntpd** collector can be configured directly through the Netdata web interface:
141
+
142
+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.
144
+3. The **Collectors → Jobs** view opens by default.
145
+4. In the Search box, type _ntpd_ (or scroll the list) to locate the **ntpd** collector.
146
+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**.
148
+
149
+
150
+#### via File
151
152
The configuration file name for this integration is `go.d/ntpd.conf`.
153
@@ -137,26 +167,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
167
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
168
sudo ./edit-config go.d/ntpd.conf
169
```
140
-#### Options
141
-
142
-The following options can be defined globally: update_every, autodetection_retry.
143
-
144
-
145
-<details open><summary>Config options</summary>
146
-
147
-| Name | Description | Default | Required |
148
-|:----|:-----------|:-------|:--------:|
149
-| update_every | Data collection frequency. | 1 | no |
150
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
151
-| address | Server address in IP:PORT format. | 127.0.0.1:123 | yes |
152
-| timeout | Connection/read/write timeout. | 1 | no |
153
-| collect_peers | Determines whether peer metrics will be collected. | no | no |
154
-
155
-</details>
170
157
-#### Examples
171
+##### Examples
172
159
-##### Basic
173
+###### Basic
174
175
A basic example configuration.
176
@@ -170,7 +184,7 @@ jobs:
184
```
185
</details>
186
173
-##### With peers metrics
187
+###### With peers metrics
188
189
Collect peers metrics.
190
@@ -185,7 +199,7 @@ jobs:
199
```
200
</details>
201
188
-##### Multi-instance
202
+###### Multi-instance
203
204
> **Note**: When you define multiple jobs, their names must be unique.
205
src/go/plugin/go.d/collector/nvidia_smi/integrations/nvidia_gpu.md
+33
-19
@@ -122,7 +122,37 @@ No action required.
122
123
### Configuration
124
125
-#### File
125
+#### Options
126
+
127
+The following options can be defined globally: update_every, autodetection_retry.
128
+
129
+
130
+<details open><summary>Config options</summary>
131
+
132
+| Name | Description | Default | Required |
133
+|:----|:-----------|:-------|:--------:|
134
+| update_every | Data collection frequency. | 10 | no |
135
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
136
+| binary_path | Path to nvidia_smi binary. The default is "nvidia_smi" and the executable is looked for in the directories specified in the PATH environment variable. | nvidia_smi | no |
137
+| timeout | The maximum duration, in seconds, to wait for an `nvidia-smi` command to complete. This setting applies differently based on the collector's mode. **Loop Mode:** In loop mode, the timeout primarily determines how long to wait for the initial `nvidia-smi` execution. If the initial query takes longer than the timeout, the collector may report an error. For systems with multiple GPUs, the initial load time can sometimes be significant (e.g., 5-10 seconds). **Regular Mode:** If the collector is in regular mode, the timeout specifies how long to wait for each individual `nvidia-smi` execution. | 10 | no |
138
+| loop_mode | When enabled, `nvidia-smi` is executed continuously in a separate thread using the `-l` option. | yes | no |
139
+
140
+</details>
141
+
142
+
143
+#### via UI
144
+
145
+The **nvidia_smi** collector can be configured directly through the Netdata web interface:
146
+
147
+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.
149
+3. The **Collectors → Jobs** view opens by default.
150
+4. In the Search box, type _nvidia_smi_ (or scroll the list) to locate the **nvidia_smi** collector.
151
+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**.
153
+
154
+
155
+#### via File
156
157
The configuration file name for this integration is `go.d/nvidia_smi.conf`.
158
@@ -142,26 +172,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
172
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
173
sudo ./edit-config go.d/nvidia_smi.conf
174
```
145
-#### Options
146
-
147
-The following options can be defined globally: update_every, autodetection_retry.
148
-
149
-
150
-<details open><summary>Config options</summary>
151
-
152
-| Name | Description | Default | Required |
153
-|:----|:-----------|:-------|:--------:|
154
-| update_every | Data collection frequency. | 10 | no |
155
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
156
-| binary_path | Path to nvidia_smi binary. The default is "nvidia_smi" and the executable is looked for in the directories specified in the PATH environment variable. | nvidia_smi | no |
157
-| timeout | The maximum duration, in seconds, to wait for an `nvidia-smi` command to complete. This setting applies differently based on the collector's mode. **Loop Mode:** In loop mode, the timeout primarily determines how long to wait for the initial `nvidia-smi` execution. If the initial query takes longer than the timeout, the collector may report an error. For systems with multiple GPUs, the initial load time can sometimes be significant (e.g., 5-10 seconds). **Regular Mode:** If the collector is in regular mode, the timeout specifies how long to wait for each individual `nvidia-smi` execution. | 10 | no |
158
-| loop_mode | When enabled, `nvidia-smi` is executed continuously in a separate thread using the `-l` option. | yes | no |
159
-
160
-</details>
175
162
-#### Examples
176
+##### Examples
177
164
-##### Custom binary path
178
+###### Custom binary path
179
180
The executable is not in the directories specified in the PATH environment variable.
181
src/go/plugin/go.d/collector/nvme/integrations/nvme_devices.md
+31
-17
@@ -137,7 +137,35 @@ Include the following option in your `docker run` command or add the device mapp
137
138
### Configuration
139
140
-#### File
140
+#### Options
141
+
142
+The following options can be defined globally: update_every, autodetection_retry.
143
+
144
+
145
+<details open><summary>Config options</summary>
146
+
147
+| Name | Description | Default | Required |
148
+|:----|:-----------|:-------|:--------:|
149
+| update_every | Data collection frequency. | 10 | no |
150
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
151
+| timeout | nvme binary execution timeout. | 2 | no |
152
+
153
+</details>
154
+
155
+
156
+#### via UI
157
+
158
+The **nvme** collector can be configured directly through the Netdata web interface:
159
+
160
+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.
162
+3. The **Collectors → Jobs** view opens by default.
163
+4. In the Search box, type _nvme_ (or scroll the list) to locate the **nvme** collector.
164
+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**.
166
+
167
+
168
+#### via File
169
170
The configuration file name for this integration is `go.d/nvme.conf`.
171
@@ -157,24 +185,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
185
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
186
sudo ./edit-config go.d/nvme.conf
187
```
160
-#### Options
161
-
162
-The following options can be defined globally: update_every, autodetection_retry.
163
-
164
-
165
-<details open><summary>Config options</summary>
166
-
167
-| Name | Description | Default | Required |
168
-|:----|:-----------|:-------|:--------:|
169
-| update_every | Data collection frequency. | 10 | no |
170
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
171
-| timeout | nvme binary execution timeout. | 2 | no |
172
-
173
-</details>
188
175
-#### Examples
189
+##### Examples
190
177
-##### Custom update_every
191
+###### Custom update_every
192
193
Allows you to override the default data collection interval.
194
src/go/plugin/go.d/collector/openldap/integrations/openldap.md
+37
-23
@@ -95,26 +95,6 @@ Follow instructions from https://www.openldap.org/doc/admin24/monitoringslapd.ht
95
96
### Configuration
97
98
-#### File
99
-
100
-The configuration file name for this integration is `go.d/openldap.conf`.
101
-
102
-The file format is YAML. Generally, the structure is:
103
-
104
-```yaml
105
-update_every: 1
106
-autodetection_retry: 0
107
-jobs:
108
- - name: some_name1
109
- - name: some_name1
110
-```
111
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
112
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
-
114
-```bash
115
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
116
-sudo ./edit-config go.d/openldap.conf
117
-```
98
#### Options
99
100
The following options can be defined globally: update_every.
@@ -136,9 +116,43 @@ The following options can be defined globally: update_every.
116
117
</details>
118
139
-#### Examples
119
141
-##### Basic
120
+#### via UI
121
+
122
+The **openldap** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _openldap_ (or scroll the list) to locate the **openldap** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `go.d/openldap.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+jobs:
142
+ - name: some_name1
143
+ - name: some_name1
144
+```
145
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
146
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+
148
+```bash
149
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
+sudo ./edit-config go.d/openldap.conf
151
+```
152
+
153
+##### Examples
154
+
155
+###### Basic
156
157
A basic example configuration.
158
@@ -150,7 +164,7 @@ jobs:
164
password: secret
165
166
```
153
-##### Multi-instance
167
+###### Multi-instance
168
169
> **Note**: When you define multiple jobs, their names must be unique.
170
src/go/plugin/go.d/collector/openvpn/integrations/openvpn.md
+35
-21
@@ -110,7 +110,37 @@ It is disabled to not break other tools which use `Management Interface`.
110
111
### Configuration
112
113
-#### File
113
+#### Options
114
+
115
+The following options can be defined globally: update_every, autodetection_retry.
116
+
117
+
118
+<details open><summary>Config options</summary>
119
+
120
+| Name | Description | Default | Required |
121
+|:----|:-----------|:-------|:--------:|
122
+| update_every | Data collection frequency. | 1 | no |
123
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
124
+| address | Server address in IP:PORT format. | 127.0.0.1:7505 | yes |
125
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
126
+| per_user_stats | User selector. Determines which user metrics will be collected. | | no |
127
+
128
+</details>
129
+
130
+
131
+#### via UI
132
+
133
+The **openvpn** collector can be configured directly through the Netdata web interface:
134
+
135
+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.
137
+3. The **Collectors → Jobs** view opens by default.
138
+4. In the Search box, type _openvpn_ (or scroll the list) to locate the **openvpn** collector.
139
+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**.
141
+
142
+
143
+#### via File
144
145
The configuration file name for this integration is `go.d/openvpn.conf`.
146
@@ -130,26 +160,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
160
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
161
sudo ./edit-config go.d/openvpn.conf
162
```
133
-#### Options
134
-
135
-The following options can be defined globally: update_every, autodetection_retry.
136
-
137
-
138
-<details open><summary>Config options</summary>
139
-
140
-| Name | Description | Default | Required |
141
-|:----|:-----------|:-------|:--------:|
142
-| update_every | Data collection frequency. | 1 | no |
143
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
144
-| address | Server address in IP:PORT format. | 127.0.0.1:7505 | yes |
145
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
146
-| per_user_stats | User selector. Determines which user metrics will be collected. | | no |
147
-
148
-</details>
163
150
-#### Examples
164
+##### Examples
165
152
-##### Basic
166
+###### Basic
167
168
A basic example configuration.
169
@@ -163,7 +177,7 @@ jobs:
177
```
178
</details>
179
166
-##### With user metrics
180
+###### With user metrics
181
182
Collect metrics of all users.
183
@@ -180,7 +194,7 @@ jobs:
194
```
195
</details>
196
183
-##### Multi-instance
197
+###### Multi-instance
198
199
> **Note**: When you define multiple jobs, their names must be unique.
200
src/go/plugin/go.d/collector/openvpn_status_log/integrations/openvpn_status_log.md
+32
-18
@@ -101,7 +101,36 @@ No action required.
101
102
### Configuration
103
104
-#### File
104
+#### Options
105
+
106
+The following options can be defined globally: update_every, autodetection_retry.
107
+
108
+
109
+<details open><summary>Config options</summary>
110
+
111
+| Name | Description | Default | Required |
112
+|:----|:-----------|:-------|:--------:|
113
+| update_every | Data collection frequency. | 1 | no |
114
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
115
+| log_path | Path to status log. | /var/log/openvpn/status.log | yes |
116
+| per_user_stats | User selector. Determines which user metrics will be collected. | | no |
117
+
118
+</details>
119
+
120
+
121
+#### via UI
122
+
123
+The **openvpn_status_log** collector can be configured directly through the Netdata web interface:
124
+
125
+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.
127
+3. The **Collectors → Jobs** view opens by default.
128
+4. In the Search box, type _openvpn_status_log_ (or scroll the list) to locate the **openvpn_status_log** collector.
129
+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**.
131
+
132
+
133
+#### via File
134
135
The configuration file name for this integration is `go.d/openvpn_status_log.conf`.
136
@@ -121,25 +150,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
150
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
sudo ./edit-config go.d/openvpn_status_log.conf
152
```
124
-#### Options
125
-
126
-The following options can be defined globally: update_every, autodetection_retry.
127
-
128
-
129
-<details open><summary>Config options</summary>
130
-
131
-| Name | Description | Default | Required |
132
-|:----|:-----------|:-------|:--------:|
133
-| update_every | Data collection frequency. | 1 | no |
134
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
135
-| log_path | Path to status log. | /var/log/openvpn/status.log | yes |
136
-| per_user_stats | User selector. Determines which user metrics will be collected. | | no |
137
-
138
-</details>
153
140
-#### Examples
154
+##### Examples
155
142
-##### With user metrics
156
+###### With user metrics
157
158
Collect metrics of all users.
159
src/go/plugin/go.d/collector/oracledb/integrations/oracle_db.md
+34
-20
@@ -160,7 +160,36 @@ GRANT SELECT_CATALOG_ROLE TO netdata;
160
161
### Configuration
162
163
-#### File
163
+#### Options
164
+
165
+The following options can be defined globally: update_every, autodetection_retry.
166
+
167
+
168
+<details open><summary>Config options</summary>
169
+
170
+| Name | Description | Default | Required |
171
+|:----|:-----------|:-------|:--------:|
172
+| update_every | Data collection frequency. | 1 | no |
173
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
174
+| dsn | Oracle server DSN (Data Source Name). Format is `oracle://username:password@host:port/service?param1=value1&...¶mN=valueN`. | | yes |
175
+| timeout | Query timeout in seconds. | 1 | no |
176
+
177
+</details>
178
+
179
+
180
+#### via UI
181
+
182
+The **oracledb** collector can be configured directly through the Netdata web interface:
183
+
184
+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.
186
+3. The **Collectors → Jobs** view opens by default.
187
+4. In the Search box, type _oracledb_ (or scroll the list) to locate the **oracledb** collector.
188
+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**.
190
+
191
+
192
+#### via File
193
194
The configuration file name for this integration is `go.d/oracledb.conf`.
195
@@ -180,25 +209,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
209
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
210
sudo ./edit-config go.d/oracledb.conf
211
```
183
-#### Options
184
-
185
-The following options can be defined globally: update_every, autodetection_retry.
186
-
187
-
188
-<details open><summary>Config options</summary>
189
-
190
-| Name | Description | Default | Required |
191
-|:----|:-----------|:-------|:--------:|
192
-| update_every | Data collection frequency. | 1 | no |
193
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
194
-| dsn | Oracle server DSN (Data Source Name). Format is `oracle://username:password@host:port/service?param1=value1&...¶mN=valueN`. | | yes |
195
-| timeout | Query timeout in seconds. | 1 | no |
196
-
197
-</details>
212
199
-#### Examples
213
+##### Examples
214
201
-##### TCP socket
215
+###### TCP socket
216
217
An example configuration.
218
@@ -212,7 +226,7 @@ jobs:
226
```
227
</details>
228
215
-##### TLS connection (TCPS)
229
+###### TLS connection (TCPS)
230
231
An example configuration for TLS connection.
232
@@ -226,7 +240,7 @@ jobs:
240
```
241
</details>
242
229
-##### Multi-instance
243
+###### Multi-instance
244
245
> **Note**: When you define multiple jobs, their names must be unique.
246
src/go/plugin/go.d/collector/pgbouncer/integrations/pgbouncer.md
+34
-20
@@ -145,7 +145,36 @@ To create the `netdata` user:
145
146
### Configuration
147
148
-#### File
148
+#### Options
149
+
150
+The following options can be defined globally: update_every, autodetection_retry.
151
+
152
+
153
+<details open><summary>Config options</summary>
154
+
155
+| Name | Description | Default | Required |
156
+|:----|:-----------|:-------|:--------:|
157
+| update_every | Data collection frequency. | 5 | no |
158
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
159
+| dsn | PgBouncer server DSN (Data Source Name). See [DSN syntax](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). | postgres://postgres:postgres@127.0.0.1:6432/pgbouncer | yes |
160
+| timeout | Query timeout in seconds. | 1 | no |
161
+
162
+</details>
163
+
164
+
165
+#### via UI
166
+
167
+The **pgbouncer** collector can be configured directly through the Netdata web interface:
168
+
169
+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.
171
+3. The **Collectors → Jobs** view opens by default.
172
+4. In the Search box, type _pgbouncer_ (or scroll the list) to locate the **pgbouncer** collector.
173
+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**.
175
+
176
+
177
+#### via File
178
179
The configuration file name for this integration is `go.d/pgbouncer.conf`.
180
@@ -165,25 +194,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
194
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
sudo ./edit-config go.d/pgbouncer.conf
196
```
168
-#### Options
169
-
170
-The following options can be defined globally: update_every, autodetection_retry.
171
-
172
-
173
-<details open><summary>Config options</summary>
174
-
175
-| Name | Description | Default | Required |
176
-|:----|:-----------|:-------|:--------:|
177
-| update_every | Data collection frequency. | 5 | no |
178
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
179
-| dsn | PgBouncer server DSN (Data Source Name). See [DSN syntax](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). | postgres://postgres:postgres@127.0.0.1:6432/pgbouncer | yes |
180
-| timeout | Query timeout in seconds. | 1 | no |
181
-
182
-</details>
197
184
-#### Examples
198
+##### Examples
199
186
-##### TCP socket
200
+###### TCP socket
201
202
An example configuration.
203
@@ -197,7 +211,7 @@ jobs:
211
```
212
</details>
213
200
-##### Unix socket
214
+###### Unix socket
215
216
An example configuration.
217
@@ -211,7 +225,7 @@ jobs:
225
```
226
</details>
227
214
-##### Multi-instance
228
+###### Multi-instance
229
230
> **Note**: When you define multiple jobs, their names must be unique.
231
src/go/plugin/go.d/collector/phpdaemon/integrations/phpdaemon.md
+39
-25
@@ -159,26 +159,6 @@ class FullStatusRequest extends Generic {
159
160
### Configuration
161
162
-#### File
163
-
164
-The configuration file name for this integration is `go.d/phpdaemon.conf`.
165
-
166
-The file format is YAML. Generally, the structure is:
167
-
168
-```yaml
169
-update_every: 1
170
-autodetection_retry: 0
171
-jobs:
172
- - name: some_name1
173
- - name: some_name1
174
-```
175
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
176
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
177
-
178
-```bash
179
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
180
-sudo ./edit-config go.d/phpdaemon.conf
181
-```
162
#### Options
163
164
The following options can be defined globally: update_every, autodetection_retry.
@@ -208,9 +188,43 @@ The following options can be defined globally: update_every, autodetection_retry
188
189
</details>
190
211
-#### Examples
191
213
-##### Basic
192
+#### via UI
193
+
194
+The **phpdaemon** collector can be configured directly through the Netdata web interface:
195
+
196
+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.
198
+3. The **Collectors → Jobs** view opens by default.
199
+4. In the Search box, type _phpdaemon_ (or scroll the list) to locate the **phpdaemon** collector.
200
+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**.
202
+
203
+
204
+#### via File
205
+
206
+The configuration file name for this integration is `go.d/phpdaemon.conf`.
207
+
208
+The file format is YAML. Generally, the structure is:
209
+
210
+```yaml
211
+update_every: 1
212
+autodetection_retry: 0
213
+jobs:
214
+ - name: some_name1
215
+ - name: some_name1
216
+```
217
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
218
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
219
+
220
+```bash
221
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
222
+sudo ./edit-config go.d/phpdaemon.conf
223
+```
224
+
225
+##### Examples
226
+
227
+###### Basic
228
229
A basic example configuration.
230
@@ -224,7 +238,7 @@ jobs:
238
```
239
</details>
240
227
-##### HTTP authentication
241
+###### HTTP authentication
242
243
HTTP authentication.
244
@@ -240,7 +254,7 @@ jobs:
254
```
255
</details>
256
243
-##### HTTPS with self-signed certificate
257
+###### HTTPS with self-signed certificate
258
259
HTTPS with self-signed certificate.
260
@@ -255,7 +269,7 @@ jobs:
269
```
270
</details>
271
258
-##### Multi-instance
272
+###### Multi-instance
273
274
> **Note**: When you define multiple jobs, their names must be unique.
275
src/go/plugin/go.d/collector/phpfpm/integrations/php-fpm.md
+39
-25
@@ -90,26 +90,6 @@ Uncomment the `pm.status_path = /status` variable in the `php-fpm` config file.
90
91
### Configuration
92
93
-#### File
94
-
95
-The configuration file name for this integration is `go.d/phpfpm.conf`.
96
-
97
-The file format is YAML. Generally, the structure is:
98
-
99
-```yaml
100
-update_every: 1
101
-autodetection_retry: 0
102
-jobs:
103
- - name: some_name1
104
- - name: some_name1
105
-```
106
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
-
109
-```bash
110
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
-sudo ./edit-config go.d/phpfpm.conf
112
-```
93
#### Options
94
95
The following options can be defined globally: update_every, autodetection_retry.
@@ -142,9 +122,43 @@ The following options can be defined globally: update_every, autodetection_retry
122
123
</details>
124
145
-#### Examples
125
147
-##### HTTP
126
+#### via UI
127
+
128
+The **phpfpm** collector can be configured directly through the Netdata web interface:
129
+
130
+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.
132
+3. The **Collectors → Jobs** view opens by default.
133
+4. In the Search box, type _phpfpm_ (or scroll the list) to locate the **phpfpm** collector.
134
+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**.
136
+
137
+
138
+#### via File
139
+
140
+The configuration file name for this integration is `go.d/phpfpm.conf`.
141
+
142
+The file format is YAML. Generally, the structure is:
143
+
144
+```yaml
145
+update_every: 1
146
+autodetection_retry: 0
147
+jobs:
148
+ - name: some_name1
149
+ - name: some_name1
150
+```
151
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
152
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
153
+
154
+```bash
155
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
156
+sudo ./edit-config go.d/phpfpm.conf
157
+```
158
+
159
+##### Examples
160
+
161
+###### HTTP
162
163
Collecting data from a local instance over HTTP.
164
@@ -158,7 +172,7 @@ jobs:
172
```
173
</details>
174
161
-##### Unix socket
175
+###### Unix socket
176
177
Collecting data from a local instance over Unix socket.
178
@@ -172,7 +186,7 @@ jobs:
186
```
187
</details>
188
175
-##### TCP socket
189
+###### TCP socket
190
191
Collecting data from a local instance over TCP socket.
192
@@ -186,7 +200,7 @@ jobs:
200
```
201
</details>
202
189
-##### Multi-instance
203
+###### Multi-instance
204
205
> **Note**: When you define multiple jobs, their names must be unique.
206
src/go/plugin/go.d/collector/pihole/integrations/pi-hole.md
+38
-24
@@ -114,26 +114,6 @@ Pi-hole administrator password is required for API authentication. Make sure to
114
115
### Configuration
116
117
-#### File
118
-
119
-The configuration file name for this integration is `go.d/pihole.conf`.
120
-
121
-The file format is YAML. Generally, the structure is:
122
-
123
-```yaml
124
-update_every: 1
125
-autodetection_retry: 0
126
-jobs:
127
- - name: some_name1
128
- - name: some_name1
129
-```
130
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
131
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
132
-
133
-```bash
134
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
135
-sudo ./edit-config go.d/pihole.conf
136
-```
117
#### Options
118
119
The following options can be defined globally: update_every, autodetection_retry.
@@ -163,9 +143,43 @@ The following options can be defined globally: update_every, autodetection_retry
143
144
</details>
145
166
-#### Examples
146
168
-##### Basic
147
+#### via UI
148
+
149
+The **pihole** collector can be configured directly through the Netdata web interface:
150
+
151
+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.
153
+3. The **Collectors → Jobs** view opens by default.
154
+4. In the Search box, type _pihole_ (or scroll the list) to locate the **pihole** collector.
155
+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**.
157
+
158
+
159
+#### via File
160
+
161
+The configuration file name for this integration is `go.d/pihole.conf`.
162
+
163
+The file format is YAML. Generally, the structure is:
164
+
165
+```yaml
166
+update_every: 1
167
+autodetection_retry: 0
168
+jobs:
169
+ - name: some_name1
170
+ - name: some_name1
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).
174
+
175
+```bash
176
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
177
+sudo ./edit-config go.d/pihole.conf
178
+```
179
+
180
+##### Examples
181
+
182
+###### Basic
183
184
A basic example configuration.
185
@@ -180,7 +194,7 @@ jobs:
194
```
195
</details>
196
183
-##### HTTPS with self-signed certificate
197
+###### HTTPS with self-signed certificate
198
199
Remote instance with enabled HTTPS and self-signed certificate.
200
@@ -196,7 +210,7 @@ jobs:
210
```
211
</details>
212
199
-##### Multi-instance
213
+###### Multi-instance
214
215
> **Note**: When you define multiple jobs, their names must be unique.
216
src/go/plugin/go.d/collector/pika/integrations/pika.md
+38
-24
@@ -106,26 +106,6 @@ No action required.
106
107
### Configuration
108
109
-#### File
110
-
111
-The configuration file name for this integration is `go.d/pika.conf`.
112
-
113
-The file format is YAML. Generally, the structure is:
114
-
115
-```yaml
116
-update_every: 1
117
-autodetection_retry: 0
118
-jobs:
119
- - name: some_name1
120
- - name: some_name1
121
-```
122
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
123
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
-
125
-```bash
126
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
127
-sudo ./edit-config go.d/pika.conf
128
-```
109
#### Options
110
111
The following options can be defined globally: update_every, autodetection_retry.
@@ -148,9 +128,43 @@ The following options can be defined globally: update_every, autodetection_retry
128
129
</details>
130
151
-#### Examples
131
153
-##### TCP socket
132
+#### via UI
133
+
134
+The **pika** collector can be configured directly through the Netdata web interface:
135
+
136
+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.
138
+3. The **Collectors → Jobs** view opens by default.
139
+4. In the Search box, type _pika_ (or scroll the list) to locate the **pika** collector.
140
+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**.
142
+
143
+
144
+#### via File
145
+
146
+The configuration file name for this integration is `go.d/pika.conf`.
147
+
148
+The file format is YAML. Generally, the structure is:
149
+
150
+```yaml
151
+update_every: 1
152
+autodetection_retry: 0
153
+jobs:
154
+ - name: some_name1
155
+ - name: some_name1
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).
159
+
160
+```bash
161
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
162
+sudo ./edit-config go.d/pika.conf
163
+```
164
+
165
+##### Examples
166
+
167
+###### TCP socket
168
169
An example configuration.
170
@@ -164,7 +178,7 @@ jobs:
178
```
179
</details>
180
167
-##### TCP socket with password
181
+###### TCP socket with password
182
183
An example configuration.
184
@@ -178,7 +192,7 @@ jobs:
192
```
193
</details>
194
181
-##### Multi-instance
195
+###### Multi-instance
196
197
> **Note**: When you define multiple jobs, their names must be unique.
198
src/go/plugin/go.d/collector/ping/integrations/ping.md
+38
-24
@@ -119,26 +119,6 @@ No action required.
119
120
### Configuration
121
122
-#### File
123
-
124
-The configuration file name for this integration is `go.d/ping.conf`.
125
-
126
-The file format is YAML. Generally, the structure is:
127
-
128
-```yaml
129
-update_every: 1
130
-autodetection_retry: 0
131
-jobs:
132
- - name: some_name1
133
- - name: some_name1
134
-```
135
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
136
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
137
-
138
-```bash
139
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
140
-sudo ./edit-config go.d/ping.conf
141
-```
122
#### Options
123
124
The following options can be defined globally: update_every, autodetection_retry.
@@ -159,9 +139,43 @@ The following options can be defined globally: update_every, autodetection_retry
139
140
</details>
141
162
-#### Examples
142
164
-##### IPv4 hosts
143
+#### via UI
144
+
145
+The **ping** collector can be configured directly through the Netdata web interface:
146
+
147
+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.
149
+3. The **Collectors → Jobs** view opens by default.
150
+4. In the Search box, type _ping_ (or scroll the list) to locate the **ping** collector.
151
+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**.
153
+
154
+
155
+#### via File
156
+
157
+The configuration file name for this integration is `go.d/ping.conf`.
158
+
159
+The file format is YAML. Generally, the structure is:
160
+
161
+```yaml
162
+update_every: 1
163
+autodetection_retry: 0
164
+jobs:
165
+ - name: some_name1
166
+ - name: some_name1
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).
170
+
171
+```bash
172
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
173
+sudo ./edit-config go.d/ping.conf
174
+```
175
+
176
+##### Examples
177
+
178
+###### IPv4 hosts
179
180
An example configuration.
181
@@ -177,7 +191,7 @@ jobs:
191
```
192
</details>
193
180
-##### Unprivileged mode
194
+###### Unprivileged mode
195
196
An example configuration.
197
@@ -194,7 +208,7 @@ jobs:
208
```
209
</details>
210
197
-##### Multi-instance
211
+###### Multi-instance
212
213
> **Note**: When you define multiple jobs, their names must be unique.
214
src/go/plugin/go.d/collector/portcheck/integrations/tcp-udp_endpoints.md
+38
-24
@@ -135,7 +135,38 @@ No action required.
135
136
### Configuration
137
138
-#### File
138
+#### Options
139
+
140
+The following options can be defined globally: update_every, autodetection_retry.
141
+
142
+
143
+<details open><summary>Config options</summary>
144
+
145
+| Name | Description | Default | Required |
146
+|:----|:-----------|:-------|:--------:|
147
+| update_every | Data collection frequency. | 5 | no |
148
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
149
+| host | Remote host address in IPv4, IPv6 format, or DNS name. | | yes |
150
+| ports | Target TCP ports. Must be specified in numeric format. | | no |
151
+| udp_ports | Target UDP ports. Must be specified in numeric format. | | no |
152
+| timeout | HTTP request timeout. | 2 | no |
153
+
154
+</details>
155
+
156
+
157
+#### via UI
158
+
159
+The **portcheck** collector can be configured directly through the Netdata web interface:
160
+
161
+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.
163
+3. The **Collectors → Jobs** view opens by default.
164
+4. In the Search box, type _portcheck_ (or scroll the list) to locate the **portcheck** collector.
165
+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**.
167
+
168
+
169
+#### via File
170
171
The configuration file name for this integration is `go.d/portcheck.conf`.
172
@@ -155,27 +186,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
186
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
187
sudo ./edit-config go.d/portcheck.conf
188
```
158
-#### Options
159
-
160
-The following options can be defined globally: update_every, autodetection_retry.
161
-
162
-
163
-<details open><summary>Config options</summary>
164
-
165
-| Name | Description | Default | Required |
166
-|:----|:-----------|:-------|:--------:|
167
-| update_every | Data collection frequency. | 5 | no |
168
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
169
-| host | Remote host address in IPv4, IPv6 format, or DNS name. | | yes |
170
-| ports | Target TCP ports. Must be specified in numeric format. | | no |
171
-| udp_ports | Target UDP ports. Must be specified in numeric format. | | no |
172
-| timeout | HTTP request timeout. | 2 | no |
173
-
174
-</details>
189
176
-#### Examples
190
+##### Examples
191
178
-##### Check TCP ports (IPv4)
192
+###### Check TCP ports (IPv4)
193
194
An example configuration.
195
@@ -192,7 +206,7 @@ jobs:
206
```
207
</details>
208
195
-##### Check TCP ports (IPv6)
209
+###### Check TCP ports (IPv6)
210
211
An example configuration.
212
@@ -209,7 +223,7 @@ jobs:
223
```
224
</details>
225
212
-##### Check UDP ports (IPv4)
226
+###### Check UDP ports (IPv4)
227
228
An example configuration.
229
@@ -226,7 +240,7 @@ jobs:
240
```
241
</details>
242
229
-##### Check UDP ports (IPv6)
243
+###### Check UDP ports (IPv6)
244
245
An example configuration.
246
@@ -243,7 +257,7 @@ jobs:
257
```
258
</details>
259
246
-##### Multi-instance
260
+###### Multi-instance
261
262
> **Note**: When you define multiple jobs, their names must be unique.
263
src/go/plugin/go.d/collector/postfix/integrations/postfix.md
+31
-17
@@ -86,7 +86,35 @@ No action required.
86
87
### Configuration
88
89
-#### File
89
+#### Options
90
+
91
+The following options can be defined globally: update_every.
92
+
93
+
94
+<details open><summary>Config options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| update_every | Data collection frequency. | 10 | no |
99
+| binary_path | Path to the `postqueue` binary. If an absolute path is provided, the collector will use it directly; otherwise, it will search for the binary in directories specified in the PATH environment variable. | /usr/sbin/postqueue | yes |
100
+| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
101
+
102
+</details>
103
+
104
+
105
+#### via UI
106
+
107
+The **postfix** collector can be configured directly through the Netdata web interface:
108
+
109
+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.
111
+3. The **Collectors → Jobs** view opens by default.
112
+4. In the Search box, type _postfix_ (or scroll the list) to locate the **postfix** collector.
113
+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**.
115
+
116
+
117
+#### via File
118
119
The configuration file name for this integration is `go.d/postfix.conf`.
120
@@ -106,24 +134,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
134
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
135
sudo ./edit-config go.d/postfix.conf
136
```
109
-#### Options
110
-
111
-The following options can be defined globally: update_every.
112
-
113
-
114
-<details open><summary>Config options</summary>
115
-
116
-| Name | Description | Default | Required |
117
-|:----|:-----------|:-------|:--------:|
118
-| update_every | Data collection frequency. | 10 | no |
119
-| binary_path | Path to the `postqueue` binary. If an absolute path is provided, the collector will use it directly; otherwise, it will search for the binary in directories specified in the PATH environment variable. | /usr/sbin/postqueue | yes |
120
-| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
121
-
122
-</details>
137
124
-#### Examples
138
+##### Examples
139
126
-##### Custom binary path
140
+###### Custom binary path
141
142
The executable is not in the directories specified in the PATH environment variable.
143
src/go/plugin/go.d/collector/postgres/integrations/postgresql.md
+38
-24
@@ -274,7 +274,39 @@ system.
274
275
### Configuration
276
277
-#### File
277
+#### Options
278
+
279
+The following options can be defined globally: update_every, autodetection_retry.
280
+
281
+
282
+<details open><summary>Config options</summary>
283
+
284
+| Name | Description | Default | Required |
285
+|:----|:-----------|:-------|:--------:|
286
+| update_every | Data collection frequency. | 5 | no |
287
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
288
+| dsn | Postgres server DSN (Data Source Name). See [DSN syntax](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). | postgres://postgres:postgres@127.0.0.1:5432/postgres | yes |
289
+| timeout | Query timeout in seconds. | 2 | no |
290
+| collect_databases_matching | Databases selector. Determines which database metrics will be collected. Syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#simple-patterns-matcher). | | no |
291
+| max_db_tables | Maximum number of tables in the database. Table metrics will not be collected for databases that have more tables than max_db_tables. 0 means no limit. | 50 | no |
292
+| max_db_indexes | Maximum number of indexes in the database. Index metrics will not be collected for databases that have more indexes than max_db_indexes. 0 means no limit. | 250 | no |
293
+
294
+</details>
295
+
296
+
297
+#### via UI
298
+
299
+The **postgres** collector can be configured directly through the Netdata web interface:
300
+
301
+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.
303
+3. The **Collectors → Jobs** view opens by default.
304
+4. In the Search box, type _postgres_ (or scroll the list) to locate the **postgres** collector.
305
+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**.
307
+
308
+
309
+#### via File
310
311
The configuration file name for this integration is `go.d/postgres.conf`.
312
@@ -294,28 +326,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
326
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
327
sudo ./edit-config go.d/postgres.conf
328
```
297
-#### Options
298
-
299
-The following options can be defined globally: update_every, autodetection_retry.
300
-
301
-
302
-<details open><summary>Config options</summary>
303
-
304
-| Name | Description | Default | Required |
305
-|:----|:-----------|:-------|:--------:|
306
-| update_every | Data collection frequency. | 5 | no |
307
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
308
-| dsn | Postgres server DSN (Data Source Name). See [DSN syntax](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING). | postgres://postgres:postgres@127.0.0.1:5432/postgres | yes |
309
-| timeout | Query timeout in seconds. | 2 | no |
310
-| collect_databases_matching | Databases selector. Determines which database metrics will be collected. Syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/go/pkg/matcher#simple-patterns-matcher). | | no |
311
-| max_db_tables | Maximum number of tables in the database. Table metrics will not be collected for databases that have more tables than max_db_tables. 0 means no limit. | 50 | no |
312
-| max_db_indexes | Maximum number of indexes in the database. Index metrics will not be collected for databases that have more indexes than max_db_indexes. 0 means no limit. | 250 | no |
313
-
314
-</details>
329
316
-#### Examples
330
+##### Examples
331
318
-##### TCP socket
332
+###### TCP socket
333
334
An example configuration.
335
@@ -325,7 +339,7 @@ jobs:
339
dsn: 'postgresql://netdata@127.0.0.1:5432/postgres'
340
341
```
328
-##### Unix socket
342
+###### Unix socket
343
344
An example configuration.
345
@@ -339,7 +353,7 @@ jobs:
353
```
354
</details>
355
342
-##### Unix socket (custom port)
356
+###### Unix socket (custom port)
357
358
Connect to PostgreSQL using a Unix socket with a non-default port (5433).
359
@@ -353,7 +367,7 @@ jobs:
367
```
368
</details>
369
356
-##### Multi-instance
370
+###### Multi-instance
371
372
> **Note**: When you define multiple jobs, their names must be unique.
373
src/go/plugin/go.d/collector/powerdns/integrations/powerdns_authoritative_server.md
+38
-24
@@ -99,26 +99,6 @@ Follow [HTTP API](https://doc.powerdns.com/authoritative/http-api/index.html#ena
99
100
### Configuration
101
102
-#### File
103
-
104
-The configuration file name for this integration is `go.d/powerdns.conf`.
105
-
106
-The file format is YAML. Generally, the structure is:
107
-
108
-```yaml
109
-update_every: 1
110
-autodetection_retry: 0
111
-jobs:
112
- - name: some_name1
113
- - name: some_name1
114
-```
115
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
116
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
117
-
118
-```bash
119
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
120
-sudo ./edit-config go.d/powerdns.conf
121
-```
102
#### Options
103
104
The following options can be defined globally: update_every, autodetection_retry.
@@ -148,9 +128,43 @@ The following options can be defined globally: update_every, autodetection_retry
128
129
</details>
130
151
-#### Examples
131
153
-##### Basic
132
+#### via UI
133
+
134
+The **powerdns** collector can be configured directly through the Netdata web interface:
135
+
136
+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.
138
+3. The **Collectors → Jobs** view opens by default.
139
+4. In the Search box, type _powerdns_ (or scroll the list) to locate the **powerdns** collector.
140
+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**.
142
+
143
+
144
+#### via File
145
+
146
+The configuration file name for this integration is `go.d/powerdns.conf`.
147
+
148
+The file format is YAML. Generally, the structure is:
149
+
150
+```yaml
151
+update_every: 1
152
+autodetection_retry: 0
153
+jobs:
154
+ - name: some_name1
155
+ - name: some_name1
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).
159
+
160
+```bash
161
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
162
+sudo ./edit-config go.d/powerdns.conf
163
+```
164
+
165
+##### Examples
166
+
167
+###### Basic
168
169
An example configuration.
170
@@ -164,7 +178,7 @@ jobs:
178
```
179
</details>
180
167
-##### HTTP authentication
181
+###### HTTP authentication
182
183
Basic HTTP authentication.
184
@@ -180,7 +194,7 @@ jobs:
194
```
195
</details>
196
183
-##### Multi-instance
197
+###### Multi-instance
198
199
> **Note**: When you define multiple jobs, their names must be unique.
200
src/go/plugin/go.d/collector/powerdns_recursor/integrations/powerdns_recursor.md
+38
-24
@@ -102,26 +102,6 @@ Follow [HTTP API](https://doc.powerdns.com/recursor/http-api/index.html#enabling
102
103
### Configuration
104
105
-#### File
106
-
107
-The configuration file name for this integration is `go.d/powerdns_recursor.conf`.
108
-
109
-The file format is YAML. Generally, the structure is:
110
-
111
-```yaml
112
-update_every: 1
113
-autodetection_retry: 0
114
-jobs:
115
- - name: some_name1
116
- - name: some_name1
117
-```
118
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
-
121
-```bash
122
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
-sudo ./edit-config go.d/powerdns_recursor.conf
124
-```
105
#### Options
106
107
The following options can be defined globally: update_every, autodetection_retry.
@@ -151,9 +131,43 @@ The following options can be defined globally: update_every, autodetection_retry
131
132
</details>
133
154
-#### Examples
134
156
-##### Basic
135
+#### via UI
136
+
137
+The **powerdns_recursor** collector can be configured directly through the Netdata web interface:
138
+
139
+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.
141
+3. The **Collectors → Jobs** view opens by default.
142
+4. In the Search box, type _powerdns_recursor_ (or scroll the list) to locate the **powerdns_recursor** collector.
143
+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**.
145
+
146
+
147
+#### via File
148
+
149
+The configuration file name for this integration is `go.d/powerdns_recursor.conf`.
150
+
151
+The file format is YAML. Generally, the structure is:
152
+
153
+```yaml
154
+update_every: 1
155
+autodetection_retry: 0
156
+jobs:
157
+ - name: some_name1
158
+ - name: some_name1
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).
162
+
163
+```bash
164
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
165
+sudo ./edit-config go.d/powerdns_recursor.conf
166
+```
167
+
168
+##### Examples
169
+
170
+###### Basic
171
172
An example configuration.
173
@@ -167,7 +181,7 @@ jobs:
181
```
182
</details>
183
170
-##### HTTP authentication
184
+###### HTTP authentication
185
186
Basic HTTP authentication.
187
@@ -183,7 +197,7 @@ jobs:
197
```
198
</details>
199
186
-##### Multi-instance
200
+###### Multi-instance
201
202
> **Note**: When you define multiple jobs, their names must be unique.
203
src/go/plugin/go.d/collector/prometheus/integrations/4d_server.md
+40
-26
@@ -89,26 +89,6 @@ Install [4D Server exporter](https://github.com/ThomasMaul/Prometheus_4D_Exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/8430ft_modem.md
+40
-26
@@ -89,26 +89,6 @@ Install [8430FT Exporter](https://github.com/dernasherbrezon/8430ft_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/a10_acos_network_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [A10-Networks Prometheus Exporter](https://github.com/a10networks/Promet
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/airthings_waveplus_air_sensor.md
+40
-26
@@ -89,26 +89,6 @@ Install [Waveplus Radon Sensor Exporter](https://github.com/jeremybz/waveplus_ex
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/akamai_edge_dns_traffic.md
+40
-26
@@ -89,26 +89,6 @@ Install [Akamai Edge DNS Traffic Exporter](https://github.com/akamai/akamai-edge
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/akamai_global_traffic_management.md
+40
-26
@@ -89,26 +89,6 @@ Install [Akamai Global Traffic Management Metrics Exporter](https://github.com/a
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/akami_cloudmonitor.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cloudmonitor exporter](https://github.com/ExpressenAB/cloudmonitor_expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/alamos_fe2_server.md
+40
-26
@@ -89,26 +89,6 @@ Install [Alamos FE2 Exporter](https://github.com/codemonauts/prometheus-fe2-expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/alibaba_cloud.md
+40
-26
@@ -89,26 +89,6 @@ Install [Alibaba Cloud Exporter](https://github.com/aylei/aliyun-exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/altaro_backup.md
+40
-26
@@ -89,26 +89,6 @@ Install [Altaro Backup Exporter](https://github.com/raph2i/altaro_backup_exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/amd_cpu_&_gpu.md
+40
-26
@@ -89,26 +89,6 @@ Install [AMD SMI Exporter](https://github.com/amd/amd_smi_exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/andrews_&_arnold_line_status.md
+40
-26
@@ -89,26 +89,6 @@ Install [Andrews & Arnold line status exporter](https://github.com/daveio/aaisp-
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/apache_airflow.md
+40
-26
@@ -89,26 +89,6 @@ Install [Airflow exporter](https://github.com/shalb/airflow-exporter) by followi
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/apache_flink.md
+40
-26
@@ -89,26 +89,6 @@ Install [Apache Flink Metrics Reporter](https://github.com/matsumana/flink_expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/apicast.md
+40
-26
@@ -89,26 +89,6 @@ Install [APIcast](https://github.com/3scale/apicast) by following the instructio
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/apple_time_machine.md
+40
-26
@@ -89,26 +89,6 @@ Install [Apple Time Machine Exporter](https://github.com/znerol/prometheus-timem
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/arm_hwcpipe.md
+40
-26
@@ -89,26 +89,6 @@ Install [ARM HWCPipe Exporter](https://github.com/ylz-at/arm-hwcpipe-exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aruba_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [Aruba Exporter](https://github.com/slashdoom/aruba_exporter) by followi
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/arvancloud_cdn.md
+40
-26
@@ -89,26 +89,6 @@ Install [ArvanCloud exporter](https://github.com/arvancloud/ar-prometheus-export
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/audisto.md
+40
-26
@@ -89,26 +89,6 @@ Install [Audisto exporter](https://github.com/ZeitOnline/audisto_exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/authlog.md
+40
-26
@@ -89,26 +89,6 @@ Install [AuthLog Exporter](https://github.com/woblerr/authlog_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_compute_instances.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS EC2 Exporter](https://github.com/O1ahmad/aws_ec2_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_spot_instance.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS EC2 Spot Exporter](https://github.com/patcadelina/ec2-spot-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_ecs.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS ECS exporter](https://github.com/bevers222/ecs-exporter) by followi
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_health_events.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS Health Exporter](https://github.com/vladvasiliu/aws-health-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_instance_health.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS instance health exporter](https://github.com/bobtfish/aws-instance-
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_quota.md
+40
-26
@@ -89,26 +89,6 @@ Install [aws_quota_exporter](https://github.com/emylincon/aws_quota_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_rds.md
+40
-26
@@ -89,26 +89,6 @@ Install [rds_exporter](https://github.com/percona/rds_exporter) by following the
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_s3_buckets.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS S3 Exporter](https://github.com/ribbybibby/s3_exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/aws_sqs.md
+40
-26
@@ -89,26 +89,6 @@ Install [AWS SQS Exporter](https://github.com/jmal98/sqs-exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/azure_ad_app_passwords.md
+40
-26
@@ -89,26 +89,6 @@ Install [Azure App Secrets monitor](https://github.com/vladvasiliu/azure-app-sec
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/azure_application.md
+40
-26
@@ -89,26 +89,6 @@ Install [Azure Monitor exporter](https://github.com/RobustPerception/azure_metri
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/azure_elastic_pool_sql.md
+40
-26
@@ -89,26 +89,6 @@ Install [Azure Elastic SQL Exporter](https://github.com/benclapp/azure_elastic_s
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/azure_resources.md
+40
-26
@@ -89,26 +89,6 @@ Install [Azure Resources Exporter](https://github.com/FXinnovation/azure_metrics
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/azure_service_bus.md
+40
-26
@@ -89,26 +89,6 @@ Install [Azure Service Bus Exporter](https://github.com/marcinbudny/servicebus_e
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/azure_sql.md
+40
-26
@@ -89,26 +89,6 @@ Install [Azure SQL exporter](https://github.com/iamseth/azure_sql_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/bigquery.md
+40
-26
@@ -89,26 +89,6 @@ Install [BigQuery Exporter](https://github.com/m-lab/prometheus-bigquery-exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/bird_routing_daemon.md
+40
-26
@@ -89,26 +89,6 @@ Install [Bird Routing Daemon Exporter](https://github.com/czerwonk/bird_exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/blackbox.md
+40
-26
@@ -89,26 +89,6 @@ Install [Blackbox exporter](https://github.com/prometheus/blackbox_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/bobcat_miner_300.md
+40
-26
@@ -89,26 +89,6 @@ Install [Bobcat Exporter](https://github.com/pperzyna/bobcat_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/borg_backup.md
+40
-26
@@ -89,26 +89,6 @@ Install [Borg backup exporter](https://github.com/k0ral/borg-exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/bosh.md
+40
-26
@@ -89,26 +89,6 @@ Install [BOSH exporter](https://github.com/bosh-prometheus/bosh_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/bpftrace_variables.md
+40
-26
@@ -89,26 +89,6 @@ Install [bpftrace exporter](https://github.com/andreasgerstmayr/bpftrace_exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/bungeecord.md
+40
-26
@@ -89,26 +89,6 @@ Install [BungeeCord Prometheus Exporter](https://github.com/weihao/bungeecord-pr
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cadvisor.md
+40
-26
@@ -89,26 +89,6 @@ Install [cAdvisor](https://github.com/google/cadvisor) by following the instruct
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/celery.md
+40
-26
@@ -89,26 +89,6 @@ Install [Celery Exporter](https://github.com/ZeitOnline/celery_redis_prometheus)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/certificate_transparency.md
+40
-26
@@ -90,26 +90,6 @@ Install [ct-exporter](https://github.com/Hsn723/ct-exporter) by following the in
90
91
### Configuration
92
93
-#### File
94
-
95
-The configuration file name for this integration is `go.d/prometheus.conf`.
96
-
97
-The file format is YAML. Generally, the structure is:
98
-
99
-```yaml
100
-update_every: 1
101
-autodetection_retry: 0
102
-jobs:
103
- - name: some_name1
104
- - name: some_name1
105
-```
106
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
-
109
-```bash
110
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
-sudo ./edit-config go.d/prometheus.conf
112
-```
93
#### Options
94
95
The following options can be defined globally: update_every, autodetection_retry.
@@ -181,9 +161,43 @@ fallback_type:
161
162
</details>
163
184
-#### Examples
164
186
-##### Basic
165
+#### via UI
166
+
167
+The **prometheus** collector can be configured directly through the Netdata web interface:
168
+
169
+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.
171
+3. The **Collectors → Jobs** view opens by default.
172
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
173
+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**.
175
+
176
+
177
+#### via File
178
+
179
+The configuration file name for this integration is `go.d/prometheus.conf`.
180
+
181
+The file format is YAML. Generally, the structure is:
182
+
183
+```yaml
184
+update_every: 1
185
+autodetection_retry: 0
186
+jobs:
187
+ - name: some_name1
188
+ - name: some_name1
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).
192
+
193
+```bash
194
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
+sudo ./edit-config go.d/prometheus.conf
196
+```
197
+
198
+##### Examples
199
+
200
+###### Basic
201
202
> **Note**: Change the port of the monitored application on which it provides metrics.
203
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1:9090/metrics
211
212
```
199
-##### Read metrics from a file
213
+###### Read metrics from a file
214
215
An example configuration to read metrics from a file.
216
@@ -211,7 +225,7 @@ jobs:
225
```
226
</details>
227
214
-##### HTTP authentication
228
+###### HTTP authentication
229
230
> **Note**: Change the port of the monitored application on which it provides metrics.
231
@@ -230,7 +244,7 @@ jobs:
244
```
245
</details>
246
233
-##### HTTPS with self-signed certificate
247
+###### HTTPS with self-signed certificate
248
249
> **Note**: Change the port of the monitored application on which it provides metrics.
250
@@ -248,7 +262,7 @@ jobs:
262
```
263
</details>
264
251
-##### Multi-instance
265
+###### Multi-instance
266
267
> **Note**: When you define multiple jobs, their names must be unique.
268
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/checkpoint_device.md
+40
-26
@@ -89,26 +89,6 @@ Install [Checkpoint exporter](https://github.com/RespiroConsulting/CheckPointExp
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/chia.md
+40
-26
@@ -89,26 +89,6 @@ Install [Chia Exporter](https://github.com/chia-network/chia-exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md
+40
-26
@@ -89,26 +89,6 @@ Install [Christ Elektronik CLM5IP Exporter](https://github.com/christmann/clm5ip
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cilium_agent.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cilium Agent](https://github.com/cilium/cilium) by following the instru
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cilium_operator.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cilium Operator](https://github.com/cilium/cilium) by following the ins
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cilium_proxy.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cilium Proxy](https://github.com/cilium/proxy) by following the instruc
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cisco_aci.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cisco ACI Exporter](https://github.com/RavuAlHemio/prometheus_aci_expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/citrix_netscaler.md
+40
-26
@@ -89,26 +89,6 @@ Install [Citrix NetScaler Exporter](https://github.com/rokett/Citrix-NetScaler-E
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/clamav_daemon.md
+40
-26
@@ -89,26 +89,6 @@ Install [ClamAV daemon stats exporter](https://github.com/sergeymakinen/clamav_e
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/clamscan_results.md
+40
-26
@@ -89,26 +89,6 @@ Install [clamscan-exporter](https://github.com/FortnoxAB/clamscan-exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/clash.md
+40
-26
@@ -89,26 +89,6 @@ Install [Clash exporter](https://github.com/elonzh/clash_exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cloud Foundry exporter](https://github.com/bosh-prometheus/cf_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry_firehose.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cloud Foundry Firehose exporter](https://github.com/bosh-prometheus/fir
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cloudflare_pcap.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cloudflare exporter](https://github.com/wehkamp/docker-prometheus-cloud
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cloudwatch.md
+40
-26
@@ -89,26 +89,6 @@ Install [CloudWatch exporter](https://github.com/prometheus/cloudwatch_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/clustercontrol_cmon.md
+40
-26
@@ -89,26 +89,6 @@ Install [CMON Exporter](https://github.com/severalnines/cmon_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/collectd.md
+40
-26
@@ -89,26 +89,6 @@ Install [Collectd exporter](https://github.com/prometheus/collectd_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/concourse.md
+40
-26
@@ -89,26 +89,6 @@ To configure the built-in Prometheus exporter, follow the [official documentatio
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/craftbeerpi.md
+40
-26
@@ -89,26 +89,6 @@ Install [CraftBeerPi exporter](https://github.com/jo-hannes/craftbeerpi_exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/crowdsec.md
+40
-26
@@ -89,26 +89,6 @@ To configure the built-in Prometheus exporter, follow the [official documentatio
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/crypto_exchanges.md
+40
-26
@@ -89,26 +89,6 @@ Install [Crypto exporter](https://github.com/ix-ai/crypto-exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cryptowatch.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cryptowat Exporter](https://github.com/nbarrientos/cryptowat_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/custom_exporter.md
+40
-26
@@ -89,26 +89,6 @@ Install [Custom Exporter](https://github.com/orange-cloudfoundry/custom_exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/cvmfs_clients.md
+40
-26
@@ -89,26 +89,6 @@ Install [CVMFS exporter](https://github.com/guilbaults/cvmfs-exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ddwrt_routers.md
+40
-26
@@ -89,26 +89,6 @@ Install [ddwrt-collector](https://github.com/camelusferus/ddwrt_collector) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_ecs_cluster.md
+40
-26
@@ -89,26 +89,6 @@ Install [Dell EMC ECS Exporter](https://github.com/paychex/prometheus-emcecs-exp
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_isilon_cluster.md
+40
-26
@@ -89,26 +89,6 @@ Install [Dell EMC Isilon Exporter](https://github.com/paychex/prometheus-isilon-
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_xtremio_cluster.md
+40
-26
@@ -89,26 +89,6 @@ Install [Dell/EMC XtremIO Exporter](https://github.com/cthiel42/prometheus-xtrem
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dell_powermax.md
+40
-26
@@ -89,26 +89,6 @@ Install [PowerMax Exporter](https://github.com/kckecheng/powermax_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dependency-track.md
+40
-26
@@ -89,26 +89,6 @@ Install [Dependency-Track Exporter](https://github.com/jetstack/dependency-track
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/digitalocean.md
+40
-26
@@ -89,26 +89,6 @@ Install [DigitalOcean Exporter](https://github.com/metalmatze/digitalocean_expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/discourse.md
+40
-26
@@ -89,26 +89,6 @@ Install [Discourse Exporter](https://github.com/discourse/discourse-prometheus)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dmarc.md
+40
-26
@@ -89,26 +89,6 @@ Install [dmarc-metrics-exporter](https://github.com/jgosmann/dmarc-metrics-expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dnsbl.md
+40
-26
@@ -89,26 +89,6 @@ Install [dnsbl-exporter](https://github.com/Luzilla/dnsbl_exporter/) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dutch_electricity_smart_meter.md
+40
-26
@@ -89,26 +89,6 @@ Install [P1Exporter - Dutch Electricity Smart Meter Exporter](https://github.com
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/dynatrace.md
+40
-26
@@ -89,26 +89,6 @@ Install [Dynatrace Exporter](https://github.com/Apside-TOP/dynatrace_exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/eaton_ups.md
+40
-26
@@ -89,26 +89,6 @@ Install [Prometheus Eaton UPS Exporter](https://github.com/psyinfra/prometheus-e
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/elgato_key_light_devices..md
+40
-26
@@ -89,26 +89,6 @@ Install [Elgato Key Light exporter](https://github.com/mdlayher/keylight_exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/energomera_smart_power_meters.md
+40
-26
@@ -89,26 +89,6 @@ Install [energomera-exporter Energomera electricity meter exporter](https://gith
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/eos.md
+40
-26
@@ -89,26 +89,6 @@ Install [EOS exporter](https://github.com/cern-eos/eos_exporter) by following th
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/etcd.md
+40
-26
@@ -85,26 +85,6 @@ No action required.
85
86
### Configuration
87
88
-#### File
89
-
90
-The configuration file name for this integration is `go.d/prometheus.conf`.
91
-
92
-The file format is YAML. Generally, the structure is:
93
-
94
-```yaml
95
-update_every: 1
96
-autodetection_retry: 0
97
-jobs:
98
- - name: some_name1
99
- - name: some_name1
100
-```
101
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
-
104
-```bash
105
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
106
-sudo ./edit-config go.d/prometheus.conf
107
-```
88
#### Options
89
90
The following options can be defined globally: update_every, autodetection_retry.
@@ -176,9 +156,43 @@ fallback_type:
156
157
</details>
158
179
-#### Examples
159
181
-##### Basic
160
+#### via UI
161
+
162
+The **prometheus** collector can be configured directly through the Netdata web interface:
163
+
164
+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.
166
+3. The **Collectors → Jobs** view opens by default.
167
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
168
+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**.
170
+
171
+
172
+#### via File
173
+
174
+The configuration file name for this integration is `go.d/prometheus.conf`.
175
+
176
+The file format is YAML. Generally, the structure is:
177
+
178
+```yaml
179
+update_every: 1
180
+autodetection_retry: 0
181
+jobs:
182
+ - name: some_name1
183
+ - name: some_name1
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).
187
+
188
+```bash
189
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
190
+sudo ./edit-config go.d/prometheus.conf
191
+```
192
+
193
+##### Examples
194
+
195
+###### Basic
196
197
> **Note**: Change the port of the monitored application on which it provides metrics.
198
@@ -191,7 +205,7 @@ jobs:
205
url: http://127.0.0.1:9090/metrics
206
207
```
194
-##### Read metrics from a file
208
+###### Read metrics from a file
209
210
An example configuration to read metrics from a file.
211
@@ -206,7 +220,7 @@ jobs:
220
```
221
</details>
222
209
-##### HTTP authentication
223
+###### HTTP authentication
224
225
> **Note**: Change the port of the monitored application on which it provides metrics.
226
@@ -225,7 +239,7 @@ jobs:
239
```
240
</details>
241
228
-##### HTTPS with self-signed certificate
242
+###### HTTPS with self-signed certificate
243
244
> **Note**: Change the port of the monitored application on which it provides metrics.
245
@@ -243,7 +257,7 @@ jobs:
257
```
258
</details>
259
246
-##### Multi-instance
260
+###### Multi-instance
261
262
> **Note**: When you define multiple jobs, their names must be unique.
263
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/excel_spreadsheet.md
+40
-26
@@ -89,26 +89,6 @@ Install [Excel Exporter](https://github.com/MarcusCalidus/excel-exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/fastd.md
+40
-26
@@ -89,26 +89,6 @@ Install [Fastd Exporter](https://github.com/freifunk-darmstadt/fastd-exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/fortigate_firewall.md
+40
-26
@@ -89,26 +89,6 @@ Install [fortigate_exporter](https://github.com/bluecmd/fortigate_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/freebsd_nfs.md
+40
-26
@@ -89,26 +89,6 @@ Install [FreeBSD NFS Exporter](https://github.com/Axcient/freebsd-nfs-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/freebsd_rctl-racct.md
+40
-26
@@ -89,26 +89,6 @@ Install [FreeBSD RCTL Exporter](https://github.com/yo000/rctl_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/freifunk_network.md
+40
-26
@@ -89,26 +89,6 @@ Install [Freifunk Exporter](https://github.com/xperimental/freifunk-exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/fritzbox_network_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [Fritzbox exporter](https://github.com/pdreker/fritz_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/frrouting.md
+40
-26
@@ -89,26 +89,6 @@ Install [FRRouting Exporter](https://github.com/tynany/frr_exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/gcp_gce.md
+40
-26
@@ -89,26 +89,6 @@ Install [GCP GCE Exporter](https://github.com/O1ahmad/gcp-gce-exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/gcp_quota.md
+40
-26
@@ -89,26 +89,6 @@ Install [GCP Quota Exporter](https://github.com/mintel/gcp-quota-exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/generic_command_line_output.md
+40
-26
@@ -89,26 +89,6 @@ Install [Generic Command Line Output Exporter](https://github.com/MarioMartReq/g
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/generic_storage_enclosure_tool.md
+40
-26
@@ -89,26 +89,6 @@ Install [jbod - Generic storage enclosure tool](https://github.com/Gandi/jbod-rs
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/github_api_rate_limit.md
+40
-26
@@ -90,26 +90,6 @@ Install [GitHub API rate limit Exporter](https://github.com/lunarway/github-rate
90
91
### Configuration
92
93
-#### File
94
-
95
-The configuration file name for this integration is `go.d/prometheus.conf`.
96
-
97
-The file format is YAML. Generally, the structure is:
98
-
99
-```yaml
100
-update_every: 1
101
-autodetection_retry: 0
102
-jobs:
103
- - name: some_name1
104
- - name: some_name1
105
-```
106
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
-
109
-```bash
110
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
-sudo ./edit-config go.d/prometheus.conf
112
-```
93
#### Options
94
95
The following options can be defined globally: update_every, autodetection_retry.
@@ -181,9 +161,43 @@ fallback_type:
161
162
</details>
163
184
-#### Examples
164
186
-##### Basic
165
+#### via UI
166
+
167
+The **prometheus** collector can be configured directly through the Netdata web interface:
168
+
169
+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.
171
+3. The **Collectors → Jobs** view opens by default.
172
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
173
+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**.
175
+
176
+
177
+#### via File
178
+
179
+The configuration file name for this integration is `go.d/prometheus.conf`.
180
+
181
+The file format is YAML. Generally, the structure is:
182
+
183
+```yaml
184
+update_every: 1
185
+autodetection_retry: 0
186
+jobs:
187
+ - name: some_name1
188
+ - name: some_name1
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).
192
+
193
+```bash
194
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
+sudo ./edit-config go.d/prometheus.conf
196
+```
197
+
198
+##### Examples
199
+
200
+###### Basic
201
202
> **Note**: Change the port of the monitored application on which it provides metrics.
203
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1:9090/metrics
211
212
```
199
-##### Read metrics from a file
213
+###### Read metrics from a file
214
215
An example configuration to read metrics from a file.
216
@@ -211,7 +225,7 @@ jobs:
225
```
226
</details>
227
214
-##### HTTP authentication
228
+###### HTTP authentication
229
230
> **Note**: Change the port of the monitored application on which it provides metrics.
231
@@ -230,7 +244,7 @@ jobs:
244
```
245
</details>
246
233
-##### HTTPS with self-signed certificate
247
+###### HTTPS with self-signed certificate
248
249
> **Note**: Change the port of the monitored application on which it provides metrics.
250
@@ -248,7 +262,7 @@ jobs:
262
```
263
</details>
264
251
-##### Multi-instance
265
+###### Multi-instance
266
267
> **Note**: When you define multiple jobs, their names must be unique.
268
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/github_repository.md
+40
-26
@@ -89,26 +89,6 @@ Install [GitHub Exporter](https://github.com/githubexporter/github-exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/gitlab_runner.md
+40
-26
@@ -89,26 +89,6 @@ To configure the built-in Prometheus exporter, follow the [official documentatio
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/gobetween.md
+40
-26
@@ -85,26 +85,6 @@ No action required.
85
86
### Configuration
87
88
-#### File
89
-
90
-The configuration file name for this integration is `go.d/prometheus.conf`.
91
-
92
-The file format is YAML. Generally, the structure is:
93
-
94
-```yaml
95
-update_every: 1
96
-autodetection_retry: 0
97
-jobs:
98
- - name: some_name1
99
- - name: some_name1
100
-```
101
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
-
104
-```bash
105
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
106
-sudo ./edit-config go.d/prometheus.conf
107
-```
88
#### Options
89
90
The following options can be defined globally: update_every, autodetection_retry.
@@ -176,9 +156,43 @@ fallback_type:
156
157
</details>
158
179
-#### Examples
159
181
-##### Basic
160
+#### via UI
161
+
162
+The **prometheus** collector can be configured directly through the Netdata web interface:
163
+
164
+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.
166
+3. The **Collectors → Jobs** view opens by default.
167
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
168
+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**.
170
+
171
+
172
+#### via File
173
+
174
+The configuration file name for this integration is `go.d/prometheus.conf`.
175
+
176
+The file format is YAML. Generally, the structure is:
177
+
178
+```yaml
179
+update_every: 1
180
+autodetection_retry: 0
181
+jobs:
182
+ - name: some_name1
183
+ - name: some_name1
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).
187
+
188
+```bash
189
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
190
+sudo ./edit-config go.d/prometheus.conf
191
+```
192
+
193
+##### Examples
194
+
195
+###### Basic
196
197
> **Note**: Change the port of the monitored application on which it provides metrics.
198
@@ -191,7 +205,7 @@ jobs:
205
url: http://127.0.0.1:9090/metrics
206
207
```
194
-##### Read metrics from a file
208
+###### Read metrics from a file
209
210
An example configuration to read metrics from a file.
211
@@ -206,7 +220,7 @@ jobs:
220
```
221
</details>
222
209
-##### HTTP authentication
223
+###### HTTP authentication
224
225
> **Note**: Change the port of the monitored application on which it provides metrics.
226
@@ -225,7 +239,7 @@ jobs:
239
```
240
</details>
241
228
-##### HTTPS with self-signed certificate
242
+###### HTTPS with self-signed certificate
243
244
> **Note**: Change the port of the monitored application on which it provides metrics.
245
@@ -243,7 +257,7 @@ jobs:
257
```
258
</details>
259
246
-##### Multi-instance
260
+###### Multi-instance
261
262
> **Note**: When you define multiple jobs, their names must be unique.
263
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/google_cloud_platform.md
+40
-26
@@ -89,26 +89,6 @@ Install [Google Cloud Platform Exporter](https://github.com/DazWilkin/gcp-export
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/google_pagespeed.md
+40
-26
@@ -89,26 +89,6 @@ Install [Pagespeed exporter](https://github.com/foomo/pagespeed_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/google_stackdriver.md
+40
-26
@@ -89,26 +89,6 @@ Install [Google Stackdriver exporter](https://github.com/prometheus-community/st
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/gpsd.md
+40
-26
@@ -89,26 +89,6 @@ Install [gpsd exporter](https://github.com/natesales/gpsd-exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/grafana.md
+40
-26
@@ -85,26 +85,6 @@ No action required.
85
86
### Configuration
87
88
-#### File
89
-
90
-The configuration file name for this integration is `go.d/prometheus.conf`.
91
-
92
-The file format is YAML. Generally, the structure is:
93
-
94
-```yaml
95
-update_every: 1
96
-autodetection_retry: 0
97
-jobs:
98
- - name: some_name1
99
- - name: some_name1
100
-```
101
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
-
104
-```bash
105
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
106
-sudo ./edit-config go.d/prometheus.conf
107
-```
88
#### Options
89
90
The following options can be defined globally: update_every, autodetection_retry.
@@ -176,9 +156,43 @@ fallback_type:
156
157
</details>
158
179
-#### Examples
159
181
-##### Basic
160
+#### via UI
161
+
162
+The **prometheus** collector can be configured directly through the Netdata web interface:
163
+
164
+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.
166
+3. The **Collectors → Jobs** view opens by default.
167
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
168
+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**.
170
+
171
+
172
+#### via File
173
+
174
+The configuration file name for this integration is `go.d/prometheus.conf`.
175
+
176
+The file format is YAML. Generally, the structure is:
177
+
178
+```yaml
179
+update_every: 1
180
+autodetection_retry: 0
181
+jobs:
182
+ - name: some_name1
183
+ - name: some_name1
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).
187
+
188
+```bash
189
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
190
+sudo ./edit-config go.d/prometheus.conf
191
+```
192
+
193
+##### Examples
194
+
195
+###### Basic
196
197
> **Note**: Change the port of the monitored application on which it provides metrics.
198
@@ -191,7 +205,7 @@ jobs:
205
url: http://127.0.0.1:9090/metrics
206
207
```
194
-##### Read metrics from a file
208
+###### Read metrics from a file
209
210
An example configuration to read metrics from a file.
211
@@ -206,7 +220,7 @@ jobs:
220
```
221
</details>
222
209
-##### HTTP authentication
223
+###### HTTP authentication
224
225
> **Note**: Change the port of the monitored application on which it provides metrics.
226
@@ -225,7 +239,7 @@ jobs:
239
```
240
</details>
241
228
-##### HTTPS with self-signed certificate
242
+###### HTTPS with self-signed certificate
243
244
> **Note**: Change the port of the monitored application on which it provides metrics.
245
@@ -243,7 +257,7 @@ jobs:
257
```
258
</details>
259
246
-##### Multi-instance
260
+###### Multi-instance
261
262
> **Note**: When you define multiple jobs, their names must be unique.
263
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/graylog_server.md
+40
-26
@@ -89,26 +89,6 @@ To configure the built-in Prometheus exporter, follow the [official documentatio
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/gtp.md
+40
-26
@@ -89,26 +89,6 @@ Install [GTP Exporter](https://github.com/wmnsk/gtp_exporter) by following the i
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/halon.md
+40
-26
@@ -89,26 +89,6 @@ Install [Halon exporter](https://github.com/tobiasbp/halon_exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hana.md
+40
-26
@@ -89,26 +89,6 @@ Install [HANA Exporter](https://github.com/jenningsloy318/hana_exporter) by foll
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hashicorp_vault_secrets.md
+40
-26
@@ -89,26 +89,6 @@ Install [Vault Assessment Prometheus Exporter](https://github.com/tomtom-interna
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hasura_graphql_server.md
+40
-26
@@ -90,26 +90,6 @@ Install [Hasura Exporter](https://github.com/zolamk/hasura-exporter) by followin
90
91
### Configuration
92
93
-#### File
94
-
95
-The configuration file name for this integration is `go.d/prometheus.conf`.
96
-
97
-The file format is YAML. Generally, the structure is:
98
-
99
-```yaml
100
-update_every: 1
101
-autodetection_retry: 0
102
-jobs:
103
- - name: some_name1
104
- - name: some_name1
105
-```
106
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
-
109
-```bash
110
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
-sudo ./edit-config go.d/prometheus.conf
112
-```
93
#### Options
94
95
The following options can be defined globally: update_every, autodetection_retry.
@@ -181,9 +161,43 @@ fallback_type:
161
162
</details>
163
184
-#### Examples
164
186
-##### Basic
165
+#### via UI
166
+
167
+The **prometheus** collector can be configured directly through the Netdata web interface:
168
+
169
+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.
171
+3. The **Collectors → Jobs** view opens by default.
172
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
173
+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**.
175
+
176
+
177
+#### via File
178
+
179
+The configuration file name for this integration is `go.d/prometheus.conf`.
180
+
181
+The file format is YAML. Generally, the structure is:
182
+
183
+```yaml
184
+update_every: 1
185
+autodetection_retry: 0
186
+jobs:
187
+ - name: some_name1
188
+ - name: some_name1
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).
192
+
193
+```bash
194
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
+sudo ./edit-config go.d/prometheus.conf
196
+```
197
+
198
+##### Examples
199
+
200
+###### Basic
201
202
> **Note**: Change the port of the monitored application on which it provides metrics.
203
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1:9090/metrics
211
212
```
199
-##### Read metrics from a file
213
+###### Read metrics from a file
214
215
An example configuration to read metrics from a file.
216
@@ -211,7 +225,7 @@ jobs:
225
```
226
</details>
227
214
-##### HTTP authentication
228
+###### HTTP authentication
229
230
> **Note**: Change the port of the monitored application on which it provides metrics.
231
@@ -230,7 +244,7 @@ jobs:
244
```
245
</details>
246
233
-##### HTTPS with self-signed certificate
247
+###### HTTPS with self-signed certificate
248
249
> **Note**: Change the port of the monitored application on which it provides metrics.
250
@@ -248,7 +262,7 @@ jobs:
262
```
263
</details>
264
251
-##### Multi-instance
265
+###### Multi-instance
266
267
> **Note**: When you define multiple jobs, their names must be unique.
268
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hdsentinel.md
+40
-26
@@ -89,26 +89,6 @@ Install [HDSentinel Exporter](https://github.com/qusielle/hdsentinel-exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/helium_hotspot.md
+40
-26
@@ -89,26 +89,6 @@ Install [Helium hotspot exporter](https://github.com/tedder/helium_hotspot_expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/helium_miner_validator.md
+40
-26
@@ -89,26 +89,6 @@ Install [Helium miner (validator) exporter](https://github.com/tedder/miner_expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hhvm.md
+40
-26
@@ -90,26 +90,6 @@ Install [HHVM Exporter](https://github.com/wikimedia/operations-software-hhvm_ex
90
91
### Configuration
92
93
-#### File
94
-
95
-The configuration file name for this integration is `go.d/prometheus.conf`.
96
-
97
-The file format is YAML. Generally, the structure is:
98
-
99
-```yaml
100
-update_every: 1
101
-autodetection_retry: 0
102
-jobs:
103
- - name: some_name1
104
- - name: some_name1
105
-```
106
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
-
109
-```bash
110
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
-sudo ./edit-config go.d/prometheus.conf
112
-```
93
#### Options
94
95
The following options can be defined globally: update_every, autodetection_retry.
@@ -181,9 +161,43 @@ fallback_type:
161
162
</details>
163
184
-#### Examples
164
186
-##### Basic
165
+#### via UI
166
+
167
+The **prometheus** collector can be configured directly through the Netdata web interface:
168
+
169
+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.
171
+3. The **Collectors → Jobs** view opens by default.
172
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
173
+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**.
175
+
176
+
177
+#### via File
178
+
179
+The configuration file name for this integration is `go.d/prometheus.conf`.
180
+
181
+The file format is YAML. Generally, the structure is:
182
+
183
+```yaml
184
+update_every: 1
185
+autodetection_retry: 0
186
+jobs:
187
+ - name: some_name1
188
+ - name: some_name1
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).
192
+
193
+```bash
194
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
+sudo ./edit-config go.d/prometheus.conf
196
+```
197
+
198
+##### Examples
199
+
200
+###### Basic
201
202
> **Note**: Change the port of the monitored application on which it provides metrics.
203
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1:9090/metrics
211
212
```
199
-##### Read metrics from a file
213
+###### Read metrics from a file
214
215
An example configuration to read metrics from a file.
216
@@ -211,7 +225,7 @@ jobs:
225
```
226
</details>
227
214
-##### HTTP authentication
228
+###### HTTP authentication
229
230
> **Note**: Change the port of the monitored application on which it provides metrics.
231
@@ -230,7 +244,7 @@ jobs:
244
```
245
</details>
246
233
-##### HTTPS with self-signed certificate
247
+###### HTTPS with self-signed certificate
248
249
> **Note**: Change the port of the monitored application on which it provides metrics.
250
@@ -248,7 +262,7 @@ jobs:
262
```
263
</details>
264
251
-##### Multi-instance
265
+###### Multi-instance
266
267
> **Note**: When you define multiple jobs, their names must be unique.
268
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hitron_cgn_series_cpe.md
+40
-26
@@ -89,26 +89,6 @@ Install [Hitron CGNV4 exporter](https://github.com/yrro/hitron-exporter) by foll
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hitron_coda_cable_modem.md
+40
-26
@@ -89,26 +89,6 @@ Install [Hitron CODA Cable Modem Exporter](https://github.com/hairyhenderson/hit
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/homebridge.md
+40
-26
@@ -89,26 +89,6 @@ Install [Homebridge Prometheus Exporter](https://github.com/lstrojny/homebridge-
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/homey.md
+40
-26
@@ -89,26 +89,6 @@ Install [Homey Exporter](https://github.com/rickardp/homey-prometheus-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/honeypot.md
+40
-26
@@ -89,26 +89,6 @@ Install [Intrinsec honeypot_exporter](https://github.com/Intrinsec/honeypot_expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hp_ilo.md
+40
-26
@@ -89,26 +89,6 @@ Install [HP iLO Metrics Exporter](https://github.com/infinityworks/hpilo-exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/huawei_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [Huawei Hilink exporter](https://github.com/eliecharra/hilink-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/hubble.md
+40
-26
@@ -89,26 +89,6 @@ To configure the built-in Prometheus exporter, follow the [official documentatio
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ibm_aix_systems_njmon.md
+40
-26
@@ -89,26 +89,6 @@ Install [NJmon](https://github.com/crooks/njmon_exporter) by following the instr
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ibm_cryptoexpress_cex_cards.md
+40
-26
@@ -89,26 +89,6 @@ Install [IBM Z CEX Device Plugin Prometheus Exporter](https://github.com/ibm-s39
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ibm_mq.md
+40
-26
@@ -89,26 +89,6 @@ Install [MQ Exporter](https://github.com/agebhar1/mq_exporter) by following the
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum.md
+40
-26
@@ -89,26 +89,6 @@ Install [IBM Spectrum Exporter](https://github.com/topine/ibm-spectrum-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum_virtualize.md
+40
-26
@@ -89,26 +89,6 @@ Install [spectrum_virtualize_exporter](https://github.com/bluecmd/spectrum_virtu
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ibm_z_hardware_management_console.md
+40
-26
@@ -89,26 +89,6 @@ Install [IBM Z HMC Exporter](https://github.com/zhmcclient/zhmc-prometheus-expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/influxdb.md
+40
-26
@@ -89,26 +89,6 @@ Install [InfluxDB exporter](https://github.com/prometheus/influxdb_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/iota_full_node.md
+40
-26
@@ -89,26 +89,6 @@ Install [IOTA Exporter](https://github.com/crholliday/iota-prom-exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ipmi_by_soundcloud.md
+40
-26
@@ -89,26 +89,6 @@ Install [SoundCloud IPMI Exporter (querying IPMI externally, blackbox-exporter s
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/iqair_airvisual_air_quality_monitors.md
+40
-26
@@ -89,26 +89,6 @@ Install [IQair Exporter](https://github.com/Packetslave/iqair_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/jarvis_standing_desk.md
+40
-26
@@ -89,26 +89,6 @@ Install [Jarvis Standing Desk Exporter](https://github.com/hairyhenderson/jarvis
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/jenkins.md
+40
-26
@@ -89,26 +89,6 @@ Install [Jenkins exporter](https://github.com/simplesurance/jenkins-exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/jetbrains_floating_license_server.md
+40
-26
@@ -89,26 +89,6 @@ Install [JetBrains Floating License Server Export](https://github.com/mkreu/jetb
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/jmx.md
+40
-26
@@ -89,26 +89,6 @@ Install [JMX Exporter](https://github.com/prometheus/jmx_exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/jolokia.md
+40
-26
@@ -89,26 +89,6 @@ Install [jolokia_exporter](https://github.com/aklinkert/jolokia_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/journald.md
+40
-26
@@ -89,26 +89,6 @@ Install [journald-exporter](https://github.com/dead-claudia/journald-exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/kafka.md
+40
-26
@@ -89,26 +89,6 @@ Install [Kafka Exporter](https://github.com/danielqsj/kafka_exporter/) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/kafka_connect.md
+40
-26
@@ -89,26 +89,6 @@ Install [Kafka Connect exporter](https://github.com/findelabs/kafka-connect-expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/kafka_consumer_lag.md
+40
-26
@@ -89,26 +89,6 @@ Install [Kafka Consumer Lag Monitoring](https://github.com/omarsmak/kafka-consum
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/kafka_zookeeper.md
+40
-26
@@ -89,26 +89,6 @@ Install [Kafka ZooKeeper Exporter](https://github.com/cloudflare/kafka_zookeeper
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/kannel.md
+40
-26
@@ -89,26 +89,6 @@ Install [Kannel Exporter](https://github.com/apostvav/kannel_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/keepalived.md
+40
-26
@@ -89,26 +89,6 @@ Install [Keepalived Exporter](https://github.com/gen2brain/keepalived_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/kubernetes_cluster_cloud_cost.md
+40
-26
@@ -89,26 +89,6 @@ Install [Kubernetes Cloud Cost Exporter](https://github.com/agilestacks/korral)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/lagerist_disk_latency.md
+40
-26
@@ -89,26 +89,6 @@ Install [Lagerist Disk latency exporter](https://github.com/Svedrin/lagerist) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ldap.md
+40
-26
@@ -89,26 +89,6 @@ Install [LDAP Exporter](https://github.com/titisan/ldap_exporter) by following t
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/linode.md
+40
-26
@@ -89,26 +89,6 @@ Install [Linode Exporter](https://github.com/DazWilkin/linode-exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/loki.md
+40
-26
@@ -89,26 +89,6 @@ Install [loki](https://github.com/grafana/loki) according to its documentation.
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/lustre_metadata.md
+40
-26
@@ -89,26 +89,6 @@ Install [Cluster Exporter](https://github.com/GSI-HPC/prometheus-cluster-exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/lynis_audit_reports.md
+40
-26
@@ -89,26 +89,6 @@ Install [lynis_exporter](https://github.com/MauveSoftware/lynis_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/machbase.md
+40
-26
@@ -89,26 +89,6 @@ Install [Machbase Exporter](https://github.com/MACHBASE/prometheus-machbase-expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/maildir.md
+40
-26
@@ -89,26 +89,6 @@ Install [mailexporter](https://github.com/cherti/mailexporter) by following the
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/meilisearch.md
+40
-26
@@ -89,26 +89,6 @@ Install [Meilisearch Exporter](https://github.com/scottaglia/meilisearch_exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/memcached_community.md
+40
-26
@@ -89,26 +89,6 @@ Install [Memcached exporter](https://github.com/prometheus/memcached_exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/meraki_dashboard.md
+40
-26
@@ -89,26 +89,6 @@ Install [Meraki dashboard data exporter using API](https://github.com/TheHolm/me
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mesos.md
+40
-26
@@ -89,26 +89,6 @@ Install [Mesos exporter](http://github.com/mesosphere/mesos_exporter) by followi
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mikrotik_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [nshttpd/mikrotik-exporter, swoga/m](https://github.com/swoga/mikrotik-e
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mikrotik_routeros_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [RouterOS exporter](https://github.com/welbymcroberts/routeros_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/minecraft.md
+40
-26
@@ -89,26 +89,6 @@ Install [Minecraft Exporter](https://github.com/sladkoff/minecraft-prometheus-ex
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/modbus_protocol.md
+40
-26
@@ -89,26 +89,6 @@ Install [modbusrtu_exporter](https://github.com/dernasherbrezon/modbusrtu_export
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mogilefs.md
+40
-26
@@ -89,26 +89,6 @@ Install [MogileFS Exporter](https://github.com/KKBOX/mogilefs-exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/monnit_sensors_mqtt.md
+40
-26
@@ -89,26 +89,6 @@ Install [Monnit Sensors MQTT Exporter WIP](https://github.com/braxton9460/monnit
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mosquitto.md
+40
-26
@@ -89,26 +89,6 @@ Install [mosquitto exporter](https://github.com/sapcc/mosquitto-exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mp707_usb_thermometer.md
+40
-26
@@ -89,26 +89,6 @@ Install [MP707 exporter](https://github.com/nradchenko/mp707_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mqtt_blackbox.md
+40
-26
@@ -89,26 +89,6 @@ Install [MQTT Blackbox Exporter](https://github.com/inovex/mqtt_blackbox_exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/mtail.md
+40
-26
@@ -89,26 +89,6 @@ Install [mtail](https://github.com/google/mtail) by following the instructions m
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/naemon.md
+40
-26
@@ -89,26 +89,6 @@ Install [Naemon / Nagios Exporter](https://github.com/Griesbacher/Iapetos) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nagios.md
+40
-26
@@ -90,26 +90,6 @@ Install [Nagios exporter](https://github.com/wbollock/nagios_exporter) by follow
90
91
### Configuration
92
93
-#### File
94
-
95
-The configuration file name for this integration is `go.d/prometheus.conf`.
96
-
97
-The file format is YAML. Generally, the structure is:
98
-
99
-```yaml
100
-update_every: 1
101
-autodetection_retry: 0
102
-jobs:
103
- - name: some_name1
104
- - name: some_name1
105
-```
106
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
-
109
-```bash
110
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
-sudo ./edit-config go.d/prometheus.conf
112
-```
93
#### Options
94
95
The following options can be defined globally: update_every, autodetection_retry.
@@ -181,9 +161,43 @@ fallback_type:
161
162
</details>
163
184
-#### Examples
164
186
-##### Basic
165
+#### via UI
166
+
167
+The **prometheus** collector can be configured directly through the Netdata web interface:
168
+
169
+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.
171
+3. The **Collectors → Jobs** view opens by default.
172
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
173
+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**.
175
+
176
+
177
+#### via File
178
+
179
+The configuration file name for this integration is `go.d/prometheus.conf`.
180
+
181
+The file format is YAML. Generally, the structure is:
182
+
183
+```yaml
184
+update_every: 1
185
+autodetection_retry: 0
186
+jobs:
187
+ - name: some_name1
188
+ - name: some_name1
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).
192
+
193
+```bash
194
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
195
+sudo ./edit-config go.d/prometheus.conf
196
+```
197
+
198
+##### Examples
199
+
200
+###### Basic
201
202
> **Note**: Change the port of the monitored application on which it provides metrics.
203
@@ -196,7 +210,7 @@ jobs:
210
url: http://127.0.0.1:9090/metrics
211
212
```
199
-##### Read metrics from a file
213
+###### Read metrics from a file
214
215
An example configuration to read metrics from a file.
216
@@ -211,7 +225,7 @@ jobs:
225
```
226
</details>
227
214
-##### HTTP authentication
228
+###### HTTP authentication
229
230
> **Note**: Change the port of the monitored application on which it provides metrics.
231
@@ -230,7 +244,7 @@ jobs:
244
```
245
</details>
246
233
-##### HTTPS with self-signed certificate
247
+###### HTTPS with self-signed certificate
248
249
> **Note**: Change the port of the monitored application on which it provides metrics.
250
@@ -248,7 +262,7 @@ jobs:
262
```
263
</details>
264
251
-##### Multi-instance
265
+###### Multi-instance
266
267
> **Note**: When you define multiple jobs, their names must be unique.
268
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nature_remo_e_lite_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [Nature Remo E series Exporter](https://github.com/kenfdev/remo-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/netapp_ontap_api.md
+40
-26
@@ -89,26 +89,6 @@ Install [Netapp ONTAP API Exporter](https://github.com/sapcc/netapp-api-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/netapp_solidfire.md
+40
-26
@@ -89,26 +89,6 @@ Install [NetApp Solidfire Exporter](https://github.com/mjavier2k/solidfire-expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/netatmo_sensors.md
+40
-26
@@ -89,26 +89,6 @@ Install [Netatmo exporter](https://github.com/xperimental/netatmo-exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/netflow.md
+40
-26
@@ -89,26 +89,6 @@ Install [netflow exporter](https://github.com/paihu/netflow_exporter) by followi
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/netmeter.md
+40
-26
@@ -89,26 +89,6 @@ Install [NetMeter Exporter](https://github.com/ssbostan/netmeter-exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/new_relic.md
+40
-26
@@ -89,26 +89,6 @@ Install [New Relic exporter](https://github.com/jfindley/newrelic_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nextcloud_servers.md
+40
-26
@@ -89,26 +89,6 @@ Install [Nextcloud exporter](https://github.com/xperimental/nextcloud-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nextdns.md
+40
-26
@@ -89,26 +89,6 @@ Install [nextdns-exporter](https://github.com/raylas/nextdns-exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nftables.md
+40
-26
@@ -89,26 +89,6 @@ Install [nftables_exporter](https://github.com/Sheridan/nftables_exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nrpe_daemon.md
+40
-26
@@ -89,26 +89,6 @@ Install [NRPE exporter](https://github.com/canonical/nrpe_exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nsx-t.md
+40
-26
@@ -89,26 +89,6 @@ Install [NSX-T Exporter](https://github.com/jk8s/nsxt_exporter) by following the
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/nvml.md
+40
-26
@@ -89,26 +89,6 @@ Install [NVML exporter](https://github.com/oko/nvml-exporter-rs) by following th
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/obs_studio.md
+40
-26
@@ -89,26 +89,6 @@ Install [OBS Studio Exporter](https://github.com/lukegb/obs_studio_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/odbc.md
+40
-26
@@ -89,26 +89,6 @@ Install [ODBC Exporter](https://github.com/MACHBASE/prometheus-odbc-exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/open_vswitch.md
+40
-26
@@ -89,26 +89,6 @@ Install [Open vSwitch Exporter](https://github.com/digitalocean/openvswitch_expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openhab.md
+40
-26
@@ -89,26 +89,6 @@ Install [OpenHAB exporter](https://github.com/pdreker/openhab_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openldap_community.md
+40
-26
@@ -89,26 +89,6 @@ Install [OpenLDAP Metrics Exporter](https://github.com/tomcz/openldap_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openrc.md
+40
-26
@@ -89,26 +89,6 @@ Install [openrc-exporter](https://git.sr.ht/~tomleb/openrc-exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openrct2.md
+40
-26
@@ -89,26 +89,6 @@ Install [OpenRCT2 Prometheus Exporter](https://github.com/terinjokes/openrct2-pr
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openroadm_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [OpenROADM NETCONF Exporter WIP](https://github.com/utdal/openroadm_expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openstack.md
+40
-26
@@ -89,26 +89,6 @@ Install [Openstack exporter](https://github.com/CanonicalLtd/prometheus-openstac
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openvas.md
+40
-26
@@ -89,26 +89,6 @@ Install [OpenVAS exporter](https://github.com/ModeClearCode/openvas_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/openweathermap.md
+40
-26
@@ -89,26 +89,6 @@ Install [OpenWeatherMap Exporter](https://github.com/Tenzer/openweathermap-expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/oracle_db_community.md
+40
-26
@@ -89,26 +89,6 @@ Install [Oracle DB Exporter](https://github.com/iamseth/oracledb_exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/otrs.md
+40
-26
@@ -89,26 +89,6 @@ Install [OTRS Exporter](https://github.com/JulianDroste/otrs_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/patroni.md
+40
-26
@@ -89,26 +89,6 @@ Install [Patroni Exporter](https://github.com/gopaytech/patroni_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/personal_weather_station.md
+40
-26
@@ -89,26 +89,6 @@ Install [Personal Weather Station Exporter](https://github.com/JohnOrthoefer/pws
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/pgbackrest.md
+40
-26
@@ -89,26 +89,6 @@ Install [pgBackRest Exporter](https://github.com/woblerr/pgbackrest_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/pgpool-ii.md
+40
-26
@@ -89,26 +89,6 @@ Install [Pgpool-II Exporter](https://github.com/pgpool/pgpool2_exporter) by foll
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/philips_hue.md
+40
-26
@@ -89,26 +89,6 @@ Install [Philips Hue Exporter](https://github.com/aexel90/hue_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/pimoroni_enviro+.md
+40
-26
@@ -89,26 +89,6 @@ Install [Pimoroni Enviro+ Exporter](https://github.com/terradolor/prometheus-env
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/pingdom.md
+40
-26
@@ -89,26 +89,6 @@ Install [Pingdom Exporter](https://github.com/veepee-oss/pingdom_exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/podman.md
+40
-26
@@ -89,26 +89,6 @@ Install [PODMAN exporter](https://github.com/containers/prometheus-podman-export
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/powerpal_devices.md
+40
-26
@@ -89,26 +89,6 @@ Install [Powerpal Exporter](https://github.com/aashley/powerpal_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/proftpd.md
+40
-26
@@ -89,26 +89,6 @@ Install [ProFTPD Exporter](https://github.com/transnano/proftpd_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/prometheus_endpoint.md
+40
-26
@@ -85,26 +85,6 @@ No action required.
85
86
### Configuration
87
88
-#### File
89
-
90
-The configuration file name for this integration is `go.d/prometheus.conf`.
91
-
92
-The file format is YAML. Generally, the structure is:
93
-
94
-```yaml
95
-update_every: 1
96
-autodetection_retry: 0
97
-jobs:
98
- - name: some_name1
99
- - name: some_name1
100
-```
101
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
-
104
-```bash
105
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
106
-sudo ./edit-config go.d/prometheus.conf
107
-```
88
#### Options
89
90
The following options can be defined globally: update_every, autodetection_retry.
@@ -176,9 +156,43 @@ fallback_type:
156
157
</details>
158
179
-#### Examples
159
181
-##### Basic
160
+#### via UI
161
+
162
+The **prometheus** collector can be configured directly through the Netdata web interface:
163
+
164
+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.
166
+3. The **Collectors → Jobs** view opens by default.
167
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
168
+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**.
170
+
171
+
172
+#### via File
173
+
174
+The configuration file name for this integration is `go.d/prometheus.conf`.
175
+
176
+The file format is YAML. Generally, the structure is:
177
+
178
+```yaml
179
+update_every: 1
180
+autodetection_retry: 0
181
+jobs:
182
+ - name: some_name1
183
+ - name: some_name1
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).
187
+
188
+```bash
189
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
190
+sudo ./edit-config go.d/prometheus.conf
191
+```
192
+
193
+##### Examples
194
+
195
+###### Basic
196
197
> **Note**: Change the port of the monitored application on which it provides metrics.
198
@@ -191,7 +205,7 @@ jobs:
205
url: http://127.0.0.1:9090/metrics
206
207
```
194
-##### Read metrics from a file
208
+###### Read metrics from a file
209
210
An example configuration to read metrics from a file.
211
@@ -206,7 +220,7 @@ jobs:
220
```
221
</details>
222
209
-##### HTTP authentication
223
+###### HTTP authentication
224
225
> **Note**: Change the port of the monitored application on which it provides metrics.
226
@@ -225,7 +239,7 @@ jobs:
239
```
240
</details>
241
228
-##### HTTPS with self-signed certificate
242
+###### HTTPS with self-signed certificate
243
244
> **Note**: Change the port of the monitored application on which it provides metrics.
245
@@ -243,7 +257,7 @@ jobs:
257
```
258
</details>
259
246
-##### Multi-instance
260
+###### Multi-instance
261
262
> **Note**: When you define multiple jobs, their names must be unique.
263
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/proxmox_ve.md
+40
-26
@@ -89,26 +89,6 @@ Install [Proxmox VE Exporter](https://github.com/prometheus-pve/prometheus-pve-e
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/radio_thermostat.md
+40
-26
@@ -89,26 +89,6 @@ Install [Radio Thermostat Exporter](https://github.com/andrewlow/radio-thermosta
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/radius.md
+40
-26
@@ -89,26 +89,6 @@ Install [RADIUS exporter](https://github.com/devon-mar/radius-exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/rancher.md
+40
-26
@@ -89,26 +89,6 @@ Install [Rancher Exporter](https://github.com/infinityworksltd/prometheus-ranche
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/raritan_pdu.md
+40
-26
@@ -89,26 +89,6 @@ Install [Raritan PDU Exporter](https://github.com/psyinfra/prometheus-raritan-pd
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/redis_queue.md
+40
-26
@@ -89,26 +89,6 @@ Install [Python RQ Exporter](https://github.com/mdawar/rq-exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ripe_atlas.md
+40
-26
@@ -89,26 +89,6 @@ Install [RIPE Atlas Exporter](https://github.com/czerwonk/atlas_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sabnzbd.md
+40
-26
@@ -89,26 +89,6 @@ Install [SABnzbd Exporter](https://github.com/msroest/sabnzbd_exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/salicru_eqx_inverter.md
+40
-26
@@ -89,26 +89,6 @@ Install [Salicru EQX inverter](https://github.com/alejandroscf/prometheus_salicr
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sense_energy.md
+40
-26
@@ -89,26 +89,6 @@ Install [Sense Energy exporter](https://github.com/ejsuncy/sense_energy_promethe
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sentry.md
+40
-26
@@ -89,26 +89,6 @@ Install [Sentry Exporter](https://github.com/snakecharmer/sentry_exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/servertech.md
+40
-26
@@ -89,26 +89,6 @@ Install [ServerTech Exporter](https://github.com/tynany/servertech_exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/shell_command.md
+40
-26
@@ -89,26 +89,6 @@ Install [Command runner exporter](https://github.com/tomwilkie/prom-run) by foll
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/shelly_humidity_sensor.md
+40
-26
@@ -89,26 +89,6 @@ Install [Shelly Exporter](https://github.com/aexel90/shelly_exporter) by followi
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sia.md
+40
-26
@@ -89,26 +89,6 @@ Install [Sia Exporter](https://github.com/tbenz9/sia_exporter) by following the
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/siemens_s7_plc.md
+40
-26
@@ -89,26 +89,6 @@ Install [Siemens S7 PLC exporter](https://github.com/MarcusCalidus/s7-plc-export
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/site_24x7.md
+40
-26
@@ -89,26 +89,6 @@ Install [site24x7 Exporter](https://github.com/svenstaro/site24x7_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/slurm.md
+40
-26
@@ -89,26 +89,6 @@ Install [slurm exporter](https://github.com/vpenso/prometheus-slurm-exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sma_inverters.md
+40
-26
@@ -89,26 +89,6 @@ Install [sma-exporter](https://github.com/dr0ps/sma_inverter_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/smart_meters_sml.md
+40
-26
@@ -89,26 +89,6 @@ Install [SML Exporter](https://github.com/mweinelt/sml-exporter) by following th
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/smartrg_808ac_cable_modem.md
+40
-26
@@ -89,26 +89,6 @@ Install [smartrg808ac_exporter](https://github.com/AdamIsrael/smartrg808ac_expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/softether_vpn_server.md
+40
-26
@@ -89,26 +89,6 @@ Install [SoftEther Exporter](https://github.com/dalance/softether_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/solar_logging_stick.md
+40
-26
@@ -89,26 +89,6 @@ Install [Solar logging stick exporter](https://gitlab.com/bhavin192/lsx-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/solaredge_inverters.md
+40
-26
@@ -89,26 +89,6 @@ Install [SolarEdge Exporter](https://github.com/dave92082/SolarEdge-Exporter) by
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/solis_ginlong_5g_inverters.md
+40
-26
@@ -89,26 +89,6 @@ Install [Solis Exporter](https://github.com/candlerb/solis_exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sonic_nos.md
+40
-26
@@ -89,26 +89,6 @@ Install [SONiC Exporter](https://github.com/kamelnetworks/sonic_exporter) by fol
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/spacelift.md
+40
-26
@@ -89,26 +89,6 @@ Install [Spacelift Exporter](https://github.com/spacelift-io/prometheus-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/speedify_cli.md
+40
-26
@@ -89,26 +89,6 @@ Install [Speedify Exporter](https://github.com/willshen/speedify_exporter) by fo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sphinx.md
+40
-26
@@ -89,26 +89,6 @@ Install [Sphinx Exporter](https://github.com/foxdalas/sphinx_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sql_database_agnostic.md
+40
-26
@@ -89,26 +89,6 @@ Install [SQL Exporter](https://github.com/free/sql_exporter) by following the in
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ssh.md
+40
-26
@@ -89,26 +89,6 @@ Install [SSH Exporter](https://github.com/Nordstrom/ssh_exporter) by following t
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ssl_certificate.md
+40
-26
@@ -89,26 +89,6 @@ Install [SSL Certificate exporter](https://github.com/ribbybibby/ssl_exporter) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/starlink_spacex.md
+40
-26
@@ -89,26 +89,6 @@ Install [Starlink Exporter (SpaceX)](https://github.com/danopstech/starlink_expo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/starwind_vsan_vsphere_edition.md
+40
-26
@@ -89,26 +89,6 @@ Install [Starwind vSAN Exporter](https://github.com/evoicefire/starwind-vsan-exp
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/statuspage.md
+40
-26
@@ -89,26 +89,6 @@ Install [StatusPage Exporter](https://github.com/vladvasiliu/statuspage-exporter
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/steam.md
+40
-26
@@ -89,26 +89,6 @@ Install [A2S Exporter](https://github.com/armsnyder/a2s-exporter) by following t
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/storidge.md
+40
-26
@@ -89,26 +89,6 @@ Install [Storidge exporter](https://github.com/Storidge/cio-user-docs/blob/maste
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/stream.md
+40
-26
@@ -89,26 +89,6 @@ Install [Stream exporter](https://github.com/carlpett/stream_exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/strongswan.md
+40
-26
@@ -89,26 +89,6 @@ Install [strongSwan/IPSec/vici Exporter](https://github.com/jlti-dev/ipsec_expor
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sunspec_solar_energy.md
+40
-26
@@ -89,26 +89,6 @@ Install [Sunspec Solar Energy Exporter](https://github.com/inosion/prometheus-su
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/suricata.md
+40
-26
@@ -89,26 +89,6 @@ Install [Suricata Exporter](https://github.com/corelight/suricata_exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/synology_activebackup.md
+40
-26
@@ -89,26 +89,6 @@ Install [Synology ActiveBackup Exporter](https://github.com/codemonauts/activeba
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/sysload.md
+40
-26
@@ -89,26 +89,6 @@ Install [Sysload Exporter](https://github.com/egmc/sysload_exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/t-rex_nvidia_gpu_miner.md
+40
-26
@@ -89,26 +89,6 @@ Install [T-Rex NVIDIA GPU Miner Exporter](https://github.com/dennisstritzke/trex
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tacacs.md
+40
-26
@@ -89,26 +89,6 @@ Install [TACACS Exporter](https://github.com/devon-mar/tacacs-exporter) by follo
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tado_smart_heating_solution.md
+40
-26
@@ -89,26 +89,6 @@ Install [Tado Exporter](https://github.com/eko/tado-exporter) by following the i
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tankerkoenig_api.md
+40
-26
@@ -89,26 +89,6 @@ Install [Tankerknig API Exporter](https://github.com/lukasmalkmus/tankerkoenig_e
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tesla_powerwall.md
+40
-26
@@ -89,26 +89,6 @@ Install [Tesla Powerwall Exporter](https://github.com/foogod/powerwall_exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tesla_vehicle.md
+40
-26
@@ -89,26 +89,6 @@ Install [Tesla exporter](https://github.com/wywywywy/tesla-prometheus-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tesla_wall_connector.md
+40
-26
@@ -89,26 +89,6 @@ Install [Tesla Wall Connector Exporter](https://github.com/benclapp/tesla_wall_c
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/tp-link_p110.md
+40
-26
@@ -89,26 +89,6 @@ Install [TP-Link P110 Exporter](https://github.com/ijohanne/prometheus-tplink-p1
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/traceroute.md
+40
-26
@@ -89,26 +89,6 @@ Install [traceroute exporter](https://github.com/jeanfabrice/prometheus-tcptrace
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/twincat_ads_web_service.md
+40
-26
@@ -89,26 +89,6 @@ Install [TwinCAT ADS Web Service exporter](https://github.com/MarcusCalidus/twin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/twitch.md
+40
-26
@@ -89,26 +89,6 @@ Install [Twitch exporter](https://github.com/damoun/twitch_exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/ubiquiti_ufiber_olt.md
+40
-26
@@ -89,26 +89,6 @@ Install [ufiber-exporter](https://github.com/swoga/ufiber-exporter) by following
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/uptimerobot.md
+40
-26
@@ -89,26 +89,6 @@ Install [Uptimerobot Exporter](https://github.com/wosc/prometheus-uptimerobot) b
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/vault_pki.md
+40
-26
@@ -89,26 +89,6 @@ Install [Vault PKI Exporter](https://github.com/aarnaud/vault-pki-exporter) by f
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/vertica.md
+40
-26
@@ -89,26 +89,6 @@ Install [vertica-prometheus-exporter](https://github.com/vertica/vertica-prometh
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/vscode.md
+40
-26
@@ -89,26 +89,6 @@ Install [VSCode Exporter](https://github.com/guicaulada/vscode-exporter) by foll
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/warp10.md
+40
-26
@@ -89,26 +89,6 @@ Install [Warp10 Exporter](https://github.com/centreon/warp10-sensision-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/xiaomi_mi_flora.md
+40
-26
@@ -89,26 +89,6 @@ Install [MiFlora / Flower Care Exporter](https://github.com/xperimental/flowerca
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/xmpp_server.md
+40
-26
@@ -89,26 +89,6 @@ Install [XMPP Server Exporter](https://github.com/horazont/xmpp-blackbox-exporte
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/yourls_url_shortener.md
+40
-26
@@ -89,26 +89,6 @@ Install [YOURLS exporter](https://github.com/just1not2/prometheus-exporter-yourl
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/zerto.md
+40
-26
@@ -89,26 +89,6 @@ Install [Zerto Exporter](https://github.com/claranet/zerto-exporter) by followin
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/zulip.md
+40
-26
@@ -89,26 +89,6 @@ Install [Zulip Exporter](https://github.com/brokenpip3/zulip-exporter) by follow
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/prometheus/integrations/zyxel_gs1200-8.md
+40
-26
@@ -89,26 +89,6 @@ Install [Zyxel GS1200 Exporter](https://github.com/robinelfrink/gs1200-exporter)
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/prometheus.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/prometheus.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -180,9 +160,43 @@ fallback_type:
160
161
</details>
162
183
-#### Examples
163
185
-##### Basic
164
+#### via UI
165
+
166
+The **prometheus** collector can be configured directly through the Netdata web interface:
167
+
168
+1. Go to **Nodes**.
169
+2. Select the node **where you want the prometheus data-collection job to run** and click the :gear: (**Configure this node**). This node will be responsible for collecting metrics.
170
+3. The **Collectors → Jobs** view opens by default.
171
+4. In the Search box, type _prometheus_ (or scroll the list) to locate the **prometheus** collector.
172
+5. Click the **+** next to the **prometheus** collector to add a new job.
173
+6. Fill in the job fields, then **Test** the configuration and **Submit**.
174
+
175
+
176
+#### via File
177
+
178
+The configuration file name for this integration is `go.d/prometheus.conf`.
179
+
180
+The file format is YAML. Generally, the structure is:
181
+
182
+```yaml
183
+update_every: 1
184
+autodetection_retry: 0
185
+jobs:
186
+ - name: some_name1
187
+ - name: some_name1
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).
191
+
192
+```bash
193
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
194
+sudo ./edit-config go.d/prometheus.conf
195
+```
196
+
197
+##### Examples
198
+
199
+###### Basic
200
201
> **Note**: Change the port of the monitored application on which it provides metrics.
202
@@ -195,7 +209,7 @@ jobs:
209
url: http://127.0.0.1:9090/metrics
210
211
```
198
-##### Read metrics from a file
212
+###### Read metrics from a file
213
214
An example configuration to read metrics from a file.
215
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### HTTP authentication
227
+###### HTTP authentication
228
229
> **Note**: Change the port of the monitored application on which it provides metrics.
230
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### HTTPS with self-signed certificate
246
+###### HTTPS with self-signed certificate
247
248
> **Note**: Change the port of the monitored application on which it provides metrics.
249
@@ -247,7 +261,7 @@ jobs:
261
```
262
</details>
263
250
-##### Multi-instance
264
+###### Multi-instance
265
266
> **Note**: When you define multiple jobs, their names must be unique.
267
> **Note**: Change the port of the monitored application on which it provides metrics.
src/go/plugin/go.d/collector/proxysql/integrations/proxysql.md
+34
-20
@@ -165,7 +165,36 @@ No action required.
165
166
### Configuration
167
168
-#### File
168
+#### Options
169
+
170
+The following options can be defined globally: update_every, autodetection_retry.
171
+
172
+
173
+<details open><summary>Config options</summary>
174
+
175
+| Name | Description | Default | Required |
176
+|:----|:-----------|:-------|:--------:|
177
+| update_every | Data collection frequency. | 1 | no |
178
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
179
+| dsn | Data Source Name. See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | stats:stats@tcp(127.0.0.1:6032)/ | yes |
180
+| timeout | Query timeout in seconds. | 1 | no |
181
+
182
+</details>
183
+
184
+
185
+#### via UI
186
+
187
+The **proxysql** collector can be configured directly through the Netdata web interface:
188
+
189
+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.
191
+3. The **Collectors → Jobs** view opens by default.
192
+4. In the Search box, type _proxysql_ (or scroll the list) to locate the **proxysql** collector.
193
+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**.
195
+
196
+
197
+#### via File
198
199
The configuration file name for this integration is `go.d/proxysql.conf`.
200
@@ -185,25 +214,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
214
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
215
sudo ./edit-config go.d/proxysql.conf
216
```
188
-#### Options
189
-
190
-The following options can be defined globally: update_every, autodetection_retry.
191
-
192
-
193
-<details open><summary>Config options</summary>
194
-
195
-| Name | Description | Default | Required |
196
-|:----|:-----------|:-------|:--------:|
197
-| update_every | Data collection frequency. | 1 | no |
198
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
199
-| dsn | Data Source Name. See [DSN syntax](https://github.com/go-sql-driver/mysql#dsn-data-source-name). | stats:stats@tcp(127.0.0.1:6032)/ | yes |
200
-| timeout | Query timeout in seconds. | 1 | no |
201
-
202
-</details>
217
204
-#### Examples
218
+##### Examples
219
206
-##### TCP socket
220
+###### TCP socket
221
222
An example configuration.
223
@@ -217,7 +231,7 @@ jobs:
231
```
232
</details>
233
220
-##### my.cnf
234
+###### my.cnf
235
236
An example configuration.
237
@@ -231,7 +245,7 @@ jobs:
245
```
246
</details>
247
234
-##### Multi-instance
248
+###### Multi-instance
249
250
> **Note**: When you define multiple jobs, their names must be unique.
251
src/go/plugin/go.d/collector/pulsar/integrations/apache_pulsar.md
+39
-25
@@ -143,26 +143,6 @@ No action required.
143
144
### Configuration
145
146
-#### File
147
-
148
-The configuration file name for this integration is `go.d/pulsar.conf`.
149
-
150
-The file format is YAML. Generally, the structure is:
151
-
152
-```yaml
153
-update_every: 1
154
-autodetection_retry: 0
155
-jobs:
156
- - name: some_name1
157
- - name: some_name1
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).
161
-
162
-```bash
163
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
164
-sudo ./edit-config go.d/pulsar.conf
165
-```
146
#### Options
147
148
The following options can be defined globally: update_every, autodetection_retry.
@@ -192,9 +172,43 @@ The following options can be defined globally: update_every, autodetection_retry
172
173
</details>
174
195
-#### Examples
175
197
-##### Basic
176
+#### via UI
177
+
178
+The **pulsar** collector can be configured directly through the Netdata web interface:
179
+
180
+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.
182
+3. The **Collectors → Jobs** view opens by default.
183
+4. In the Search box, type _pulsar_ (or scroll the list) to locate the **pulsar** collector.
184
+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**.
186
+
187
+
188
+#### via File
189
+
190
+The configuration file name for this integration is `go.d/pulsar.conf`.
191
+
192
+The file format is YAML. Generally, the structure is:
193
+
194
+```yaml
195
+update_every: 1
196
+autodetection_retry: 0
197
+jobs:
198
+ - name: some_name1
199
+ - name: some_name1
200
+```
201
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
202
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
203
+
204
+```bash
205
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
206
+sudo ./edit-config go.d/pulsar.conf
207
+```
208
+
209
+##### Examples
210
+
211
+###### Basic
212
213
A basic example configuration.
214
@@ -204,7 +218,7 @@ jobs:
218
url: http://127.0.0.1:8080/metrics
219
220
```
207
-##### HTTP authentication
221
+###### HTTP authentication
222
223
Basic HTTP authentication.
224
@@ -220,7 +234,7 @@ jobs:
234
```
235
</details>
236
223
-##### HTTPS with self-signed certificate
237
+###### HTTPS with self-signed certificate
238
239
Do not validate server certificate chain and hostname.
240
@@ -236,7 +250,7 @@ jobs:
250
```
251
</details>
252
239
-##### Multi-instance
253
+###### Multi-instance
254
255
> **Note**: When you define multiple jobs, their names must be unique.
256
src/go/plugin/go.d/collector/puppet/integrations/puppet.md
+37
-23
@@ -89,26 +89,6 @@ No action required.
89
90
### Configuration
91
92
-#### File
93
-
94
-The configuration file name for this integration is `go.d/puppet.conf`.
95
-
96
-The file format is YAML. Generally, the structure is:
97
-
98
-```yaml
99
-update_every: 1
100
-autodetection_retry: 0
101
-jobs:
102
- - name: some_name1
103
- - name: some_name1
104
-```
105
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
-
108
-```bash
109
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
110
-sudo ./edit-config go.d/puppet.conf
111
-```
92
#### Options
93
94
The following options can be defined globally: update_every, autodetection_retry.
@@ -136,9 +116,43 @@ The following options can be defined globally: update_every, autodetection_retry
116
117
</details>
118
139
-#### Examples
119
141
-##### Basic with self-signed certificate
120
+#### via UI
121
+
122
+The **puppet** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _puppet_ (or scroll the list) to locate the **puppet** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `go.d/puppet.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+jobs:
142
+ - name: some_name1
143
+ - name: some_name1
144
+```
145
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
146
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+
148
+```bash
149
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
+sudo ./edit-config go.d/puppet.conf
151
+```
152
+
153
+##### Examples
154
+
155
+###### Basic with self-signed certificate
156
157
Puppet with self-signed TLS certificate.
158
@@ -153,7 +167,7 @@ jobs:
167
```
168
</details>
169
156
-##### Multi-instance
170
+###### Multi-instance
171
172
> **Note**: When you define multiple jobs, their names must be unique.
173
src/go/plugin/go.d/collector/rabbitmq/integrations/rabbitmq.md
+38
-24
@@ -205,26 +205,6 @@ To enable see [Management Plugin](https://www.rabbitmq.com/management.html#getti
205
206
### Configuration
207
208
-#### File
209
-
210
-The configuration file name for this integration is `go.d/rabbitmq.conf`.
211
-
212
-The file format is YAML. Generally, the structure is:
213
-
214
-```yaml
215
-update_every: 1
216
-autodetection_retry: 0
217
-jobs:
218
- - name: some_name1
219
- - name: some_name1
220
-```
221
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
222
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
223
-
224
-```bash
225
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
226
-sudo ./edit-config go.d/rabbitmq.conf
227
-```
208
#### Options
209
210
The following options can be defined globally: update_every, autodetection_retry.
@@ -255,9 +235,43 @@ The following options can be defined globally: update_every, autodetection_retry
235
236
</details>
237
258
-#### Examples
238
260
-##### Basic
239
+#### via UI
240
+
241
+The **rabbitmq** collector can be configured directly through the Netdata web interface:
242
+
243
+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.
245
+3. The **Collectors → Jobs** view opens by default.
246
+4. In the Search box, type _rabbitmq_ (or scroll the list) to locate the **rabbitmq** collector.
247
+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**.
249
+
250
+
251
+#### via File
252
+
253
+The configuration file name for this integration is `go.d/rabbitmq.conf`.
254
+
255
+The file format is YAML. Generally, the structure is:
256
+
257
+```yaml
258
+update_every: 1
259
+autodetection_retry: 0
260
+jobs:
261
+ - name: some_name1
262
+ - name: some_name1
263
+```
264
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
265
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
266
+
267
+```bash
268
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
269
+sudo ./edit-config go.d/rabbitmq.conf
270
+```
271
+
272
+##### Examples
273
+
274
+###### Basic
275
276
An example configuration.
277
@@ -271,7 +285,7 @@ jobs:
285
```
286
</details>
287
274
-##### Basic HTTP auth
288
+###### Basic HTTP auth
289
290
Local server with basic HTTP authentication.
291
@@ -287,7 +301,7 @@ jobs:
301
```
302
</details>
303
290
-##### Multi-instance
304
+###### Multi-instance
305
306
> **Note**: When you define multiple jobs, their names must be unique.
307
src/go/plugin/go.d/collector/redis/integrations/redis.md
+39
-25
@@ -123,26 +123,6 @@ No action required.
123
124
### Configuration
125
126
-#### File
127
-
128
-The configuration file name for this integration is `go.d/redis.conf`.
129
-
130
-The file format is YAML. Generally, the structure is:
131
-
132
-```yaml
133
-update_every: 1
134
-autodetection_retry: 0
135
-jobs:
136
- - name: some_name1
137
- - name: some_name1
138
-```
139
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
140
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
141
-
142
-```bash
143
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
144
-sudo ./edit-config go.d/redis.conf
145
-```
126
#### Options
127
128
The following options can be defined globally: update_every, autodetection_retry.
@@ -165,9 +145,43 @@ The following options can be defined globally: update_every, autodetection_retry
145
146
</details>
147
168
-#### Examples
148
170
-##### TCP socket
149
+#### via UI
150
+
151
+The **redis** collector can be configured directly through the Netdata web interface:
152
+
153
+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.
155
+3. The **Collectors → Jobs** view opens by default.
156
+4. In the Search box, type _redis_ (or scroll the list) to locate the **redis** collector.
157
+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**.
159
+
160
+
161
+#### via File
162
+
163
+The configuration file name for this integration is `go.d/redis.conf`.
164
+
165
+The file format is YAML. Generally, the structure is:
166
+
167
+```yaml
168
+update_every: 1
169
+autodetection_retry: 0
170
+jobs:
171
+ - name: some_name1
172
+ - name: some_name1
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).
176
+
177
+```bash
178
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
179
+sudo ./edit-config go.d/redis.conf
180
+```
181
+
182
+##### Examples
183
+
184
+###### TCP socket
185
186
An example configuration.
187
@@ -181,7 +195,7 @@ jobs:
195
```
196
</details>
197
184
-##### Unix socket
198
+###### Unix socket
199
200
An example configuration.
201
@@ -195,7 +209,7 @@ jobs:
209
```
210
</details>
211
198
-##### TCP socket with password
212
+###### TCP socket with password
213
214
An example configuration.
215
@@ -209,7 +223,7 @@ jobs:
223
```
224
</details>
225
212
-##### Multi-instance
226
+###### Multi-instance
227
228
> **Note**: When you define multiple jobs, their names must be unique.
229
src/go/plugin/go.d/collector/rethinkdb/integrations/rethinkdb.md
+36
-22
@@ -109,7 +109,38 @@ No action required.
109
110
### Configuration
111
112
-#### File
112
+#### Options
113
+
114
+The following options can be defined globally: update_every, autodetection_retry.
115
+
116
+
117
+<details open><summary>Config options</summary>
118
+
119
+| Name | Description | Default | Required |
120
+|:----|:-----------|:-------|:--------:|
121
+| update_every | Data collection frequency. | 1 | no |
122
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
123
+| address | The IP address and port where the RethinkDB service listens for connections. | 127.0.0.1:28015 | yes |
124
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
125
+| username | Username used for authentication. | | no |
126
+| password | Password used for authentication. | | no |
127
+
128
+</details>
129
+
130
+
131
+#### via UI
132
+
133
+The **rethinkdb** collector can be configured directly through the Netdata web interface:
134
+
135
+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.
137
+3. The **Collectors → Jobs** view opens by default.
138
+4. In the Search box, type _rethinkdb_ (or scroll the list) to locate the **rethinkdb** collector.
139
+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**.
141
+
142
+
143
+#### via File
144
145
The configuration file name for this integration is `go.d/rethinkdb.conf`.
146
@@ -129,27 +160,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
160
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
161
sudo ./edit-config go.d/rethinkdb.conf
162
```
132
-#### Options
133
-
134
-The following options can be defined globally: update_every, autodetection_retry.
135
-
136
-
137
-<details open><summary>Config options</summary>
138
-
139
-| Name | Description | Default | Required |
140
-|:----|:-----------|:-------|:--------:|
141
-| update_every | Data collection frequency. | 1 | no |
142
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
143
-| address | The IP address and port where the RethinkDB service listens for connections. | 127.0.0.1:28015 | yes |
144
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
145
-| username | Username used for authentication. | | no |
146
-| password | Password used for authentication. | | no |
147
-
148
-</details>
163
150
-#### Examples
164
+##### Examples
165
152
-##### Basic
166
+###### Basic
167
168
A basic example configuration.
169
@@ -163,7 +177,7 @@ jobs:
177
```
178
</details>
179
166
-##### With authentication
180
+###### With authentication
181
182
An example configuration with authentication.
183
@@ -179,7 +193,7 @@ jobs:
193
```
194
</details>
195
182
-##### Multi-instance
196
+###### Multi-instance
197
198
> **Note**: When you define multiple jobs, their names must be unique.
199
src/go/plugin/go.d/collector/riakkv/integrations/riak_kv.md
+39
-25
@@ -113,26 +113,6 @@ See the RiakKV [configuration reference](https://docs.riak.com/riak/kv/2.2.3/dev
113
114
### Configuration
115
116
-#### File
117
-
118
-The configuration file name for this integration is `go.d/riakkv.conf`.
119
-
120
-The file format is YAML. Generally, the structure is:
121
-
122
-```yaml
123
-update_every: 1
124
-autodetection_retry: 0
125
-jobs:
126
- - name: some_name1
127
- - name: some_name1
128
-```
129
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
130
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
131
-
132
-```bash
133
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
134
-sudo ./edit-config go.d/riakkv.conf
135
-```
116
#### Options
117
118
The following options can be defined globally: update_every, autodetection_retry.
@@ -162,9 +142,43 @@ The following options can be defined globally: update_every, autodetection_retry
142
143
</details>
144
165
-#### Examples
145
167
-##### Basic
146
+#### via UI
147
+
148
+The **riakkv** collector can be configured directly through the Netdata web interface:
149
+
150
+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.
152
+3. The **Collectors → Jobs** view opens by default.
153
+4. In the Search box, type _riakkv_ (or scroll the list) to locate the **riakkv** collector.
154
+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**.
156
+
157
+
158
+#### via File
159
+
160
+The configuration file name for this integration is `go.d/riakkv.conf`.
161
+
162
+The file format is YAML. Generally, the structure is:
163
+
164
+```yaml
165
+update_every: 1
166
+autodetection_retry: 0
167
+jobs:
168
+ - name: some_name1
169
+ - name: some_name1
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).
173
+
174
+```bash
175
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
176
+sudo ./edit-config go.d/riakkv.conf
177
+```
178
+
179
+##### Examples
180
+
181
+###### Basic
182
183
A basic example configuration.
184
@@ -174,7 +188,7 @@ jobs:
188
url: http://127.0.0.1:8098/stats
189
190
```
177
-##### HTTP authentication
191
+###### HTTP authentication
192
193
Basic HTTP authentication.
194
@@ -190,7 +204,7 @@ jobs:
204
```
205
</details>
206
193
-##### HTTPS with self-signed certificate
207
+###### HTTPS with self-signed certificate
208
209
With enabled HTTPS and self-signed certificate.
210
@@ -205,7 +219,7 @@ jobs:
219
```
220
</details>
221
208
-##### Multi-instance
222
+###### Multi-instance
223
224
> **Note**: When you define multiple jobs, their names must be unique.
225
src/go/plugin/go.d/collector/rspamd/integrations/rspamd.md
+38
-24
@@ -88,26 +88,6 @@ No action required.
88
89
### Configuration
90
91
-#### File
92
-
93
-The configuration file name for this integration is `go.d/rspamd.conf`.
94
-
95
-The file format is YAML. Generally, the structure is:
96
-
97
-```yaml
98
-update_every: 1
99
-autodetection_retry: 0
100
-jobs:
101
- - name: some_name1
102
- - name: some_name1
103
-```
104
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
-
107
-```bash
108
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
109
-sudo ./edit-config go.d/rspamd.conf
110
-```
91
#### Options
92
93
The following options can be defined globally: update_every, autodetection_retry.
@@ -137,9 +117,43 @@ The following options can be defined globally: update_every, autodetection_retry
117
118
</details>
119
140
-#### Examples
120
142
-##### Basic
121
+#### via UI
122
+
123
+The **rspamd** collector can be configured directly through the Netdata web interface:
124
+
125
+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.
127
+3. The **Collectors → Jobs** view opens by default.
128
+4. In the Search box, type _rspamd_ (or scroll the list) to locate the **rspamd** collector.
129
+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**.
131
+
132
+
133
+#### via File
134
+
135
+The configuration file name for this integration is `go.d/rspamd.conf`.
136
+
137
+The file format is YAML. Generally, the structure is:
138
+
139
+```yaml
140
+update_every: 1
141
+autodetection_retry: 0
142
+jobs:
143
+ - name: some_name1
144
+ - name: some_name1
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).
148
+
149
+```bash
150
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
+sudo ./edit-config go.d/rspamd.conf
152
+```
153
+
154
+##### Examples
155
+
156
+###### Basic
157
158
A basic example configuration.
159
@@ -149,7 +163,7 @@ jobs:
163
url: http://127.0.0.1:11334
164
165
```
152
-##### HTTP authentication
166
+###### HTTP authentication
167
168
Basic HTTP authentication.
169
@@ -165,7 +179,7 @@ jobs:
179
```
180
</details>
181
168
-##### Multi-instance
182
+###### Multi-instance
183
184
> **Note**: When you define multiple jobs, their names must be unique.
185
src/go/plugin/go.d/collector/samba/integrations/samba.md
+30
-16
@@ -132,7 +132,34 @@ There are no alerts configured by default for this integration.
132
133
### Configuration
134
135
-#### File
135
+#### Options
136
+
137
+The following options can be defined globally: update_every.
138
+
139
+
140
+<details open><summary>Config options</summary>
141
+
142
+| Name | Description | Default | Required |
143
+|:----|:-----------|:-------|:--------:|
144
+| update_every | Data collection frequency. | 10 | no |
145
+| timeout | smbstatus binary execution timeout. | 2 | no |
146
+
147
+</details>
148
+
149
+
150
+#### via UI
151
+
152
+The **samba** collector can be configured directly through the Netdata web interface:
153
+
154
+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.
156
+3. The **Collectors → Jobs** view opens by default.
157
+4. In the Search box, type _samba_ (or scroll the list) to locate the **samba** collector.
158
+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**.
160
+
161
+
162
+#### via File
163
164
The configuration file name for this integration is `go.d/samba.conf`.
165
@@ -152,23 +179,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
179
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
180
sudo ./edit-config go.d/samba.conf
181
```
155
-#### Options
156
-
157
-The following options can be defined globally: update_every.
158
-
159
-
160
-<details open><summary>Config options</summary>
161
-
162
-| Name | Description | Default | Required |
163
-|:----|:-----------|:-------|:--------:|
164
-| update_every | Data collection frequency. | 10 | no |
165
-| timeout | smbstatus binary execution timeout. | 2 | no |
166
-
167
-</details>
182
169
-#### Examples
183
+##### Examples
184
171
-##### Custom update_every
185
+###### Custom update_every
186
187
Allows you to override the default data collection interval.
188
src/go/plugin/go.d/collector/scaleio/integrations/dell_emc_scaleio.md
+37
-23
@@ -138,26 +138,6 @@ No action required.
138
139
### Configuration
140
141
-#### File
142
-
143
-The configuration file name for this integration is `go.d/scaleio.conf`.
144
-
145
-The file format is YAML. Generally, the structure is:
146
-
147
-```yaml
148
-update_every: 1
149
-autodetection_retry: 0
150
-jobs:
151
- - name: some_name1
152
- - name: some_name1
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).
156
-
157
-```bash
158
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
159
-sudo ./edit-config go.d/scaleio.conf
160
-```
141
#### Options
142
143
The following options can be defined globally: update_every, autodetection_retry.
@@ -187,9 +167,43 @@ The following options can be defined globally: update_every, autodetection_retry
167
168
</details>
169
190
-#### Examples
170
192
-##### Basic
171
+#### via UI
172
+
173
+The **scaleio** collector can be configured directly through the Netdata web interface:
174
+
175
+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.
177
+3. The **Collectors → Jobs** view opens by default.
178
+4. In the Search box, type _scaleio_ (or scroll the list) to locate the **scaleio** collector.
179
+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**.
181
+
182
+
183
+#### via File
184
+
185
+The configuration file name for this integration is `go.d/scaleio.conf`.
186
+
187
+The file format is YAML. Generally, the structure is:
188
+
189
+```yaml
190
+update_every: 1
191
+autodetection_retry: 0
192
+jobs:
193
+ - name: some_name1
194
+ - name: some_name1
195
+```
196
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
197
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
198
+
199
+```bash
200
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
201
+sudo ./edit-config go.d/scaleio.conf
202
+```
203
+
204
+##### Examples
205
+
206
+###### Basic
207
208
An example configuration.
209
@@ -206,7 +220,7 @@ jobs:
220
```
221
</details>
222
209
-##### Multi-instance
223
+###### Multi-instance
224
225
> **Note**: When you define multiple jobs, their names must be unique.
226
src/go/plugin/go.d/collector/sensors/integrations/linux_sensors.md
+35
-21
@@ -117,7 +117,38 @@ No action required.
117
118
### Configuration
119
120
-#### File
120
+#### Options
121
+
122
+The following options can be defined globally: update_every.
123
+
124
+
125
+<details open><summary>Config options</summary>
126
+
127
+| Name | Description | Default | Required |
128
+|:----|:-----------|:-------|:--------:|
129
+| update_every | Data collection frequency. | 10 | no |
130
+| relabel | A list used to update existing sensor labels or add labels to sensors that don't have them. | [] | no |
131
+| relabel[].chip | [Pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns) to match the `chip_id` label value. | | no |
132
+| relabel[].sensors | A list of sensors to be relabeled for the specified chip. | [] | no |
133
+| relabel[].sensors[].name | The exact sensor name (e.g., `'temp1'`, `'in1'`, `'voltage1'`). | | no |
134
+| relabel[].sensors[].label | The new label value for the sensor. | | no |
135
+
136
+</details>
137
+
138
+
139
+#### via UI
140
+
141
+The **sensors** collector can be configured directly through the Netdata web interface:
142
+
143
+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.
145
+3. The **Collectors → Jobs** view opens by default.
146
+4. In the Search box, type _sensors_ (or scroll the list) to locate the **sensors** collector.
147
+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**.
149
+
150
+
151
+#### via File
152
153
The configuration file name for this integration is `go.d/sensors.conf`.
154
@@ -137,27 +168,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
168
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
169
sudo ./edit-config go.d/sensors.conf
170
```
140
-#### Options
141
-
142
-The following options can be defined globally: update_every.
143
-
144
-
145
-<details open><summary>Config options</summary>
146
-
147
-| Name | Description | Default | Required |
148
-|:----|:-----------|:-------|:--------:|
149
-| update_every | Data collection frequency. | 10 | no |
150
-| relabel | A list used to update existing sensor labels or add labels to sensors that don't have them. | [] | no |
151
-| relabel[].chip | [Pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns) to match the `chip_id` label value. | | no |
152
-| relabel[].sensors | A list of sensors to be relabeled for the specified chip. | [] | no |
153
-| relabel[].sensors[].name | The exact sensor name (e.g., `'temp1'`, `'in1'`, `'voltage1'`). | | no |
154
-| relabel[].sensors[].label | The new label value for the sensor. | | no |
155
-
156
-</details>
171
158
-#### Examples
172
+##### Examples
173
160
-##### Custom update_every
174
+###### Custom update_every
175
176
Allows you to override the default data collection interval.
177
@@ -171,7 +185,7 @@ jobs:
185
```
186
</details>
187
174
-##### Renaming labels
188
+###### Renaming labels
189
190
Allows you to override/add labels.
191
src/go/plugin/go.d/collector/smartctl/integrations/s.m.a.r.t..md
+38
-24
@@ -145,26 +145,6 @@ Install `smartmontools` version 7.0 or later using your distribution's package m
145
146
### Configuration
147
148
-#### File
149
-
150
-The configuration file name for this integration is `go.d/smartctl.conf`.
151
-
152
-The file format is YAML. Generally, the structure is:
153
-
154
-```yaml
155
-update_every: 1
156
-autodetection_retry: 0
157
-jobs:
158
- - name: some_name1
159
- - name: some_name1
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).
163
-
164
-```bash
165
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
166
-sudo ./edit-config go.d/smartctl.conf
167
-```
148
#### Options
149
150
The following options can be defined globally: update_every.
@@ -197,9 +177,43 @@ The valid arguments to this option are:
177
178
</details>
179
200
-#### Examples
180
202
-##### Custom devices poll interval
181
+#### via UI
182
+
183
+The **smartctl** collector can be configured directly through the Netdata web interface:
184
+
185
+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.
187
+3. The **Collectors → Jobs** view opens by default.
188
+4. In the Search box, type _smartctl_ (or scroll the list) to locate the **smartctl** collector.
189
+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**.
191
+
192
+
193
+#### via File
194
+
195
+The configuration file name for this integration is `go.d/smartctl.conf`.
196
+
197
+The file format is YAML. Generally, the structure is:
198
+
199
+```yaml
200
+update_every: 1
201
+autodetection_retry: 0
202
+jobs:
203
+ - name: some_name1
204
+ - name: some_name1
205
+```
206
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
208
+
209
+```bash
210
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
211
+sudo ./edit-config go.d/smartctl.conf
212
+```
213
+
214
+##### Examples
215
+
216
+###### Custom devices poll interval
217
218
Allows you to override the default devices poll interval (data collection).
219
@@ -213,7 +227,7 @@ jobs:
227
```
228
</details>
229
216
-##### Concurrent scanning for multiple devices
230
+###### Concurrent scanning for multiple devices
231
232
This example demonstrates enabling concurrent scanning to improve performance when monitoring many devices.
233
@@ -228,7 +242,7 @@ jobs:
242
```
243
</details>
244
231
-##### Extra devices
245
+###### Extra devices
246
247
This example demonstrates using `extra_devices` to manually add a storage device (`/dev/sdc`) not automatically detected by `smartctl --scan`.
248
src/go/plugin/go.d/collector/snmp/integrations/snmp_devices.md
+37
-23
@@ -138,26 +138,6 @@ No action required.
138
139
### Configuration
140
141
-#### File
142
-
143
-The configuration file name for this integration is `go.d/snmp.conf`.
144
-
145
-The file format is YAML. Generally, the structure is:
146
-
147
-```yaml
148
-update_every: 1
149
-autodetection_retry: 0
150
-jobs:
151
- - name: some_name1
152
- - name: some_name1
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).
156
-
157
-```bash
158
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
159
-sudo ./edit-config go.d/snmp.conf
160
-```
141
#### Options
142
143
The following options can be defined globally: update_every, autodetection_retry.
@@ -238,9 +218,43 @@ The encryption algorithm for SNMPv3 messages that require privacy (`user.priv_pr
218
219
</details>
220
241
-#### Examples
221
243
-##### SNMPv1/2
222
+#### via UI
223
+
224
+The **snmp** collector can be configured directly through the Netdata web interface:
225
+
226
+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.
228
+3. The **Collectors → Jobs** view opens by default.
229
+4. In the Search box, type _snmp_ (or scroll the list) to locate the **snmp** collector.
230
+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**.
232
+
233
+
234
+#### via File
235
+
236
+The configuration file name for this integration is `go.d/snmp.conf`.
237
+
238
+The file format is YAML. Generally, the structure is:
239
+
240
+```yaml
241
+update_every: 1
242
+autodetection_retry: 0
243
+jobs:
244
+ - name: some_name1
245
+ - name: some_name1
246
+```
247
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
248
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
249
+
250
+```bash
251
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
252
+sudo ./edit-config go.d/snmp.conf
253
+```
254
+
255
+##### Examples
256
+
257
+###### SNMPv1/2
258
259
In this example:
260
@@ -264,7 +278,7 @@ jobs:
278
```
279
</details>
280
267
-##### SNMPv3
281
+###### SNMPv3
282
283
To use SNMPv3:
284
src/go/plugin/go.d/collector/spigotmc/integrations/spigotmc.md
+33
-19
@@ -88,7 +88,36 @@ No action required.
88
89
### Configuration
90
91
-#### File
91
+#### Options
92
+
93
+The following options can be defined globally: update_every, autodetection_retry.
94
+
95
+
96
+<details open><summary>Config options</summary>
97
+
98
+| Name | Description | Default | Required |
99
+|:----|:-----------|:-------|:--------:|
100
+| update_every | Data collection frequency. | 1 | no |
101
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
102
+| address | The IP address and port where the SpigotMC server listens for RCON connections. | 127.0.0.1:25575 | yes |
103
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
104
+
105
+</details>
106
+
107
+
108
+#### via UI
109
+
110
+The **spigotmc** collector can be configured directly through the Netdata web interface:
111
+
112
+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.
114
+3. The **Collectors → Jobs** view opens by default.
115
+4. In the Search box, type _spigotmc_ (or scroll the list) to locate the **spigotmc** collector.
116
+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**.
118
+
119
+
120
+#### via File
121
122
The configuration file name for this integration is `go.d/spigotmc.conf`.
123
@@ -108,25 +137,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
137
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
138
sudo ./edit-config go.d/spigotmc.conf
139
```
111
-#### Options
112
-
113
-The following options can be defined globally: update_every, autodetection_retry.
114
-
115
-
116
-<details open><summary>Config options</summary>
117
-
118
-| Name | Description | Default | Required |
119
-|:----|:-----------|:-------|:--------:|
120
-| update_every | Data collection frequency. | 1 | no |
121
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
122
-| address | The IP address and port where the SpigotMC server listens for RCON connections. | 127.0.0.1:25575 | yes |
123
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
124
-
125
-</details>
140
127
-#### Examples
141
+##### Examples
142
129
-##### Basic
143
+###### Basic
144
145
A basic example configuration.
146
@@ -141,7 +155,7 @@ jobs:
155
```
156
</details>
157
144
-##### Multi-instance
158
+###### Multi-instance
159
160
> **Note**: When you define multiple jobs, their names must be unique.
161
src/go/plugin/go.d/collector/squid/integrations/squid.md
+37
-23
@@ -88,26 +88,6 @@ No action required.
88
89
### Configuration
90
91
-#### File
92
-
93
-The configuration file name for this integration is `go.d/squid.conf`.
94
-
95
-The file format is YAML. Generally, the structure is:
96
-
97
-```yaml
98
-update_every: 1
99
-autodetection_retry: 0
100
-jobs:
101
- - name: some_name1
102
- - name: some_name1
103
-```
104
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
-
107
-```bash
108
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
109
-sudo ./edit-config go.d/squid.conf
110
-```
91
#### Options
92
93
The following options can be defined globally: update_every, autodetection_retry.
@@ -137,9 +117,43 @@ The following options can be defined globally: update_every, autodetection_retry
117
118
</details>
119
140
-#### Examples
120
142
-##### Basic
121
+#### via UI
122
+
123
+The **squid** collector can be configured directly through the Netdata web interface:
124
+
125
+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.
127
+3. The **Collectors → Jobs** view opens by default.
128
+4. In the Search box, type _squid_ (or scroll the list) to locate the **squid** collector.
129
+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**.
131
+
132
+
133
+#### via File
134
+
135
+The configuration file name for this integration is `go.d/squid.conf`.
136
+
137
+The file format is YAML. Generally, the structure is:
138
+
139
+```yaml
140
+update_every: 1
141
+autodetection_retry: 0
142
+jobs:
143
+ - name: some_name1
144
+ - name: some_name1
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).
148
+
149
+```bash
150
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
+sudo ./edit-config go.d/squid.conf
152
+```
153
+
154
+##### Examples
155
+
156
+###### Basic
157
158
A basic example configuration.
159
@@ -149,7 +163,7 @@ jobs:
163
url: http://127.0.0.1:3128
164
165
```
152
-##### Multi-instance
166
+###### Multi-instance
167
168
> **Note**: When you define multiple jobs, their names must be unique.
169
src/go/plugin/go.d/collector/squidlog/integrations/squid_log_files.md
+35
-21
@@ -99,26 +99,6 @@ No action required.
99
100
### Configuration
101
102
-#### File
103
-
104
-The configuration file name for this integration is `go.d/squidlog.conf`.
105
-
106
-The file format is YAML. Generally, the structure is:
107
-
108
-```yaml
109
-update_every: 1
110
-autodetection_retry: 0
111
-jobs:
112
- - name: some_name1
113
- - name: some_name1
114
-```
115
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
116
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
117
-
118
-```bash
119
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
120
-sudo ./edit-config go.d/squidlog.conf
121
-```
102
#### Options
103
104
Squid [log format codes](https://www.squid-cache.org/Doc/config/logformat/).
@@ -223,7 +203,41 @@ parser:
203
204
</details>
205
226
-#### Examples
206
+
207
+#### via UI
208
+
209
+The **squidlog** collector can be configured directly through the Netdata web interface:
210
+
211
+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.
213
+3. The **Collectors → Jobs** view opens by default.
214
+4. In the Search box, type _squidlog_ (or scroll the list) to locate the **squidlog** collector.
215
+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**.
217
+
218
+
219
+#### via File
220
+
221
+The configuration file name for this integration is `go.d/squidlog.conf`.
222
+
223
+The file format is YAML. Generally, the structure is:
224
+
225
+```yaml
226
+update_every: 1
227
+autodetection_retry: 0
228
+jobs:
229
+ - name: some_name1
230
+ - name: some_name1
231
+```
232
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
233
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
234
+
235
+```bash
236
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
237
+sudo ./edit-config go.d/squidlog.conf
238
+```
239
+
240
+##### Examples
241
There are no configuration examples.
242
243
src/go/plugin/go.d/collector/storcli/integrations/storecli_raid.md
+30
-16
@@ -148,7 +148,34 @@ No action required.
148
149
### Configuration
150
151
-#### File
151
+#### Options
152
+
153
+The following options can be defined globally: update_every.
154
+
155
+
156
+<details open><summary>Config options</summary>
157
+
158
+| Name | Description | Default | Required |
159
+|:----|:-----------|:-------|:--------:|
160
+| update_every | Data collection frequency. | 10 | no |
161
+| timeout | storcli binary execution timeout. | 2 | no |
162
+
163
+</details>
164
+
165
+
166
+#### via UI
167
+
168
+The **storcli** collector can be configured directly through the Netdata web interface:
169
+
170
+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.
172
+3. The **Collectors → Jobs** view opens by default.
173
+4. In the Search box, type _storcli_ (or scroll the list) to locate the **storcli** collector.
174
+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**.
176
+
177
+
178
+#### via File
179
180
The configuration file name for this integration is `go.d/storcli.conf`.
181
@@ -168,23 +195,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
195
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
196
sudo ./edit-config go.d/storcli.conf
197
```
171
-#### Options
172
-
173
-The following options can be defined globally: update_every.
174
-
175
-
176
-<details open><summary>Config options</summary>
177
-
178
-| Name | Description | Default | Required |
179
-|:----|:-----------|:-------|:--------:|
180
-| update_every | Data collection frequency. | 10 | no |
181
-| timeout | storcli binary execution timeout. | 2 | no |
182
-
183
-</details>
198
185
-#### Examples
199
+##### Examples
200
187
-##### Custom update_every
201
+###### Custom update_every
202
203
Allows you to override the default data collection interval.
204
src/go/plugin/go.d/collector/supervisord/integrations/supervisor.md
+34
-20
@@ -106,7 +106,36 @@ No action required.
106
107
### Configuration
108
109
-#### File
109
+#### Options
110
+
111
+The following options can be defined globally: update_every, autodetection_retry.
112
+
113
+
114
+<details open><summary>Config options</summary>
115
+
116
+| Name | Description | Default | Required |
117
+|:----|:-----------|:-------|:--------:|
118
+| update_every | Data collection frequency. | 1 | no |
119
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
120
+| url | Server URL. | http://127.0.0.1:9001/RPC2 | yes |
121
+| timeout | System bus requests timeout. | 1 | no |
122
+
123
+</details>
124
+
125
+
126
+#### via UI
127
+
128
+The **supervisord** collector can be configured directly through the Netdata web interface:
129
+
130
+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.
132
+3. The **Collectors → Jobs** view opens by default.
133
+4. In the Search box, type _supervisord_ (or scroll the list) to locate the **supervisord** collector.
134
+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**.
136
+
137
+
138
+#### via File
139
140
The configuration file name for this integration is `go.d/supervisord.conf`.
141
@@ -126,25 +155,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
155
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
156
sudo ./edit-config go.d/supervisord.conf
157
```
129
-#### Options
130
-
131
-The following options can be defined globally: update_every, autodetection_retry.
132
-
133
-
134
-<details open><summary>Config options</summary>
135
-
136
-| Name | Description | Default | Required |
137
-|:----|:-----------|:-------|:--------:|
138
-| update_every | Data collection frequency. | 1 | no |
139
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
140
-| url | Server URL. | http://127.0.0.1:9001/RPC2 | yes |
141
-| timeout | System bus requests timeout. | 1 | no |
142
-
143
-</details>
158
145
-#### Examples
159
+##### Examples
160
147
-##### HTTP
161
+###### HTTP
162
163
Collect metrics via HTTP.
164
@@ -158,7 +172,7 @@ jobs:
172
```
173
</details>
174
161
-##### Socket
175
+###### Socket
176
177
Collect metrics via Unix socket.
178
@@ -171,7 +185,7 @@ Collect metrics via Unix socket.
185
```
186
</details>
187
174
-##### Multi-instance
188
+###### Multi-instance
189
190
> **Note**: When you define multiple jobs, their names must be unique.
191
src/go/plugin/go.d/collector/systemdunits/integrations/systemd_units.md
+39
-25
@@ -127,26 +127,6 @@ No action required.
127
128
### Configuration
129
130
-#### File
131
-
132
-The configuration file name for this integration is `go.d/systemdunits.conf`.
133
-
134
-The file format is YAML. Generally, the structure is:
135
-
136
-```yaml
137
-update_every: 1
138
-autodetection_retry: 0
139
-jobs:
140
- - name: some_name1
141
- - name: some_name1
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).
145
-
146
-```bash
147
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
148
-sudo ./edit-config go.d/systemdunits.conf
149
-```
130
#### Options
131
132
The following options can be defined globally: update_every, autodetection_retry.
@@ -197,9 +177,43 @@ includes:
177
178
</details>
179
200
-#### Examples
180
202
-##### Service units
181
+#### via UI
182
+
183
+The **systemdunits** collector can be configured directly through the Netdata web interface:
184
+
185
+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.
187
+3. The **Collectors → Jobs** view opens by default.
188
+4. In the Search box, type _systemdunits_ (or scroll the list) to locate the **systemdunits** collector.
189
+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**.
191
+
192
+
193
+#### via File
194
+
195
+The configuration file name for this integration is `go.d/systemdunits.conf`.
196
+
197
+The file format is YAML. Generally, the structure is:
198
+
199
+```yaml
200
+update_every: 1
201
+autodetection_retry: 0
202
+jobs:
203
+ - name: some_name1
204
+ - name: some_name1
205
+```
206
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
208
+
209
+```bash
210
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
211
+sudo ./edit-config go.d/systemdunits.conf
212
+```
213
+
214
+##### Examples
215
+
216
+###### Service units
217
218
Collect state of all service type units.
219
@@ -214,7 +228,7 @@ jobs:
228
```
229
</details>
230
217
-##### One specific unit
231
+###### One specific unit
232
233
Collect state of one specific unit.
234
@@ -229,7 +243,7 @@ jobs:
243
```
244
</details>
245
232
-##### All unit types
246
+###### All unit types
247
248
Collect state of all units.
249
@@ -244,7 +258,7 @@ jobs:
258
```
259
</details>
260
247
-##### Multi-instance
261
+###### Multi-instance
262
263
> **Note**: When you define multiple jobs, their names must be unique.
264
src/go/plugin/go.d/collector/tengine/integrations/tengine.md
+39
-25
@@ -93,26 +93,6 @@ The default line format is the only supported format.
93
94
### Configuration
95
96
-#### File
97
-
98
-The configuration file name for this integration is `go.d/tengine.conf`.
99
-
100
-The file format is YAML. Generally, the structure is:
101
-
102
-```yaml
103
-update_every: 1
104
-autodetection_retry: 0
105
-jobs:
106
- - name: some_name1
107
- - name: some_name1
108
-```
109
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
-
112
-```bash
113
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
114
-sudo ./edit-config go.d/tengine.conf
115
-```
96
#### Options
97
98
The following options can be defined globally: update_every, autodetection_retry.
@@ -142,9 +122,43 @@ The following options can be defined globally: update_every, autodetection_retry
122
123
</details>
124
145
-#### Examples
125
147
-##### Basic
126
+#### via UI
127
+
128
+The **tengine** collector can be configured directly through the Netdata web interface:
129
+
130
+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.
132
+3. The **Collectors → Jobs** view opens by default.
133
+4. In the Search box, type _tengine_ (or scroll the list) to locate the **tengine** collector.
134
+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**.
136
+
137
+
138
+#### via File
139
+
140
+The configuration file name for this integration is `go.d/tengine.conf`.
141
+
142
+The file format is YAML. Generally, the structure is:
143
+
144
+```yaml
145
+update_every: 1
146
+autodetection_retry: 0
147
+jobs:
148
+ - name: some_name1
149
+ - name: some_name1
150
+```
151
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
152
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
153
+
154
+```bash
155
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
156
+sudo ./edit-config go.d/tengine.conf
157
+```
158
+
159
+##### Examples
160
+
161
+###### Basic
162
163
An example configuration.
164
@@ -158,7 +172,7 @@ jobs:
172
```
173
</details>
174
161
-##### HTTP authentication
175
+###### HTTP authentication
176
177
Local server with basic HTTP authentication.
178
@@ -174,7 +188,7 @@ jobs:
188
```
189
</details>
190
177
-##### HTTPS with self-signed certificate
191
+###### HTTPS with self-signed certificate
192
193
Tengine with enabled HTTPS and self-signed certificate.
194
@@ -189,7 +203,7 @@ jobs:
203
```
204
</details>
205
192
-##### Multi-instance
206
+###### Multi-instance
207
208
> **Note**: When you define multiple jobs, their names must be unique.
209
src/go/plugin/go.d/collector/tomcat/integrations/tomcat.md
+37
-23
@@ -130,26 +130,6 @@ Once you've created the `netdata` user, you'll need to configure the username an
130
131
### Configuration
132
133
-#### File
134
-
135
-The configuration file name for this integration is `go.d/tomcat.conf`.
136
-
137
-The file format is YAML. Generally, the structure is:
138
-
139
-```yaml
140
-update_every: 1
141
-autodetection_retry: 0
142
-jobs:
143
- - name: some_name1
144
- - name: some_name1
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).
148
-
149
-```bash
150
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
151
-sudo ./edit-config go.d/tomcat.conf
152
-```
133
#### Options
134
135
The following options can be defined globally: update_every, autodetection_retry.
@@ -179,9 +159,43 @@ The following options can be defined globally: update_every, autodetection_retry
159
160
</details>
161
182
-#### Examples
162
184
-##### Basic
163
+#### via UI
164
+
165
+The **tomcat** collector can be configured directly through the Netdata web interface:
166
+
167
+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.
169
+3. The **Collectors → Jobs** view opens by default.
170
+4. In the Search box, type _tomcat_ (or scroll the list) to locate the **tomcat** collector.
171
+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**.
173
+
174
+
175
+#### via File
176
+
177
+The configuration file name for this integration is `go.d/tomcat.conf`.
178
+
179
+The file format is YAML. Generally, the structure is:
180
+
181
+```yaml
182
+update_every: 1
183
+autodetection_retry: 0
184
+jobs:
185
+ - name: some_name1
186
+ - name: some_name1
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).
190
+
191
+```bash
192
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
193
+sudo ./edit-config go.d/tomcat.conf
194
+```
195
+
196
+##### Examples
197
+
198
+###### Basic
199
200
A basic example configuration.
201
@@ -193,7 +207,7 @@ jobs:
207
password: Doe
208
209
```
196
-##### Multi-instance
210
+###### Multi-instance
211
212
> **Note**: When you define multiple jobs, their names must be unique.
213
src/go/plugin/go.d/collector/tor/integrations/tor.md
+34
-20
@@ -91,7 +91,37 @@ Enable `ControlPort` in `/etc/tor/torrc`.
91
92
### Configuration
93
94
-#### File
94
+#### Options
95
+
96
+The following options can be defined globally: update_every, autodetection_retry.
97
+
98
+
99
+<details open><summary>Config options</summary>
100
+
101
+| Name | Description | Default | Required |
102
+|:----|:-----------|:-------|:--------:|
103
+| update_every | Data collection frequency. | 1 | no |
104
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
105
+| address | The IP address and port where the Tor's Control Port listens for connections. | 127.0.0.1:9051 | yes |
106
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
107
+| password | Password for authentication. | | no |
108
+
109
+</details>
110
+
111
+
112
+#### via UI
113
+
114
+The **tor** collector can be configured directly through the Netdata web interface:
115
+
116
+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.
118
+3. The **Collectors → Jobs** view opens by default.
119
+4. In the Search box, type _tor_ (or scroll the list) to locate the **tor** collector.
120
+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**.
122
+
123
+
124
+#### via File
125
126
The configuration file name for this integration is `go.d/tor.conf`.
127
@@ -111,26 +141,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
141
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
142
sudo ./edit-config go.d/tor.conf
143
```
114
-#### Options
115
-
116
-The following options can be defined globally: update_every, autodetection_retry.
117
-
118
-
119
-<details open><summary>Config options</summary>
120
-
121
-| Name | Description | Default | Required |
122
-|:----|:-----------|:-------|:--------:|
123
-| update_every | Data collection frequency. | 1 | no |
124
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
125
-| address | The IP address and port where the Tor's Control Port listens for connections. | 127.0.0.1:9051 | yes |
126
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
127
-| password | Password for authentication. | | no |
128
-
129
-</details>
144
131
-#### Examples
145
+##### Examples
146
133
-##### Basic
147
+###### Basic
148
149
A basic example configuration.
150
@@ -145,7 +159,7 @@ jobs:
159
```
160
</details>
161
148
-##### Multi-instance
162
+###### Multi-instance
163
164
> **Note**: When you define multiple jobs, their names must be unique.
165
src/go/plugin/go.d/collector/traefik/integrations/traefik.md
+38
-24
@@ -87,26 +87,6 @@ To enable see [Prometheus exporter](https://doc.traefik.io/traefik/observability
87
88
### Configuration
89
90
-#### File
91
-
92
-The configuration file name for this integration is `go.d/traefik.conf`.
93
-
94
-The file format is YAML. Generally, the structure is:
95
-
96
-```yaml
97
-update_every: 1
98
-autodetection_retry: 0
99
-jobs:
100
- - name: some_name1
101
- - name: some_name1
102
-```
103
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
-
106
-```bash
107
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
108
-sudo ./edit-config go.d/traefik.conf
109
-```
90
#### Options
91
92
The following options can be defined globally: update_every, autodetection_retry.
@@ -136,9 +116,43 @@ The following options can be defined globally: update_every, autodetection_retry
116
117
</details>
118
139
-#### Examples
119
141
-##### Basic
120
+#### via UI
121
+
122
+The **traefik** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _traefik_ (or scroll the list) to locate the **traefik** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `go.d/traefik.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+jobs:
142
+ - name: some_name1
143
+ - name: some_name1
144
+```
145
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
146
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+
148
+```bash
149
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
+sudo ./edit-config go.d/traefik.conf
151
+```
152
+
153
+##### Examples
154
+
155
+###### Basic
156
157
An example configuration.
158
@@ -152,7 +166,7 @@ jobs:
166
```
167
</details>
168
155
-##### Basic HTTP auth
169
+###### Basic HTTP auth
170
171
Local server with basic HTTP authentication.
172
@@ -168,7 +182,7 @@ jobs:
182
```
183
</details>
184
171
-##### Multi-instance
185
+###### Multi-instance
186
187
> **Note**: When you define multiple jobs, their names must be unique.
188
src/go/plugin/go.d/collector/typesense/integrations/typesense.md
+37
-23
@@ -102,26 +102,6 @@ Without an API key, the collector will only collect health status information.
102
103
### Configuration
104
105
-#### File
106
-
107
-The configuration file name for this integration is `go.d/typesense.conf`.
108
-
109
-The file format is YAML. Generally, the structure is:
110
-
111
-```yaml
112
-update_every: 1
113
-autodetection_retry: 0
114
-jobs:
115
- - name: some_name1
116
- - name: some_name1
117
-```
118
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
-
121
-```bash
122
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
123
-sudo ./edit-config go.d/typesense.conf
124
-```
105
#### Options
106
107
The following options can be defined globally: update_every, autodetection_retry.
@@ -152,9 +132,43 @@ The following options can be defined globally: update_every, autodetection_retry
132
133
</details>
134
155
-#### Examples
135
157
-##### Basic
136
+#### via UI
137
+
138
+The **typesense** collector can be configured directly through the Netdata web interface:
139
+
140
+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.
142
+3. The **Collectors → Jobs** view opens by default.
143
+4. In the Search box, type _typesense_ (or scroll the list) to locate the **typesense** collector.
144
+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**.
146
+
147
+
148
+#### via File
149
+
150
+The configuration file name for this integration is `go.d/typesense.conf`.
151
+
152
+The file format is YAML. Generally, the structure is:
153
+
154
+```yaml
155
+update_every: 1
156
+autodetection_retry: 0
157
+jobs:
158
+ - name: some_name1
159
+ - name: some_name1
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).
163
+
164
+```bash
165
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
166
+sudo ./edit-config go.d/typesense.conf
167
+```
168
+
169
+##### Examples
170
+
171
+###### Basic
172
173
A basic example configuration.
174
@@ -165,7 +179,7 @@ jobs:
179
api_key: XYZ
180
181
```
168
-##### Multi-instance
182
+###### Multi-instance
183
184
> **Note**: When you define multiple jobs, their names must be unique.
185
src/go/plugin/go.d/collector/unbound/integrations/unbound.md
+38
-24
@@ -154,26 +154,6 @@ For auto-detection parameters from `unbound.conf`:
154
155
### Configuration
156
157
-#### File
158
-
159
-The configuration file name for this integration is `go.d/unbound.conf`.
160
-
161
-The file format is YAML. Generally, the structure is:
162
-
163
-```yaml
164
-update_every: 1
165
-autodetection_retry: 0
166
-jobs:
167
- - name: some_name1
168
- - name: some_name1
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).
172
-
173
-```bash
174
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
175
-sudo ./edit-config go.d/unbound.conf
176
-```
157
#### Options
158
159
The following options can be defined globally: update_every, autodetection_retry.
@@ -197,9 +177,43 @@ The following options can be defined globally: update_every, autodetection_retry
177
178
</details>
179
200
-#### Examples
180
202
-##### Basic
181
+#### via UI
182
+
183
+The **unbound** collector can be configured directly through the Netdata web interface:
184
+
185
+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.
187
+3. The **Collectors → Jobs** view opens by default.
188
+4. In the Search box, type _unbound_ (or scroll the list) to locate the **unbound** collector.
189
+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**.
191
+
192
+
193
+#### via File
194
+
195
+The configuration file name for this integration is `go.d/unbound.conf`.
196
+
197
+The file format is YAML. Generally, the structure is:
198
+
199
+```yaml
200
+update_every: 1
201
+autodetection_retry: 0
202
+jobs:
203
+ - name: some_name1
204
+ - name: some_name1
205
+```
206
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
207
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
208
+
209
+```bash
210
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
211
+sudo ./edit-config go.d/unbound.conf
212
+```
213
+
214
+##### Examples
215
+
216
+###### Basic
217
218
An example configuration.
219
@@ -213,7 +227,7 @@ jobs:
227
```
228
</details>
229
216
-##### Unix socket
230
+###### Unix socket
231
232
Connecting through Unix socket.
233
@@ -227,7 +241,7 @@ jobs:
241
```
242
</details>
243
230
-##### Multi-instance
244
+###### Multi-instance
245
246
> **Note**: When you define multiple jobs, their names must be unique.
247
src/go/plugin/go.d/collector/upsd/integrations/ups_nut.md
+33
-19
@@ -116,7 +116,36 @@ No action required.
116
117
### Configuration
118
119
-#### File
119
+#### Options
120
+
121
+The following options can be defined globally: update_every, autodetection_retry.
122
+
123
+
124
+<details open><summary>Config options</summary>
125
+
126
+| Name | Description | Default | Required |
127
+|:----|:-----------|:-------|:--------:|
128
+| update_every | Data collection frequency. | 1 | no |
129
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
130
+| address | UPS daemon address in IP:PORT format. | 127.0.0.1:3493 | yes |
131
+| timeout | Connection/read/write timeout in seconds. The timeout includes name resolution, if required. | 2 | no |
132
+
133
+</details>
134
+
135
+
136
+#### via UI
137
+
138
+The **upsd** collector can be configured directly through the Netdata web interface:
139
+
140
+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.
142
+3. The **Collectors → Jobs** view opens by default.
143
+4. In the Search box, type _upsd_ (or scroll the list) to locate the **upsd** collector.
144
+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**.
146
+
147
+
148
+#### via File
149
150
The configuration file name for this integration is `go.d/upsd.conf`.
151
@@ -136,25 +165,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
165
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
166
sudo ./edit-config go.d/upsd.conf
167
```
139
-#### Options
140
-
141
-The following options can be defined globally: update_every, autodetection_retry.
142
-
143
-
144
-<details open><summary>Config options</summary>
145
-
146
-| Name | Description | Default | Required |
147
-|:----|:-----------|:-------|:--------:|
148
-| update_every | Data collection frequency. | 1 | no |
149
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
150
-| address | UPS daemon address in IP:PORT format. | 127.0.0.1:3493 | yes |
151
-| timeout | Connection/read/write timeout in seconds. The timeout includes name resolution, if required. | 2 | no |
152
-
153
-</details>
168
155
-#### Examples
169
+##### Examples
170
157
-##### Basic
171
+###### Basic
172
173
A basic example configuration.
174
@@ -168,7 +182,7 @@ jobs:
182
```
183
</details>
184
171
-##### Multi-instance
185
+###### Multi-instance
186
187
> **Note**: When you define multiple jobs, their names must be unique.
188
src/go/plugin/go.d/collector/uwsgi/integrations/uwsgi.md
+33
-19
@@ -118,7 +118,36 @@ See [Stats Server](https://uwsgi-docs.readthedocs.io/en/latest/StatsServer.html)
118
119
### Configuration
120
121
-#### File
121
+#### Options
122
+
123
+The following options can be defined globally: update_every, autodetection_retry.
124
+
125
+
126
+<details open><summary>Config options</summary>
127
+
128
+| Name | Description | Default | Required |
129
+|:----|:-----------|:-------|:--------:|
130
+| update_every | Data collection frequency. | 1 | no |
131
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
132
+| address | The IP address and port where the UWSGI [Stats Server](https://uwsgi-docs.readthedocs.io/en/latest/StatsServer.html) listens for connections. | 127.0.0.1:1717 | yes |
133
+| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
134
+
135
+</details>
136
+
137
+
138
+#### via UI
139
+
140
+The **uwsgi** collector can be configured directly through the Netdata web interface:
141
+
142
+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.
144
+3. The **Collectors → Jobs** view opens by default.
145
+4. In the Search box, type _uwsgi_ (or scroll the list) to locate the **uwsgi** collector.
146
+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**.
148
+
149
+
150
+#### via File
151
152
The configuration file name for this integration is `go.d/uwsgi.conf`.
153
@@ -138,25 +167,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
167
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
168
sudo ./edit-config go.d/uwsgi.conf
169
```
141
-#### Options
142
-
143
-The following options can be defined globally: update_every, autodetection_retry.
144
-
145
-
146
-<details open><summary>Config options</summary>
147
-
148
-| Name | Description | Default | Required |
149
-|:----|:-----------|:-------|:--------:|
150
-| update_every | Data collection frequency. | 1 | no |
151
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
152
-| address | The IP address and port where the UWSGI [Stats Server](https://uwsgi-docs.readthedocs.io/en/latest/StatsServer.html) listens for connections. | 127.0.0.1:1717 | yes |
153
-| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |
154
-
155
-</details>
170
157
-#### Examples
171
+##### Examples
172
159
-##### Basic
173
+###### Basic
174
175
A basic example configuration.
176
@@ -170,7 +184,7 @@ jobs:
184
```
185
</details>
186
173
-##### Multi-instance
187
+###### Multi-instance
188
189
> **Note**: When you define multiple jobs, their names must be unique.
190
src/go/plugin/go.d/collector/varnish/integrations/varnish.md
+32
-18
@@ -125,7 +125,36 @@ No action required.
125
126
### Configuration
127
128
-#### File
128
+#### Options
129
+
130
+The following options can be defined globally: update_every.
131
+
132
+
133
+<details open><summary>Config options</summary>
134
+
135
+| Name | Description | Default | Required |
136
+|:----|:-----------|:-------|:--------:|
137
+| update_every | Data collection frequency. | 10 | no |
138
+| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
139
+| instance_name | Specifies the name of the Varnish instance to collect metrics from. This corresponds to the `-n` argument used with the [varnishstat](https://varnish-cache.org/docs/trunk/reference/varnishstat.html) command. | | no |
140
+| docker_container | Specifies the name of the Docker container where the Varnish instance is running. If set, the `varnishstat` command will be executed within this container. | | no |
141
+
142
+</details>
143
+
144
+
145
+#### via UI
146
+
147
+The **varnish** collector can be configured directly through the Netdata web interface:
148
+
149
+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.
151
+3. The **Collectors → Jobs** view opens by default.
152
+4. In the Search box, type _varnish_ (or scroll the list) to locate the **varnish** collector.
153
+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**.
155
+
156
+
157
+#### via File
158
159
The configuration file name for this integration is `go.d/varnish.conf`.
160
@@ -145,25 +174,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
174
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
175
sudo ./edit-config go.d/varnish.conf
176
```
148
-#### Options
149
-
150
-The following options can be defined globally: update_every.
151
-
152
-
153
-<details open><summary>Config options</summary>
154
-
155
-| Name | Description | Default | Required |
156
-|:----|:-----------|:-------|:--------:|
157
-| update_every | Data collection frequency. | 10 | no |
158
-| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
159
-| instance_name | Specifies the name of the Varnish instance to collect metrics from. This corresponds to the `-n` argument used with the [varnishstat](https://varnish-cache.org/docs/trunk/reference/varnishstat.html) command. | | no |
160
-| docker_container | Specifies the name of the Docker container where the Varnish instance is running. If set, the `varnishstat` command will be executed within this container. | | no |
161
-
162
-</details>
177
164
-#### Examples
178
+##### Examples
179
166
-##### Custom update_every
180
+###### Custom update_every
181
182
Allows you to override the default data collection interval.
183
src/go/plugin/go.d/collector/vcsa/integrations/vcenter_server_appliance.md
+37
-23
@@ -143,26 +143,6 @@ No action required.
143
144
### Configuration
145
146
-#### File
147
-
148
-The configuration file name for this integration is `go.d/vcsa.conf`.
149
-
150
-The file format is YAML. Generally, the structure is:
151
-
152
-```yaml
153
-update_every: 1
154
-autodetection_retry: 0
155
-jobs:
156
- - name: some_name1
157
- - name: some_name1
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).
161
-
162
-```bash
163
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
164
-sudo ./edit-config go.d/vcsa.conf
165
-```
146
#### Options
147
148
The following options can be defined globally: update_every, autodetection_retry.
@@ -192,9 +172,43 @@ The following options can be defined globally: update_every, autodetection_retry
172
173
</details>
174
195
-#### Examples
175
197
-##### Basic
176
+#### via UI
177
+
178
+The **vcsa** collector can be configured directly through the Netdata web interface:
179
+
180
+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.
182
+3. The **Collectors → Jobs** view opens by default.
183
+4. In the Search box, type _vcsa_ (or scroll the list) to locate the **vcsa** collector.
184
+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**.
186
+
187
+
188
+#### via File
189
+
190
+The configuration file name for this integration is `go.d/vcsa.conf`.
191
+
192
+The file format is YAML. Generally, the structure is:
193
+
194
+```yaml
195
+update_every: 1
196
+autodetection_retry: 0
197
+jobs:
198
+ - name: some_name1
199
+ - name: some_name1
200
+```
201
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
202
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
203
+
204
+```bash
205
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
206
+sudo ./edit-config go.d/vcsa.conf
207
+```
208
+
209
+##### Examples
210
+
211
+###### Basic
212
213
An example configuration.
214
@@ -210,7 +224,7 @@ jobs:
224
```
225
</details>
226
213
-##### Multi-instance
227
+###### Multi-instance
228
229
> **Note**: When you define multiple jobs, their names must be unique.
230
src/go/plugin/go.d/collector/vernemq/integrations/vernemq.md
+38
-24
@@ -194,26 +194,6 @@ No action required.
194
195
### Configuration
196
197
-#### File
198
-
199
-The configuration file name for this integration is `go.d/vernemq.conf`.
200
-
201
-The file format is YAML. Generally, the structure is:
202
-
203
-```yaml
204
-update_every: 1
205
-autodetection_retry: 0
206
-jobs:
207
- - name: some_name1
208
- - name: some_name1
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).
212
-
213
-```bash
214
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
215
-sudo ./edit-config go.d/vernemq.conf
216
-```
197
#### Options
198
199
The following options can be defined globally: update_every, autodetection_retry.
@@ -243,9 +223,43 @@ The following options can be defined globally: update_every, autodetection_retry
223
224
</details>
225
246
-#### Examples
226
248
-##### Basic
227
+#### via UI
228
+
229
+The **vernemq** collector can be configured directly through the Netdata web interface:
230
+
231
+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.
233
+3. The **Collectors → Jobs** view opens by default.
234
+4. In the Search box, type _vernemq_ (or scroll the list) to locate the **vernemq** collector.
235
+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**.
237
+
238
+
239
+#### via File
240
+
241
+The configuration file name for this integration is `go.d/vernemq.conf`.
242
+
243
+The file format is YAML. Generally, the structure is:
244
+
245
+```yaml
246
+update_every: 1
247
+autodetection_retry: 0
248
+jobs:
249
+ - name: some_name1
250
+ - name: some_name1
251
+```
252
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
253
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
254
+
255
+```bash
256
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
257
+sudo ./edit-config go.d/vernemq.conf
258
+```
259
+
260
+##### Examples
261
+
262
+###### Basic
263
264
An example configuration.
265
@@ -259,7 +273,7 @@ jobs:
273
```
274
</details>
275
262
-##### HTTP authentication
276
+###### HTTP authentication
277
278
Local instance with basic HTTP authentication.
279
@@ -275,7 +289,7 @@ jobs:
289
```
290
</details>
291
278
-##### Multi-instance
292
+###### Multi-instance
293
294
> **Note**: When you define multiple jobs, their names must be unique.
295
src/go/plugin/go.d/collector/vsphere/integrations/vmware_vcenter_server.md
+37
-23
@@ -180,26 +180,6 @@ No action required.
180
181
### Configuration
182
183
-#### File
184
-
185
-The configuration file name for this integration is `go.d/vsphere.conf`.
186
-
187
-The file format is YAML. Generally, the structure is:
188
-
189
-```yaml
190
-update_every: 1
191
-autodetection_retry: 0
192
-jobs:
193
- - name: some_name1
194
- - name: some_name1
195
-```
196
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
197
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
198
-
199
-```bash
200
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
201
-sudo ./edit-config go.d/vsphere.conf
202
-```
183
#### Options
184
185
The following options can be defined globally: update_every, autodetection_retry.
@@ -261,9 +241,43 @@ Metrics of VMs matching the selector will be collected.
241
242
</details>
243
264
-#### Examples
244
266
-##### Basic
245
+#### via UI
246
+
247
+The **vsphere** collector can be configured directly through the Netdata web interface:
248
+
249
+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.
251
+3. The **Collectors → Jobs** view opens by default.
252
+4. In the Search box, type _vsphere_ (or scroll the list) to locate the **vsphere** collector.
253
+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**.
255
+
256
+
257
+#### via File
258
+
259
+The configuration file name for this integration is `go.d/vsphere.conf`.
260
+
261
+The file format is YAML. Generally, the structure is:
262
+
263
+```yaml
264
+update_every: 1
265
+autodetection_retry: 0
266
+jobs:
267
+ - name: some_name1
268
+ - name: some_name1
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).
272
+
273
+```bash
274
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
275
+sudo ./edit-config go.d/vsphere.conf
276
+```
277
+
278
+##### Examples
279
+
280
+###### Basic
281
282
A basic example configuration.
283
@@ -275,7 +289,7 @@ jobs:
289
password : somepassword
290
291
```
278
-##### Multi-instance
292
+###### Multi-instance
293
294
> **Note**: When you define multiple jobs, their names must be unique.
295
src/go/plugin/go.d/collector/w1sensor/integrations/1-wire_sensors.md
+30
-16
@@ -86,7 +86,34 @@ Make sure `wire`, `w1_gpio`, and `w1_therm` kernel modules are loaded.
86
87
### Configuration
88
89
-#### File
89
+#### Options
90
+
91
+The following options can be defined globally: update_every.
92
+
93
+
94
+<details open><summary>Config options</summary>
95
+
96
+| Name | Description | Default | Required |
97
+|:----|:-----------|:-------|:--------:|
98
+| update_every | Data collection frequency. | 1 | no |
99
+| sensors_path | Directory path containing sensor folders with w1_slave files. | /sys/bus/w1/devices | no |
100
+
101
+</details>
102
+
103
+
104
+#### via UI
105
+
106
+The **w1sensor** collector can be configured directly through the Netdata web interface:
107
+
108
+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.
110
+3. The **Collectors → Jobs** view opens by default.
111
+4. In the Search box, type _w1sensor_ (or scroll the list) to locate the **w1sensor** collector.
112
+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**.
114
+
115
+
116
+#### via File
117
118
The configuration file name for this integration is `go.d/w1sensor.conf`.
119
@@ -106,23 +133,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
133
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
134
sudo ./edit-config go.d/w1sensor.conf
135
```
109
-#### Options
110
-
111
-The following options can be defined globally: update_every.
112
-
113
-
114
-<details open><summary>Config options</summary>
115
-
116
-| Name | Description | Default | Required |
117
-|:----|:-----------|:-------|:--------:|
118
-| update_every | Data collection frequency. | 1 | no |
119
-| sensors_path | Directory path containing sensor folders with w1_slave files. | /sys/bus/w1/devices | no |
120
-
121
-</details>
136
123
-#### Examples
137
+##### Examples
138
125
-##### Custom sensor device path
139
+###### Custom sensor device path
140
141
Monitors a virtual sensor when the w1_slave file is located in a custom directory instead of the default location.
142
src/go/plugin/go.d/collector/weblog/integrations/web_server_log_files.md
+35
-21
@@ -157,26 +157,6 @@ No action required.
157
158
### Configuration
159
160
-#### File
161
-
162
-The configuration file name for this integration is `go.d/web_log.conf`.
163
-
164
-The file format is YAML. Generally, the structure is:
165
-
166
-```yaml
167
-update_every: 1
168
-autodetection_retry: 0
169
-jobs:
170
- - name: some_name1
171
- - name: some_name1
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).
175
-
176
-```bash
177
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
178
-sudo ./edit-config go.d/web_log.conf
179
-```
160
#### Options
161
162
Weblog is aware of how to parse and interpret the following fields (**known fields**):
@@ -344,7 +324,41 @@ regexp_config:
324
325
</details>
326
347
-#### Examples
327
+
328
+#### via UI
329
+
330
+The **web_log** collector can be configured directly through the Netdata web interface:
331
+
332
+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.
334
+3. The **Collectors → Jobs** view opens by default.
335
+4. In the Search box, type _web_log_ (or scroll the list) to locate the **web_log** collector.
336
+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**.
338
+
339
+
340
+#### via File
341
+
342
+The configuration file name for this integration is `go.d/web_log.conf`.
343
+
344
+The file format is YAML. Generally, the structure is:
345
+
346
+```yaml
347
+update_every: 1
348
+autodetection_retry: 0
349
+jobs:
350
+ - name: some_name1
351
+ - name: some_name1
352
+```
353
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
354
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
355
+
356
+```bash
357
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
358
+sudo ./edit-config go.d/web_log.conf
359
+```
360
+
361
+##### Examples
362
There are no configuration examples.
363
364
src/go/plugin/go.d/collector/whoisquery/integrations/domain_expiration_date.md
+35
-21
@@ -90,7 +90,38 @@ No action required.
90
91
### Configuration
92
93
-#### File
93
+#### Options
94
+
95
+The following options can be defined globally: update_every, autodetection_retry.
96
+
97
+
98
+<details open><summary>Config options</summary>
99
+
100
+| Name | Description | Default | Required |
101
+|:----|:-----------|:-------|:--------:|
102
+| update_every | Data collection frequency. | 60 | no |
103
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
104
+| source | Domain address. | | yes |
105
+| days_until_expiration_warning | Number of days before the alarm status is warning. | 30 | no |
106
+| days_until_expiration_critical | Number of days before the alarm status is critical. | 15 | no |
107
+| timeout | The query timeout in seconds. | 5 | no |
108
+
109
+</details>
110
+
111
+
112
+#### via UI
113
+
114
+The **whoisquery** collector can be configured directly through the Netdata web interface:
115
+
116
+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.
118
+3. The **Collectors → Jobs** view opens by default.
119
+4. In the Search box, type _whoisquery_ (or scroll the list) to locate the **whoisquery** collector.
120
+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**.
122
+
123
+
124
+#### via File
125
126
The configuration file name for this integration is `go.d/whoisquery.conf`.
127
@@ -110,27 +141,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
141
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
142
sudo ./edit-config go.d/whoisquery.conf
143
```
113
-#### Options
114
-
115
-The following options can be defined globally: update_every, autodetection_retry.
116
-
117
-
118
-<details open><summary>Config options</summary>
119
-
120
-| Name | Description | Default | Required |
121
-|:----|:-----------|:-------|:--------:|
122
-| update_every | Data collection frequency. | 60 | no |
123
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
124
-| source | Domain address. | | yes |
125
-| days_until_expiration_warning | Number of days before the alarm status is warning. | 30 | no |
126
-| days_until_expiration_critical | Number of days before the alarm status is critical. | 15 | no |
127
-| timeout | The query timeout in seconds. | 5 | no |
128
-
129
-</details>
144
131
-#### Examples
145
+##### Examples
146
133
-##### Basic
147
+###### Basic
148
149
Basic configuration example
150
@@ -144,7 +158,7 @@ jobs:
158
```
159
</details>
160
147
-##### Multi-instance
161
+###### Multi-instance
162
163
> **Note**: When you define more than one job, their names must be unique.
164
src/go/plugin/go.d/collector/wireguard/integrations/wireguard.md
+29
-15
@@ -109,7 +109,34 @@ No action required.
109
110
### Configuration
111
112
-#### File
112
+#### Options
113
+
114
+The following options can be defined globally: update_every, autodetection_retry.
115
+
116
+
117
+<details open><summary>Config options</summary>
118
+
119
+| Name | Description | Default | Required |
120
+|:----|:-----------|:-------|:--------:|
121
+| update_every | Data collection frequency. | 1 | no |
122
+| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
123
+
124
+</details>
125
+
126
+
127
+#### via UI
128
+
129
+The **wireguard** collector can be configured directly through the Netdata web interface:
130
+
131
+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.
133
+3. The **Collectors → Jobs** view opens by default.
134
+4. In the Search box, type _wireguard_ (or scroll the list) to locate the **wireguard** collector.
135
+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**.
137
+
138
+
139
+#### via File
140
141
The configuration file name for this integration is `go.d/wireguard.conf`.
142
@@ -129,21 +156,8 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
156
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
157
sudo ./edit-config go.d/wireguard.conf
158
```
132
-#### Options
133
-
134
-The following options can be defined globally: update_every, autodetection_retry.
135
-
136
-
137
-<details open><summary>Config options</summary>
138
-
139
-| Name | Description | Default | Required |
140
-|:----|:-----------|:-------|:--------:|
141
-| update_every | Data collection frequency. | 1 | no |
142
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
143
-
144
-</details>
159
146
-#### Examples
160
+##### Examples
161
There are no configuration examples.
162
163
src/go/plugin/go.d/collector/x509check/integrations/x.509_certificate.md
+39
-25
@@ -94,26 +94,6 @@ No action required.
94
95
### Configuration
96
97
-#### File
98
-
99
-The configuration file name for this integration is `go.d/x509check.conf`.
100
-
101
-The file format is YAML. Generally, the structure is:
102
-
103
-```yaml
104
-update_every: 1
105
-autodetection_retry: 0
106
-jobs:
107
- - name: some_name1
108
- - name: some_name1
109
-```
110
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
111
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
-
113
-```bash
114
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
115
-sudo ./edit-config go.d/x509check.conf
116
-```
97
#### Options
98
99
The following options can be defined globally: update_every, autodetection_retry.
@@ -136,9 +116,43 @@ The following options can be defined globally: update_every, autodetection_retry
116
117
</details>
118
139
-#### Examples
119
141
-##### Website certificate
120
+#### via UI
121
+
122
+The **x509check** collector can be configured directly through the Netdata web interface:
123
+
124
+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.
126
+3. The **Collectors → Jobs** view opens by default.
127
+4. In the Search box, type _x509check_ (or scroll the list) to locate the **x509check** collector.
128
+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**.
130
+
131
+
132
+#### via File
133
+
134
+The configuration file name for this integration is `go.d/x509check.conf`.
135
+
136
+The file format is YAML. Generally, the structure is:
137
+
138
+```yaml
139
+update_every: 1
140
+autodetection_retry: 0
141
+jobs:
142
+ - name: some_name1
143
+ - name: some_name1
144
+```
145
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
146
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+
148
+```bash
149
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
150
+sudo ./edit-config go.d/x509check.conf
151
+```
152
+
153
+##### Examples
154
+
155
+###### Website certificate
156
157
Website certificate.
158
@@ -152,7 +166,7 @@ jobs:
166
```
167
</details>
168
155
-##### Local file certificate
169
+###### Local file certificate
170
171
Local file certificate.
172
@@ -166,7 +180,7 @@ jobs:
180
```
181
</details>
182
169
-##### SMTP certificate
183
+###### SMTP certificate
184
185
SMTP certificate.
186
@@ -180,7 +194,7 @@ jobs:
194
```
195
</details>
196
183
-##### Multi-instance
197
+###### Multi-instance
198
199
> **Note**: When you define more than one job, their names must be unique.
200
src/go/plugin/go.d/collector/yugabytedb/integrations/yugabytedb.md
+39
-25
@@ -340,26 +340,6 @@ No action required.
340
341
### Configuration
342
343
-#### File
344
-
345
-The configuration file name for this integration is `go.d/yugabytedb.conf`.
346
-
347
-The file format is YAML. Generally, the structure is:
348
-
349
-```yaml
350
-update_every: 1
351
-autodetection_retry: 0
352
-jobs:
353
- - name: some_name1
354
- - name: some_name1
355
-```
356
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
357
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
358
-
359
-```bash
360
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
361
-sudo ./edit-config go.d/yugabytedb.conf
362
-```
343
#### Options
344
345
The following options can be defined globally: update_every, autodetection_retry.
@@ -389,9 +369,43 @@ The following options can be defined globally: update_every, autodetection_retry
369
370
</details>
371
392
-#### Examples
372
394
-##### Basic
373
+#### via UI
374
+
375
+The **yugabytedb** collector can be configured directly through the Netdata web interface:
376
+
377
+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.
379
+3. The **Collectors → Jobs** view opens by default.
380
+4. In the Search box, type _yugabytedb_ (or scroll the list) to locate the **yugabytedb** collector.
381
+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**.
383
+
384
+
385
+#### via File
386
+
387
+The configuration file name for this integration is `go.d/yugabytedb.conf`.
388
+
389
+The file format is YAML. Generally, the structure is:
390
+
391
+```yaml
392
+update_every: 1
393
+autodetection_retry: 0
394
+jobs:
395
+ - name: some_name1
396
+ - name: some_name1
397
+```
398
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
399
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
400
+
401
+```bash
402
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
403
+sudo ./edit-config go.d/yugabytedb.conf
404
+```
405
+
406
+##### Examples
407
+
408
+###### Basic
409
410
A basic example configuration.
411
@@ -404,7 +418,7 @@ jobs:
418
# url: http://127.0.0.1:13000/prometheus-metrics # YSQL
419
420
```
407
-##### HTTP authentication
421
+###### HTTP authentication
422
423
Basic HTTP authentication.
424
@@ -420,7 +434,7 @@ jobs:
434
```
435
</details>
436
423
-##### HTTPS with self-signed certificate
437
+###### HTTPS with self-signed certificate
438
439
NGINX with enabled HTTPS and self-signed certificate.
440
@@ -435,7 +449,7 @@ jobs:
449
```
450
</details>
451
438
-##### Multi-instance
452
+###### Multi-instance
453
454
> **Note**: When you define multiple jobs, their names must be unique.
455
src/go/plugin/go.d/collector/zfspool/integrations/zfs_pools.md
+31
-17
@@ -116,7 +116,35 @@ No action required.
116
117
### Configuration
118
119
-#### File
119
+#### Options
120
+
121
+The following options can be defined globally: update_every.
122
+
123
+
124
+<details open><summary>Config options</summary>
125
+
126
+| Name | Description | Default | Required |
127
+|:----|:-----------|:-------|:--------:|
128
+| update_every | Data collection frequency. | 10 | no |
129
+| binary_path | Path to the `zpool` binary. If an absolute path is provided, the collector will use it directly; otherwise, it will search for the binary in directories specified in the PATH environment variable. | /usr/bin/zpool | yes |
130
+| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
131
+
132
+</details>
133
+
134
+
135
+#### via UI
136
+
137
+The **zfspool** collector can be configured directly through the Netdata web interface:
138
+
139
+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.
141
+3. The **Collectors → Jobs** view opens by default.
142
+4. In the Search box, type _zfspool_ (or scroll the list) to locate the **zfspool** collector.
143
+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**.
145
+
146
+
147
+#### via File
148
149
The configuration file name for this integration is `go.d/zfspool.conf`.
150
@@ -136,24 +164,10 @@ Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/n
164
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
165
sudo ./edit-config go.d/zfspool.conf
166
```
139
-#### Options
140
-
141
-The following options can be defined globally: update_every.
142
-
143
-
144
-<details open><summary>Config options</summary>
145
-
146
-| Name | Description | Default | Required |
147
-|:----|:-----------|:-------|:--------:|
148
-| update_every | Data collection frequency. | 10 | no |
149
-| binary_path | Path to the `zpool` binary. If an absolute path is provided, the collector will use it directly; otherwise, it will search for the binary in directories specified in the PATH environment variable. | /usr/bin/zpool | yes |
150
-| timeout | Timeout for executing the binary, specified in seconds. | 2 | no |
151
-
152
-</details>
167
154
-#### Examples
168
+##### Examples
169
156
-##### Custom binary path
170
+###### Custom binary path
171
172
The executable is not in the directories specified in the PATH environment variable.
173
src/go/plugin/go.d/collector/zookeeper/integrations/zookeeper.md
+38
-24
@@ -107,26 +107,6 @@ Add `mntr` to Zookeeper's [4lw.commands.whitelist](https://zookeeper.apache.org/
107
108
### Configuration
109
110
-#### File
111
-
112
-The configuration file name for this integration is `go.d/zookeeper.conf`.
113
-
114
-The file format is YAML. Generally, the structure is:
115
-
116
-```yaml
117
-update_every: 1
118
-autodetection_retry: 0
119
-jobs:
120
- - name: some_name1
121
- - name: some_name1
122
-```
123
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
124
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
-
126
-```bash
127
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
128
-sudo ./edit-config go.d/zookeeper.conf
129
-```
110
#### Options
111
112
The following options can be defined globally: update_every, autodetection_retry.
@@ -148,9 +128,43 @@ The following options can be defined globally: update_every, autodetection_retry
128
129
</details>
130
151
-#### Examples
131
153
-##### Basic
132
+#### via UI
133
+
134
+The **zookeeper** collector can be configured directly through the Netdata web interface:
135
+
136
+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.
138
+3. The **Collectors → Jobs** view opens by default.
139
+4. In the Search box, type _zookeeper_ (or scroll the list) to locate the **zookeeper** collector.
140
+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**.
142
+
143
+
144
+#### via File
145
+
146
+The configuration file name for this integration is `go.d/zookeeper.conf`.
147
+
148
+The file format is YAML. Generally, the structure is:
149
+
150
+```yaml
151
+update_every: 1
152
+autodetection_retry: 0
153
+jobs:
154
+ - name: some_name1
155
+ - name: some_name1
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).
159
+
160
+```bash
161
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
162
+sudo ./edit-config go.d/zookeeper.conf
163
+```
164
+
165
+##### Examples
166
+
167
+###### Basic
168
169
Local server.
170
@@ -164,7 +178,7 @@ jobs:
178
```
179
</details>
180
167
-##### TLS with self-signed certificate
181
+###### TLS with self-signed certificate
182
183
Zookeeper with TLS and self-signed certificate.
184
@@ -180,7 +194,7 @@ jobs:
194
```
195
</details>
196
183
-##### Multi-instance
197
+###### Multi-instance
198
199
> **Note**: When you define multiple jobs, their names must be unique.
200
src/health/notifications/alerta/README.md
+17
-14
@@ -34,18 +34,6 @@ You can send Netdata alerts to Alerta to see alerts coming from many Netdata hos
34
35
### Configuration
36
37
-#### File
38
-
39
-The configuration file name for this integration is `health_alarm_notify.conf`.
40
-
41
-
42
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
43
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
-
45
-```bash
46
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
47
-sudo ./edit-config health_alarm_notify.conf
48
-```
37
#### Options
38
39
The following options can be defined for this notification
@@ -85,9 +73,24 @@ The values you provide should be defined as environments in `/etc/alertad.conf`
73
74
</details>
75
88
-#### Examples
76
90
-##### Basic Configuration
77
+
78
+#### via File
79
+
80
+The configuration file name for this integration is `health_alarm_notify.conf`.
81
+
82
+
83
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
84
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
85
+
86
+```bash
87
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
88
+sudo ./edit-config health_alarm_notify.conf
89
+```
90
+
91
+##### Examples
92
+
93
+###### Basic Configuration
94
95
96
src/health/notifications/awssns/README.md
+17
-14
@@ -51,18 +51,6 @@ You can send notifications through Amazon SNS using Netdata's Agent alert notifi
51
52
### Configuration
53
54
-#### File
55
-
56
-The configuration file name for this integration is `health_alarm_notify.conf`.
57
-
58
-
59
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
60
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
61
-
62
-```bash
63
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
64
-sudo ./edit-config health_alarm_notify.conf
65
-```
54
#### Options
55
56
The following options can be defined for this notification
@@ -136,9 +124,24 @@ role_recipients_awssns[sitemgr]="arn:aws:sns:us-east-2:123456789012:Sites"
124
125
</details>
126
139
-#### Examples
127
141
-##### Basic Configuration
128
+
129
+#### via File
130
+
131
+The configuration file name for this integration is `health_alarm_notify.conf`.
132
+
133
+
134
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
135
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
136
+
137
+```bash
138
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
139
+sudo ./edit-config health_alarm_notify.conf
140
+```
141
+
142
+##### Examples
143
+
144
+###### Basic Configuration
145
146
An example working configuration would be:
147
src/health/notifications/custom/README.md
+17
-14
@@ -31,18 +31,6 @@ Netdata Agent's alert notification feature allows you to send custom notificatio
31
32
### Configuration
33
34
-#### File
35
-
36
-The configuration file name for this integration is `health_alarm_notify.conf`.
37
-
38
-
39
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
40
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
-
42
-```bash
43
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
44
-sudo ./edit-config health_alarm_notify.conf
45
-```
34
#### Options
35
36
The following options can be defined for this notification
@@ -142,9 +130,24 @@ The supported variables that you can use for the function's `msg` variable are:
130
131
</details>
132
145
-#### Examples
133
147
-##### Basic Configuration
134
+
135
+#### via File
136
+
137
+The configuration file name for this integration is `health_alarm_notify.conf`.
138
+
139
+
140
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
141
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
142
+
143
+```bash
144
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
145
+sudo ./edit-config health_alarm_notify.conf
146
+```
147
+
148
+##### Examples
149
+
150
+###### Basic Configuration
151
152
153
src/health/notifications/discord/README.md
+17
-14
@@ -33,18 +33,6 @@ Send notifications to Discord using Netdata's Agent alert notification feature,
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -75,9 +63,24 @@ The values you provide should already exist as Discord channels in your server.
63
64
</details>
65
78
-#### Examples
66
80
-##### Basic Configuration
67
+
68
+#### via File
69
+
70
+The configuration file name for this integration is `health_alarm_notify.conf`.
71
+
72
+
73
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
74
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
75
+
76
+```bash
77
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
78
+sudo ./edit-config health_alarm_notify.conf
79
+```
80
+
81
+##### Examples
82
+
83
+###### Basic Configuration
84
85
86
src/health/notifications/dynatrace/README.md
+17
-14
@@ -36,18 +36,6 @@ You can send notifications to Dynatrace using Netdata's Agent alert notification
36
37
### Configuration
38
39
-#### File
40
-
41
-The configuration file name for this integration is `health_alarm_notify.conf`.
42
-
43
-
44
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
45
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
-
47
-```bash
48
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
49
-sudo ./edit-config health_alarm_notify.conf
50
-```
39
#### Options
40
41
The following options can be defined for this notification
@@ -78,9 +66,24 @@ You can read more [here](https://www.dynatrace.com/support/help/dynatrace-api/en
66
67
</details>
68
81
-#### Examples
69
83
-##### Basic Configuration
70
+
71
+#### via File
72
+
73
+The configuration file name for this integration is `health_alarm_notify.conf`.
74
+
75
+
76
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
77
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
78
+
79
+```bash
80
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
81
+sudo ./edit-config health_alarm_notify.conf
82
+```
83
+
84
+##### Examples
85
+
86
+###### Basic Configuration
87
88
89
src/health/notifications/email/README.md
+17
-14
@@ -43,18 +43,6 @@ Send notifications via Email using Netdata's Agent alert notification feature, w
43
44
### Configuration
45
46
-#### File
47
-
48
-The configuration file name for this integration is `health_alarm_notify.conf`.
49
-
50
-
51
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
52
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
53
-
54
-```bash
55
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
56
-sudo ./edit-config health_alarm_notify.conf
57
-```
46
#### Options
47
48
The following options can be defined for this notification
@@ -83,9 +71,24 @@ role_recipients_email[sitemgr]="sites@example.com"
71
72
</details>
73
86
-#### Examples
74
88
-##### Basic Configuration
75
+
76
+#### via File
77
+
78
+The configuration file name for this integration is `health_alarm_notify.conf`.
79
+
80
+
81
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
82
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
83
+
84
+```bash
85
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
86
+sudo ./edit-config health_alarm_notify.conf
87
+```
88
+
89
+##### Examples
90
+
91
+###### Basic Configuration
92
93
94
src/health/notifications/flock/README.md
+17
-14
@@ -32,18 +32,6 @@ Send notifications to Flock using Netdata's Agent alert notification feature, wh
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `health_alarm_notify.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config health_alarm_notify.conf
46
-```
35
#### Options
36
37
The following options can be defined for this notification
@@ -71,9 +59,24 @@ role_recipients_flock[sitemgr]="sites"
59
60
</details>
61
74
-#### Examples
62
76
-##### Basic Configuration
63
+
64
+#### via File
65
+
66
+The configuration file name for this integration is `health_alarm_notify.conf`.
67
+
68
+
69
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
70
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
71
+
72
+```bash
73
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
74
+sudo ./edit-config health_alarm_notify.conf
75
+```
76
+
77
+##### Examples
78
+
79
+###### Basic Configuration
80
81
82
src/health/notifications/gotify/README.md
+17
-14
@@ -33,18 +33,6 @@ You can send alerts to your Gotify instance using Netdata's Agent alert notifica
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -59,9 +47,24 @@ The following options can be defined for this notification
47
48
</details>
49
62
-#### Examples
50
64
-##### Basic Configuration
51
+
52
+#### via File
53
+
54
+The configuration file name for this integration is `health_alarm_notify.conf`.
55
+
56
+
57
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
58
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
59
+
60
+```bash
61
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
62
+sudo ./edit-config health_alarm_notify.conf
63
+```
64
+
65
+##### Examples
66
+
67
+###### Basic Configuration
68
69
70
src/health/notifications/ilert/README.md
+17
-14
@@ -33,18 +33,6 @@ Sending notification to ilert via Netdata's Agent alert notification feature inc
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -58,9 +46,24 @@ The following options can be defined for this notification
46
47
</details>
48
61
-#### Examples
49
63
-##### Basic Configuration
50
+
51
+#### via File
52
+
53
+The configuration file name for this integration is `health_alarm_notify.conf`.
54
+
55
+
56
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
57
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
58
+
59
+```bash
60
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
61
+sudo ./edit-config health_alarm_notify.conf
62
+```
63
+
64
+##### Examples
65
+
66
+###### Basic Configuration
67
68
69
src/health/notifications/irc/README.md
+17
-14
@@ -32,18 +32,6 @@ Send notifications to IRC using Netdata's Agent alert notification feature, whic
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `health_alarm_notify.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config health_alarm_notify.conf
46
-```
35
#### Options
36
37
The following options can be defined for this notification
@@ -88,9 +76,24 @@ role_recipients_irc[sitemgr]="#sites"
76
77
</details>
78
91
-#### Examples
79
93
-##### Basic Configuration
80
+
81
+#### via File
82
+
83
+The configuration file name for this integration is `health_alarm_notify.conf`.
84
+
85
+
86
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
87
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
88
+
89
+```bash
90
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
91
+sudo ./edit-config health_alarm_notify.conf
92
+```
93
+
94
+##### Examples
95
+
96
+###### Basic Configuration
97
98
99
src/health/notifications/kavenegar/README.md
+17
-14
@@ -33,18 +33,6 @@ You can send notifications to Kavenegar using Netdata's Agent alert notification
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -77,9 +65,24 @@ The values you provide should be defined as environments in `/etc/alertad.conf`
65
66
</details>
67
80
-#### Examples
68
82
-##### Basic Configuration
69
+
70
+#### via File
71
+
72
+The configuration file name for this integration is `health_alarm_notify.conf`.
73
+
74
+
75
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
76
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
77
+
78
+```bash
79
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
80
+sudo ./edit-config health_alarm_notify.conf
81
+```
82
+
83
+##### Examples
84
+
85
+###### Basic Configuration
86
87
88
src/health/notifications/matrix/README.md
+17
-14
@@ -34,18 +34,6 @@ Send notifications to Matrix network rooms using Netdata's Agent alert notificat
34
35
### Configuration
36
37
-#### File
38
-
39
-The configuration file name for this integration is `health_alarm_notify.conf`.
40
-
41
-
42
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
43
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
-
45
-```bash
46
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
47
-sudo ./edit-config health_alarm_notify.conf
48
-```
37
#### Options
38
39
The following options can be defined for this notification
@@ -89,9 +77,24 @@ role_recipients_matrix[sitemgr]="!roomid6:homeservername"
77
78
</details>
79
92
-#### Examples
80
94
-##### Basic Configuration
81
+
82
+#### via File
83
+
84
+The configuration file name for this integration is `health_alarm_notify.conf`.
85
+
86
+
87
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
88
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
89
+
90
+```bash
91
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
92
+sudo ./edit-config health_alarm_notify.conf
93
+```
94
+
95
+##### Examples
96
+
97
+###### Basic Configuration
98
99
100
src/health/notifications/messagebird/README.md
+17
-14
@@ -32,18 +32,6 @@ Send notifications to MessageBird using Netdata's Agent alert notification featu
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `health_alarm_notify.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config health_alarm_notify.conf
46
-```
35
#### Options
36
37
The following options can be defined for this notification
@@ -74,9 +62,24 @@ role_recipients_messagebird[sitemgr]="+15555555550"
62
63
</details>
64
77
-#### Examples
65
79
-##### Basic Configuration
66
+
67
+#### via File
68
+
69
+The configuration file name for this integration is `health_alarm_notify.conf`.
70
+
71
+
72
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
73
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
74
+
75
+```bash
76
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
77
+sudo ./edit-config health_alarm_notify.conf
78
+```
79
+
80
+##### Examples
81
+
82
+###### Basic Configuration
83
84
85
src/health/notifications/msteams/README.md
+17
-14
@@ -33,18 +33,6 @@ You can send Netdata alerts to Microsoft Teams using Netdata's Agent alert notif
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -76,9 +64,24 @@ role_recipients_msteams[sitemgr]="CHANNEL6"
64
65
</details>
66
79
-#### Examples
67
81
-##### Basic Configuration
68
+
69
+#### via File
70
+
71
+The configuration file name for this integration is `health_alarm_notify.conf`.
72
+
73
+
74
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
75
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
76
+
77
+```bash
78
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
79
+sudo ./edit-config health_alarm_notify.conf
80
+```
81
+
82
+##### Examples
83
+
84
+###### Basic Configuration
85
86
87
src/health/notifications/ntfy/README.md
+17
-14
@@ -34,18 +34,6 @@ You can send alerts to an ntfy server using Netdata's Agent alert notification f
34
35
### Configuration
36
37
-#### File
38
-
39
-The configuration file name for this integration is `health_alarm_notify.conf`.
40
-
41
-
42
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
43
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
-
45
-```bash
46
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
47
-sudo ./edit-config health_alarm_notify.conf
48
-```
37
#### Options
38
39
The following options can be defined for this notification
@@ -97,9 +85,24 @@ Ensure that the token user has proper read/write access to the provided topic in
85
86
</details>
87
100
-#### Examples
88
102
-##### Basic Configuration
89
+
90
+#### via File
91
+
92
+The configuration file name for this integration is `health_alarm_notify.conf`.
93
+
94
+
95
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
96
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+
98
+```bash
99
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
100
+sudo ./edit-config health_alarm_notify.conf
101
+```
102
+
103
+##### Examples
104
+
105
+###### Basic Configuration
106
107
108
src/health/notifications/opsgenie/README.md
+17
-14
@@ -33,18 +33,6 @@ You can send notifications to Opsgenie using Netdata's Agent alert notification
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -59,9 +47,24 @@ The following options can be defined for this notification
47
48
</details>
49
62
-#### Examples
50
64
-##### Basic Configuration
51
+
52
+#### via File
53
+
54
+The configuration file name for this integration is `health_alarm_notify.conf`.
55
+
56
+
57
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
58
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
59
+
60
+```bash
61
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
62
+sudo ./edit-config health_alarm_notify.conf
63
+```
64
+
65
+##### Examples
66
+
67
+###### Basic Configuration
68
69
70
src/health/notifications/pagerduty/README.md
+17
-14
@@ -35,18 +35,6 @@ You can send notifications to PagerDuty using Netdata's Agent alert notification
35
36
### Configuration
37
38
-#### File
39
-
40
-The configuration file name for this integration is `health_alarm_notify.conf`.
41
-
42
-
43
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
44
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
45
-
46
-```bash
47
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
48
-sudo ./edit-config health_alarm_notify.conf
49
-```
38
#### Options
39
40
The following options can be defined for this notification
@@ -75,9 +63,24 @@ role_recipients_pd[sitemgr]="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf"
63
64
</details>
65
78
-#### Examples
66
80
-##### Basic Configuration
67
+
68
+#### via File
69
+
70
+The configuration file name for this integration is `health_alarm_notify.conf`.
71
+
72
+
73
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
74
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
75
+
76
+```bash
77
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
78
+sudo ./edit-config health_alarm_notify.conf
79
+```
80
+
81
+##### Examples
82
+
83
+###### Basic Configuration
84
85
86
src/health/notifications/prowl/README.md
+17
-14
@@ -38,18 +38,6 @@ Send notifications to Prowl using Netdata's Agent alert notification feature, wh
38
39
### Configuration
40
41
-#### File
42
-
43
-The configuration file name for this integration is `health_alarm_notify.conf`.
44
-
45
-
46
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
47
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
48
-
49
-```bash
50
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
51
-sudo ./edit-config health_alarm_notify.conf
52
-```
41
#### Options
42
43
The following options can be defined for this notification
@@ -78,9 +66,24 @@ role_recipients_prowl[sitemgr]="FFFFFFFFFF"
66
67
</details>
68
81
-#### Examples
69
83
-##### Basic Configuration
70
+
71
+#### via File
72
+
73
+The configuration file name for this integration is `health_alarm_notify.conf`.
74
+
75
+
76
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
77
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
78
+
79
+```bash
80
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
81
+sudo ./edit-config health_alarm_notify.conf
82
+```
83
+
84
+##### Examples
85
+
86
+###### Basic Configuration
87
88
89
src/health/notifications/pushbullet/README.md
+17
-14
@@ -32,18 +32,6 @@ Send notifications to Pushbullet using Netdata's Agent alert notification featur
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `health_alarm_notify.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config health_alarm_notify.conf
46
-```
35
#### Options
36
37
The following options can be defined for this notification
@@ -75,9 +63,24 @@ role_recipients_pushbullet[sitemgr]="user4@mail.com"
63
64
</details>
65
78
-#### Examples
66
80
-##### Basic Configuration
67
+
68
+#### via File
69
+
70
+The configuration file name for this integration is `health_alarm_notify.conf`.
71
+
72
+
73
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
74
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
75
+
76
+```bash
77
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
78
+sudo ./edit-config health_alarm_notify.conf
79
+```
80
+
81
+##### Examples
82
+
83
+###### Basic Configuration
84
85
86
src/health/notifications/pushover/README.md
+17
-14
@@ -36,18 +36,6 @@ Send notification to Pushover using Netdata's Agent alert notification feature,
36
37
### Configuration
38
39
-#### File
40
-
41
-The configuration file name for this integration is `health_alarm_notify.conf`.
42
-
43
-
44
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
45
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
-
47
-```bash
48
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
49
-sudo ./edit-config health_alarm_notify.conf
50
-```
39
#### Options
40
41
The following options can be defined for this notification
@@ -77,9 +65,24 @@ role_recipients_pushover[sitemgr]="USERTOKEN7"
65
66
</details>
67
80
-#### Examples
68
82
-##### Basic Configuration
69
+
70
+#### via File
71
+
72
+The configuration file name for this integration is `health_alarm_notify.conf`.
73
+
74
+
75
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
76
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
77
+
78
+```bash
79
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
80
+sudo ./edit-config health_alarm_notify.conf
81
+```
82
+
83
+##### Examples
84
+
85
+###### Basic Configuration
86
87
88
src/health/notifications/rocketchat/README.md
+17
-14
@@ -33,18 +33,6 @@ Send notifications to Rocket.Chat using Netdata's Agent alert notification featu
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -74,9 +62,24 @@ role_recipients_rocketchat[sitemgr]="sites"
62
63
</details>
64
77
-#### Examples
65
79
-##### Basic Configuration
66
+
67
+#### via File
68
+
69
+The configuration file name for this integration is `health_alarm_notify.conf`.
70
+
71
+
72
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
73
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
74
+
75
+```bash
76
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
77
+sudo ./edit-config health_alarm_notify.conf
78
+```
79
+
80
+##### Examples
81
+
82
+###### Basic Configuration
83
84
85
src/health/notifications/signl4/README.md
+17
-14
@@ -33,18 +33,6 @@ You can send notifications to SIGNL4 using Netdata's Agent alert notification fe
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -58,9 +46,24 @@ The following options can be defined for this notification
46
47
</details>
48
61
-#### Examples
49
63
-##### Basic Configuration
50
+
51
+#### via File
52
+
53
+The configuration file name for this integration is `health_alarm_notify.conf`.
54
+
55
+
56
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
57
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
58
+
59
+```bash
60
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
61
+sudo ./edit-config health_alarm_notify.conf
62
+```
63
+
64
+##### Examples
65
+
66
+###### Basic Configuration
67
68
69
src/health/notifications/slack/README.md
+17
-14
@@ -33,18 +33,6 @@ Send notifications to a Slack workspace using Netdata's Agent alert notification
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -59,9 +47,24 @@ The following options can be defined for this notification
47
48
</details>
49
62
-#### Examples
50
64
-##### Basic Configuration
51
+
52
+#### via File
53
+
54
+The configuration file name for this integration is `health_alarm_notify.conf`.
55
+
56
+
57
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
58
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
59
+
60
+```bash
61
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
62
+sudo ./edit-config health_alarm_notify.conf
63
+```
64
+
65
+##### Examples
66
+
67
+###### Basic Configuration
68
69
70
src/health/notifications/smseagle/README.md
+17
-14
@@ -39,18 +39,6 @@ Optional: Enable the "Access to resources of all users" checkbox if you want thi
39
40
### Configuration
41
42
-#### File
43
-
44
-The configuration file name for this integration is `health_alarm_notify.conf`.
45
-
46
-
47
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
48
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
49
-
50
-```bash
51
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
52
-sudo ./edit-config health_alarm_notify.conf
53
-```
42
#### Options
43
44
The following options can be defined for this notification
@@ -108,9 +96,24 @@ ID of the voice model, required for TTS Advanced.
96
97
</details>
98
111
-#### Examples
99
113
-##### Basic Configuration
100
+
101
+#### via File
102
+
103
+The configuration file name for this integration is `health_alarm_notify.conf`.
104
+
105
+
106
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
107
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
+
109
+```bash
110
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
111
+sudo ./edit-config health_alarm_notify.conf
112
+```
113
+
114
+##### Examples
115
+
116
+###### Basic Configuration
117
118
119
src/health/notifications/smstools3/README.md
+17
-14
@@ -37,18 +37,6 @@ The SMS Server Tools 3 is a SMS Gateway software which can send and receive shor
37
38
### Configuration
39
40
-#### File
41
-
42
-The configuration file name for this integration is `health_alarm_notify.conf`.
43
-
44
-
45
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
-
48
-```bash
49
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
50
-sudo ./edit-config health_alarm_notify.conf
51
-```
40
#### Options
41
42
The following options can be defined for this notification
@@ -86,9 +74,24 @@ role_recipients_sms[sitemgr]="PHONE6"
74
75
</details>
76
89
-#### Examples
77
91
-##### Basic Configuration
78
+
79
+#### via File
80
+
81
+The configuration file name for this integration is `health_alarm_notify.conf`.
82
+
83
+
84
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
85
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
86
+
87
+```bash
88
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
89
+sudo ./edit-config health_alarm_notify.conf
90
+```
91
+
92
+##### Examples
93
+
94
+###### Basic Configuration
95
96
97
src/health/notifications/syslog/README.md
+17
-14
@@ -32,18 +32,6 @@ Send notifications to Syslog using Netdata's Agent alert notification feature, w
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `health_alarm_notify.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config health_alarm_notify.conf
46
-```
35
#### Options
36
37
The following options can be defined for this notification
@@ -90,9 +78,24 @@ role_recipients_syslog[sitemgr]="daemon.notice@loghost6:514/netdata"
78
79
</details>
80
93
-#### Examples
81
95
-##### Basic Configuration
82
+
83
+#### via File
84
+
85
+The configuration file name for this integration is `health_alarm_notify.conf`.
86
+
87
+
88
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
89
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
90
+
91
+```bash
92
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
93
+sudo ./edit-config health_alarm_notify.conf
94
+```
95
+
96
+##### Examples
97
+
98
+###### Basic Configuration
99
100
101
src/health/notifications/telegram/README.md
+17
-14
@@ -33,18 +33,6 @@ Send notifications to Telegram using Netdata's Agent alert notification feature,
33
34
### Configuration
35
36
-#### File
37
-
38
-The configuration file name for this integration is `health_alarm_notify.conf`.
39
-
40
-
41
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
-
44
-```bash
45
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46
-sudo ./edit-config health_alarm_notify.conf
47
-```
36
#### Options
37
38
The following options can be defined for this notification
@@ -75,9 +63,24 @@ role_recipients_telegram[sitemgr]="-49999333876"
63
64
</details>
65
78
-#### Examples
66
80
-##### Basic Configuration
67
+
68
+#### via File
69
+
70
+The configuration file name for this integration is `health_alarm_notify.conf`.
71
+
72
+
73
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
74
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
75
+
76
+```bash
77
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
78
+sudo ./edit-config health_alarm_notify.conf
79
+```
80
+
81
+##### Examples
82
+
83
+###### Basic Configuration
84
85
86
src/health/notifications/twilio/README.md
+17
-14
@@ -32,18 +32,6 @@ Send notifications to Twilio using Netdata's Agent alert notification feature, w
32
33
### Configuration
34
35
-#### File
36
-
37
-The configuration file name for this integration is `health_alarm_notify.conf`.
38
-
39
-
40
-You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
-
43
-```bash
44
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
45
-sudo ./edit-config health_alarm_notify.conf
46
-```
35
#### Options
36
37
The following options can be defined for this notification
@@ -74,9 +62,24 @@ role_recipients_twilio[sitemgr]="+15555555550"
62
63
</details>
64
77
-#### Examples
65
79
-##### Basic Configuration
66
+
67
+#### via File
68
+
69
+The configuration file name for this integration is `health_alarm_notify.conf`.
70
+
71
+
72
+You can edit the configuration file using the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-a-configuration-file-using-edit-config) script from the
73
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
74
+
75
+```bash
76
+cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
77
+sudo ./edit-config health_alarm_notify.conf
78
+```
79
+
80
+##### Examples
81
+
82
+###### Basic Configuration
83
84
85