1815a1b5d · cryptotaxi247/netdata-1

src/collectors/windows.plugin/integrations/ms_sql_server.md

+26

@@ -135,6 +135,8 @@ There are no alerts configured by default for this integration.

135

136 #### Configure SQL Server for Monitoring

137

138 +For **each SQL Server** instance you want to monitor, complete the following steps:

139 +

140 1. **Create Monitoring User**

141

142 Create an SQL Server user with the necessary permissions to collect monitoring data:

@@ -170,6 +172,30 @@ There are no alerts configured by default for this integration.

172 GO

173 ```

174

175 +3. **Configure SQL Server Network Settings**

176 +

177 + Enable SQL Server to accept TCP connections:

178 +

179 + - Open `SQL Server Configuration Manager`

180 + - Expand `SQL Server Network Configuration`

181 + - Select `Protocols for <instance name>` in the console panel

182 + - Double-click the `TCP` protocol in the details panel and set `Enabled` to `Yes`

183 + - Go to the `IP Address` tab and locate the `IPAII` section:

184 + - Clear any value from the `TCP Dynamic Ports` field

185 + - Enter a port number in the `TCP Port` field (default is `1433`)

186 + - Select `SQL Server Services` and restart your SQL Server instance

187 +

188 +4. **Configure SQL Server Authentication (Optional)**

189 +

190 + If you're using SQL Server authentication (rather than Windows authentication):

191 +

192 + - Open `SQL Server Management Studio`

193 + - Right-click your server and select `Properties`

194 + - Select `Security` in the left panel

195 + - Choose `SQL Server and Windows Authentication mode` under `Server authentication`

196 + - Click `OK`

197 + - Right-click your server and select `Restart`

198 +

199

200

201 ### Configuration

src/go/plugin/go.d/collector/activemq/integrations/activemq.md

+6

@@ -240,6 +240,12 @@ should give you clues as to why the collector isn't working.

240 ./go.d.plugin -d -m activemq

241 ```

242

243 + To debug a specific job:

244 +

245 + ```bash

246 + ./go.d.plugin -d -m activemq -j jobName

247 + ```

248 +

249 ### Getting Logs

250

251 If you're encountering problems with the `activemq` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/adaptecraid/integrations/adaptec_raid.md

+6

@@ -204,6 +204,12 @@ should give you clues as to why the collector isn't working.

204 ./go.d.plugin -d -m adaptec_raid

205 ```

206

207 + To debug a specific job:

208 +

209 + ```bash

210 + ./go.d.plugin -d -m adaptec_raid -j jobName

211 + ```

212 +

213 ### Getting Logs

214

215 If you're encountering problems with the `adaptec_raid` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/ap/integrations/access_points.md

+6

@@ -174,6 +174,12 @@ should give you clues as to why the collector isn't working.

174 ./go.d.plugin -d -m ap

175 ```

176

177 + To debug a specific job:

178 +

179 + ```bash

180 + ./go.d.plugin -d -m ap -j jobName

181 + ```

182 +

183 ### Getting Logs

184

185 If you're encountering problems with the `ap` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/apache/integrations/apache.md

+6

@@ -246,6 +246,12 @@ should give you clues as to why the collector isn't working.

246 ./go.d.plugin -d -m apache

247 ```

248

249 + To debug a specific job:

250 +

251 + ```bash

252 + ./go.d.plugin -d -m apache -j jobName

253 + ```

254 +

255 ### Getting Logs

256

257 If you're encountering problems with the `apache` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/apache/integrations/httpd.md

+6

@@ -246,6 +246,12 @@ should give you clues as to why the collector isn't working.

246 ./go.d.plugin -d -m apache

247 ```

248

249 + To debug a specific job:

250 +

251 + ```bash

252 + ./go.d.plugin -d -m apache -j jobName

253 + ```

254 +

255 ### Getting Logs

256

257 If you're encountering problems with the `apache` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/apcupsd/integrations/apc_ups.md

+6

@@ -212,6 +212,12 @@ should give you clues as to why the collector isn't working.

212 ./go.d.plugin -d -m apcupsd

213 ```

214

215 + To debug a specific job:

216 +

217 + ```bash

218 + ./go.d.plugin -d -m apcupsd -j jobName

219 + ```

220 +

221 ### Getting Logs

222

223 If you're encountering problems with the `apcupsd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/beanstalk/integrations/beanstalk.md

+6

@@ -225,6 +225,12 @@ should give you clues as to why the collector isn't working.

225 ./go.d.plugin -d -m beanstalk

226 ```

227

228 + To debug a specific job:

229 +

230 + ```bash

231 + ./go.d.plugin -d -m beanstalk -j jobName

232 + ```

233 +

234 ### Getting Logs

235

236 If you're encountering problems with the `beanstalk` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/boinc/integrations/boinc.md

+6

@@ -201,6 +201,12 @@ should give you clues as to why the collector isn't working.

201 ./go.d.plugin -d -m boinc

202 ```

203

204 + To debug a specific job:

205 +

206 + ```bash

207 + ./go.d.plugin -d -m boinc -j jobName

208 + ```

209 +

210 ### Getting Logs

211

212 If you're encountering problems with the `boinc` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/cassandra/integrations/cassandra.md

+6

@@ -285,6 +285,12 @@ should give you clues as to why the collector isn't working.

285 ./go.d.plugin -d -m cassandra

286 ```

287

288 + To debug a specific job:

289 +

290 + ```bash

291 + ./go.d.plugin -d -m cassandra -j jobName

292 + ```

293 +

294 ### Getting Logs

295

296 If you're encountering problems with the `cassandra` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/ceph/integrations/ceph.md

+6

@@ -279,6 +279,12 @@ should give you clues as to why the collector isn't working.

279 ./go.d.plugin -d -m ceph

280 ```

281

282 + To debug a specific job:

283 +

284 + ```bash

285 + ./go.d.plugin -d -m ceph -j jobName

286 + ```

287 +

288 ### Getting Logs

289

290 If you're encountering problems with the `ceph` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/chrony/integrations/chrony.md

+6

@@ -199,6 +199,12 @@ should give you clues as to why the collector isn't working.

199 ./go.d.plugin -d -m chrony

200 ```

201

202 + To debug a specific job:

203 +

204 + ```bash

205 + ./go.d.plugin -d -m chrony -j jobName

206 + ```

207 +

208 ### Getting Logs

209

210 If you're encountering problems with the `chrony` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/clickhouse/integrations/clickhouse.md

+6

@@ -340,6 +340,12 @@ should give you clues as to why the collector isn't working.

340 ./go.d.plugin -d -m clickhouse

341 ```

342

343 + To debug a specific job:

344 +

345 + ```bash

346 + ./go.d.plugin -d -m clickhouse -j jobName

347 + ```

348 +

349 ### Getting Logs

350

351 If you're encountering problems with the `clickhouse` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/cockroachdb/integrations/cockroachdb.md

+6

@@ -295,6 +295,12 @@ should give you clues as to why the collector isn't working.

295 ./go.d.plugin -d -m cockroachdb

296 ```

297

298 + To debug a specific job:

299 +

300 + ```bash

301 + ./go.d.plugin -d -m cockroachdb -j jobName

302 + ```

303 +

304 ### Getting Logs

305

306 If you're encountering problems with the `cockroachdb` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/consul/integrations/consul.md

+6

@@ -331,6 +331,12 @@ should give you clues as to why the collector isn't working.

331 ./go.d.plugin -d -m consul

332 ```

333

334 + To debug a specific job:

335 +

336 + ```bash

337 + ./go.d.plugin -d -m consul -j jobName

338 + ```

339 +

340 ### Getting Logs

341

342 If you're encountering problems with the `consul` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/coredns/integrations/coredns.md

+6

@@ -301,6 +301,12 @@ should give you clues as to why the collector isn't working.

301 ./go.d.plugin -d -m coredns

302 ```

303

304 + To debug a specific job:

305 +

306 + ```bash

307 + ./go.d.plugin -d -m coredns -j jobName

308 + ```

309 +

310 ### Getting Logs

311

312 If you're encountering problems with the `coredns` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/couchbase/integrations/couchbase.md

+6

@@ -219,6 +219,12 @@ should give you clues as to why the collector isn't working.

219 ./go.d.plugin -d -m couchbase

220 ```

221

222 + To debug a specific job:

223 +

224 + ```bash

225 + ./go.d.plugin -d -m couchbase -j jobName

226 + ```

227 +

228 ### Getting Logs

229

230 If you're encountering problems with the `couchbase` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/couchdb/integrations/couchdb.md

+6

@@ -232,6 +232,12 @@ should give you clues as to why the collector isn't working.

232 ./go.d.plugin -d -m couchdb

233 ```

234

235 + To debug a specific job:

236 +

237 + ```bash

238 + ./go.d.plugin -d -m couchdb -j jobName

239 + ```

240 +

241 ### Getting Logs

242

243 If you're encountering problems with the `couchdb` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dmcache/integrations/dmcache_devices.md

+6

@@ -170,6 +170,12 @@ should give you clues as to why the collector isn't working.

170 ./go.d.plugin -d -m dmcache

171 ```

172

173 + To debug a specific job:

174 +

175 + ```bash

176 + ./go.d.plugin -d -m dmcache -j jobName

177 + ```

178 +

179 ### Getting Logs

180

181 If you're encountering problems with the `dmcache` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dnsdist/integrations/dnsdist.md

+6

@@ -217,6 +217,12 @@ should give you clues as to why the collector isn't working.

217 ./go.d.plugin -d -m dnsdist

218 ```

219

220 + To debug a specific job:

221 +

222 + ```bash

223 + ./go.d.plugin -d -m dnsdist -j jobName

224 + ```

225 +

226 ### Getting Logs

227

228 If you're encountering problems with the `dnsdist` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dnsmasq/integrations/dnsmasq.md

+6

@@ -202,6 +202,12 @@ should give you clues as to why the collector isn't working.

202 ./go.d.plugin -d -m dnsmasq

203 ```

204

205 + To debug a specific job:

206 +

207 + ```bash

208 + ./go.d.plugin -d -m dnsmasq -j jobName

209 + ```

210 +

211 ### Getting Logs

212

213 If you're encountering problems with the `dnsmasq` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md

+6

@@ -214,6 +214,12 @@ should give you clues as to why the collector isn't working.

214 ./go.d.plugin -d -m dnsmasq_dhcp

215 ```

216

217 + To debug a specific job:

218 +

219 + ```bash

220 + ./go.d.plugin -d -m dnsmasq_dhcp -j jobName

221 + ```

222 +

223 ### Getting Logs

224

225 If you're encountering problems with the `dnsmasq_dhcp` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dnsquery/integrations/dns_query.md

+6

@@ -208,6 +208,12 @@ should give you clues as to why the collector isn't working.

208 ./go.d.plugin -d -m dns_query

209 ```

210

211 + To debug a specific job:

212 +

213 + ```bash

214 + ./go.d.plugin -d -m dns_query -j jobName

215 + ```

216 +

217 ### Getting Logs

218

219 If you're encountering problems with the `dns_query` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/docker/integrations/docker.md

+6

@@ -216,6 +216,12 @@ should give you clues as to why the collector isn't working.

216 ./go.d.plugin -d -m docker

217 ```

218

219 + To debug a specific job:

220 +

221 + ```bash

222 + ./go.d.plugin -d -m docker -j jobName

223 + ```

224 +

225 ### Getting Logs

226

227 If you're encountering problems with the `docker` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/docker_engine/integrations/docker_engine.md

+6

@@ -236,6 +236,12 @@ should give you clues as to why the collector isn't working.

236 ./go.d.plugin -d -m docker_engine

237 ```

238

239 + To debug a specific job:

240 +

241 + ```bash

242 + ./go.d.plugin -d -m docker_engine -j jobName

243 + ```

244 +

245 ### Getting Logs

246

247 If you're encountering problems with the `docker_engine` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dockerhub/integrations/docker_hub_repository.md

+6

@@ -181,6 +181,12 @@ should give you clues as to why the collector isn't working.

181 ./go.d.plugin -d -m dockerhub

182 ```

183

184 + To debug a specific job:

185 +

186 + ```bash

187 + ./go.d.plugin -d -m dockerhub -j jobName

188 + ```

189 +

190 ### Getting Logs

191

192 If you're encountering problems with the `dockerhub` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/dovecot/integrations/dovecot.md

+6

@@ -216,6 +216,12 @@ should give you clues as to why the collector isn't working.

216 ./go.d.plugin -d -m dovecot

217 ```

218

219 + To debug a specific job:

220 +

221 + ```bash

222 + ./go.d.plugin -d -m dovecot -j jobName

223 + ```

224 +

225 ### Getting Logs

226

227 If you're encountering problems with the `dovecot` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/elasticsearch/integrations/elasticsearch.md

+6

@@ -350,6 +350,12 @@ should give you clues as to why the collector isn't working.

350 ./go.d.plugin -d -m elasticsearch

351 ```

352

353 + To debug a specific job:

354 +

355 + ```bash

356 + ./go.d.plugin -d -m elasticsearch -j jobName

357 + ```

358 +

359 ### Getting Logs

360

361 If you're encountering problems with the `elasticsearch` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/elasticsearch/integrations/opensearch.md

+6

@@ -350,6 +350,12 @@ should give you clues as to why the collector isn't working.

350 ./go.d.plugin -d -m elasticsearch

351 ```

352

353 + To debug a specific job:

354 +

355 + ```bash

356 + ./go.d.plugin -d -m elasticsearch -j jobName

357 + ```

358 +

359 ### Getting Logs

360

361 If you're encountering problems with the `elasticsearch` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/envoy/integrations/envoy.md

+6

@@ -278,6 +278,12 @@ should give you clues as to why the collector isn't working.

278 ./go.d.plugin -d -m envoy

279 ```

280

281 + To debug a specific job:

282 +

283 + ```bash

284 + ./go.d.plugin -d -m envoy -j jobName

285 + ```

286 +

287 ### Getting Logs

288

289 If you're encountering problems with the `envoy` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/ethtool/integrations/optical_modules.md

+6

@@ -173,6 +173,12 @@ should give you clues as to why the collector isn't working.

173 ./go.d.plugin -d -m ethtool

174 ```

175

176 + To debug a specific job:

177 +

178 + ```bash

179 + ./go.d.plugin -d -m ethtool -j jobName

180 + ```

181 +

182 ### Getting Logs

183

184 If you're encountering problems with the `ethtool` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/exim/integrations/exim.md

+6

@@ -163,6 +163,12 @@ should give you clues as to why the collector isn't working.

163 ./go.d.plugin -d -m exim

164 ```

165

166 + To debug a specific job:

167 +

168 + ```bash

169 + ./go.d.plugin -d -m exim -j jobName

170 + ```

171 +

172 ### Getting Logs

173

174 If you're encountering problems with the `exim` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/fail2ban/integrations/fail2ban.md

+6

@@ -178,6 +178,12 @@ should give you clues as to why the collector isn't working.

178 ./go.d.plugin -d -m fail2ban

179 ```

180

181 + To debug a specific job:

182 +

183 + ```bash

184 + ./go.d.plugin -d -m fail2ban -j jobName

185 + ```

186 +

187 ### Getting Logs

188

189 If you're encountering problems with the `fail2ban` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/filecheck/integrations/files_and_directories.md

+6

@@ -252,6 +252,12 @@ should give you clues as to why the collector isn't working.

252 ./go.d.plugin -d -m filecheck

253 ```

254

255 + To debug a specific job:

256 +

257 + ```bash

258 + ./go.d.plugin -d -m filecheck -j jobName

259 + ```

260 +

261 ### Getting Logs

262

263 If you're encountering problems with the `filecheck` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/fluentd/integrations/fluentd.md

+6

@@ -228,6 +228,12 @@ should give you clues as to why the collector isn't working.

228 ./go.d.plugin -d -m fluentd

229 ```

230

231 + To debug a specific job:

232 +

233 + ```bash

234 + ./go.d.plugin -d -m fluentd -j jobName

235 + ```

236 +

237 ### Getting Logs

238

239 If you're encountering problems with the `fluentd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/freeradius/integrations/freeradius.md

+6

@@ -206,6 +206,12 @@ should give you clues as to why the collector isn't working.

206 ./go.d.plugin -d -m freeradius

207 ```

208

209 + To debug a specific job:

210 +

211 + ```bash

212 + ./go.d.plugin -d -m freeradius -j jobName

213 + ```

214 +

215 ### Getting Logs

216

217 If you're encountering problems with the `freeradius` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/gearman/integrations/gearman.md

+6

@@ -207,6 +207,12 @@ should give you clues as to why the collector isn't working.

207 ./go.d.plugin -d -m gearman

208 ```

209

210 + To debug a specific job:

211 +

212 + ```bash

213 + ./go.d.plugin -d -m gearman -j jobName

214 + ```

215 +

216 ### Getting Logs

217

218 If you're encountering problems with the `gearman` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/geth/integrations/go-ethereum.md

+6

@@ -224,6 +224,12 @@ should give you clues as to why the collector isn't working.

224 ./go.d.plugin -d -m geth

225 ```

226

227 + To debug a specific job:

228 +

229 + ```bash

230 + ./go.d.plugin -d -m geth -j jobName

231 + ```

232 +

233 ### Getting Logs

234

235 If you're encountering problems with the `geth` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/haproxy/integrations/haproxy.md

+6

@@ -248,6 +248,12 @@ should give you clues as to why the collector isn't working.

248 ./go.d.plugin -d -m haproxy

249 ```

250

251 + To debug a specific job:

252 +

253 + ```bash

254 + ./go.d.plugin -d -m haproxy -j jobName

255 + ```

256 +

257 ### Getting Logs

258

259 If you're encountering problems with the `haproxy` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/hddtemp/integrations/hdd_temperature.md

+6

@@ -196,6 +196,12 @@ should give you clues as to why the collector isn't working.

196 ./go.d.plugin -d -m hddtemp

197 ```

198

199 + To debug a specific job:

200 +

201 + ```bash

202 + ./go.d.plugin -d -m hddtemp -j jobName

203 + ```

204 +

205 ### Getting Logs

206

207 If you're encountering problems with the `hddtemp` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/hdfs/integrations/hadoop_distributed_file_system_hdfs.md

+6

@@ -258,6 +258,12 @@ should give you clues as to why the collector isn't working.

258 ./go.d.plugin -d -m hfs

259 ```

260

261 + To debug a specific job:

262 +

263 + ```bash

264 + ./go.d.plugin -d -m hfs -j jobName

265 + ```

266 +

267 ### Getting Logs

268

269 If you're encountering problems with the `hfs` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/hpssa/integrations/hpe_smart_arrays.md

+6

@@ -243,6 +243,12 @@ should give you clues as to why the collector isn't working.

243 ./go.d.plugin -d -m hpssa

244 ```

245

246 + To debug a specific job:

247 +

248 + ```bash

249 + ./go.d.plugin -d -m hpssa -j jobName

250 + ```

251 +

252 ### Getting Logs

253

254 If you're encountering problems with the `hpssa` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/httpcheck/integrations/http_endpoints.md

+6

@@ -346,6 +346,12 @@ should give you clues as to why the collector isn't working.

346 ./go.d.plugin -d -m httpcheck

347 ```

348

349 + To debug a specific job:

350 +

351 + ```bash

352 + ./go.d.plugin -d -m httpcheck -j jobName

353 + ```

354 +

355 ### Getting Logs

356

357 If you're encountering problems with the `httpcheck` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/icecast/integrations/icecast.md

+6

@@ -198,6 +198,12 @@ should give you clues as to why the collector isn't working.

198 ./go.d.plugin -d -m icecast

199 ```

200

201 + To debug a specific job:

202 +

203 + ```bash

204 + ./go.d.plugin -d -m icecast -j jobName

205 + ```

206 +

207 ### Getting Logs

208

209 If you're encountering problems with the `icecast` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/intelgpu/integrations/intel_gpu.md

+6

@@ -185,6 +185,12 @@ should give you clues as to why the collector isn't working.

185 ./go.d.plugin -d -m intelgpu

186 ```

187

188 + To debug a specific job:

189 +

190 + ```bash

191 + ./go.d.plugin -d -m intelgpu -j jobName

192 + ```

193 +

194 ### Getting Logs

195

196 If you're encountering problems with the `intelgpu` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/ipfs/integrations/ipfs.md

+6

@@ -218,6 +218,12 @@ should give you clues as to why the collector isn't working.

218 ./go.d.plugin -d -m ipfs

219 ```

220

221 + To debug a specific job:

222 +

223 + ```bash

224 + ./go.d.plugin -d -m ipfs -j jobName

225 + ```

226 +

227 ### Getting Logs

228

229 If you're encountering problems with the `ipfs` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/isc_dhcpd/integrations/isc_dhcp.md

+6

@@ -203,6 +203,12 @@ should give you clues as to why the collector isn't working.

203 ./go.d.plugin -d -m isc_dhcpd

204 ```

205

206 + To debug a specific job:

207 +

208 + ```bash

209 + ./go.d.plugin -d -m isc_dhcpd -j jobName

210 + ```

211 +

212 ### Getting Logs

213

214 If you're encountering problems with the `isc_dhcpd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/k8s_kubelet/integrations/kubelet.md

+6

@@ -226,6 +226,12 @@ should give you clues as to why the collector isn't working.

226 ./go.d.plugin -d -m k8s_kubelet

227 ```

228

229 + To debug a specific job:

230 +

231 + ```bash

232 + ./go.d.plugin -d -m k8s_kubelet -j jobName

233 + ```

234 +

235 ### Getting Logs

236

237 If you're encountering problems with the `k8s_kubelet` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/k8s_kubeproxy/integrations/kubeproxy.md

+6

@@ -193,6 +193,12 @@ should give you clues as to why the collector isn't working.

193 ./go.d.plugin -d -m k8s_kubeproxy

194 ```

195

196 + To debug a specific job:

197 +

198 + ```bash

199 + ./go.d.plugin -d -m k8s_kubeproxy -j jobName

200 + ```

201 +

202 ### Getting Logs

203

204 If you're encountering problems with the `k8s_kubeproxy` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/k8s_state/integrations/kubernetes_cluster_state.md

+6

@@ -279,6 +279,12 @@ should give you clues as to why the collector isn't working.

279 ./go.d.plugin -d -m k8s_state

280 ```

281

282 + To debug a specific job:

283 +

284 + ```bash

285 + ./go.d.plugin -d -m k8s_state -j jobName

286 + ```

287 +

288 ### Getting Logs

289

290 If you're encountering problems with the `k8s_state` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/lighttpd/integrations/lighttpd.md

+6

@@ -238,6 +238,12 @@ should give you clues as to why the collector isn't working.

238 ./go.d.plugin -d -m lighttpd

239 ```

240

241 + To debug a specific job:

242 +

243 + ```bash

244 + ./go.d.plugin -d -m lighttpd -j jobName

245 + ```

246 +

247 ### Getting Logs

248

249 If you're encountering problems with the `lighttpd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/litespeed/integrations/litespeed.md

+6

@@ -168,6 +168,12 @@ should give you clues as to why the collector isn't working.

168 ./go.d.plugin -d -m litespeed

169 ```

170

171 + To debug a specific job:

172 +

173 + ```bash

174 + ./go.d.plugin -d -m litespeed -j jobName

175 + ```

176 +

177 ### Getting Logs

178

179 If you're encountering problems with the `litespeed` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/logind/integrations/systemd-logind_users.md

+6

@@ -144,6 +144,12 @@ should give you clues as to why the collector isn't working.

144 ./go.d.plugin -d -m logind

145 ```

146

147 + To debug a specific job:

148 +

149 + ```bash

150 + ./go.d.plugin -d -m logind -j jobName

151 + ```

152 +

153 ### Getting Logs

154

155 If you're encountering problems with the `logind` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/logstash/integrations/logstash.md

+6

@@ -255,6 +255,12 @@ should give you clues as to why the collector isn't working.

255 ./go.d.plugin -d -m logstash

256 ```

257

258 + To debug a specific job:

259 +

260 + ```bash

261 + ./go.d.plugin -d -m logstash -j jobName

262 + ```

263 +

264 ### Getting Logs

265

266 If you're encountering problems with the `logstash` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/lvm/integrations/lvm_logical_volumes.md

+6

@@ -177,6 +177,12 @@ should give you clues as to why the collector isn't working.

177 ./go.d.plugin -d -m lvm

178 ```

179

180 + To debug a specific job:

181 +

182 + ```bash

183 + ./go.d.plugin -d -m lvm -j jobName

184 + ```

185 +

186 ### Getting Logs

187

188 If you're encountering problems with the `lvm` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/maxscale/integrations/maxscale.md

+6

@@ -248,6 +248,12 @@ should give you clues as to why the collector isn't working.

248 ./go.d.plugin -d -m maxscale

249 ```

250

251 + To debug a specific job:

252 +

253 + ```bash

254 + ./go.d.plugin -d -m maxscale -j jobName

255 + ```

256 +

257 ### Getting Logs

258

259 If you're encountering problems with the `maxscale` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/megacli/integrations/megacli_megaraid.md

+6

@@ -225,6 +225,12 @@ should give you clues as to why the collector isn't working.

225 ./go.d.plugin -d -m megacli

226 ```

227

228 + To debug a specific job:

229 +

230 + ```bash

231 + ./go.d.plugin -d -m megacli -j jobName

232 + ```

233 +

234 ### Getting Logs

235

236 If you're encountering problems with the `megacli` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/memcached/integrations/memcached.md

+6

@@ -203,6 +203,12 @@ should give you clues as to why the collector isn't working.

203 ./go.d.plugin -d -m memcached

204 ```

205

206 + To debug a specific job:

207 +

208 + ```bash

209 + ./go.d.plugin -d -m memcached -j jobName

210 + ```

211 +

212 ### Getting Logs

213

214 If you're encountering problems with the `memcached` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/mongodb/integrations/mongodb.md

+6

@@ -363,6 +363,12 @@ should give you clues as to why the collector isn't working.

363 ./go.d.plugin -d -m mongodb

364 ```

365

366 + To debug a specific job:

367 +

368 + ```bash

369 + ./go.d.plugin -d -m mongodb -j jobName

370 + ```

371 +

372 ### Getting Logs

373

374 If you're encountering problems with the `mongodb` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/monit/integrations/monit.md

+6

@@ -227,6 +227,12 @@ should give you clues as to why the collector isn't working.

227 ./go.d.plugin -d -m monit

228 ```

229

230 + To debug a specific job:

231 +

232 + ```bash

233 + ./go.d.plugin -d -m monit -j jobName

234 + ```

235 +

236 ### Getting Logs

237

238 If you're encountering problems with the `monit` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/mysql/integrations/mariadb.md

+6

@@ -373,6 +373,12 @@ should give you clues as to why the collector isn't working.

373 ./go.d.plugin -d -m mysql

374 ```

375

376 + To debug a specific job:

377 +

378 + ```bash

379 + ./go.d.plugin -d -m mysql -j jobName

380 + ```

381 +

382 ### Getting Logs

383

384 If you're encountering problems with the `mysql` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/mysql/integrations/mysql.md

+6

@@ -373,6 +373,12 @@ should give you clues as to why the collector isn't working.

373 ./go.d.plugin -d -m mysql

374 ```

375

376 + To debug a specific job:

377 +

378 + ```bash

379 + ./go.d.plugin -d -m mysql -j jobName

380 + ```

381 +

382 ### Getting Logs

383

384 If you're encountering problems with the `mysql` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/mysql/integrations/percona_mysql.md

+6

@@ -373,6 +373,12 @@ should give you clues as to why the collector isn't working.

373 ./go.d.plugin -d -m mysql

374 ```

375

376 + To debug a specific job:

377 +

378 + ```bash

379 + ./go.d.plugin -d -m mysql -j jobName

380 + ```

381 +

382 ### Getting Logs

383

384 If you're encountering problems with the `mysql` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nats/integrations/nats.md

+6

@@ -394,6 +394,12 @@ should give you clues as to why the collector isn't working.

394 ./go.d.plugin -d -m nats

395 ```

396

397 + To debug a specific job:

398 +

399 + ```bash

400 + ./go.d.plugin -d -m nats -j jobName

401 + ```

402 +

403 ### Getting Logs

404

405 If you're encountering problems with the `nats` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nginx/integrations/nginx.md

+6

@@ -239,6 +239,12 @@ should give you clues as to why the collector isn't working.

239 ./go.d.plugin -d -m nginx

240 ```

241

242 + To debug a specific job:

243 +

244 + ```bash

245 + ./go.d.plugin -d -m nginx -j jobName

246 + ```

247 +

248 ### Getting Logs

249

250 If you're encountering problems with the `nginx` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nginxplus/integrations/nginx_plus.md

+6

@@ -420,6 +420,12 @@ should give you clues as to why the collector isn't working.

420 ./go.d.plugin -d -m nginxplus

421 ```

422

423 + To debug a specific job:

424 +

425 + ```bash

426 + ./go.d.plugin -d -m nginxplus -j jobName

427 + ```

428 +

429 ### Getting Logs

430

431 If you're encountering problems with the `nginxplus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nginxunit/integrations/nginx_unit.md

+6

@@ -234,6 +234,12 @@ should give you clues as to why the collector isn't working.

234 ./go.d.plugin -d -m nginxunit

235 ```

236

237 + To debug a specific job:

238 +

239 + ```bash

240 + ./go.d.plugin -d -m nginxunit -j jobName

241 + ```

242 +

243 ### Getting Logs

244

245 If you're encountering problems with the `nginxunit` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nginxvts/integrations/nginx_vts.md

+6

@@ -240,6 +240,12 @@ should give you clues as to why the collector isn't working.

240 ./go.d.plugin -d -m nginxvts

241 ```

242

243 + To debug a specific job:

244 +

245 + ```bash

246 + ./go.d.plugin -d -m nginxvts -j jobName

247 + ```

248 +

249 ### Getting Logs

250

251 If you're encountering problems with the `nginxvts` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nsd/integrations/nsd.md

+6

@@ -179,6 +179,12 @@ should give you clues as to why the collector isn't working.

179 ./go.d.plugin -d -m nsd

180 ```

181

182 + To debug a specific job:

183 +

184 + ```bash

185 + ./go.d.plugin -d -m nsd -j jobName

186 + ```

187 +

188 ### Getting Logs

189

190 If you're encountering problems with the `nsd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/ntpd/integrations/ntpd.md

+6

@@ -235,6 +235,12 @@ should give you clues as to why the collector isn't working.

235 ./go.d.plugin -d -m ntpd

236 ```

237

238 + To debug a specific job:

239 +

240 + ```bash

241 + ./go.d.plugin -d -m ntpd -j jobName

242 + ```

243 +

244 ### Getting Logs

245

246 If you're encountering problems with the `ntpd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nvidia_smi/integrations/nvidia_gpu.md

+6

@@ -205,6 +205,12 @@ should give you clues as to why the collector isn't working.

205 ./go.d.plugin -d -m nvidia_smi

206 ```

207

208 + To debug a specific job:

209 +

210 + ```bash

211 + ./go.d.plugin -d -m nvidia_smi -j jobName

212 + ```

213 +

214 ### Getting Logs

215

216 If you're encountering problems with the `nvidia_smi` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/nvme/integrations/nvme_devices.md

+6

@@ -218,6 +218,12 @@ should give you clues as to why the collector isn't working.

218 ./go.d.plugin -d -m nvme

219 ```

220

221 + To debug a specific job:

222 +

223 + ```bash

224 + ./go.d.plugin -d -m nvme -j jobName

225 + ```

226 +

227 ### Getting Logs

228

229 If you're encountering problems with the `nvme` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/openldap/integrations/openldap.md

+6

@@ -200,6 +200,12 @@ should give you clues as to why the collector isn't working.

200 ./go.d.plugin -d -m openldap

201 ```

202

203 + To debug a specific job:

204 +

205 + ```bash

206 + ./go.d.plugin -d -m openldap -j jobName

207 + ```

208 +

209 ### Getting Logs

210

211 If you're encountering problems with the `openldap` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/openvpn/integrations/openvpn.md

+6

@@ -230,6 +230,12 @@ should give you clues as to why the collector isn't working.

230 ./go.d.plugin -d -m openvpn

231 ```

232

233 + To debug a specific job:

234 +

235 + ```bash

236 + ./go.d.plugin -d -m openvpn -j jobName

237 + ```

238 +

239 ### Getting Logs

240

241 If you're encountering problems with the `openvpn` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/openvpn_status_log/integrations/openvpn_status_log.md

+6

@@ -185,6 +185,12 @@ should give you clues as to why the collector isn't working.

185 ./go.d.plugin -d -m openvpn_status_log

186 ```

187

188 + To debug a specific job:

189 +

190 + ```bash

191 + ./go.d.plugin -d -m openvpn_status_log -j jobName

192 + ```

193 +

194 ### Getting Logs

195

196 If you're encountering problems with the `openvpn_status_log` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/oracledb/integrations/oracle_db.md

+6

@@ -276,6 +276,12 @@ should give you clues as to why the collector isn't working.

276 ./go.d.plugin -d -m oracledb

277 ```

278

279 + To debug a specific job:

280 +

281 + ```bash

282 + ./go.d.plugin -d -m oracledb -j jobName

283 + ```

284 +

285 ### Getting Logs

286

287 If you're encountering problems with the `oracledb` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/pgbouncer/integrations/pgbouncer.md

+6

@@ -261,6 +261,12 @@ should give you clues as to why the collector isn't working.

261 ./go.d.plugin -d -m pgbouncer

262 ```

263

264 + To debug a specific job:

265 +

266 + ```bash

267 + ./go.d.plugin -d -m pgbouncer -j jobName

268 + ```

269 +

270 ### Getting Logs

271

272 If you're encountering problems with the `pgbouncer` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/phpdaemon/integrations/phpdaemon.md

+6

@@ -305,6 +305,12 @@ should give you clues as to why the collector isn't working.

305 ./go.d.plugin -d -m phpdaemon

306 ```

307

308 + To debug a specific job:

309 +

310 + ```bash

311 + ./go.d.plugin -d -m phpdaemon -j jobName

312 + ```

313 +

314 ### Getting Logs

315

316 If you're encountering problems with the `phpdaemon` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/phpfpm/integrations/php-fpm.md

+6

@@ -236,6 +236,12 @@ should give you clues as to why the collector isn't working.

236 ./go.d.plugin -d -m phpfpm

237 ```

238

239 + To debug a specific job:

240 +

241 + ```bash

242 + ./go.d.plugin -d -m phpfpm -j jobName

243 + ```

244 +

245 ### Getting Logs

246

247 If you're encountering problems with the `phpfpm` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/pihole/integrations/pi-hole.md

+6

@@ -248,6 +248,12 @@ should give you clues as to why the collector isn't working.

248 ./go.d.plugin -d -m pihole

249 ```

250

251 + To debug a specific job:

252 +

253 + ```bash

254 + ./go.d.plugin -d -m pihole -j jobName

255 + ```

256 +

257 ### Getting Logs

258

259 If you're encountering problems with the `pihole` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/pika/integrations/pika.md

+6

@@ -228,6 +228,12 @@ should give you clues as to why the collector isn't working.

228 ./go.d.plugin -d -m pika

229 ```

230

231 + To debug a specific job:

232 +

233 + ```bash

234 + ./go.d.plugin -d -m pika -j jobName

235 + ```

236 +

237 ### Getting Logs

238

239 If you're encountering problems with the `pika` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/ping/integrations/ping.md

+6

@@ -249,6 +249,12 @@ should give you clues as to why the collector isn't working.

249 ./go.d.plugin -d -m ping

250 ```

251

252 + To debug a specific job:

253 +

254 + ```bash

255 + ./go.d.plugin -d -m ping -j jobName

256 + ```

257 +

258 ### Getting Logs

259

260 If you're encountering problems with the `ping` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/portcheck/integrations/tcp-udp_endpoints.md

+6

@@ -299,6 +299,12 @@ should give you clues as to why the collector isn't working.

299 ./go.d.plugin -d -m portcheck

300 ```

301

302 + To debug a specific job:

303 +

304 + ```bash

305 + ./go.d.plugin -d -m portcheck -j jobName

306 + ```

307 +

308 ### Getting Logs

309

310 If you're encountering problems with the `portcheck` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/postfix/integrations/postfix.md

+6

@@ -167,6 +167,12 @@ should give you clues as to why the collector isn't working.

167 ./go.d.plugin -d -m postfix

168 ```

169

170 + To debug a specific job:

171 +

172 + ```bash

173 + ./go.d.plugin -d -m postfix -j jobName

174 + ```

175 +

176 ### Getting Logs

177

178 If you're encountering problems with the `postfix` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/postgres/integrations/postgresql.md

+6

@@ -403,6 +403,12 @@ should give you clues as to why the collector isn't working.

403 ./go.d.plugin -d -m postgres

404 ```

405

406 + To debug a specific job:

407 +

408 + ```bash

409 + ./go.d.plugin -d -m postgres -j jobName

410 + ```

411 +

412 ### Getting Logs

413

414 If you're encountering problems with the `postgres` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/powerdns/integrations/powerdns_authoritative_server.md

+6

@@ -230,6 +230,12 @@ should give you clues as to why the collector isn't working.

230 ./go.d.plugin -d -m powerdns

231 ```

232

233 + To debug a specific job:

234 +

235 + ```bash

236 + ./go.d.plugin -d -m powerdns -j jobName

237 + ```

238 +

239 ### Getting Logs

240

241 If you're encountering problems with the `powerdns` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/powerdns_recursor/integrations/powerdns_recursor.md

+6

@@ -233,6 +233,12 @@ should give you clues as to why the collector isn't working.

233 ./go.d.plugin -d -m powerdns_recursor

234 ```

235

236 + To debug a specific job:

237 +

238 + ```bash

239 + ./go.d.plugin -d -m powerdns_recursor -j jobName

240 + ```

241 +

242 ### Getting Logs

243

244 If you're encountering problems with the `powerdns_recursor` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/4d_server.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/8430ft_modem.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/a10_acos_network_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/airthings_waveplus_air_sensor.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/akamai_edge_dns_traffic.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/akamai_global_traffic_management.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/akami_cloudmonitor.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/alamos_fe2_server.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/alibaba_cloud.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/altaro_backup.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/amd_cpu_&_gpu.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/andrews_&_arnold_line_status.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/apache_airflow.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/apache_flink.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/apicast.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/apple_time_machine.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/arm_hwcpipe.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aruba_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/arvancloud_cdn.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/audisto.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/authlog.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_compute_instances.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_ec2_spot_instance.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_ecs.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_health_events.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_instance_health.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_quota.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_rds.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_s3_buckets.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/aws_sqs.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/azure_ad_app_passwords.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/azure_application.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/azure_elastic_pool_sql.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/azure_resources.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/azure_service_bus.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/azure_sql.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/bigquery.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/bird_routing_daemon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/blackbox.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/bobcat_miner_300.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/borg_backup.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/bosh.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/bpftrace_variables.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/bungeecord.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cadvisor.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/celery.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/certificate_transparency.md

+6

@@ -299,6 +299,12 @@ should give you clues as to why the collector isn't working.

299 ./go.d.plugin -d -m prometheus

300 ```

301

302 + To debug a specific job:

303 +

304 + ```bash

305 + ./go.d.plugin -d -m prometheus -j jobName

306 + ```

307 +

308 ### Getting Logs

309

310 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/checkpoint_device.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/chia.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cilium_agent.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cilium_operator.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cilium_proxy.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cisco_aci.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/citrix_netscaler.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/clamav_daemon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/clamscan_results.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/clash.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cloud_foundry_firehose.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cloudflare_pcap.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cloudwatch.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/clustercontrol_cmon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/collectd.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/concourse.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/craftbeerpi.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/crowdsec.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/crypto_exchanges.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cryptowatch.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/custom_exporter.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/cvmfs_clients.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ddwrt_routers.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_ecs_cluster.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_isilon_cluster.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dell_emc_xtremio_cluster.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dell_powermax.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dependency-track.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/digitalocean.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/discourse.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dmarc.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dnsbl.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dutch_electricity_smart_meter.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/dynatrace.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/eaton_ups.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/elgato_key_light_devices..md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/energomera_smart_power_meters.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/eos.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/etcd.md

+6

@@ -294,6 +294,12 @@ should give you clues as to why the collector isn't working.

294 ./go.d.plugin -d -m prometheus

295 ```

296

297 + To debug a specific job:

298 +

299 + ```bash

300 + ./go.d.plugin -d -m prometheus -j jobName

301 + ```

302 +

303 ### Getting Logs

304

305 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/excel_spreadsheet.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/fastd.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/fortigate_firewall.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/freebsd_nfs.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/freebsd_rctl-racct.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/freifunk_network.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/fritzbox_network_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/frrouting.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/gcp_gce.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/gcp_quota.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/generic_command_line_output.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/generic_storage_enclosure_tool.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/github_api_rate_limit.md

+6

@@ -299,6 +299,12 @@ should give you clues as to why the collector isn't working.

299 ./go.d.plugin -d -m prometheus

300 ```

301

302 + To debug a specific job:

303 +

304 + ```bash

305 + ./go.d.plugin -d -m prometheus -j jobName

306 + ```

307 +

308 ### Getting Logs

309

310 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/github_repository.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/gitlab_runner.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/gobetween.md

+6

@@ -294,6 +294,12 @@ should give you clues as to why the collector isn't working.

294 ./go.d.plugin -d -m prometheus

295 ```

296

297 + To debug a specific job:

298 +

299 + ```bash

300 + ./go.d.plugin -d -m prometheus -j jobName

301 + ```

302 +

303 ### Getting Logs

304

305 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/google_cloud_platform.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/google_pagespeed.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/google_stackdriver.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/gpsd.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/grafana.md

+6

@@ -294,6 +294,12 @@ should give you clues as to why the collector isn't working.

294 ./go.d.plugin -d -m prometheus

295 ```

296

297 + To debug a specific job:

298 +

299 + ```bash

300 + ./go.d.plugin -d -m prometheus -j jobName

301 + ```

302 +

303 ### Getting Logs

304

305 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/graylog_server.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/gtp.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/halon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hana.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hashicorp_vault_secrets.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hasura_graphql_server.md

+6

@@ -299,6 +299,12 @@ should give you clues as to why the collector isn't working.

299 ./go.d.plugin -d -m prometheus

300 ```

301

302 + To debug a specific job:

303 +

304 + ```bash

305 + ./go.d.plugin -d -m prometheus -j jobName

306 + ```

307 +

308 ### Getting Logs

309

310 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hdsentinel.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/helium_hotspot.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/helium_miner_validator.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hhvm.md

+6

@@ -299,6 +299,12 @@ should give you clues as to why the collector isn't working.

299 ./go.d.plugin -d -m prometheus

300 ```

301

302 + To debug a specific job:

303 +

304 + ```bash

305 + ./go.d.plugin -d -m prometheus -j jobName

306 + ```

307 +

308 ### Getting Logs

309

310 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hitron_cgn_series_cpe.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hitron_coda_cable_modem.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/homebridge.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/homey.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/honeypot.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hp_ilo.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/huawei_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/hubble.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ibm_aix_systems_njmon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ibm_cryptoexpress_cex_cards.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ibm_mq.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ibm_spectrum_virtualize.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ibm_z_hardware_management_console.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/influxdb.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/iota_full_node.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ipmi_by_soundcloud.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/iqair_airvisual_air_quality_monitors.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/jarvis_standing_desk.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/jenkins.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/jetbrains_floating_license_server.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/jmx.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/jolokia.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/journald.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/kafka.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/kafka_connect.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/kafka_consumer_lag.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/kafka_zookeeper.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/kannel.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/keepalived.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/kubernetes_cluster_cloud_cost.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/lagerist_disk_latency.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ldap.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/linode.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/loki.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/lustre_metadata.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/lynis_audit_reports.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/machbase.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/maildir.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/meilisearch.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/memcached_community.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/meraki_dashboard.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mesos.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mikrotik_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mikrotik_routeros_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/minecraft.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/modbus_protocol.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mogilefs.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/monnit_sensors_mqtt.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mosquitto.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mp707_usb_thermometer.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mqtt_blackbox.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/mtail.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/naemon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nagios.md

+6

@@ -299,6 +299,12 @@ should give you clues as to why the collector isn't working.

299 ./go.d.plugin -d -m prometheus

300 ```

301

302 + To debug a specific job:

303 +

304 + ```bash

305 + ./go.d.plugin -d -m prometheus -j jobName

306 + ```

307 +

308 ### Getting Logs

309

310 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nature_remo_e_lite_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/netapp_ontap_api.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/netapp_solidfire.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/netatmo_sensors.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/netflow.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/netmeter.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/new_relic.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nextcloud_servers.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nextdns.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nftables.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nrpe_daemon.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nsx-t.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/nvml.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/obs_studio.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/odbc.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/open_vswitch.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openhab.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openldap_community.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openrc.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openrct2.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openroadm_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openstack.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openvas.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/openweathermap.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/oracle_db_community.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/otrs.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/patroni.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/personal_weather_station.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/pgbackrest.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/pgpool-ii.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/philips_hue.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/pimoroni_enviro+.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/pingdom.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/podman.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/powerpal_devices.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/proftpd.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/prometheus_endpoint.md

+6

@@ -294,6 +294,12 @@ should give you clues as to why the collector isn't working.

294 ./go.d.plugin -d -m prometheus

295 ```

296

297 + To debug a specific job:

298 +

299 + ```bash

300 + ./go.d.plugin -d -m prometheus -j jobName

301 + ```

302 +

303 ### Getting Logs

304

305 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/proxmox_ve.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/radio_thermostat.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/radius.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/rancher.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/raritan_pdu.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/redis_queue.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ripe_atlas.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sabnzbd.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/salicru_eqx_inverter.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sense_energy.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sentry.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/servertech.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/shell_command.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/shelly_humidity_sensor.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sia.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/siemens_s7_plc.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/site_24x7.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/slurm.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sma_inverters.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/smart_meters_sml.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/smartrg_808ac_cable_modem.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/softether_vpn_server.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/solar_logging_stick.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/solaredge_inverters.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/solis_ginlong_5g_inverters.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sonic_nos.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/spacelift.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/speedify_cli.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sphinx.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sql_database_agnostic.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ssh.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ssl_certificate.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/starlink_spacex.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/starwind_vsan_vsphere_edition.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/statuspage.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/steam.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/storidge.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/stream.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/strongswan.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sunspec_solar_energy.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/suricata.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/synology_activebackup.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/sysload.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/t-rex_nvidia_gpu_miner.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tacacs.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tado_smart_heating_solution.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tankerkoenig_api.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tesla_powerwall.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tesla_vehicle.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tesla_wall_connector.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/tp-link_p110.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/traceroute.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/twincat_ads_web_service.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/twitch.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/ubiquiti_ufiber_olt.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/uptimerobot.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/vault_pki.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/vertica.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/vscode.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/warp10.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/xiaomi_mi_flora.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/xmpp_server.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/yourls_url_shortener.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/zerto.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/zulip.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/prometheus/integrations/zyxel_gs1200-8.md

+6

@@ -298,6 +298,12 @@ should give you clues as to why the collector isn't working.

298 ./go.d.plugin -d -m prometheus

299 ```

300

301 + To debug a specific job:

302 +

303 + ```bash

304 + ./go.d.plugin -d -m prometheus -j jobName

305 + ```

306 +

307 ### Getting Logs

308

309 If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/proxysql/integrations/proxysql.md

+6

@@ -281,6 +281,12 @@ should give you clues as to why the collector isn't working.

281 ./go.d.plugin -d -m proxysql

282 ```

283

284 + To debug a specific job:

285 +

286 + ```bash

287 + ./go.d.plugin -d -m proxysql -j jobName

288 + ```

289 +

290 ### Getting Logs

291

292 If you're encountering problems with the `proxysql` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/pulsar/integrations/apache_pulsar.md

+6

@@ -286,6 +286,12 @@ should give you clues as to why the collector isn't working.

286 ./go.d.plugin -d -m pulsar

287 ```

288

289 + To debug a specific job:

290 +

291 + ```bash

292 + ./go.d.plugin -d -m pulsar -j jobName

293 + ```

294 +

295 ### Getting Logs

296

297 If you're encountering problems with the `pulsar` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/puppet/integrations/puppet.md

+6

@@ -205,6 +205,12 @@ should give you clues as to why the collector isn't working.

205 ./go.d.plugin -d -m puppet

206 ```

207

208 + To debug a specific job:

209 +

210 + ```bash

211 + ./go.d.plugin -d -m puppet -j jobName

212 + ```

213 +

214 ### Getting Logs

215

216 If you're encountering problems with the `puppet` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/rabbitmq/integrations/rabbitmq.md

+6

@@ -337,6 +337,12 @@ should give you clues as to why the collector isn't working.

337 ./go.d.plugin -d -m rabbitmq

338 ```

339

340 + To debug a specific job:

341 +

342 + ```bash

343 + ./go.d.plugin -d -m rabbitmq -j jobName

344 + ```

345 +

346 ### Getting Logs

347

348 If you're encountering problems with the `rabbitmq` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/redis/integrations/redis.md

+6

@@ -259,6 +259,12 @@ should give you clues as to why the collector isn't working.

259 ./go.d.plugin -d -m redis

260 ```

261

262 + To debug a specific job:

263 +

264 + ```bash

265 + ./go.d.plugin -d -m redis -j jobName

266 + ```

267 +

268 ### Getting Logs

269

270 If you're encountering problems with the `redis` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/rethinkdb/integrations/rethinkdb.md

+6

@@ -229,6 +229,12 @@ should give you clues as to why the collector isn't working.

229 ./go.d.plugin -d -m rethinkdb

230 ```

231

232 + To debug a specific job:

233 +

234 + ```bash

235 + ./go.d.plugin -d -m rethinkdb -j jobName

236 + ```

237 +

238 ### Getting Logs

239

240 If you're encountering problems with the `rethinkdb` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/riakkv/integrations/riak_kv.md

+6

@@ -255,6 +255,12 @@ should give you clues as to why the collector isn't working.

255 ./go.d.plugin -d -m riakkv

256 ```

257

258 + To debug a specific job:

259 +

260 + ```bash

261 + ./go.d.plugin -d -m riakkv -j jobName

262 + ```

263 +

264 ### Getting Logs

265

266 If you're encountering problems with the `riakkv` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/rspamd/integrations/rspamd.md

+6

@@ -215,6 +215,12 @@ should give you clues as to why the collector isn't working.

215 ./go.d.plugin -d -m rspamd

216 ```

217

218 + To debug a specific job:

219 +

220 + ```bash

221 + ./go.d.plugin -d -m rspamd -j jobName

222 + ```

223 +

224 ### Getting Logs

225

226 If you're encountering problems with the `rspamd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/samba/integrations/samba.md

+6

@@ -212,6 +212,12 @@ should give you clues as to why the collector isn't working.

212 ./go.d.plugin -d -m samba

213 ```

214

215 + To debug a specific job:

216 +

217 + ```bash

218 + ./go.d.plugin -d -m samba -j jobName

219 + ```

220 +

221 ### Getting Logs

222

223 If you're encountering problems with the `samba` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/scaleio/integrations/dell_emc_scaleio.md

+6

@@ -262,6 +262,12 @@ should give you clues as to why the collector isn't working.

262 ./go.d.plugin -d -m scaleio

263 ```

264

265 + To debug a specific job:

266 +

267 + ```bash

268 + ./go.d.plugin -d -m scaleio -j jobName

269 + ```

270 +

271 ### Getting Logs

272

273 If you're encountering problems with the `scaleio` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/sensors/integrations/linux_sensors.md

+6

@@ -221,6 +221,12 @@ should give you clues as to why the collector isn't working.

221 ./go.d.plugin -d -m sensors

222 ```

223

224 + To debug a specific job:

225 +

226 + ```bash

227 + ./go.d.plugin -d -m sensors -j jobName

228 + ```

229 +

230 ### Getting Logs

231

232 If you're encountering problems with the `sensors` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/smartctl/integrations/s.m.a.r.t..md

+6

@@ -259,6 +259,12 @@ should give you clues as to why the collector isn't working.

259 ./go.d.plugin -d -m smartctl

260 ```

261

262 + To debug a specific job:

263 +

264 + ```bash

265 + ./go.d.plugin -d -m smartctl -j jobName

266 + ```

267 +

268 ### Getting Logs

269

270 If you're encountering problems with the `smartctl` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/snmp/integrations/snmp_devices.md

+6

@@ -486,6 +486,12 @@ should give you clues as to why the collector isn't working.

486 ./go.d.plugin -d -m snmp

487 ```

488

489 + To debug a specific job:

490 +

491 + ```bash

492 + ./go.d.plugin -d -m snmp -j jobName

493 + ```

494 +

495 ### Getting Logs

496

497 If you're encountering problems with the `snmp` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/spigotmc/integrations/spigotmc.md

+6

@@ -193,6 +193,12 @@ should give you clues as to why the collector isn't working.

193 ./go.d.plugin -d -m spigotmc

194 ```

195

196 + To debug a specific job:

197 +

198 + ```bash

199 + ./go.d.plugin -d -m spigotmc -j jobName

200 + ```

201 +

202 ### Getting Logs

203

204 If you're encountering problems with the `spigotmc` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/squid/integrations/squid.md

+6

@@ -199,6 +199,12 @@ should give you clues as to why the collector isn't working.

199 ./go.d.plugin -d -m squid

200 ```

201

202 + To debug a specific job:

203 +

204 + ```bash

205 + ./go.d.plugin -d -m squid -j jobName

206 + ```

207 +

208 ### Getting Logs

209

210 If you're encountering problems with the `squid` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/squidlog/integrations/squid_log_files.md

+6

@@ -256,6 +256,12 @@ should give you clues as to why the collector isn't working.

256 ./go.d.plugin -d -m squidlog

257 ```

258

259 + To debug a specific job:

260 +

261 + ```bash

262 + ./go.d.plugin -d -m squidlog -j jobName

263 + ```

264 +

265 ### Getting Logs

266

267 If you're encountering problems with the `squidlog` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/storcli/integrations/storecli_raid.md

+6

@@ -228,6 +228,12 @@ should give you clues as to why the collector isn't working.

228 ./go.d.plugin -d -m storcli

229 ```

230

231 + To debug a specific job:

232 +

233 + ```bash

234 + ./go.d.plugin -d -m storcli -j jobName

235 + ```

236 +

237 ### Getting Logs

238

239 If you're encountering problems with the `storcli` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/supervisord/integrations/supervisor.md

+6

@@ -221,6 +221,12 @@ should give you clues as to why the collector isn't working.

221 ./go.d.plugin -d -m supervisord

222 ```

223

224 + To debug a specific job:

225 +

226 + ```bash

227 + ./go.d.plugin -d -m supervisord -j jobName

228 + ```

229 +

230 ### Getting Logs

231

232 If you're encountering problems with the `supervisord` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/systemdunits/integrations/systemd_units.md

+6

@@ -296,6 +296,12 @@ should give you clues as to why the collector isn't working.

296 ./go.d.plugin -d -m systemdunits

297 ```

298

299 + To debug a specific job:

300 +

301 + ```bash

302 + ./go.d.plugin -d -m systemdunits -j jobName

303 + ```

304 +

305 ### Getting Logs

306

307 If you're encountering problems with the `systemdunits` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/tengine/integrations/tengine.md

+6

@@ -239,6 +239,12 @@ should give you clues as to why the collector isn't working.

239 ./go.d.plugin -d -m tengine

240 ```

241

242 + To debug a specific job:

243 +

244 + ```bash

245 + ./go.d.plugin -d -m tengine -j jobName

246 + ```

247 +

248 ### Getting Logs

249

250 If you're encountering problems with the `tengine` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/tomcat/integrations/tomcat.md

+6

@@ -247,6 +247,12 @@ should give you clues as to why the collector isn't working.

247 ./go.d.plugin -d -m tomcat

248 ```

249

250 + To debug a specific job:

251 +

252 + ```bash

253 + ./go.d.plugin -d -m tomcat -j jobName

254 + ```

255 +

256 ### Getting Logs

257

258 If you're encountering problems with the `tomcat` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/tor/integrations/tor.md

+6

@@ -197,6 +197,12 @@ should give you clues as to why the collector isn't working.

197 ./go.d.plugin -d -m tor

198 ```

199

200 + To debug a specific job:

201 +

202 + ```bash

203 + ./go.d.plugin -d -m tor -j jobName

204 + ```

205 +

206 ### Getting Logs

207

208 If you're encountering problems with the `tor` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/traefik/integrations/traefik.md

+6

@@ -218,6 +218,12 @@ should give you clues as to why the collector isn't working.

218 ./go.d.plugin -d -m traefik

219 ```

220

221 + To debug a specific job:

222 +

223 + ```bash

224 + ./go.d.plugin -d -m traefik -j jobName

225 + ```

226 +

227 ### Getting Logs

228

229 If you're encountering problems with the `traefik` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/typesense/integrations/typesense.md

+6

@@ -217,6 +217,12 @@ should give you clues as to why the collector isn't working.

217 ./go.d.plugin -d -m typesense

218 ```

219

220 + To debug a specific job:

221 +

222 + ```bash

223 + ./go.d.plugin -d -m typesense -j jobName

224 + ```

225 +

226 ### Getting Logs

227

228 If you're encountering problems with the `typesense` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/unbound/integrations/unbound.md

+6

@@ -277,6 +277,12 @@ should give you clues as to why the collector isn't working.

277 ./go.d.plugin -d -m unbound

278 ```

279

280 + To debug a specific job:

281 +

282 + ```bash

283 + ./go.d.plugin -d -m unbound -j jobName

284 + ```

285 +

286 ### Getting Logs

287

288 If you're encountering problems with the `unbound` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/upsd/integrations/ups_nut.md

+6

@@ -218,6 +218,12 @@ should give you clues as to why the collector isn't working.

218 ./go.d.plugin -d -m upsd

219 ```

220

221 + To debug a specific job:

222 +

223 + ```bash

224 + ./go.d.plugin -d -m upsd -j jobName

225 + ```

226 +

227 ### Getting Logs

228

229 If you're encountering problems with the `upsd` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/uwsgi/integrations/uwsgi.md

+6

@@ -220,6 +220,12 @@ should give you clues as to why the collector isn't working.

220 ./go.d.plugin -d -m uwsgi

221 ```

222

223 + To debug a specific job:

224 +

225 + ```bash

226 + ./go.d.plugin -d -m uwsgi -j jobName

227 + ```

228 +

229 ### Getting Logs

230

231 If you're encountering problems with the `uwsgi` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/varnish/integrations/varnish.md

+6

@@ -203,6 +203,12 @@ should give you clues as to why the collector isn't working.

203 ./go.d.plugin -d -m varnish

204 ```

205

206 + To debug a specific job:

207 +

208 + ```bash

209 + ./go.d.plugin -d -m varnish -j jobName

210 + ```

211 +

212 ### Getting Logs

213

214 If you're encountering problems with the `varnish` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/vcsa/integrations/vcenter_server_appliance.md

+6

@@ -264,6 +264,12 @@ should give you clues as to why the collector isn't working.

264 ./go.d.plugin -d -m vcsa

265 ```

266

267 + To debug a specific job:

268 +

269 + ```bash

270 + ./go.d.plugin -d -m vcsa -j jobName

271 + ```

272 +

273 ### Getting Logs

274

275 If you're encountering problems with the `vcsa` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/vernemq/integrations/vernemq.md

+6

@@ -325,6 +325,12 @@ should give you clues as to why the collector isn't working.

325 ./go.d.plugin -d -m vernemq

326 ```

327

328 + To debug a specific job:

329 +

330 + ```bash

331 + ./go.d.plugin -d -m vernemq -j jobName

332 + ```

333 +

334 ### Getting Logs

335

336 If you're encountering problems with the `vernemq` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/vsphere/integrations/vmware_vcenter_server.md

+6

@@ -329,6 +329,12 @@ should give you clues as to why the collector isn't working.

329 ./go.d.plugin -d -m vsphere

330 ```

331

332 + To debug a specific job:

333 +

334 + ```bash

335 + ./go.d.plugin -d -m vsphere -j jobName

336 + ```

337 +

338 ### Getting Logs

339

340 If you're encountering problems with the `vsphere` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/w1sensor/integrations/1-wire_sensors.md

+6

@@ -162,6 +162,12 @@ should give you clues as to why the collector isn't working.

162 ./go.d.plugin -d -m w1sensor

163 ```

164

165 + To debug a specific job:

166 +

167 + ```bash

168 + ./go.d.plugin -d -m w1sensor -j jobName

169 + ```

170 +

171 ### Getting Logs

172

173 If you're encountering problems with the `w1sensor` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/weblog/integrations/web_server_log_files.md

+6

@@ -377,6 +377,12 @@ should give you clues as to why the collector isn't working.

377 ./go.d.plugin -d -m web_log

378 ```

379

380 + To debug a specific job:

381 +

382 + ```bash

383 + ./go.d.plugin -d -m web_log -j jobName

384 + ```

385 +

386 ### Getting Logs

387

388 If you're encountering problems with the `web_log` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/whoisquery/integrations/domain_expiration_date.md

+6

@@ -194,6 +194,12 @@ should give you clues as to why the collector isn't working.

194 ./go.d.plugin -d -m whoisquery

195 ```

196

197 + To debug a specific job:

198 +

199 + ```bash

200 + ./go.d.plugin -d -m whoisquery -j jobName

201 + ```

202 +

203 ### Getting Logs

204

205 If you're encountering problems with the `whoisquery` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/wireguard/integrations/wireguard.md

+6

@@ -176,6 +176,12 @@ should give you clues as to why the collector isn't working.

176 ./go.d.plugin -d -m wireguard

177 ```

178

179 + To debug a specific job:

180 +

181 + ```bash

182 + ./go.d.plugin -d -m wireguard -j jobName

183 + ```

184 +

185 ### Getting Logs

186

187 If you're encountering problems with the `wireguard` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/x509check/integrations/x.509_certificate.md

+6

@@ -233,6 +233,12 @@ should give you clues as to why the collector isn't working.

233 ./go.d.plugin -d -m x509check

234 ```

235

236 + To debug a specific job:

237 +

238 + ```bash

239 + ./go.d.plugin -d -m x509check -j jobName

240 + ```

241 +

242 ### Getting Logs

243

244 If you're encountering problems with the `x509check` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/yugabytedb/integrations/yugabytedb.md

+6

@@ -485,6 +485,12 @@ should give you clues as to why the collector isn't working.

485 ./go.d.plugin -d -m yugabytedb

486 ```

487

488 + To debug a specific job:

489 +

490 + ```bash

491 + ./go.d.plugin -d -m yugabytedb -j jobName

492 + ```

493 +

494 ### Getting Logs

495

496 If you're encountering problems with the `yugabytedb` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/zfspool/integrations/zfs_pools.md

+6

@@ -197,6 +197,12 @@ should give you clues as to why the collector isn't working.

197 ./go.d.plugin -d -m zfspool

198 ```

199

200 + To debug a specific job:

201 +

202 + ```bash

203 + ./go.d.plugin -d -m zfspool -j jobName

204 + ```

205 +

206 ### Getting Logs

207

208 If you're encountering problems with the `zfspool` collector, follow these steps to retrieve logs and identify potential issues:

src/go/plugin/go.d/collector/zookeeper/integrations/zookeeper.md

+6

@@ -230,6 +230,12 @@ should give you clues as to why the collector isn't working.

230 ./go.d.plugin -d -m zookeeper

231 ```

232

233 + To debug a specific job:

234 +

235 + ```bash

236 + ./go.d.plugin -d -m zookeeper -j jobName

237 + ```

238 +

239 ### Getting Logs

240

241 If you're encountering problems with the `zookeeper` collector, follow these steps to retrieve logs and identify potential issues:

Regenerate integrations docs (#20430)