Skip to content

Ingest New Documentation #2916

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Ingest New Documentation #2916

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
232 changes: 124 additions & 108 deletions docs/Alerts & Notifications/Alert Configuration Reference.mdx
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 0 additions & 2 deletions ...Alerts & Notifications/Notifications/Agent Dispatched Notifications/AWS SNS.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,5 +152,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/Alerta.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,5 +137,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/Custom.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,5 +183,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...Alerts & Notifications/Notifications/Agent Dispatched Notifications/Discord.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...erts & Notifications/Notifications/Agent Dispatched Notifications/Dynatrace.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,5 +133,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/Email.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,5 +134,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/Flock.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,5 +121,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/Gotify.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,5 +105,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/IRC.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,5 +141,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...erts & Notifications/Notifications/Agent Dispatched Notifications/Kavenegar.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,5 +128,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/Matrix.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,5 +141,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...ts & Notifications/Notifications/Agent Dispatched Notifications/MessageBird.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ... Notifications/Notifications/Agent Dispatched Notifications/Microsoft Teams.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,5 +126,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...lerts & Notifications/Notifications/Agent Dispatched Notifications/OpsGenie.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,5 +105,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...erts & Notifications/Notifications/Agent Dispatched Notifications/PagerDuty.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/Prowl.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,5 +127,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...lerts & Notifications/Notifications/Agent Dispatched Notifications/PushOver.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,5 +127,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...rts & Notifications/Notifications/Agent Dispatched Notifications/Pushbullet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...rts & Notifications/Notifications/Agent Dispatched Notifications/RocketChat.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,5 +124,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/SIGNL4.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,5 +103,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/SMS.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,5 +135,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...lerts & Notifications/Notifications/Agent Dispatched Notifications/SMSEagle.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,5 +167,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/Slack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,5 +108,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...lerts & Notifications/Notifications/Agent Dispatched Notifications/Telegram.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,5 +126,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/Twilio.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,5 +126,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/ilert.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,5 +103,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions docs/Alerts & Notifications/Notifications/Agent Dispatched Notifications/ntfy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,5 +146,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Agent Dispatched Notifications/syslog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,5 +141,3 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
```

Note that this will test _all_ alert mechanisms for the selected role.


2 changes: 0 additions & 2 deletions ...ts & Notifications/Notifications/Centralized Cloud Notifications/Amazon SNS.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,5 +49,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/ama
- Notifications: The notification types you want to receive
- **Integration configuration**
- Topic ARN: The topic provided on AWS SNS (with region) for where to publish your notifications.


2 changes: 0 additions & 2 deletions ...lerts & Notifications/Notifications/Centralized Cloud Notifications/Discord.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,5 +46,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/dis
- **Integration configuration**
- Webhook URL: The URL you copied from the previous section
- Channel Parameters: Select the channel type which the notifications will be sent to, if it is a Forum channel, you need to specify a thread name


2 changes: 0 additions & 2 deletions ...ts & Notifications/Notifications/Centralized Cloud Notifications/Mattermost.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,5 +50,3 @@ For more details please check [Incoming webhooks for Mattermost](https://develop
- Notifications: The notification types you want to receive
- **Integration configuration**
- Webhook URL: URL provided on Mattermost for the channel you want to receive your notifications


2 changes: 0 additions & 2 deletions ...Notifications/Notifications/Centralized Cloud Notifications/Microsoft Teams.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,5 +50,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/mic
- Notifications: The notification types you want to receive
- **Integration configuration**
- Microsoft Teams Incoming Webhook URL: The Incoming Webhook URL that you copied earlier.


2 changes: 0 additions & 2 deletions ...ifications/Notifications/Centralized Cloud Notifications/Netdata Mobile App.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,5 +37,3 @@ In order to login to the Netdata Mobile App
### Netdata Configuration

After linking your device, enable the toggle for **Mobile App Notifications** under the same settings panel.


2 changes: 0 additions & 2 deletions ...erts & Notifications/Notifications/Centralized Cloud Notifications/Opsgenie.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,5 +45,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/ops
- Notifications: The notification types you want to receive
- **Integration configuration**
- API Key: The key provided on Opsgenie for the channel you want to receive your notifications


2 changes: 0 additions & 2 deletions ...rts & Notifications/Notifications/Centralized Cloud Notifications/PagerDuty.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,5 +47,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/pag
- **Integration configuration**
- Integration Key: A 32 character key provided by PagerDuty to receive events on your service.
- Integration URL (Alert Events): The URL provided by PagerDuty where Netdata Cloud will send notifications.


2 changes: 0 additions & 2 deletions ...ts & Notifications/Notifications/Centralized Cloud Notifications/RocketChat.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,5 +51,3 @@ For more details please check [Incoming webhooks for RocketChat](https://docs.ro
- Notifications: The notification types you want to receive
- **Integration configuration**
- Webhook URL: URL provided on RocketChat for the channel you want to receive your notifications


2 changes: 0 additions & 2 deletions ...ts & Notifications/Notifications/Centralized Cloud Notifications/ServiceNow.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,5 +49,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/ser
- Instance URL: The base URL of your ServiceNow instance (for example, `https://my-instance.service-now.com/`).
- Username: The username of the ServiceNow integration user you created.
- Password: The password of the ServiceNow integration user you created.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Centralized Cloud Notifications/Slack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,5 +52,3 @@ For more details please check [Incoming webhooks for Slack](https://slack.com/he
- Notifications: The notification types you want to receive
- **Integration configuration**
- Webhook URL: URL provided on Slack for the channel you want to receive your notifications


2 changes: 0 additions & 2 deletions ...otifications/Notifications/Centralized Cloud Notifications/Splunk VictorOps.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,5 +40,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/spl
- Notifications: The notification types you want to receive
- **Integration configuration**
- Destination URL - The URL provided by VictorOps of your REST endpoint.


2 changes: 0 additions & 2 deletions ...Alerts & Notifications/Notifications/Centralized Cloud Notifications/Splunk.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,5 +41,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/spl
- **Integration configuration**
- HTTP Event Collector URI: The URI of your HTTP event collector in Splunk
- HTTP Event Collector Token: The token that Splunk provided to you when you created the HTTP Event Collector


2 changes: 0 additions & 2 deletions ...erts & Notifications/Notifications/Centralized Cloud Notifications/Telegram.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,5 +50,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/tel
- Bot Token: The token of your bot
- Chat ID: The chat id where your bot will deliver messages to
- Topic ID: The identifier of the chat topic to which your bot will send messages. If omitted or 0, messages will be sent to the General topic. If topics are not supported, messages will be sent to the chat.


2 changes: 0 additions & 2 deletions ...lerts & Notifications/Notifications/Centralized Cloud Notifications/Webhook.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -202,5 +202,3 @@ In basic authorization, the client sends a request with an Authorization header
##### Bearer token authentication

In bearer token authentication, the client sends a request with an Authorization header that includes a bearer token. The server then uses this token to authenticate the client. Bearer tokens are typically generated by an authentication service, and are passed to the client after a successful authentication. If this method is selected, the user can set the token to be used for connecting to the destination service.


2 changes: 0 additions & 2 deletions .../Alerts & Notifications/Notifications/Centralized Cloud Notifications/ilert.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,5 +52,3 @@ slug: "/alerts-&-notifications/notifications/centralized-cloud-notifications/ile
- Notifications: The notification types you want to receive
- **Integration configuration**
- Alert Source API key: The key you copied in the ilert configuration step.


15 changes: 9 additions & 6 deletions docs/Alerts & Notifications/Overriding Stock Alerts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,13 @@ This guide explains how to customize Netdata's stock alerts. User configurations

## Quick Reference

| Goal | Method |
|-------------------------------------|--------------------------------------|
| Change thresholds for ALL instances | Create a template with the same name |
| Change thresholds for ONE instance | Create an alarm with the same name |
| Disable an alert completely | Use `enabled alarms` in netdata.conf |
| Silence notifications only | Set `to: silent` |
| Goal | Method |
|-------------------------------------|----------------------------------------------------------------------------------------------------|
| Change thresholds for ALL instances | Create a template with the same name |
| Change thresholds for ONE instance | Create an alarm with the same name |
| Disable an alert completely | Use `enabled alarms` in netdata.conf |
| Enable only specific alerts | Use [`enabled alarms` without `*`](/docs/alerts-&-notifications/alert-configuration-reference#enable-only-specific-alerts-whitelist) |
| Silence notifications only | Set `to: silent` |

## Understanding Overrides

Expand Down Expand Up @@ -176,6 +177,8 @@ In your `netdata.conf` (edit it with `sudo ./edit-config netdata.conf`):

This disables `20min_steal_cpu` and `disk_space_usage` while keeping all other alerts (`*`).

This is a `netdata.conf` change, so restart your Netdata Agent to apply it — `netdatacli reload-health` (see [Applying Changes](#applying-changes) below) only reloads `health.d/*.conf` files, not `netdata.conf`.

### Option B: Per-Alert Disable

Create an override that never matches:
Expand Down
2 changes: 0 additions & 2 deletions ...ecting Metrics/Collectors/Applications/Active Directory Certificate Service.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,5 +147,3 @@ Metrics:
| adcs.cert_signed_certificate_timestamp_lists | lists | lists/s |
| adcs.cert_signed_certificate_timestamp_list_processing_time | processing_time | seconds |
| adcs.cert_retrieval_processing_time | processing_time | seconds |


2 changes: 0 additions & 2 deletions ...lecting Metrics/Collectors/Applications/Active Directory Federation Service.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,5 +159,3 @@ Metrics:
| adfs.windows_integrated_authentications | authentications | authentications/s |
| adfs.wsfed_token_requests_success | success | requests/s |
| adfs.wstrust_token_requests_success | success | requests/s |


2 changes: 0 additions & 2 deletions docs/Collecting Metrics/Collectors/Applications/Active Directory.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,5 +226,3 @@ Metrics:
| ad.sam_enumerations | enumeration | enumerations/s |
| ad.sam_membership_changes | change | changes/s |
| ad.sam_password_changes | change | changes/s |


3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/Alamos FE2 server.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/AuthLog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



2 changes: 0 additions & 2 deletions docs/Collecting Metrics/Collectors/Applications/BOINC.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,5 +280,3 @@ If your Netdata runs in a Docker container named "netdata" (replace if different
```bash
docker logs netdata 2>&1 | grep boinc
```


3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/BungeeCord.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



2 changes: 0 additions & 2 deletions docs/Collecting Metrics/Collectors/Applications/CUPS.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,5 +148,3 @@ Metrics:
|:------|:----------|:----|
| cups.destination_job_num | pending, held, processing | jobs |
| cups.destination_job_size | pending, held, processing | KB |


3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/Celery.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/Chia.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/ClamAV daemon.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/Clamscan results.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/Collectd.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



2 changes: 0 additions & 2 deletions docs/Collecting Metrics/Collectors/Applications/Consul.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -411,5 +411,3 @@ If your Netdata runs in a Docker container named "netdata" (replace if different
```bash
docker logs netdata 2>&1 | grep consul
```


3 changes: 0 additions & 3 deletions docs/Collecting Metrics/Collectors/Applications/Crowdsec.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,6 +490,3 @@ docker logs netdata 2>&1 | grep prometheus
### Disappearing or sparse metrics not clearing alerts

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.



Loading