Regenerate integrations docs (#22529)

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -370,4 +370,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

370 docker logs netdata 2>&1 | grep prometheus

371 ```

372

373 +### Disappearing or sparse metrics not clearing alerts

374 +

375 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

376 +

377 +

378

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

src/go/plugin/go.d/collector/prometheus/integrations/freebsd_rctl-racct.md

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -370,4 +370,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

370 docker logs netdata 2>&1 | grep prometheus

371 ```

372

373 +### Disappearing or sparse metrics not clearing alerts

374 +

375 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

376 +

377 +

378

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -370,4 +370,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

370 docker logs netdata 2>&1 | grep prometheus

371 ```

372

373 +### Disappearing or sparse metrics not clearing alerts

374 +

375 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

376 +

377 +

378

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -375,4 +375,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

375 docker logs netdata 2>&1 | grep prometheus

376 ```

377

378 +### Disappearing or sparse metrics not clearing alerts

379 +

380 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

381 +

382 +

383

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

src/go/plugin/go.d/collector/prometheus/integrations/pgpool-ii.md

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

src/go/plugin/go.d/collector/prometheus/integrations/pimoroni_enviro+.md

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -371,4 +371,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

371 docker logs netdata 2>&1 | grep prometheus

372 ```

373

374 +### Disappearing or sparse metrics not clearing alerts

375 +

376 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

377 +

378 +

379

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -370,4 +370,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

370 docker logs netdata 2>&1 | grep prometheus

371 ```

372

373 +### Disappearing or sparse metrics not clearing alerts

374 +

375 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

376 +

377 +

378

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382

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

+5

@@ -374,4 +374,9 @@ If your Netdata runs in a Docker container named "netdata" (replace if different

374 docker logs netdata 2>&1 | grep prometheus

375 ```

376

377 +### Disappearing or sparse metrics not clearing alerts

378 +

379 +When a metric disappears from the Prometheus endpoint response (for example, a gauge that is only exposed when its value is greater than 0), Netdata does not require any special value to stop tracking it. The Prometheus collector automatically detects metrics that are no longer present in the scrape response. After 10 consecutive collection cycles where the metric is absent, the associated chart is automatically removed and any alerts on that chart will clear. You do not need to send a special value (such as 0, NaN, or StaleNaN) — simply omitting the metric from the response is sufficient. Note that during the 10-cycle grace period, the last known value remains and alerts may not clear immediately.

380 +

381 +

382