PR to change absolute links to relative (#17720)
Fotis Voutsas committed
May 21, 2024 at 12:58 UTC
d3ff7e981896461e416c30e456d2f243b0b69ac1
729 files changed
+2339
-2359
README.md
+7
-7
@@ -256,7 +256,7 @@ Check the [systemd-journal plugin of Netdata](https://github.com/netdata/netdata
256
Netdata can be installed on all Linux, macOS, and FreeBSD systems. We provide binary packages for the most popular operating systems and package managers.
257
258
- Install on [Ubuntu, Debian CentOS, Fedora, Suse, Red Hat, Arch, Alpine, Gentoo, even BusyBox](https://learn.netdata.cloud/docs/installing/one-line-installer-for-all-linux-systems).
259
- - Install with [Docker](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md).<br/>
259
+ - Install with [Docker](/packaging/docker/README.md).<br/>
260
Netdata is a [Verified Publisher on DockerHub](https://hub.docker.com/r/netdata/netdata) and our users enjoy free unlimited DockerHub pulls :heart_eyes:.
261
- Install on [MacOS](https://learn.netdata.cloud/docs/installing/macos) :metal:.
262
- Install on [FreeBSD](https://learn.netdata.cloud/docs/installing/freebsd) and [pfSense](https://learn.netdata.cloud/docs/installing/pfsense).
@@ -409,7 +409,7 @@ The core of Netdata is developed in C. We have our own `libnetdata`, that provid
409
Like POSIX `MUTEX` and `RWLOCK` but a lot faster, based on atomic operations, with significantly smaller memory impact, while being portable.
410
411
- **`PGC`**<br/>
412
- A caching layer that can be used to cache any kind of time-related data, with automatic indexing (based on a tree of JudyL arrays), memory management, evictions, flushing, pressure management. This is extensively used in `dbengine`. For more see [here](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md).
412
+ A caching layer that can be used to cache any kind of time-related data, with automatic indexing (based on a tree of JudyL arrays), memory management, evictions, flushing, pressure management. This is extensively used in `dbengine`. For more see [here](/src/database/engine/README.md).
413
414
The above, and many more, allow Netdata developers to work on the application fast and with confidence. Most of the business logic in Netdata is a work of mixing the above.
415
@@ -429,7 +429,7 @@ Of course it is! We do our best to ensure it is!
429
We understand that Netdata is a software piece that is installed on millions of production systems across the world. So, it is important for us, Netdata to be as secure as possible:
430
431
- We follow the [Open Source Security Foundation](https://bestpractices.coreinfrastructure.org/en/projects/2231) best practices.
432
- - We have given great attention to detail when it comes to security design. Check out our [security design](https://github.com/netdata/netdata/blob/master/docs/security-and-privacy-design/README.md).
432
+ - We have given great attention to detail when it comes to security design. Check out our [security design](/docs/security-and-privacy-design/README.md).
433
- Netdata is a popular open-source project and is frequently tested by many security analysts.
434
- Check also our [security policies and advisories published so far](https://github.com/netdata/netdata/security).
435
@@ -746,7 +746,7 @@ The Netdata Agent is shipped with multiple UI versions:
746
747
- `http://agent.ip:19999/v0/`, the original open-source single-node UI, GPLv3+.
748
- `http://agent.ip:19999/v1/`, the latest open-source single-node UI, GPLv3+.
749
-- `http://agent.ip:19999/v2/`, a snapshot of the latest Netdata Cloud UI as it was at the time the agent was released, licensed to be distributed with Netdata Agents under [NCUL1](https://github.com/netdata/netdata/blob/master/src/web/gui/v2/LICENSE.md).
749
+- `http://agent.ip:19999/v2/`, a snapshot of the latest Netdata Cloud UI as it was at the time the agent was released, licensed to be distributed with Netdata Agents under [NCUL1](/src/web/gui/v2/LICENSE.md).
750
751
When you access a Netdata Agent via `http://agent.ip:19999/` a splash screen attempts to use the latest live version of Netdata Cloud UI (downloaded from Cloudflare). This only happens when the web browser has internet connectivity and Netdata Cloud is not disabled at the agent configuration. Otherwise, it falls back to `http://agent.ip:19999/v2/`.
752
@@ -845,12 +845,12 @@ General information about contributions:
845
- Found a bug? Open a [GitHub issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+).
846
- Read our [Contributing Guide](https://github.com/netdata/.github/blob/main/CONTRIBUTING.md), which contains all the information you need to contribute to Netdata, such as improving our documentation, engaging in the community, and developing new features. We've made it as frictionless as possible, but if you need help, just ping us on our community forums!
847
848
-Package maintainers should read the guide on [building Netdata from source](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/source.md) for
848
+Package maintainers should read the guide on [building Netdata from source](/packaging/installer/methods/source.md) for
849
instructions on building each Netdata component from the source and preparing a package.
850
851
## License
852
853
Netdata is released under [GPLv3+](https://github.com/netdata/netdata/blob/master/LICENSE). Netdata re-distributes other open-source tools and libraries. Please check the
854
-[third party licenses](https://github.com/netdata/netdata/blob/master/REDISTRIBUTED.md).
854
+[third party licenses](/REDISTRIBUTED.md).
855
856
-The Latest Netdata UI, is distributed under [NCUL1](https://github.com/netdata/netdata/blob/master/src/web/gui/v2/LICENSE.md). It also uses third party open source components. Check the [UI third party licenses](https://github.com/netdata/netdata/blob/master/src/web/gui/v2/3D_PARTY_LICENSES.txt)
856
+The Latest Netdata UI, is distributed under [NCUL1](/src/web/gui/v2/LICENSE.md). It also uses third party open source components. Check the [UI third party licenses](https://github.com/netdata/netdata/blob/master/src/web/gui/v2/3D_PARTY_LICENSES.txt)
docs/alerts-and-notifications/creating-alerts-with-netdata-alerts-configuration-manager.md
+2
-2
@@ -8,7 +8,7 @@ The Netdata Alerts Configuration Manager enables subscribers to easily set up al
8
2. Click the **Alert icon** in the top right corner of the chart.
9
3. The Alert Configuration Manager will open, showing the default thresholds. Modify these thresholds as needed, the alert definition on the right will update automatically.
10
4. For additional settings, toggle **Show advanced**.
11
-5. After configuring the alert, copy the generated alert definition from the code box. Paste this into an existing or new custom health configuration file located at `<path to netdata install>/etc/netdata/health.d/` on a Parent Agent or a Standalone Child Agent. The guide to edit health configuration files is available [here](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#edit-health-configuration-files).
11
+5. After configuring the alert, copy the generated alert definition from the code box. Paste this into an existing or new custom health configuration file located at `<path to netdata install>/etc/netdata/health.d/` on a Parent Agent or a Standalone Child Agent. The guide to edit health configuration files is available [here](/src/health/REFERENCE.md#edit-health-configuration-files).
12
6. To activate the new alert, run the command `<path to netdata install>/usr/sbin/netdatacli reload-health`.
13
14
## Alerts Configuration Manager Sections
@@ -23,7 +23,7 @@ An alert is triggered whenever a metric crosses a threshold:
23
24
### Metrics Lookup, Filtering and Formula Section
25
26
-You can read more about the different options in the [Alerts reference documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md)
26
+You can read more about the different options in the [Alerts reference documentation](/src/health/REFERENCE.md)
27
28
- **Metrics Lookup**: Adjust the database lookup parameters directly in the UI, including method (`avg`, `sum`, `min`, `max`, etc.), computation style, dimensions, duration, and options like `absolute` or `percentage`.
29
- **Alert Filtering**: The **show advanced** checkbox allows filtering of alert health checks for specific infrastructure components. Options include selecting hosts, nodes, instances, chart labels, and operating systems.
docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md
+6
-6
@@ -5,16 +5,16 @@ Netdata Cloud sends alert notifications for nodes in warning, critical, or unrea
5
## Benefits of Centralized Notifications
6
7
- Consolidate health status views across all infrastructure in one place.
8
-- Set up and [manage your alert notifications easily](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md).
9
-- Expedite troubleshooting with tools like [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md) and the [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md).
8
+- Set up and [manage your alert notifications easily](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md).
9
+- Expedite troubleshooting with tools like [Metric Correlations](/docs/metric-correlations.md) and the [Anomaly Advisor](/docs/dashboards-and-charts/anomaly-advisor-tab.md).
10
11
To avoid notification overload, **flood protection** is triggered when a node frequently disconnects or sends excessive alerts, highlighting potential issues.
12
13
-Admins must [enable alert notifications](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-space-notification-settings) for their Space(s). All users can then customize their notification preferences through their [account menu](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-user-notification-settings).
13
+Admins must [enable alert notifications](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-space-notification-settings) for their Space(s). All users can then customize their notification preferences through their [account menu](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-user-notification-settings).
14
15
> **Note**
16
>
17
-> Centralized alerts in Netdata Cloud are separate from the [Netdata Agent](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/README.md) notifications. Alerts must be [configured individually](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) on each node.
17
+> Centralized alerts in Netdata Cloud are separate from the [Netdata Agent](/docs/alerts-and-notifications/notifications/README.md) notifications. Alerts must be [configured individually](/src/health/REFERENCE.md) on each node.
18
19
## Alert Notifications
20
@@ -38,11 +38,11 @@ Available to all plans, includes basic methods like Email and Discord.
38
39
#### Business
40
41
-Exclusive to [paid plans](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-subscription-plans.md), includes advanced services like PagerDuty and Slack.
41
+Exclusive to [paid plans](/docs/netdata-cloud/netdata-subscription-plans.md), includes advanced services like PagerDuty and Slack.
42
43
## Alert Notification Silencing Rules
44
45
-Netdata Cloud offers a silencing rule engine to mute alert notifications based on specific conditions related to nodes or alert types. Learn how to manage these settings [here](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md).
45
+Netdata Cloud offers a silencing rule engine to mute alert notifications based on specific conditions related to nodes or alert types. Learn how to manage these settings [here](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md).
46
47
## Flood Protection
48
docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md
+3
-3
@@ -22,7 +22,7 @@ To manage space notification settings, you will need the following:
22
23
Notes:
24
* For Netadata provided ones you can't delete the existing notification method configuration.
25
-* Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-classification))
25
+* Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-classification))
26
27
### Steps
28
@@ -55,13 +55,13 @@ To manage user specific notification settings, you will need the following:
55
- A Cloud account
56
- Have access to, at least, a space
57
58
-Note: If an administrator has disabled a Personal [service level](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification method this will override any user specific setting.
58
+Note: If an administrator has disabled a Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification method this will override any user specific setting.
59
60
### Steps
61
62
1. Click on the **User notification settings** shortcut on top of the help button
63
1. You are presented with:
64
- - The Personal [service level](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification methods you can manage
64
+ - The Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification methods you can manage
65
- The list spaces and rooms inside those where you have access to
66
- If you're an administrator, Manager or Troubleshooter you'll also see the Rooms from a space you don't have access to on **All Rooms** tab and you can activate notifications for them by joining the room
67
1. On this modal you will be able to:
docs/category-overview-pages/machine-learning-and-assisted-troubleshooting.md
+3
-3
@@ -2,6 +2,6 @@
2
3
Netdata provides a variety of Machine Learning features to help you troubleshoot certain scenarios that might come up.
4
5
-- K-means clustering [Machine Learning models](https://github.com/netdata/netdata/blob/master/src/ml/README.md) are trained to power the [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md) on the dashboard, which allows you to identify anomalies in your infrastructure
6
-- [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md) are possible through the dashboard using the [Two-sample Kolmogorov Smirnov](https://en.wikipedia.org/wiki/Kolmogorov%E2%80%93Smirnov_test#Two-sample_Kolmogorov%E2%80%93Smirnov_test) statistical test and Volume heuristic measures
7
-- The [Netdata Assistant](https://github.com/netdata/netdata/blob/master/docs/netdata-assistant.md) is able to answer your prompts when it comes to troubleshooting alerts and anomalies.
5
+- K-means clustering [Machine Learning models](/src/ml/README.md) are trained to power the [Anomaly Advisor](/docs/dashboards-and-charts/anomaly-advisor-tab.md) on the dashboard, which allows you to identify anomalies in your infrastructure
6
+- [Metric Correlations](/docs/metric-correlations.md) are possible through the dashboard using the [Two-sample Kolmogorov Smirnov](https://en.wikipedia.org/wiki/Kolmogorov%E2%80%93Smirnov_test#Two-sample_Kolmogorov%E2%80%93Smirnov_test) statistical test and Volume heuristic measures
7
+- The [Netdata Assistant](/docs/netdata-assistant.md) is able to answer your prompts when it comes to troubleshooting alerts and anomalies.
docs/collecting-metrics/application-metrics.md
+18
-18
@@ -15,7 +15,7 @@ web servers, databases, message brokers, email servers, search platforms, and mu
15
pre-installed with every Netdata Agent and usually require zero configuration. Netdata also collects and visualizes
16
resource utilization per application on Linux systems using `apps.plugin`.
17
18
-[**apps.plugin**](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md) looks at the Linux process tree every second, much like `top` or
18
+[**apps.plugin**](/src/collectors/apps.plugin/README.md) looks at the Linux process tree every second, much like `top` or
19
`ps fax`, and collects resource utilization information on every running process. By reading the process tree, Netdata
20
shows CPU, disk, networking, processes, and eBPF for every application or Linux user. Unlike `top` or `ps fax`, Netdata
21
adds a layer of meaningful visualization on top of the process tree metrics, such as grouping applications into useful
@@ -24,42 +24,42 @@ charts under **Users**, and per-user group charts under **User Groups**.
24
25
Our most popular application collectors:
26
27
-- [Prometheus endpoints](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/README.md): Gathers
27
+- [Prometheus endpoints](/src/go/collectors/go.d.plugin/modules/prometheus/README.md): Gathers
28
metrics from one or more Prometheus endpoints that use the OpenMetrics exposition format. Auto-detects more than 600
29
endpoints.
30
-- [Web server logs (Apache, NGINX)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md):
30
+- [Web server logs (Apache, NGINX)](/src/go/collectors/go.d.plugin/modules/weblog/README.md):
31
Tail access logs and provide very detailed web server performance statistics. This module is able to parse 200k+
32
rows in less than half a second.
33
-- [MySQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/README.md): Collect database global,
33
+- [MySQL](/src/go/collectors/go.d.plugin/modules/mysql/README.md): Collect database global,
34
replication, and per-user statistics.
35
-- [Redis](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/redis/README.md): Monitor database status by
35
+- [Redis](/src/go/collectors/go.d.plugin/modules/redis/README.md): Monitor database status by
36
reading the server's response to the `INFO` command.
37
-- [Apache](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/apache/README.md): Collect Apache web server
37
+- [Apache](/src/go/collectors/go.d.plugin/modules/apache/README.md): Collect Apache web server
38
performance metrics via the `server-status?auto` endpoint.
39
-- [Nginx](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nginx/README.md): Monitor web server status
39
+- [Nginx](/src/go/collectors/go.d.plugin/modules/nginx/README.md): Monitor web server status
40
information by gathering metrics via `ngx_http_stub_status_module`.
41
-- [Postgres](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/postgres/README.md): Collect database health
41
+- [Postgres](/src/go/collectors/go.d.plugin/modules/postgres/README.md): Collect database health
42
and performance metrics.
43
-- [ElasticSearch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/elasticsearch/README.md): Collect search
43
+- [ElasticSearch](/src/go/collectors/go.d.plugin/modules/elasticsearch/README.md): Collect search
44
engine performance and health statistics. Optionally collects per-index metrics.
45
-- [PHP-FPM](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/phpfpm/README.md): Collect application summary
45
+- [PHP-FPM](/src/go/collectors/go.d.plugin/modules/phpfpm/README.md): Collect application summary
46
and processes health metrics by scraping the status page (`/status?full`).
47
48
-Our [supported collectors list](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md#service-and-application-collectors) shows all Netdata's
48
+Our [supported collectors list](/src/collectors/COLLECTORS.md#service-and-application-collectors) shows all Netdata's
49
application metrics collectors, including those for containers/k8s clusters.
50
51
## Collect metrics from applications running on Windows
52
53
Netdata is fully capable of collecting and visualizing metrics from applications running on Windows systems. The only
54
-caveat is that you must [install Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md) on a separate system or a compatible VM because there
54
+caveat is that you must [install Netdata](/packaging/installer/README.md) on a separate system or a compatible VM because there
55
is no native Windows version of the Netdata Agent.
56
57
-Once you have Netdata running on that separate system, you can follow the [collectors configuration reference](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md) documentation to tell the collector to look for exposed metrics on the Windows system's IP
57
+Once you have Netdata running on that separate system, you can follow the [collectors configuration reference](/src/collectors/REFERENCE.md) documentation to tell the collector to look for exposed metrics on the Windows system's IP
58
address or hostname, plus the applicable port.
59
60
For example, you have a MySQL database with a root password of `my-secret-pw` running on a Windows system with the IP
61
address 203.0.113.0. you can configure the [MySQL
62
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/README.md) to look at `203.0.113.0:3306`:
62
+collector](/src/go/collectors/go.d.plugin/modules/mysql/README.md) to look at `203.0.113.0:3306`:
63
64
```yml
65
jobs:
@@ -68,16 +68,16 @@ jobs:
68
```
69
70
This same logic applies to any application in our [supported collectors
71
-list](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md#service-and-application-collectors) that can run on Windows.
71
+list](/src/collectors/COLLECTORS.md#service-and-application-collectors) that can run on Windows.
72
73
## What's next?
74
75
-If you haven't yet seen the [supported collectors list](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md) give it a once-over for any
75
+If you haven't yet seen the [supported collectors list](/src/collectors/COLLECTORS.md) give it a once-over for any
76
additional applications you may want to monitor using Netdata's native collectors, or the [generic Prometheus
77
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/README.md).
77
+collector](/src/go/collectors/go.d.plugin/modules/prometheus/README.md).
78
79
Collecting all the available metrics on your nodes, and across your entire infrastructure, is just one piece of the
80
puzzle. Next, learn more about Netdata's famous real-time visualizations by [seeing an overview of your
81
-infrastructure](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/home-tab.md) using Netdata Cloud.
81
+infrastructure](/docs/dashboards-and-charts/home-tab.md) using Netdata Cloud.
82
83
docs/collecting-metrics/container-metrics.md
+19
-19
@@ -13,35 +13,35 @@ learn_rel_path: "Concepts"
13
Thanks to close integration with Linux cgroups and the virtual files it maintains under `/sys/fs/cgroup`, Netdata can
14
monitor the health, status, and resource utilization of many different types of Linux containers.
15
16
-Netdata uses [cgroups.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md) to poll `/sys/fs/cgroup` and convert the raw data
16
+Netdata uses [cgroups.plugin](/src/collectors/cgroups.plugin/README.md) to poll `/sys/fs/cgroup` and convert the raw data
17
into human-readable metrics and meaningful visualizations. Through cgroups, Netdata is compatible with **all Linux
18
containers**, such as Docker, LXC, LXD, Libvirt, systemd-nspawn, and more. Read more about [Docker-specific
19
monitoring](#collect-docker-metrics) below.
20
21
Netdata also has robust **Kubernetes monitoring** support thanks to a
22
-[Helmchart](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md) to automate deployment, collectors for k8s agent services, and
22
+[Helmchart](/packaging/installer/methods/kubernetes.md) to automate deployment, collectors for k8s agent services, and
23
robust [service discovery](https://github.com/netdata/agent-service-discovery/#service-discovery) to monitor the
24
services running inside of pods in your k8s cluster. Read more about [Kubernetes
25
monitoring](#collect-kubernetes-metrics) below.
26
27
A handful of additional collectors gather metrics from container-related services, such as
28
-[dockerd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/docker/README.md) or [Docker
29
-Engine](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/docker_engine/README.md). You can find all
28
+[dockerd](/src/go/collectors/go.d.plugin/modules/docker/README.md) or [Docker
29
+Engine](/src/go/collectors/go.d.plugin/modules/docker_engine/README.md). You can find all
30
container collectors in our supported collectors list under the
31
-[containers/VMs](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md#containers-and-vms) and
32
-[Kubernetes](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md#containers-and-vms) headings.
31
+[containers/VMs](/src/collectors/COLLECTORS.md#containers-and-vms) and
32
+[Kubernetes](/src/collectors/COLLECTORS.md#containers-and-vms) headings.
33
34
## Collect Docker metrics
35
36
Netdata has robust Docker monitoring thanks to the aforementioned
37
-[cgroups.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md). By polling cgroups every second, Netdata can produce meaningful
37
+[cgroups.plugin](/src/collectors/cgroups.plugin/README.md). By polling cgroups every second, Netdata can produce meaningful
38
visualizations about the CPU, memory, disk, and network utilization of all running containers on the host system with
39
zero configuration.
40
41
Netdata also collects metrics from applications running inside of Docker containers. For example, if you create a MySQL
42
database container using `docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag`, it exposes
43
metrics on port 3306. You can configure the [MySQL
44
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/README.md) to look at `127.0.0.0:3306` for
44
+collector](/src/go/collectors/go.d.plugin/modules/mysql/README.md) to look at `127.0.0.0:3306` for
45
MySQL metrics:
46
47
```yml
@@ -51,17 +51,17 @@ jobs:
51
```
52
53
Netdata then collects metrics from the container itself, but also dozens [MySQL-specific
54
-metrics](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/README.md#charts) as well.
54
+metrics](/src/go/collectors/go.d.plugin/modules/mysql/README.md#charts) as well.
55
56
### Collect metrics from applications running in Docker containers
57
58
-You could use this technique to monitor an entire infrastructure of Docker containers. The same [enable and configure](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md) procedures apply whether an application runs on the host system or inside
58
+You could use this technique to monitor an entire infrastructure of Docker containers. The same [enable and configure](/src/collectors/REFERENCE.md) procedures apply whether an application runs on the host system or inside
59
a container. You may need to configure the target endpoint if it's not the application's default.
60
61
-Netdata can even [run in a Docker container](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md) itself, and then collect metrics about the
61
+Netdata can even [run in a Docker container](/packaging/docker/README.md) itself, and then collect metrics about the
62
host system, its own container with cgroups, and any applications you want to monitor.
63
64
-See our [application metrics doc](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/application-metrics.md) for details about Netdata's application metrics
64
+See our [application metrics doc](/docs/collecting-metrics/application-metrics.md) for details about Netdata's application metrics
65
collection capabilities.
66
67
## Collect Kubernetes metrics
@@ -76,26 +76,26 @@ your k8s infrastructure.
76
configuration files for [compatible
77
applications](https://github.com/netdata/helmchart#service-discovery-and-supported-services) and any endpoints
78
covered by our [generic Prometheus
79
- collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/README.md). With these
79
+ collector](/src/go/collectors/go.d.plugin/modules/prometheus/README.md). With these
80
configuration files, Netdata collects metrics from any compatible applications as they run _inside_ a pod.
81
Service discovery happens without manual intervention as pods are created, destroyed, or moved between nodes.
82
-- A [Kubelet collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubelet/README.md), which runs
82
+- A [Kubelet collector](/src/go/collectors/go.d.plugin/modules/k8s_kubelet/README.md), which runs
83
on each node in a k8s cluster to monitor the number of pods/containers, the volume of operations on each container,
84
and more.
85
-- A [kube-proxy collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/README.md), which
85
+- A [kube-proxy collector](/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/README.md), which
86
also runs on each node and monitors latency and the volume of HTTP requests to the proxy.
87
-- A [cgroups collector](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md), which collects CPU, memory, and bandwidth metrics for
87
+- A [cgroups collector](/src/collectors/cgroups.plugin/README.md), which collects CPU, memory, and bandwidth metrics for
88
each container running on your k8s cluster.
89
90
For a holistic view of Netdata's Kubernetes monitoring capabilities, see our guide: [_Monitor a Kubernetes (k8s) cluster
91
-with Netdata_](https://github.com/netdata/netdata/blob/master/docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md).
91
+with Netdata_](/docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md).
92
93
## What's next?
94
95
Netdata is capable of collecting metrics from hundreds of applications, such as web servers, databases, messaging
96
-brokers, and more. See more in the [application metrics doc](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/application-metrics.md).
96
+brokers, and more. See more in the [application metrics doc](/docs/collecting-metrics/application-metrics.md).
97
98
If you already have all the information you need about collecting metrics, move into Netdata's meaningful visualizations
99
-with [seeing an overview of your infrastructure](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/home-tab.md) using Netdata Cloud.
99
+with [seeing an overview of your infrastructure](/docs/dashboards-and-charts/home-tab.md) using Netdata Cloud.
100
101
docs/collecting-metrics/system-metrics.md
+13
-13
@@ -11,52 +11,52 @@ learn_rel_path: "Concepts"
11
# Collect system metrics with Netdata
12
13
Netdata collects thousands of metrics directly from the operating systems of physical and virtual systems, IoT/edge
14
-devices, and [containers](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/container-metrics.md) with zero configuration.
14
+devices, and [containers](/docs/collecting-metrics/container-metrics.md) with zero configuration.
15
16
To gather system metrics, Netdata uses roughly a dozen plugins, each of which has one or more collectors for very
17
specific metrics exposed by the host. The system metrics Netdata users interact with most for health monitoring and
18
performance troubleshooting are collected and visualized by `proc.plugin`, `cgroups.plugin`, and `ebpf.plugin`.
19
20
-[**proc.plugin**](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/README.md) gathers metrics from the `/proc` and `/sys` folders in Linux
20
+[**proc.plugin**](/src/collectors/proc.plugin/README.md) gathers metrics from the `/proc` and `/sys` folders in Linux
21
systems, along with a few other endpoints, and is responsible for the bulk of the system metrics collected and
22
visualized by Netdata. It collects CPU, memory, disks, load, networking, mount points, and more with zero configuration.
23
It even allows Netdata to monitor its own resource utilization!
24
25
-[**cgroups.plugin**](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md) collects rich metrics about containers and virtual machines
25
+[**cgroups.plugin**](/src/collectors/cgroups.plugin/README.md) collects rich metrics about containers and virtual machines
26
using the virtual files under `/sys/fs/cgroup`. By reading cgroups, Netdata can instantly collect resource utilization
27
metrics for systemd services, all containers (Docker, LXC, LXD, Libvirt, systemd-nspawn), and more. Learn more in the
28
-[collecting container metrics](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/container-metrics.md) doc.
28
+[collecting container metrics](/docs/collecting-metrics/container-metrics.md) doc.
29
30
-[**ebpf.plugin**](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md): Netdata's extended Berkeley Packet Filter (eBPF) collector
30
+[**ebpf.plugin**](/src/collectors/ebpf.plugin/README.md): Netdata's extended Berkeley Packet Filter (eBPF) collector
31
monitors Linux kernel-level metrics for file descriptors, virtual filesystem IO, and process management. You can use our
32
eBPF collector to analyze how and when a process accesses files, when it makes system calls, whether it leaks memory or
33
creating zombie processes, and more.
34
35
While the above plugins and associated collectors are the most important for system metrics, there are many others. You
36
-can find all system collectors in our [supported collectors list](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md#system-collectors).
36
+can find all system collectors in our [supported collectors list](/src/collectors/COLLECTORS.md#system-collectors).
37
38
## Collect Windows system metrics
39
40
Netdata is also capable of monitoring Windows systems. The [Windows
41
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/README.md) integrates with
41
+collector](/src/go/collectors/go.d.plugin/modules/windows/README.md) integrates with
42
[windows_exporter](https://github.com/prometheus-community/windows_exporter), a small Go-based binary that you can run
43
on Windows systems. The Windows collector then gathers metrics from an endpoint created by windows_exporter, for more
44
-details see [the requirements](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/README.md#requirements).
44
+details see [the requirements](/src/go/collectors/go.d.plugin/modules/windows/README.md#requirements).
45
46
-Next, [configure](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/README.md#configuration) the Windows
46
+Next, [configure](/src/go/collectors/go.d.plugin/modules/windows/README.md#configuration) the Windows
47
collector to point to the URL and port of your exposed endpoint. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
48
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. You'll start seeing Windows system metrics, such as CPU
48
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. You'll start seeing Windows system metrics, such as CPU
49
utilization, memory, bandwidth per NIC, number of processes, and much more.
50
51
For information about collecting metrics from applications _running on Windows systems_, see the [application metrics
52
-doc](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/application-metrics.md#collect-metrics-from-applications-running-on-windows).
52
+doc](/docs/collecting-metrics/application-metrics.md#collect-metrics-from-applications-running-on-windows).
53
54
## What's next?
55
56
-Because there's some overlap between system metrics and [container metrics](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/container-metrics.md), you
56
+Because there's some overlap between system metrics and [container metrics](/docs/collecting-metrics/container-metrics.md), you
57
should investigate Netdata's container compatibility if you use them heavily in your infrastructure.
58
59
-If you don't use containers, skip ahead to collecting [application metrics](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/application-metrics.md) with
59
+If you don't use containers, skip ahead to collecting [application metrics](/docs/collecting-metrics/application-metrics.md) with
60
Netdata.
61
62
docs/dashboards-and-charts/README.md
+11
-11
@@ -13,15 +13,15 @@ By default, the Agent dashboard shows the latest version (matching Netdata Cloud
13
14
The Netdata dashboard consists of the following main sections:
15
16
-- [Home tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/home-tab.md)
17
-- [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md)
18
-- [Netdata charts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md)
19
-- [Metrics tab and single node tabs](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md)
20
-- [Top tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/top-tab.md)
21
-- [Logs tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/logs-tab.md)
22
-- [Dashboards tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md)
23
-- [Alerts tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/alerts-tab.md)
24
-- [Events tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/events-feed.md)
16
+- [Home tab](/docs/dashboards-and-charts/home-tab.md)
17
+- [Nodes tab](/docs/dashboards-and-charts/nodes-tab.md)
18
+- [Netdata charts](/docs/dashboards-and-charts/netdata-charts.md)
19
+- [Metrics tab and single node tabs](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md)
20
+- [Top tab](/docs/dashboards-and-charts/top-tab.md)
21
+- [Logs tab](/docs/dashboards-and-charts/logs-tab.md)
22
+- [Dashboards tab](/docs/dashboards-and-charts/dashboards-tab.md)
23
+- [Alerts tab](/docs/dashboards-and-charts/alerts-tab.md)
24
+- [Events tab](/docs/dashboards-and-charts/events-feed.md)
25
26
> **Note**
27
>
@@ -31,10 +31,10 @@ The Netdata dashboard consists of the following main sections:
31
32
### Netdata Cloud
33
34
-You can access the dashboard at <https://app.netdata.cloud/> and [sign-in with an account or sign-up](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/README.md) if you don't have an account yet.
34
+You can access the dashboard at <https://app.netdata.cloud/> and [sign-in with an account or sign-up](/docs/netdata-cloud/authentication-and-authorization/README.md) if you don't have an account yet.
35
36
### Netdata Agent
37
38
To view your Netdata dashboard, open a web browser and enter the address `http://NODE:19999` - replace `NODE` with your Agent's IP address or hostname. If the Agent is on the same machine, use http://localhost:19999.
39
40
-Documentation for previous Agent dashboard can still be found [here](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md).
40
+Documentation for previous Agent dashboard can still be found [here](/src/web/gui/README.md).
docs/dashboards-and-charts/alerts-tab.md
+3
-3
@@ -41,11 +41,11 @@ By clicking on the name of an entry of the table you can access that alert's det
41
- Configuration section
42
- Instance values - Node Instances
43
44
-At the bottom of the panel you can click the green button "View alert page" to open a [dynamic tab](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/monitor-your-infrastructure.md#dynamic-tabs) containing all the info for this alert in a tab format, where you can also run correlations and go to the node's chart that raised the particular alert.
44
+At the bottom of the panel you can click the green button "View alert page" to open a [dynamic tab](/docs/netdata-cloud/monitor-your-infrastructure.md#dynamic-tabs) containing all the info for this alert in a tab format, where you can also run correlations and go to the node's chart that raised the particular alert.
45
46
### Silence an alert
47
48
-From this tab, the "Silencing" column shows if there is any rule present for each alert, and from the "Actions" column you can create a new [silencing rule](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#alert-notifications-silencing-rules) for this alert, or get help and information about this alert from the [Netdata Assistant](https://github.com/netdata/netdata/blob/master/docs/netdata-assistant.md).
48
+From this tab, the "Silencing" column shows if there is any rule present for each alert, and from the "Actions" column you can create a new [silencing rule](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#alert-notifications-silencing-rules) for this alert, or get help and information about this alert from the [Netdata Assistant](/docs/netdata-assistant.md).
49
50
## Alert Configurations tab
51
@@ -55,7 +55,7 @@ By running alerts we mean alerts that are related to some metric that is or was
55
56
You can control which columns are visible by using the gear icon on the right-hand side.
57
58
-Similarly to the previous tab, you can see the silencing status of an alert, while also being able to dig deeper and show the configuration for the alert and ask the [Netdata Assistant](https://github.com/netdata/netdata/blob/master/docs/netdata-assistant.md) for help.
58
+Similarly to the previous tab, you can see the silencing status of an alert, while also being able to dig deeper and show the configuration for the alert and ask the [Netdata Assistant](/docs/netdata-assistant.md) for help.
59
60
### See the configuration for an alert
61
docs/dashboards-and-charts/anomaly-advisor-tab.md
+4
-4
@@ -1,11 +1,11 @@
1
# Anomaly Advisor tab
2
3
-The Anomaly Advisor tab lets you focus on potentially anomalous metrics and charts related to a particular highlighted window of interest. In addition to this tab, each chart in the [Metrics tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) also has an [Anomaly Rate ribbon](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#anomaly-rate-ribbon).
3
+The Anomaly Advisor tab lets you focus on potentially anomalous metrics and charts related to a particular highlighted window of interest. In addition to this tab, each chart in the [Metrics tab](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) also has an [Anomaly Rate ribbon](/docs/dashboards-and-charts/netdata-charts.md#anomaly-rate-ribbon).
4
5
6
-More details about configuration can be found in the [ML documentation](https://github.com/netdata/netdata/blob/master/src/ml/README.md#configuration).
6
+More details about configuration can be found in the [ML documentation](/src/ml/README.md#configuration).
7
8
-This tab uses our [Anomaly Rate ML feature](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate---averageanomaly-bit) to score metrics in terms of anomalous behavior.
8
+This tab uses our [Anomaly Rate ML feature](/src/ml/README.md#anomaly-rate---averageanomaly-bit) to score metrics in terms of anomalous behavior.
9
10
- The "Anomaly Rate" chart shows the percentage of anomalous metrics over time per node.
11
@@ -17,7 +17,7 @@ Once you have highlighted a window of interest, you should see an ordered list o
17
18
> **Tip**
19
>
20
-> You can also use the [node filter](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/node-filter.md) to select which nodes you want to include or exclude.
20
+> You can also use the [node filter](/docs/dashboards-and-charts/node-filter.md) to select which nodes you want to include or exclude.
21
22
The right side of the page displays an anomaly index for the highlighted timeline of interest. The index is sorted from most anomalous (highest level of anomaly) to least (lowest level of anomaly). Clicking on an entry in the index will get you to the corresponding chart for the anomalous metric.
23
docs/dashboards-and-charts/dashboards-tab.md
+6
-6
@@ -12,7 +12,7 @@ In the modal, give your custom dashboard a name, and click **+ Add**.
12
13
- The **Add Chart** button on the top right of the interface adds your first chart card. From the dropdown, select either **All Nodes** or a specific node.
14
15
- Next, select the context. You'll see a preview of the chart before you finish adding it. In this modal you can also [interact with the chart](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md), meaning you can configure all the aspects of the [NIDL framework](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#nidl-framework) of the chart and more in detail, you can:
15
+ Next, select the context. You'll see a preview of the chart before you finish adding it. In this modal you can also [interact with the chart](/docs/dashboards-and-charts/netdata-charts.md), meaning you can configure all the aspects of the [NIDL framework](/docs/dashboards-and-charts/netdata-charts.md#nidl-framework) of the chart and more in detail, you can:
16
- define which `group by` method to use
17
- select the aggregation function over the data source
18
- select nodes
@@ -21,7 +21,7 @@ In the modal, give your custom dashboard a name, and click **+ Add**.
21
- select labels
22
- select the aggregation function over time
23
24
- After you are done configuring the chart, you can also change the type of the chart from the right hand side of the [Title bar](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#title-bar), and select which of the final dimensions you want to be visible and in what order, from the [Dimensions bar](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#dimensions-bar).
24
+ After you are done configuring the chart, you can also change the type of the chart from the right hand side of the [Title bar](/docs/dashboards-and-charts/netdata-charts.md#title-bar), and select which of the final dimensions you want to be visible and in what order, from the [Dimensions bar](/docs/dashboards-and-charts/netdata-charts.md#dimensions-bar).
25
26
- The **Add Text** button on the top right of the interface creates a new card with user-defined text, which you can use to describe or document a particular dashboard's meaning and purpose.
27
@@ -35,13 +35,13 @@ Dashboards are designed to be interactive and flexible so you can design them to
35
36
### Charts
37
38
-The charts you add to any dashboard are [fully interactive](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md), just like any other Netdata chart. You can zoom in and out, highlight timeframes, and more.
38
+The charts you add to any dashboard are [fully interactive](/docs/dashboards-and-charts/netdata-charts.md), just like any other Netdata chart. You can zoom in and out, highlight timeframes, and more.
39
40
Charts also synchronize as you interact with them, even across contexts _or_ nodes.
41
42
### Text cards
43
44
-You can use text cards as notes to explain to other members of the [War Room](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms) the purpose of the dashboard's arrangement.
44
+You can use text cards as notes to explain to other members of the [War Room](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms) the purpose of the dashboard's arrangement.
45
46
By clicking the `T` icon on the text box, you can switch between font sizes.
47
@@ -56,7 +56,7 @@ To resize any element on a dashboard, click on the bottom-right corner and drag
56
57
### Go to chart
58
59
-Quickly jump to the location of the chart in either the [Metrics tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) or if the chart refers to a single node, its single node dashboard by clicking the 3-dot icon in the corner of any chart to open a menu. Hit the **Go to Chart** item.
59
+Quickly jump to the location of the chart in either the [Metrics tab](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) or if the chart refers to a single node, its single node dashboard by clicking the 3-dot icon in the corner of any chart to open a menu. Hit the **Go to Chart** item.
60
61
You'll land directly on that chart of interest, but you can now scroll up and down to correlate your findings with other
62
charts. Of course, you can continue to zoom, highlight, and pan through time just as you're used to with Netdata Charts.
@@ -93,4 +93,4 @@ Because of the visual complexity of individual charts, dashboards require a mini
93
94
## What's next?
95
96
-Once you've designed a dashboard or two, make sure to [invite your team](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team) if you haven't already. You can add these new users to the same War Room to let them see the same dashboards without any effort.
96
+Once you've designed a dashboard or two, make sure to [invite your team](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team) if you haven't already. You can add these new users to the same War Room to let them see the same dashboards without any effort.
docs/dashboards-and-charts/events-feed.md
+2
-2
@@ -61,12 +61,12 @@ At a high-level view, these are the domains from which the Events feed will prov
61
62
## Who can access the events?
63
64
-All users will be able to see events from the Topology and Alerts domain but Auditing events, once these are added, will only be accessible to administrators. For more details check the [Netdata Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md).
64
+All users will be able to see events from the Topology and Alerts domain but Auditing events, once these are added, will only be accessible to administrators. For more details check the [Netdata Role-Based Access model](/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md).
65
66
## How to use the events feed
67
68
1. Click on the **Events** tab (located near the top of your screen)
69
-1. You will be presented with a table listing the events that occurred from the timeframe defined on the [date time picker](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/visualization-date-and-time-controls.md#date-and-time-selector)
69
+1. You will be presented with a table listing the events that occurred from the timeframe defined on the [date time picker](/docs/dashboards-and-charts/visualization-date-and-time-controls.md#date-and-time-selector)
70
1. You can use the filtering capabilities available on right-hand bar to slice through the results provided. See more details on [event types and filters](#event-types-and-filters)
71
72
> **Note**
docs/dashboards-and-charts/import-export-print-snapshot.md
+3
-3
@@ -5,7 +5,7 @@ description: >-
5
they've already happened, and are interoperable with any other node
6
running Netdata."
7
type: "how-to"
8
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/import-export-print-snapshot.md"
8
+custom_edit_url: "/docs/dashboards-and-charts/import-export-print-snapshot.md"
9
sidebar_label: "Import, export, and print a snapshot"
10
learn_status: "Published"
11
learn_topic_type: "Tasks"
@@ -15,7 +15,7 @@ learn_rel_path: "Operations"
15
# Import, export, and print a snapshot
16
17
>❗This feature is only available on v1 dashboards, it hasn't been port-forwarded to v2.
18
-> For more information on accessing dashboards check [this documentation](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md).
18
+> For more information on accessing dashboards check [this documentation](/docs/dashboards-and-charts/README.md).
19
20
21
Netdata can export snapshots of the contents of your dashboard at a given time, which you can then import into any other
@@ -23,7 +23,7 @@ node running Netdata. Or, you can create a print-ready version of your dashboard
23
paper.
24
25
Snapshots can be incredibly useful for diagnosing anomalies after they've already happened. Let's say Netdata triggered a warning alert while you were asleep. In the morning, you can [select the
26
-timeframe](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/visualization-date-and-time-controls.md) when the alert triggered, export a snapshot, and send it to a
26
+timeframe](/docs/dashboards-and-charts/visualization-date-and-time-controls.md) when the alert triggered, export a snapshot, and send it to a
27
28
colleague for further analysis.
29
docs/dashboards-and-charts/kubernetes-tab.md
+4
-4
@@ -1,10 +1,10 @@
1
# Kubernetes tab
2
3
-The Netdata dashboards feature enhanced visualizations for the resource utilization of Kubernetes (k8s) clusters, embedded in the default [Metrics tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) dashboard.
3
+The Netdata dashboards feature enhanced visualizations for the resource utilization of Kubernetes (k8s) clusters, embedded in the default [Metrics tab](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) dashboard.
4
5
-These visualizations include a health map for viewing the status of k8s pods/containers, in addition to [Netdata charts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md) for viewing per-second CPU, memory, disk, and networking metrics from k8s nodes.
5
+These visualizations include a health map for viewing the status of k8s pods/containers, in addition to [Netdata charts](/docs/dashboards-and-charts/netdata-charts.md) for viewing per-second CPU, memory, disk, and networking metrics from k8s nodes.
6
7
-See our [Kubernetes deployment instructions](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md) for details on deploying Netdata on your Kubernetes cluster.
7
+See our [Kubernetes deployment instructions](/packaging/installer/methods/kubernetes.md) for details on deploying Netdata on your Kubernetes cluster.
8
9
## Available Kubernetes metrics
10
@@ -35,7 +35,7 @@ their associated pods.
35
36
At the top of the Kubernetes containers section there is a map, that with a given context colorizes the containers in terms of their utilization.
37
38
-The filtering of this map is controlled by using the [NIDL framework](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#nidl-framework) from the definition bar of the chart.
38
+The filtering of this map is controlled by using the [NIDL framework](/docs/dashboards-and-charts/netdata-charts.md#nidl-framework) from the definition bar of the chart.
39
40
### Detailed information
41
docs/dashboards-and-charts/logs-tab.md
+9
-9
@@ -1,16 +1,16 @@
1
# Logs tab
2
3
-The Logs tab is using the [`systemd` journal plugin](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md), to present a structured view into your infrastructure's `systemd` logs.
3
+The Logs tab is using the [`systemd` journal plugin](/src/collectors/systemd-journal.plugin/README.md), to present a structured view into your infrastructure's `systemd` logs.
4
5
-We have a thorough section explaining how you can [work with logs](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/working-with-logs.md), detailing how the plugin works, and what other utilities are used under the hood to provide you with the visualizations and the log entries.
5
+We have a thorough section explaining how you can [work with logs](/docs/category-overview-pages/working-with-logs.md), detailing how the plugin works, and what other utilities are used under the hood to provide you with the visualizations and the log entries.
6
7
-The [`systemd` journal plugin](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md) documentation has information about:
7
+The [`systemd` journal plugin](/src/collectors/systemd-journal.plugin/README.md) documentation has information about:
8
9
-- [Key features the plugin provides](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md#key-features)
10
-- [Journal sources](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md#journal-sources)
11
-- [Journal fields](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md#journal-fields)
12
-- [Full-text search](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md#full-text-search)
13
-- [Query performance](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md#query-performance)
14
-- [Performance at scale](https://github.com/netdata/netdata/blob/master/src/collectors/systemd-journal.plugin/README.md#performance-at-scale)
9
+- [Key features the plugin provides](/src/collectors/systemd-journal.plugin/README.md#key-features)
10
+- [Journal sources](/src/collectors/systemd-journal.plugin/README.md#journal-sources)
11
+- [Journal fields](/src/collectors/systemd-journal.plugin/README.md#journal-fields)
12
+- [Full-text search](/src/collectors/systemd-journal.plugin/README.md#full-text-search)
13
+- [Query performance](/src/collectors/systemd-journal.plugin/README.md#query-performance)
14
+- [Performance at scale](/src/collectors/systemd-journal.plugin/README.md#performance-at-scale)
15
16
We recommend you to read through that document, to better understand how the plugin and the visualizations work.
docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md
+3
-3
@@ -1,14 +1,14 @@
1
# Metrics tab and single node tabs
2
3
-The Metrics tab is where all the time series [charts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md) for all the nodes of a War Room are located.
3
+The Metrics tab is where all the time series [charts](/docs/dashboards-and-charts/netdata-charts.md) for all the nodes of a War Room are located.
4
5
You can also see single-node dashboards, essentially the same dashboard the Metrics tab offers but only for one node. They are reached from most places in the UI, often by clicking the name of a node.
6
7
-From this tab, a user can also reach the Integrations tab and run [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md)
7
+From this tab, a user can also reach the Integrations tab and run [Metric Correlations](/docs/metric-correlations.md)
8
9
## Dashboard structure
10
11
-The dashboard consists of various charts presented in different chart types. They are categorized based on their [context](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#contexts) and at the beginning of each section, there is a predefined arrangement of charts helping you to get an overview for that particular section.
11
+The dashboard consists of various charts presented in different chart types. They are categorized based on their [context](/docs/dashboards-and-charts/netdata-charts.md#contexts) and at the beginning of each section, there is a predefined arrangement of charts helping you to get an overview for that particular section.
12
13
## Chart navigation Menu
14
docs/dashboards-and-charts/netdata-charts.md
+10
-10
@@ -13,14 +13,14 @@ These charts provide a lot of useful information, so that you can:
13
- View the combined anomaly rate of all underlying data with the [Anomaly Rate ribbon](#anomaly-rate-ribbon)
14
- Explore even more details about a chart's metrics through [hovering over certain elements of it](#hover-over-the-chart)
15
- Use intuitive tooling and shortcuts to pan, zoom or highlight areas of interest in your charts
16
-- On highlight, get easy access to [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md) to see other metrics with similar patterns
16
+- On highlight, get easy access to [Metric Correlations](/docs/metric-correlations.md) to see other metrics with similar patterns
17
- Have the dimensions sorted based on name or value
18
- View information about the chart, its plugin, context, and type
19
- View individual metric collection status about a chart
20
21
These charts are available on Netdata Cloud's
22
-[Metrics tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md), [single sode tabs](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) and
23
-on your [Custom Dashboards](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md).
22
+[Metrics tab](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md), [single sode tabs](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) and
23
+on your [Custom Dashboards](/docs/dashboards-and-charts/dashboards-tab.md).
24
25
## Overview
26
@@ -42,8 +42,8 @@ With a quick glance you have immediate information available at your disposal:
42
While Netdata's charts require no configuration and are easy to interact with, they have a lot of underlying complexity. To meaningfully organize charts out of the box based on what's happening in your nodes, Netdata uses the concepts of [dimensions](#dimensions), [contexts](#contexts), and [families](#families).
43
44
Understanding how these work will help you more easily navigate the dashboard,
45
-[write new alerts](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md), or play around
46
-with the [API](https://github.com/netdata/netdata/blob/master/src/web/api/README.md).
45
+[write new alerts](/src/health/REFERENCE.md), or play around
46
+with the [API](/src/web/api/README.md).
47
48
### Dimensions
49
@@ -71,7 +71,7 @@ whereas anything after the `.` is specified either by the chart's developer or b
71
72
By default, a chart's type affects where it fits in the menu, while its family creates submenus.
73
74
-Netdata also relies on contexts for [alert configuration](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) (the [`on` line](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-on)).
74
+Netdata also relies on contexts for [alert configuration](/src/health/REFERENCE.md) (the [`on` line](/src/health/REFERENCE.md#alert-line-on)).
75
76
### Families
77
@@ -104,7 +104,7 @@ When you start interacting with a chart, you'll notice valuable information on t
104
105
The elements that you can find on this top bar are:
106
107
-- **Netdata icon**: this indicates that data is continuously being updated, this happens if [Time controls](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/visualization-date-and-time-controls.md#time-controls) are in Play or Force Play mode.
107
+- **Netdata icon**: this indicates that data is continuously being updated, this happens if [Time controls](/docs/dashboards-and-charts/visualization-date-and-time-controls.md#time-controls) are in Play or Force Play mode.
108
- **Chart title**: on the chart title you can see the title together with the metric being displayed, as well as the unit of measurement.
109
- **Chart status icon**: possible values are: Loading, Timeout, Error or No data, otherwise this icon is not shown.
110
@@ -262,7 +262,7 @@ By default the aggregation applied is _average_ but the user can choose differen
262
- Delta
263
- Single or Double exponential smoothing
264
265
-For more details on each, you can refer to our Agent's HTTP API details on [Data Queries - Data Grouping](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md#data-grouping).
265
+For more details on each, you can refer to our Agent's HTTP API details on [Data Queries - Data Grouping](/src/web/api/queries/README.md#data-grouping).
266
267
### Reset to defaults
268
@@ -318,7 +318,7 @@ All these indicators are also visualized per dimension, in the pop-over that app
318
319
## Play, Pause and Reset
320
321
-Your charts are controlled using the available [Time controls](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/visualization-date-and-time-controls.md#time-controls).
321
+Your charts are controlled using the available [Time controls](/docs/dashboards-and-charts/visualization-date-and-time-controls.md#time-controls).
322
Besides these, when interacting with the chart you can also activate these controls by:
323
324
- Hovering over any chart to temporarily pause it - this momentarily switches time control to Pause, so that you can
@@ -363,7 +363,7 @@ it like pushing the current timeframe off the screen to see what came before or
363
Selecting timeframes is useful when you see an interesting spike or change in a chart and want to investigate further by:
364
365
- Looking at the same period of time on other charts/sections
366
-- Running [metric correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md) to filter metrics that also show something different in the selected period, vs the previous one
366
+- Running [metric correlations](/docs/metric-correlations.md) to filter metrics that also show something different in the selected period, vs the previous one
367
368
| Interaction | Keyboard/mouse | Touchpad/touchscreen |
369
|:-----------------------------------|:---------------------------------------------------------|:---------------------|
docs/dashboards-and-charts/node-filter.md
+1
-1
@@ -6,7 +6,7 @@ Inside the filter, the nodes get categorized into three groups:
6
7
| Group | Description |
8
|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
9
-| Live | Nodes that are currently online, collecting and streaming metrics to Cloud. Live nodes display raised [Alert](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/alerts-tab.md) counters, [Machine Learning](https://github.com/netdata/netdata/blob/master/src/ml/README.md) availability, and [Functions](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) availability |
9
+| Live | Nodes that are currently online, collecting and streaming metrics to Cloud. Live nodes display raised [Alert](/docs/dashboards-and-charts/alerts-tab.md) counters, [Machine Learning](/src/ml/README.md) availability, and [Functions](/docs/top-monitoring-netdata-functions.md) availability |
10
| Stale | Nodes that are offline and not streaming metrics to Cloud. Only historical data can be presented from a parent node. For these nodes you can only see their ML status, as they are not online to provide more information |
11
| Offline | Nodes that are offline, not streaming metrics to Cloud and not available in any parent node. Offline nodes are automatically deleted after 30 days and can also be deleted manually. |
12
docs/dashboards-and-charts/nodes-tab.md
+2
-2
@@ -1,6 +1,6 @@
1
# Nodes tab
2
3
-The nodes tab provides a summarized view of your [War Room](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms), allowing you to view quick information per node.
3
+The nodes tab provides a summarized view of your [War Room](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms), allowing you to view quick information per node.
4
5
> **Tip**
6
>
@@ -28,7 +28,7 @@ Each node row allows you to:
28
- View Machine Learning status
29
- View Functions capability status
30
- Add configuration (beta)
31
-- [Add alert silencing rules](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md)
31
+- [Add alert silencing rules](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md)
32
- View a set of key attributes collected on your node
33
34
## Right bar
docs/dashboards-and-charts/top-tab.md
+3
-3
@@ -1,15 +1,15 @@
1
# Top tab
2
3
-The Top tab allows you to run [Netdata Functions](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) on a node where a Netdata Agent is running. These routines are exposed by a given collector.
3
+The Top tab allows you to run [Netdata Functions](/docs/top-monitoring-netdata-functions.md) on a node where a Netdata Agent is running. These routines are exposed by a given collector.
4
They can be used to retrieve additional information to help you troubleshoot or to trigger some action to happen on the node itself.
5
6
> **Tip**
7
>
8
-> You can also execute a Function from the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md), by pressing the `f(x)` button.
8
+> You can also execute a Function from the [Nodes tab](/docs/dashboards-and-charts/nodes-tab.md), by pressing the `f(x)` button.
9
10
> **Note**
11
>
12
-> If you get an error saying that your node can't execute Functions please check the [prerequisites](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md#prerequisites).
12
+> If you get an error saying that your node can't execute Functions please check the [prerequisites](/docs/top-monitoring-netdata-functions.md#prerequisites).
13
14
The main view of this tab provides you with (depending on the Function) two elements: a visualization on the top and a table on the bottom.
15
docs/dashboards-and-charts/visualization-date-and-time-controls.md
+2
-2
@@ -27,7 +27,7 @@ The date and time selector allows you to change the visible timeframe and change
27
28
### Pick timeframes to visualize
29
30
-While [panning through time and zooming in/out](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md) from charts it is helpful when you're looking a recent history, or want to do granular troubleshooting, what if you want to see metrics from 6 hours ago? Or 6 days?
30
+While [panning through time and zooming in/out](/docs/dashboards-and-charts/netdata-charts.md) from charts it is helpful when you're looking a recent history, or want to do granular troubleshooting, what if you want to see metrics from 6 hours ago? Or 6 days?
31
32
Netdata's dashboard features a **timeframe selector** to help you visualize specific timeframes in a few helpful ways.
33
By default, it shows a certain number of minutes of historical metrics based on the your browser's viewport to ensure it's always showing per-second granularity.
@@ -81,7 +81,7 @@ beyond stored historical metrics, you'll see this message:
81
82
83
84
-At any time, [configure the internal TSDB's storage capacity](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) to expand your
84
+At any time, [configure the internal TSDB's storage capacity](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) to expand your
85
depth of historical metrics.
86
87
### Timezone selector
docs/deployment-guides/README.md
+1
-1
@@ -12,7 +12,7 @@ There are 3 components to structure your Netdata ecosystem:
12
13
2. **Netdata Parents**
14
15
- To create [observability centralization points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md) within your infrastructure, to offload Netdata Agents functions from your production systems, to provide high-availability of your data, increased data retention and isolation of your nodes.
15
+ To create [observability centralization points](/docs/observability-centralization-points/README.md) within your infrastructure, to offload Netdata Agents functions from your production systems, to provide high-availability of your data, increased data retention and isolation of your nodes.
16
17
Netdata Parents are implemented using the Netdata Agent software. Any Netdata Agent can be an Agent for a node and a Parent for other Agents, at the same time.
18
docs/deployment-guides/deployment-strategies.md
+12
-12
@@ -10,7 +10,7 @@ This section provides a quick overview of a few common deployment options. The n
10
To help our users have a complete experience of Netdata when they install it for the first time, a Netdata Agent with default configuration
11
is a complete monitoring solution out of the box, having all these features enabled and available.
12
13
-The Agent will act as a _stand-alone_ Agent by default, and this is great to start out with for small setups and home labs. By [connecting each Agent to Cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md), you can see an overview of all your nodes, with aggregated charts and centralized alerting, without setting up a Parent.
13
+The Agent will act as a _stand-alone_ Agent by default, and this is great to start out with for small setups and home labs. By [connecting each Agent to Cloud](/src/claim/README.md), you can see an overview of all your nodes, with aggregated charts and centralized alerting, without setting up a Parent.
14
15
16
@@ -38,17 +38,17 @@ With both Parent Agents connected to Cloud, Cloud will route queries to either P
38
39
### Stand-alone Deployment
40
41
-The stand-alone setup is configured out of the box with reasonable defaults, but please consult our [configuration documentation](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/cheatsheet.md) for details, including the overview of [common configuration changes](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/common-configuration-changes.md).
41
+The stand-alone setup is configured out of the box with reasonable defaults, but please consult our [configuration documentation](/docs/netdata-agent/configuration/cheatsheet.md) for details, including the overview of [common configuration changes](/docs/netdata-agent/configuration/common-configuration-changes.md).
42
43
### Parent – Child Deployment
44
45
-For setups involving Child and Parent Agents, the Agents need to be configured for [_streaming_](https://github.com/netdata/netdata/blob/master/src/streaming/README.md), through the configuration file `stream.conf`. This will instruct the Child to stream data to the Parent and the Parent to accept streaming connections for one or more Child Agents. To secure this connection, both need set up a shared API key (to replace the string `API_KEY` in the examples below). Additionally, the Child is configured with one or more addresses of Parent Agents (`PARENT_IP_ADDRESS`).
45
+For setups involving Child and Parent Agents, the Agents need to be configured for [_streaming_](/src/streaming/README.md), through the configuration file `stream.conf`. This will instruct the Child to stream data to the Parent and the Parent to accept streaming connections for one or more Child Agents. To secure this connection, both need set up a shared API key (to replace the string `API_KEY` in the examples below). Additionally, the Child is configured with one or more addresses of Parent Agents (`PARENT_IP_ADDRESS`).
46
47
An API key is a key created with `uuidgen` and is used for authentication and/or customization in the Parent side. I.e. a Child will stream using the API key, and a Parent is configured to accept connections from Child, but can also apply different options for children by using multiple different API keys. The easiest setup uses just one API key for all Child Agents.
48
49
#### Child config
50
51
-As mentioned above, the recommendation is to not claim the Child to Cloud directly during your setup, avoiding establishing an [ACLK](https://github.com/netdata/netdata/blob/master/src/aclk/README.md) connection.
51
+As mentioned above, the recommendation is to not claim the Child to Cloud directly during your setup, avoiding establishing an [ACLK](/src/aclk/README.md) connection.
52
53
To reduce the footprint of the Netdata Agent on your production system, some capabilities can be switched OFF on the Child and kept ON on the Parent. In this example, Machine Learning and Alerting are disabled in the Child, so that the Parent can take the load. We also use RAM instead of disk to store metrics with limited retention, covering temporary network issues.
54
@@ -101,7 +101,7 @@ Set the following parameters:
101
102
#### Parent config
103
104
-For the Parent, besides setting up streaming, the example will also provide an example configuration of multiple [tiers](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiering) of metrics [storage](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md), for 10 children, with about 2k metrics each.
104
+For the Parent, besides setting up streaming, the example will also provide an example configuration of multiple [tiers](/src/database/engine/README.md#tiering) of metrics [storage](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md), for 10 children, with about 2k metrics each.
105
106
- 1s granularity at tier 0 for 1 week
107
- 1m granularity at tier 1 for 1 month
@@ -208,32 +208,32 @@ On both Netdata Parent and all Child Agents, edit `stream.conf` with `/etc/netda
208
209
We strongly recommend the following configuration changes for production deployments:
210
211
-1. Understand Netdata's [security and privacy design](https://github.com/netdata/netdata/blob/master/docs/security-and-privacy-design/README.md) and
212
- [secure your nodes](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/securing-netdata-agents.md)
211
+1. Understand Netdata's [security and privacy design](/docs/security-and-privacy-design/README.md) and
212
+ [secure your nodes](/docs/netdata-agent/securing-netdata-agents.md)
213
214
To safeguard your infrastructure and comply with your organization's security policies.
215
216
-2. Set up [streaming and replication](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) to:
216
+2. Set up [streaming and replication](/src/streaming/README.md) to:
217
218
- Offload Netdata Agents running on production systems and free system resources for the production applications running on them.
219
- Isolate production systems from the rest of the world and improve security.
220
- Increase data retention.
221
- Make your data highly available.
222
223
-3. [Optimize the Netdata Agents system utilization and performance](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md)
223
+3. [Optimize the Netdata Agents system utilization and performance](/docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md)
224
225
To save valuable system resources, especially when running on weak IoT devices.
226
227
We also suggest that you:
228
229
-1. [Use Netdata Cloud to access the dashboards](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/monitor-your-infrastructure.md)
229
+1. [Use Netdata Cloud to access the dashboards](/docs/netdata-cloud/monitor-your-infrastructure.md)
230
231
For increased security, user management and access to our latest tools for advanced dashboarding and troubleshooting.
232
233
-2. [Change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md)
233
+2. [Change how long Netdata stores metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md)
234
235
To control Netdata's memory use, when you have a lot of ephemeral metrics.
236
237
-3. [Use host labels](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md)
237
+3. [Use host labels](/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md)
238
239
To organize systems, metrics, and alerts.
docs/deployment-guides/standalone-deployment.md
+1
-1
@@ -77,7 +77,7 @@ No special configuration needed.
77
| Centrally dispatched alert notifications | Yes, via Netdata Cloud |
78
| Data are exclusively on-prem | Yes, Netdata Cloud queries Netdata Agents to satisfy dashboard queries. |
79
80
-By [connecting all Netdata agents to Netdata Cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md), you can have a unified infrastructure view of all your nodes, with aggregated charts, without configuring [observability centralization points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md).
80
+By [connecting all Netdata agents to Netdata Cloud](/src/claim/README.md), you can have a unified infrastructure view of all your nodes, with aggregated charts, without configuring [observability centralization points](/docs/observability-centralization-points/README.md).
81
82
```mermaid
83
flowchart LR
docs/developer-and-contributor-corner/collect-apache-nginx-web-logs.md
+4
-4
@@ -8,7 +8,7 @@ You can use the [LTSV log format](http://ltsv.org/), track TLS and cipher usage,
8
ever. In one test on a system with SSD storage, the collector consistently parsed the logs for 200,000 requests in
9
200ms, using ~30% of a single core.
10
11
-The [web_log](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md) collector is currently compatible
11
+The [web_log](/src/go/collectors/go.d.plugin/modules/weblog/README.md) collector is currently compatible
12
with [Nginx](https://nginx.org/en/) and [Apache](https://httpd.apache.org/).
13
14
This guide will walk you through using the new Go-based web log collector to turn the logs these web servers
@@ -82,7 +82,7 @@ jobs:
82
```
83
84
Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
85
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. Netdata should pick up your web server's access log and
85
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. Netdata should pick up your web server's access log and
86
begin showing real-time charts!
87
88
### Custom log formats and fields
@@ -91,7 +91,7 @@ The web log collector is capable of parsing custom Nginx and Apache log formats
91
leave that topic for a separate guide.
92
93
We do have [extensive
94
-documentation](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md#custom-log-format) on how
94
+documentation](/src/go/collectors/go.d.plugin/modules/weblog/README.md#custom-log-format) on how
95
to build custom parsing for Nginx and Apache logs.
96
97
## Tweak web log collector alerts
@@ -109,4 +109,4 @@ You can also edit this file directly with `edit-config`:
109
```
110
111
For more information about editing the defaults or writing new alert entities, see our
112
-[health monitoring documentation](https://github.com/netdata/netdata/blob/master/src/health/README.md).
112
+[health monitoring documentation](/src/health/README.md).
docs/developer-and-contributor-corner/collect-unbound-metrics.md
+2
-2
@@ -59,7 +59,7 @@ You may not need to do any more configuration to have Netdata collect your Unbou
59
60
If you followed the steps above to enable `remote-control` and make your Unbound files readable by Netdata, that should
61
be enough. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
62
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. You should see Unbound metrics in your Netdata
62
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. You should see Unbound metrics in your Netdata
63
dashboard!
64
65
@@ -104,7 +104,7 @@ Netdata will attempt to read `unbound.conf` to get the appropriate `address`, `c
104
`tls_key` parameters.
105
106
Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
107
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
107
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
108
109
### Manual setup for a remote Unbound server
110
docs/developer-and-contributor-corner/customize.md
+3
-3
@@ -2,9 +2,9 @@
2
3
> ### Disclaimer
4
>
5
-> This document is only applicable to the v1 version of the dashboard and doesn't affect the [Netdata Dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md).
5
+> This document is only applicable to the v1 version of the dashboard and doesn't affect the [Netdata Dashboard](/docs/dashboards-and-charts/README.md).
6
7
-While the [Netdata dashboard](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md) comes preconfigured with hundreds of charts and
7
+While the [Netdata dashboard](/src/web/gui/README.md) comes preconfigured with hundreds of charts and
8
thousands of metrics, you may want to alter your experience based on a particular use case or preferences.
9
10
## Dashboard settings
@@ -64,7 +64,7 @@ Edit the file with customizations to the `title`, `icon`, and `info` fields. Rep
64
icon from [Font Awesome](https://fontawesome.com/cheatsheet) to customize the icons that appear throughout the
65
dashboard.
66
67
-Save the file, then navigate to your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) to edit `netdata.conf`. Add
67
+Save the file, then navigate to your [Netdata config directory](/docs/netdata-agent/configuration/README.md) to edit `netdata.conf`. Add
68
the following line to the `[web]` section to tell Netdata where to find your custom configuration.
69
70
```conf
docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md
+12
-12
@@ -38,7 +38,7 @@ To follow this tutorial, you need:
38
- A free Netdata Cloud account. [Sign up](https://app.netdata.cloud/sign-up?cloudRoute=/spaces) if you don't have one
39
already.
40
- A working cluster running Kubernetes v1.9 or newer, with a Netdata deployment and connected parent/child nodes. See
41
- our [Kubernetes deployment process](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md) for details on deployment and
41
+ our [Kubernetes deployment process](/packaging/installer/methods/kubernetes.md) for details on deployment and
42
conneting to Cloud.
43
- The [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) command line tool, within [one minor version
44
difference](https://kubernetes.io/docs/tasks/tools/install-kubectl/#before-you-begin) of your cluster, on an
@@ -123,7 +123,7 @@ visualizations](https://user-images.githubusercontent.com/1153921/109049195-349f
123
124
### Health map
125
126
-The first visualization is the [health map](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md#health-map),
126
+The first visualization is the [health map](/docs/dashboards-and-charts/kubernetes-tab.md#health-map),
127
which places each container into its own box, then varies the intensity of their color to visualize the resource
128
utilization. By default, the health map shows the **average CPU utilization as a percentage of the configured limit**
129
for every container in your cluster.
@@ -137,7 +137,7 @@ Let's explore the most colorful box by hovering over it.
137
container](https://user-images.githubusercontent.com/1153921/109049544-a8417980-7695-11eb-80a7-109b4a645a27.png)
138
139
The **Context** tab shows `rabbitmq-5bb66bb6c9-6xr5b` as the container's image name, which means this container is
140
-running a [RabbitMQ](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/rabbitmq/README.md) workload.
140
+running a [RabbitMQ](/src/go/collectors/go.d.plugin/modules/rabbitmq/README.md) workload.
141
142
Click the **Metrics** tab to see real-time metrics from that container. Unsurprisingly, it shows a spike in CPU
143
utilization at regular intervals.
@@ -156,7 +156,7 @@ different namespaces.
156
158
159
-Each composite chart has a [definition bar](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#definition-bar)
159
+Each composite chart has a [definition bar](/docs/dashboards-and-charts/netdata-charts.md#definition-bar)
160
for complete customization. For example, grouping the top chart by `k8s_container_name` reveals new information.
161
162
@@ -166,20 +166,20 @@ for complete customization. For example, grouping the top chart by `k8s_containe
166
Netdata has a [service discovery plugin](https://github.com/netdata/agent-service-discovery), which discovers and
167
creates configuration files for [compatible
168
services](https://github.com/netdata/helmchart#service-discovery-and-supported-services) and any endpoints covered by
169
-our [generic Prometheus collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/README.md).
169
+our [generic Prometheus collector](/src/go/collectors/go.d.plugin/modules/prometheus/README.md).
170
Netdata uses these files to collect metrics from any compatible application as they run _inside_ of a pod. Service
171
discovery happens without manual intervention as pods are created, destroyed, or moved between nodes.
172
173
Service metrics show up on the Overview as well, beneath the **Kubernetes** section, and are labeled according to the
174
service in question. For example, the **RabbitMQ** section has numerous charts from the [`rabbitmq`
175
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/rabbitmq/README.md):
175
+collector](/src/go/collectors/go.d.plugin/modules/rabbitmq/README.md):
176
177
179
180
> The robot-shop cluster has more supported services, such as MySQL, which are not visible with zero configuration. This
181
> is usually because of services running on non-default ports, using non-default names, or required passwords. Read up
182
-> on [configuring service discovery](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md#configure-service-discovery) to collect
182
+> on [configuring service discovery](/packaging/installer/methods/kubernetes.md#configure-service-discovery) to collect
183
> more service metrics.
184
185
Service metrics are essential to infrastructure monitoring, as they're the best indicator of the end-user experience,
@@ -193,7 +193,7 @@ Netdata also automatically collects metrics from two essential Kubernetes proces
193
194
The **k8s kubelet** section visualizes metrics from the Kubernetes agent responsible for managing every pod on a given
195
node. This also happens without any configuration thanks to the [kubelet
196
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubelet/README.md).
196
+collector](/src/go/collectors/go.d.plugin/modules/k8s_kubelet/README.md).
197
198
Monitoring each node's kubelet can be invaluable when diagnosing issues with your Kubernetes cluster. For example, you
199
can see if the number of running containers/pods has dropped, which could signal a fault or crash in a particular
@@ -209,7 +209,7 @@ configuration-related errors, and the actual vs. desired numbers of volumes, plu
209
The **k8s kube-proxy** section displays metrics about the network proxy that runs on each node in your Kubernetes
210
cluster. kube-proxy lets pods communicate with each other and accept sessions from outside your cluster. Its metrics are
211
collected by the [kube-proxy
212
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/README.md).
212
+collector](/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/README.md).
213
214
With Netdata, you can monitor how often your k8s proxies are syncing proxy rules between nodes. Dramatic changes in
215
these figures could indicate an anomaly in your cluster that's worthy of further investigation.
@@ -229,9 +229,9 @@ clusters of all sizes.
229
- [Netdata Helm chart](https://github.com/netdata/helmchart)
230
- [Netdata service discovery](https://github.com/netdata/agent-service-discovery)
231
- [Netdata Agent · `kubelet`
232
- collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubelet/README.md)
232
+ collector](/src/go/collectors/go.d.plugin/modules/k8s_kubelet/README.md)
233
- [Netdata Agent · `kube-proxy`
234
- collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/README.md)
235
-- [Netdata Agent · `cgroups.plugin`](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md)
234
+ collector](/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/README.md)
235
+- [Netdata Agent · `cgroups.plugin`](/src/collectors/cgroups.plugin/README.md)
236
237
docs/developer-and-contributor-corner/lamp-stack.md
+21
-21
@@ -51,7 +51,7 @@ To follow this tutorial, you need:
51
## Install the Netdata Agent
52
53
If you don't have the free, open-source Netdata monitoring agent installed on your node yet, get started with a [single
54
-kickstart command](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md):
54
+kickstart command](/packaging/installer/README.md):
55
56
<OneLineInstallWget/>
57
@@ -61,15 +61,15 @@ replacing `NODE` with the hostname or IP address of your system.
61
62
## Enable hardware and Linux system monitoring
63
64
-There's nothing you need to do to enable [system monitoring](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/system-metrics.md) and Linux monitoring with
64
+There's nothing you need to do to enable [system monitoring](/docs/collecting-metrics/system-metrics.md) and Linux monitoring with
65
the Netdata Agent, which autodetects metrics from CPUs, memory, disks, networking devices, and Linux processes like
66
systemd without any configuration. If you're using containers, Netdata automatically collects resource utilization
67
-metrics from each using the [cgroups data collector](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md).
67
+metrics from each using the [cgroups data collector](/src/collectors/cgroups.plugin/README.md).
68
69
## Enable Apache monitoring
70
71
Let's begin by configuring Apache to work with Netdata's [Apache data
72
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/apache/README.md).
72
+collector](/src/go/collectors/go.d.plugin/modules/apache/README.md).
73
74
Actually, there's nothing for you to do to enable Apache monitoring with Netdata.
75
@@ -80,7 +80,7 @@ metrics](https://httpd.apache.org/docs/2.4/mod/mod_status.html), which is just _
80
## Enable web log monitoring
81
82
The Netdata Agent also comes with a [web log
83
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md), which reads Apache's access
83
+collector](/src/go/collectors/go.d.plugin/modules/weblog/README.md), which reads Apache's access
84
log file, processes each line, and converts them into per-second metrics. On Debian systems, it reads the file at
85
`/var/log/apache2/access.log`.
86
@@ -93,7 +93,7 @@ monitoring.
93
94
Because your MySQL database is password-protected, you do need to tell MySQL to allow the `netdata` user to connect to
95
without a password. Netdata's [MySQL data
96
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/README.md) collects metrics in _read-only_
96
+collector](/src/go/collectors/go.d.plugin/modules/mysql/README.md) collects metrics in _read-only_
97
mode, without being able to alter or affect operations in any way.
98
99
First, log into the MySQL shell. Then, run the following three commands, one at a time:
@@ -105,15 +105,15 @@ FLUSH PRIVILEGES;
105
```
106
107
Run `sudo systemctl restart netdata`, or the [appropriate alternative for your
108
-system](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation), to collect dozens of metrics every second for robust MySQL monitoring.
108
+system](/packaging/installer/README.md#maintaining-a-netdata-agent-installation), to collect dozens of metrics every second for robust MySQL monitoring.
109
110
## Enable PHP monitoring
111
112
Unlike Apache or MySQL, PHP isn't a service that you can monitor directly, unless you instrument a PHP-based application
113
-with [StatsD](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/README.md).
113
+with [StatsD](/src/collectors/statsd.plugin/README.md).
114
115
However, if you use [PHP-FPM](https://php-fpm.org/) in your LAMP stack, you can monitor that process with our [PHP-FPM
116
-data collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/phpfpm/README.md).
116
+data collector](/src/go/collectors/go.d.plugin/modules/phpfpm/README.md).
117
118
Open your PHP-FPM configuration for editing, replacing `7.4` with your version of PHP:
119
@@ -159,12 +159,12 @@ If the Netdata Agent isn't already open in your browser, open a new tab and navi
159
160
> If you [signed up](https://app.netdata.cloud/sign-up?cloudRoute=/spaces) for Netdata Cloud earlier, you can also view
161
> the exact same LAMP stack metrics there, plus additional features, like drag-and-drop custom dashboards. Be sure to
162
-> [connecting your node](https://github.com/netdata/netdata/blob/master/src/claim/README.md) to start streaming metrics to your browser through Netdata Cloud.
162
+> [connecting your node](/src/claim/README.md) to start streaming metrics to your browser through Netdata Cloud.
163
164
Netdata automatically organizes all metrics and charts onto a single page for easy navigation. Peek at gauges to see
165
overall system performance, then scroll down to see more. Click-and-drag with your mouse to pan _all_ charts back and
166
forth through different time intervals, or hold `SHIFT` and use the scrollwheel (or two-finger scroll) to zoom in and
167
-out. Check out our doc on [interacting with charts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md) for all the details.
167
+out. Check out our doc on [interacting with charts](/docs/dashboards-and-charts/netdata-charts.md) for all the details.
168
169
170
@@ -197,15 +197,15 @@ Here's a quick reference for what charts you might want to focus on after settin
197
The Netdata Agent comes with hundreds of pre-configured alerts to help you keep tabs on your system, including 19 alerts
198
designed for smarter LAMP stack monitoring.
199
200
-Click the 🔔 icon in the top navigation to [see active alerts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/alerts-tab.md). The **Active** tabs
200
+Click the 🔔 icon in the top navigation to [see active alerts](/docs/dashboards-and-charts/alerts-tab.md). The **Active** tabs
201
shows any alerts currently triggered, while the **All** tab displays a list of _every_ pre-configured alert. The
202
203
205
206
-[Tweak alerts](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) based on your infrastructure monitoring needs, and to see these alerts
206
+[Tweak alerts](/src/health/REFERENCE.md) based on your infrastructure monitoring needs, and to see these alerts
207
in other places, like your inbox or a Slack channel, [enable a notification
208
-method](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/README.md).
208
+method](/docs/alerts-and-notifications/notifications/README.md).
209
210
## What's next?
211
@@ -215,7 +215,7 @@ services. The per-second metrics granularity means you have the most accurate in
215
any LAMP-related issues.
216
217
Another powerful way to monitor the availability of a LAMP stack is the [`httpcheck`
218
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/README.md), which pings a web server at
218
+collector](/src/go/collectors/go.d.plugin/modules/httpcheck/README.md), which pings a web server at
219
a regular interval and tells you whether if and how quickly it's responding. The `response_match` option also lets you
220
monitor when the web server's response isn't what you expect it to be, which might happen if PHP-FPM crashes, for
221
example.
@@ -225,14 +225,14 @@ we're not covering it here, but it _does_ work in a single-node setup. Just don'
225
node crashed.
226
227
If you're planning on managing more than one node, or want to take advantage of advanced features, like finding the
228
-source of issues faster with [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md),
228
+source of issues faster with [Metric Correlations](/docs/metric-correlations.md),
229
[sign up](https://app.netdata.cloud/sign-up?cloudRoute=/spaces) for a free Netdata Cloud account.
230
231
### Related reference documentation
232
233
-- [Netdata Agent · Get started](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md)
234
-- [Netdata Agent · Apache data collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/apache/README.md)
235
-- [Netdata Agent · Web log collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md)
236
-- [Netdata Agent · MySQL data collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/README.md)
237
-- [Netdata Agent · PHP-FPM data collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/phpfpm/README.md)
233
+- [Netdata Agent · Get started](/packaging/installer/README.md)
234
+- [Netdata Agent · Apache data collector](/src/go/collectors/go.d.plugin/modules/apache/README.md)
235
+- [Netdata Agent · Web log collector](/src/go/collectors/go.d.plugin/modules/weblog/README.md)
236
+- [Netdata Agent · MySQL data collector](/src/go/collectors/go.d.plugin/modules/mysql/README.md)
237
+- [Netdata Agent · PHP-FPM data collector](/src/go/collectors/go.d.plugin/modules/phpfpm/README.md)
238
docs/developer-and-contributor-corner/monitor-cockroachdb.md
+3
-3
@@ -11,7 +11,7 @@ learn_rel_path: "Miscellaneous"
11
12
[CockroachDB](https://github.com/cockroachdb/cockroach) is an open-source project that brings SQL databases into
13
scalable, disaster-resilient cloud deployments. Thanks to
14
-a [new CockroachDB collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/cockroachdb/README.md)
14
+a [new CockroachDB collector](/src/go/collectors/go.d.plugin/modules/cockroachdb/README.md)
15
released in
16
[v1.20](https://blog.netdata.cloud/posts/release-1.20/), you can now monitor any number of CockroachDB databases with
17
maximum granularity using Netdata. Collect more than 50 unique metrics and put them on interactive visualizations
@@ -38,7 +38,7 @@ display them on the dashboard.
38
39
If your CockroachDB instance is accessible through `http://localhost:8080/` or `http://127.0.0.1:8080`, your setup is
40
complete. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
41
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, and refresh your browser. You should see CockroachDB
41
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, and refresh your browser. You should see CockroachDB
42
metrics in your Netdata dashboard!
43
44
<figure>
@@ -115,4 +115,4 @@ cd /etc/netdata/ # Replace with your Netdata configuration directory, if not /et
115
./edit-config health.d/cockroachdb.conf # You may need to use `sudo` for write privileges
116
```
117
118
-For more information about editing the defaults or writing new alert entities, see our documentation on [configuring health alerts](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md).
118
+For more information about editing the defaults or writing new alert entities, see our documentation on [configuring health alerts](/src/health/REFERENCE.md).
docs/developer-and-contributor-corner/monitor-debug-applications-ebpf.md
+10
-10
@@ -12,7 +12,7 @@ learn_rel_path: "Operations"
12
13
When trying to troubleshoot or debug a finicky application, there's no such thing as too much information. At Netdata,
14
we developed programs that connect to the [_extended Berkeley Packet Filter_ (eBPF) virtual
15
-machine](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md) to help you see exactly how specific applications are interacting with the
15
+machine](/src/collectors/ebpf.plugin/README.md) to help you see exactly how specific applications are interacting with the
16
Linux kernel. With these charts, you can root out bugs, discover optimizations, diagnose memory leaks, and much more.
17
18
This means you can see exactly how often, and in what volume, the application creates processes, opens files, writes to
@@ -29,7 +29,7 @@ To start troubleshooting an application with eBPF metrics, you need to ensure yo
29
displays those metrics independent from any other process.
30
31
You can use the `apps_groups.conf` file to configure which applications appear in charts generated by
32
-[`apps.plugin`](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md). Once you edit this file and create a new group for the application
32
+[`apps.plugin`](/src/collectors/apps.plugin/README.md). Once you edit this file and create a new group for the application
33
you want to monitor, you can see how it's interacting with the Linux kernel via real-time eBPF metrics.
34
35
Let's assume you have an application that runs on the process `custom-app`. To monitor eBPF metrics for that application
@@ -61,12 +61,12 @@ dev: custom-app
61
```
62
63
Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
64
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to begin seeing metrics for this particular
64
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to begin seeing metrics for this particular
65
group+process. You can also add additional processes to the same group.
66
67
You can set up `apps_groups.conf` to more show more precise eBPF metrics for any application or service running on your
68
system, even if it's a standard package like Redis, Apache, or any other [application/service Netdata collects
69
-from](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md).
69
+from](/src/collectors/COLLECTORS.md).
70
71
```conf
72
# -----------------------------------------------------------------------------
@@ -86,7 +86,7 @@ to show other charts that will help you debug and troubleshoot how it interacts
86
87
## Configure the eBPF collector to monitor errors
88
89
-The eBPF collector has [two possible modes](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md#ebpf-load-mode): `entry` and `return`. The default
89
+The eBPF collector has [two possible modes](/src/collectors/ebpf.plugin/README.md#ebpf-load-mode): `entry` and `return`. The default
90
is `entry`, and only monitors calls to kernel functions, but the `return` also monitors and charts _whether these calls
91
return in error_.
92
@@ -110,7 +110,7 @@ Replace `entry` with `return`:
110
```
111
112
Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
113
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
113
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
114
115
## Get familiar with per-application eBPF metrics and charts
116
@@ -122,7 +122,7 @@ Pay particular attention to the charts in the **ebpf file**, **ebpf syscall**, *
122
sub-sections. These charts are populated by low-level Linux kernel metrics thanks to eBPF, and showcase the volume of
123
calls to open/close files, call functions like `do_fork`, IO activity on the VFS, and much more.
124
125
-See the [eBPF collector documentation](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md#integration-with-appsplugin) for the full list
125
+See the [eBPF collector documentation](/src/collectors/ebpf.plugin/README.md#integration-with-appsplugin) for the full list
126
of per-application charts.
127
128
Let's show some examples of how you can first identify normal eBPF patterns, then use that knowledge to identify
@@ -239,16 +239,16 @@ same application on multiple systems and want to correlate how it performs on ea
239
findings with someone else on your team.
240
241
If you don't already have a Netdata Cloud account, go [sign in](https://app.netdata.cloud) and get started for free.
242
-You can also read how to [monitor your infrastructure with Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/monitor-your-infrastructure.md) to understand the key features that it has to offer.
242
+You can also read how to [monitor your infrastructure with Netdata Cloud](/docs/netdata-cloud/monitor-your-infrastructure.md) to understand the key features that it has to offer.
243
244
Once you've added one or more nodes to a Space in Netdata Cloud, you can see aggregated eBPF metrics in the Overview
245
dashboard under the same **Applications** or **eBPF** sections that you
246
-find on the local Agent dashboard. Or, [create new dashboards](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md) using eBPF metrics
246
+find on the local Agent dashboard. Or, [create new dashboards](/docs/dashboards-and-charts/dashboards-tab.md) using eBPF metrics
247
from any number of distributed nodes to see how your application interacts with multiple Linux kernels on multiple Linux
248
systems.
249
250
Now that you can see eBPF metrics in Netdata Cloud, you can [invite your
251
-team](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team) and share your findings with others.
251
+team](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team) and share your findings with others.
252
253
254
docs/developer-and-contributor-corner/monitor-hadoop-cluster.md
+4
-4
@@ -27,8 +27,8 @@ alternative, like the guide available from
27
28
For more specifics on the collection modules used in this guide, read the respective pages in our documentation:
29
30
-- [HDFS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/hdfs/README.md)
31
-- [Zookeeper](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/zookeeper/README.md)
30
+- [HDFS](/src/go/collectors/go.d.plugin/modules/hdfs/README.md)
31
+- [Zookeeper](/src/go/collectors/go.d.plugin/modules/zookeeper/README.md)
32
33
## Set up your HDFS and Zookeeper installations
34
@@ -164,7 +164,7 @@ jobs:
164
address : 203.0.113.10:2182
165
```
166
167
-Finally, [restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
167
+Finally, [restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
168
169
```sh
170
sudo systemctl restart netdata
@@ -188,4 +188,4 @@ sudo /etc/netdata/edit-config health.d/zookeeper.conf
188
```
189
190
For more information about editing the defaults or writing new alert entities, see our
191
-[health monitoring documentation](https://github.com/netdata/netdata/blob/master/src/health/README.md).
191
+[health monitoring documentation](/src/health/README.md).
docs/developer-and-contributor-corner/pi-hole-raspberry-pi.md
+6
-6
@@ -81,7 +81,7 @@ service](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi
81
finished setting up Pi-hole at this point.
82
83
As far as configuring Netdata to monitor Pi-hole metrics, there's nothing you actually need to do. Netdata's [Pi-hole
84
-collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/pihole/README.md) will autodetect the new service
84
+collector](/src/go/collectors/go.d.plugin/modules/pihole/README.md) will autodetect the new service
85
running on your Raspberry Pi and immediately start collecting metrics every second.
86
87
Restart Netdata with `sudo systemctl restart netdata`, which will then recognize that Pi-hole is running and start a
@@ -103,9 +103,9 @@ action](https://user-images.githubusercontent.com/1153921/80827388-b9fee100-8b98
103
### Enable temperature sensor monitoring
104
105
You need to manually enable Netdata's built-in [temperature sensor
106
-collector](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/sensors/README.md) to start collecting metrics.
106
+collector](/src/collectors/charts.d.plugin/sensors/README.md) to start collecting metrics.
107
108
-> Netdata uses a few plugins to manage its [collectors](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md), each using a different language: Go,
108
+> Netdata uses a few plugins to manage its [collectors](/src/collectors/REFERENCE.md), each using a different language: Go,
109
> Python, Node.js, and Bash. While our Go collectors are undergoing the most active development, we still support the
110
> other languages. In this case, you need to enable a temperature sensor collector that's written in Bash.
111
@@ -123,7 +123,7 @@ Raspberry Pi temperature sensor monitoring.
123
### Storing historical metrics on your Raspberry Pi
124
125
By default, Netdata allocates 256 MiB in disk space to store historical metrics inside the [database
126
-engine](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md). On the Raspberry Pi used for this guide, Netdata collects 1,500 metrics every
126
+engine](/src/database/engine/README.md). On the Raspberry Pi used for this guide, Netdata collects 1,500 metrics every
127
second, which equates to storing 3.5 days worth of historical metrics.
128
129
You can increase this allocation by editing `netdata.conf` and increasing the `dbengine multihost disk space` setting to
@@ -135,6 +135,6 @@ more than 256.
135
```
136
137
Use our [database sizing
138
-calculator](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
139
-and the [Database configuration documentation](https://github.com/netdata/netdata/blob/master/src/database/README.md) to help you determine the right
138
+calculator](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
139
+and the [Database configuration documentation](/src/database/README.md) to help you determine the right
140
setting for your Raspberry Pi.
docs/developer-and-contributor-corner/process.md
+9
-9
@@ -37,16 +37,16 @@ With Netdata's process monitoring, you can:
37
38
## Prerequisites
39
40
-- One or more Linux nodes running [Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md)
40
+- One or more Linux nodes running [Netdata](/packaging/installer/README.md)
41
- A general understanding of how
42
- to [configure the Netdata Agent](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md)
42
+ to [configure the Netdata Agent](/docs/netdata-agent/configuration/README.md)
43
using `edit-config`.
44
- A Netdata Cloud account. [Sign up](https://app.netdata.cloud) if you don't have one already.
45
46
## How does Netdata do process monitoring?
47
48
The Netdata Agent already knows to look for hundreds
49
-of [standard applications that we support via collectors](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md),
49
+of [standard applications that we support via collectors](/src/collectors/COLLECTORS.md),
50
and groups them based on their
51
purpose. Let's say you want to monitor a MySQL
52
database using its process. The Netdata Agent already knows to look for processes with the string `mysqld` in their
@@ -55,12 +55,12 @@ process-specific charts.
55
56
The process and groups settings are used by two unique and powerful collectors.
57
58
-[**`apps.plugin`**](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md) looks at the Linux
58
+[**`apps.plugin`**](/src/collectors/apps.plugin/README.md) looks at the Linux
59
process tree every second, much like `top` or
60
`ps fax`, and collects resource utilization information on every running process. It then automatically adds a layer of
61
meaningful visualization on top of these metrics, and creates per-process/application charts.
62
63
-[**`ebpf.plugin`**](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md): Netdata's extended
63
+[**`ebpf.plugin`**](/src/collectors/ebpf.plugin/README.md): Netdata's extended
64
Berkeley Packet Filter (eBPF) collector
65
monitors Linux kernel-level metrics for file descriptors, virtual filesystem IO, and process management, and then hands
66
process-specific metrics over to `apps.plugin` for visualization. The eBPF collector also collects and visualizes
@@ -130,7 +130,7 @@ aware of hundreds of processes, and collects metrics from them automatically.
130
But, if you want to change the grouping behavior, add an application that isn't yet supported in the Netdata Agent, or
131
monitor a custom application, you need to edit the `apps_groups.conf` configuration file.
132
133
-Navigate to your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) and
133
+Navigate to your [Netdata config directory](/docs/netdata-agent/configuration/README.md) and
134
use `edit-config` to edit the file.
135
136
```bash
@@ -146,7 +146,7 @@ others, and groups them into `sql`. That makes sense, since all these processes
146
sql: mysqld* mariad* postgres* postmaster* oracle_* ora_* sqlservr
147
```
148
149
-These groups are then reflected as [dimensions](https://github.com/netdata/netdata/blob/master/src/web/README.md#dimensions)
149
+These groups are then reflected as [dimensions](/src/web/README.md#dimensions)
150
within Netdata's charts.
151
152
 for your system, to start collecting utilization metrics
183
+the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to start collecting utilization metrics
184
from your application. Time to [visualize your process metrics](#visualize-process-metrics).
185
186
### Custom applications
@@ -207,7 +207,7 @@ custom-app: custom-app
207
```
208
209
Restart Netdata with `sudo systemctl restart netdata`, or
210
-the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to start collecting utilization metrics
210
+the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to start collecting utilization metrics
211
from your application.
212
213
## Visualize process metrics
docs/developer-and-contributor-corner/python-collector.md
+9
-9
@@ -1,8 +1,8 @@
1
# Develop a custom data collector in Python
2
3
-The Netdata Agent uses [data collectors](https://github.com/netdata/netdata/blob/master/src/collectors/README.md) to
3
+The Netdata Agent uses [data collectors](/src/collectors/README.md) to
4
fetch metrics from hundreds of system, container, and service endpoints. While the Netdata team and community has built
5
-[powerful collectors](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md) for most system, container,
5
+[powerful collectors](/src/collectors/COLLECTORS.md) for most system, container,
6
and service/application endpoints, some custom applications can't be monitored by default.
7
8
In this tutorial, you'll learn how to leverage the [Python programming language](https://www.python.org/) to build a
@@ -22,7 +22,7 @@ want to make it available for other users, you should create the pull request in
22
## What you need to get started
23
24
- A physical or virtual Linux system, which we'll call a _node_.
25
- - A working [installation of Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md) monitoring agent.
25
+ - A working [installation of Netdata](/packaging/installer/README.md) monitoring agent.
26
27
### Quick start
28
@@ -33,7 +33,7 @@ For a quick start, you can look at the
33
Netdata (as opposed to having to install Netdata from source again with your new changes) you can copy over the relevant
34
file to where Netdata expects it and then either `sudo systemctl restart netdata` to have it be picked up and used by
35
Netdata or you can just run the updated collector in debug mode by following a process like below (this assumes you have
36
-[installed Netdata from a GitHub fork](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md) you
36
+[installed Netdata from a GitHub fork](/packaging/installer/methods/manual.md) you
37
have made to do your development on).
38
39
```bash
@@ -73,7 +73,7 @@ The basic elements of a Netdata collector are:
73
- `get_data()`: The basic function of the plugin which will return to Netdata the correct values.
74
75
**Note**: All names are better explained in the
76
-[External Plugins Documentation](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md).
76
+[External Plugins Documentation](/src/collectors/plugins.d/README.md).
77
Parameters like `priority` and `update_every` mentioned in that documentation are handled by the `python.d.plugin`,
78
not by each collection module.
79
@@ -117,7 +117,7 @@ context, charttype]`, where:
117
that is `A.B`, with `A` being the name of the collector, and `B` being the name of the specific metric.
118
- `charttype`: Either `line`, `area`, or `stacked`. If null line is the default value.
119
120
-You can read more about `family` and `context` in the [web dashboard](https://github.com/netdata/netdata/blob/master/src/web/README.md#families) doc.
120
+You can read more about `family` and `context` in the [web dashboard](/src/web/README.md#families) doc.
121
122
Once the chart has been defined, you should define the dimensions of the chart. Dimensions are basically the metrics to
123
be represented in this chart and each chart can have more than one dimension. In order to define the dimensions, the
@@ -410,7 +410,7 @@ ORDER = [
410
]
411
```
412
413
-[Restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) with `sudo systemctl restart netdata` to see the new humidity
413
+[Restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) with `sudo systemctl restart netdata` to see the new humidity
414
chart:
415
416
@@ -467,7 +467,7 @@ ORDER = [
467
]
468
```
469
470
-[Restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) with `sudo systemctl restart netdata` to see the new
470
+[Restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) with `sudo systemctl restart netdata` to see the new
471
min/max/average temperature chart with multiple dimensions:
472
473
@@ -521,7 +521,7 @@ variables and inform the user about the defaults. For example, take a look at th
521
[GitHub](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/example/example.conf).
522
523
You can read more about the configuration file on the [`python.d.plugin`
524
-documentation](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md).
524
+documentation](/src/collectors/python.d.plugin/README.md).
525
526
You can find the source code for the above examples on [GitHub](https://github.com/papajohn-uop/netdata).
527
docs/developer-and-contributor-corner/raspberry-pi-anomaly-detection.md
+6
-6
@@ -6,7 +6,7 @@ We love IoT and edge at Netdata, we also love machine learning. Even better if w
6
of monitoring increasingly complex systems.
7
8
We recently explored what might be involved in enabling our Python-based [anomalies
9
-collector](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/anomalies/README.md) on a Raspberry Pi. To our delight, it's actually quite
9
+collector](/src/collectors/python.d.plugin/anomalies/README.md) on a Raspberry Pi. To our delight, it's actually quite
10
straightforward!
11
12
Read on to learn all the steps and enable unsupervised anomaly detection on your on Raspberry Pi(s).
@@ -17,14 +17,14 @@ Read on to learn all the steps and enable unsupervised anomaly detection on your
17
18
- A Raspberry Pi running Raspbian, which we'll call a _node_.
19
- The [open-source Netdata](https://github.com/netdata/netdata) monitoring agent. If you don't have it installed on your
20
- node yet, [get started now](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md).
20
+ node yet, [get started now](/packaging/installer/README.md).
21
22
## Install dependencies
23
24
First make sure Netdata is using Python 3 when it runs Python-based data collectors.
25
26
-Next, open `netdata.conf` using [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf)
27
-from within the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory). Scroll down to the
26
+Next, open `netdata.conf` using [`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf)
27
+from within the [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory). Scroll down to the
28
`[plugin:python.d]` section to pass in the `-ppython3` command option.
29
30
```conf
@@ -53,7 +53,7 @@ LLVM_CONFIG=llvm-config-9 pip3 install --user llvmlite numpy==1.20.1 netdata-pan
53
54
## Enable the anomalies collector
55
56
-Now you're ready to enable the collector and [restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
56
+Now you're ready to enable the collector and [restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
57
58
```bash
59
sudo ./edit-config python.d.conf
@@ -75,7 +75,7 @@ centralized cloud somewhere) is the resource utilization impact of running a mon
75
76
With the default configuration, the anomalies collector uses about 6.5% of CPU at each run. During the retraining step,
77
CPU utilization jumps to between 20-30% for a few seconds, but you can [configure
78
-retraining](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/anomalies/README.md#configuration) to happen less often if you wish.
78
+retraining](/src/collectors/python.d.plugin/anomalies/README.md#configuration) to happen less often if you wish.
79
80
docs/developer-and-contributor-corner/running-through-cf-tunnels.md
+2
-2
@@ -86,7 +86,7 @@ RestartSec=5s
86
WantedBy=multi-user.target
87
```
88
89
-You can edit the configuration file using the `edit-config` script from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
89
+You can edit the configuration file using the `edit-config` script from the Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
90
91
- Edit `netdata.conf` and input:
92
@@ -102,7 +102,7 @@ You can edit the configuration file using the `edit-config` script from the Netd
102
destination = tcp:127.0.0.1:19999
103
```
104
105
-[Restart the Agents](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation), and you are done!
105
+[Restart the Agents](/packaging/installer/README.md#maintaining-a-netdata-agent-installation), and you are done!
106
107
You should now be able to have a Local Dashboard that gets its metrics from Child instances, running through Cloudflare tunnels.
108
docs/developer-and-contributor-corner/style-guide.md
+7
-21
@@ -3,7 +3,7 @@
3
The _Netdata style guide_ establishes editorial guidelines for any writing produced by the Netdata team or the Netdata community, including documentation, articles, in-product UX copy, and more.
4
5
> ### Note
6
-> This document is meant to be accompanied by the [Documentation Guidelines](https://github.com/netdata/netdata/blob/master/docs/guidelines.md). If you want to contribute to Netdata's documentation, please read it too.
6
+> This document is meant to be accompanied by the [Documentation Guidelines](/docs/guidelines.md). If you want to contribute to Netdata's documentation, please read it too.
7
8
Both internal Netdata teams and external contributors to any of Netdata's open-source projects should reference and adhere to this style guide as much as possible.
9
@@ -238,8 +238,8 @@ reader.
238
239
| | |
240
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------|
241
-| Not recommended | To install Netdata, click [here](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md). |
242
-| **Recommended** | To install Netdata, read the [installation instructions](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md). |
241
+| Not recommended | To install Netdata, click [here](/packaging/installer/README.md). |
242
+| **Recommended** | To install Netdata, read the [installation instructions](/packaging/installer/README.md). |
243
244
Use links as often as required to provide necessary context. Blog posts and guides require fewer hyperlinks than
245
documentation.
@@ -293,7 +293,7 @@ Netdata Agent installation will have commands under the same paths. When applica
293
path, providing a recommendation or instructions on how to view the running configuration, which includes the correct
294
paths.
295
296
-For example, the [configuration](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) doc first
296
+For example, the [configuration](/docs/netdata-agent/configuration/README.md) doc first
297
teaches users how to find the Netdata config
298
directory and navigate to it, then runs commands from the `/etc/netdata` path so that the instructions are more
299
universal.
@@ -303,7 +303,7 @@ Don't include full paths, beginning from the system's root (`/`), as these might
303
| | |
304
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
305
| Not recommended | Use `edit-config` to edit Netdata's configuration: `sudo /etc/netdata/edit-config netdata.conf`. |
306
-| **Recommended** | Use `edit-config` to edit Netdata's configuration by first navigating to your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory), which is typically at `/etc/netdata`, then running `sudo edit-config netdata.conf`. |
306
+| **Recommended** | Use `edit-config` to edit Netdata's configuration by first navigating to your [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory), which is typically at `/etc/netdata`, then running `sudo edit-config netdata.conf`. |
307
308
### `sudo`
309
@@ -329,20 +329,6 @@ paragraphs, styled text, lists, tables, and more.
329
330
The following sections describe situations in which a specific syntax is required.
331
332
-### Syntax standards (`remark-lint`)
333
-
334
-The Netdata team uses [`remark-lint`](https://github.com/remarkjs/remark-lint) for Markdown code styling.
335
-
336
-- Use a maximum of 120 characters per line.
337
-- Begin headings with hashes, such as `# H1 heading`, `## H2 heading`, and so on.
338
-- Use `_` for italics/emphasis.
339
-- Use `**` for bold.
340
-- Use dashes `-` to begin an unordered list, and put a single space after the dash.
341
-- Tables should be padded so that pipes line up vertically with added whitespace.
342
-
343
-If you want to see all the settings, open the
344
-[`remarkrc.js`](https://github.com/netdata/netdata/blob/master/.remarkrc.js) file in the `netdata/netdata` repository.
345
-
332
### References to UI elements
333
334
When referencing a user interface (UI) element in Netdata, reference the label text of the link/button with Markdown's
@@ -464,14 +450,14 @@ The following tables describe the standard spelling, capitalization, and usage o
450
451
| Term | Definition |
452
|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
467
-| **claimed node** | A node that you've proved ownership of by completing the [connecting to Cloud process](https://github.com/netdata/netdata/blob/master/src/claim/README.md). The claimed node will then appear in your Space and any War Rooms you added it to. |
453
+| **claimed node** | A node that you've proved ownership of by completing the [connecting to Cloud process](/src/claim/README.md). The claimed node will then appear in your Space and any War Rooms you added it to. |
454
| **Netdata** | The company behind the open-source Netdata Agent and the Netdata Cloud web application. Never use _netdata_ or _NetData_. <br /><br />In general, focus on the user's goals, actions, and solutions rather than what the company provides. For example, write _Learn more about enabling alert notifications on your preferred platforms_ instead of _Netdata sends alert notifications to your preferred platforms_. |
455
| **Netdata Agent** | The free and open source [monitoring agent](https://github.com/netdata/netdata) that you can install on all of your distributed systems, whether they're physical, virtual, containerized, ephemeral, and more. The Agent monitors systems running Linux, Docker, Kubernetes, macOS, FreeBSD, and more, and collects metrics from hundreds of popular services and applications. |
456
| **Netdata Cloud** | The web application hosted at [https://app.netdata.cloud](https://app.netdata.cloud) that helps you monitor an entire infrastructure of distributed systems in real time. <br /><br />Never use _Cloud_ without the preceding _Netdata_ to avoid ambiguity. |
457
| **Netdata community forum** | The Discourse-powered forum for feature requests, Netdata Cloud technical support, and conversations about Netdata's monitoring and troubleshooting products. |
458
| **node** | A system on which the Netdata Agent is installed. The system can be physical, virtual, in a Docker container, and more. Depending on your infrastructure, you may have one, dozens, or hundreds of nodes. Some nodes are _ephemeral_, in that they're created/destroyed automatically by an orchestrator service. |
459
| **Space** | The highest level container within Netdata Cloud for a user to organize their team members and nodes within their infrastructure. A Space likely represents an entire organization or a large team. <br /><br />_Space_ is always capitalized. |
474
-| **unreachable node** | A connected node with a disrupted [Agent-Cloud link](https://github.com/netdata/netdata/blob/master/src/aclk/README.md). Unreachable could mean the node no longer exists or is experiencing network connectivity issues with Cloud. |
460
+| **unreachable node** | A connected node with a disrupted [Agent-Cloud link](/src/aclk/README.md). Unreachable could mean the node no longer exists or is experiencing network connectivity issues with Cloud. |
461
| **visited node** | A node which has had its Agent dashboard directly visited by a user. A list of these is maintained on a per-user basis. |
462
| **War Room** | A smaller grouping of nodes where users can view key metrics in real-time and monitor the health of many nodes with their alert status. War Rooms can be used to organize nodes in any way that makes sense for your infrastructure, such as by a service, purpose, physical location, and more. <br /><br />_War Room_ is always capitalized. |
463
docs/exporting-metrics/README.md
+41
-41
@@ -1,7 +1,7 @@
1
# Export metrics to external time-series databases
2
3
Netdata allows you to export metrics to external time-series databases with the [exporting
4
-engine](https://github.com/netdata/netdata/blob/master/src/exporting/README.md). This system uses a number of **connectors** to initiate connections to [more than
4
+engine](/src/exporting/README.md). This system uses a number of **connectors** to initiate connections to [more than
5
thirty](#supported-databases) supported databases, including InfluxDB, Prometheus, Graphite, ElasticSearch, and much
6
more.
7
@@ -19,48 +19,48 @@ analysis, or correlation with other tools, such as application tracing.
19
## Supported databases
20
21
Netdata supports exporting metrics to the following databases through several
22
-[connectors](https://github.com/netdata/netdata/blob/master/src/exporting/README.md#features). Once you find the connector that works for your database, open its
23
-documentation and the [enabling a connector](https://github.com/netdata/netdata/blob/master/docs/exporting-metrics/enable-an-exporting-connector.md) doc for details on enabling it.
22
+[connectors](/src/exporting/README.md#features). Once you find the connector that works for your database, open its
23
+documentation and the [enabling a connector](/docs/exporting-metrics/enable-an-exporting-connector.md) doc for details on enabling it.
24
25
-- **AppOptics**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
26
-- **AWS Kinesis**: [AWS Kinesis Data Streams](https://github.com/netdata/netdata/blob/master/src/exporting/aws_kinesis/README.md)
27
-- **Azure Data Explorer**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
28
-- **Azure Event Hubs**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
29
-- **Blueflood**: [Graphite](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md)
30
-- **Chronix**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
31
-- **Cortex**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
32
-- **CrateDB**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
33
-- **ElasticSearch**: [Graphite](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md), [Prometheus remote
34
- write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
35
-- **Gnocchi**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
36
-- **Google BigQuery**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
37
-- **Google Cloud Pub/Sub**: [Google Cloud Pub/Sub Service](https://github.com/netdata/netdata/blob/master/src/exporting/pubsub/README.md)
38
-- **Graphite**: [Graphite](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md), [Prometheus remote
39
- write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
40
-- **InfluxDB**: [Graphite](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md), [Prometheus remote
41
- write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
42
-- **IRONdb**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
43
-- **JSON**: [JSON document databases](https://github.com/netdata/netdata/blob/master/src/exporting/json/README.md)
44
-- **Kafka**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
45
-- **KairosDB**: [Graphite](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md), [OpenTSDB](https://github.com/netdata/netdata/blob/master/src/exporting/opentsdb/README.md)
46
-- **M3DB**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
47
-- **MetricFire**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
48
-- **MongoDB**: [MongoDB](https://github.com/netdata/netdata/blob/master/src/exporting/mongodb/README.md)
49
-- **New Relic**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
50
-- **OpenTSDB**: [OpenTSDB](https://github.com/netdata/netdata/blob/master/src/exporting/opentsdb/README.md), [Prometheus remote
51
- write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
52
-- **PostgreSQL**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
25
+- **AppOptics**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
26
+- **AWS Kinesis**: [AWS Kinesis Data Streams](/src/exporting/aws_kinesis/README.md)
27
+- **Azure Data Explorer**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
28
+- **Azure Event Hubs**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
29
+- **Blueflood**: [Graphite](/src/exporting/graphite/README.md)
30
+- **Chronix**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
31
+- **Cortex**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
32
+- **CrateDB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
33
+- **ElasticSearch**: [Graphite](/src/exporting/graphite/README.md), [Prometheus remote
34
+ write](/src/exporting/prometheus/remote_write/README.md)
35
+- **Gnocchi**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
36
+- **Google BigQuery**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
37
+- **Google Cloud Pub/Sub**: [Google Cloud Pub/Sub Service](/src/exporting/pubsub/README.md)
38
+- **Graphite**: [Graphite](/src/exporting/graphite/README.md), [Prometheus remote
39
+ write](/src/exporting/prometheus/remote_write/README.md)
40
+- **InfluxDB**: [Graphite](/src/exporting/graphite/README.md), [Prometheus remote
41
+ write](/src/exporting/prometheus/remote_write/README.md)
42
+- **IRONdb**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
43
+- **JSON**: [JSON document databases](/src/exporting/json/README.md)
44
+- **Kafka**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
45
+- **KairosDB**: [Graphite](/src/exporting/graphite/README.md), [OpenTSDB](/src/exporting/opentsdb/README.md)
46
+- **M3DB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
47
+- **MetricFire**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
48
+- **MongoDB**: [MongoDB](/src/exporting/mongodb/README.md)
49
+- **New Relic**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
50
+- **OpenTSDB**: [OpenTSDB](/src/exporting/opentsdb/README.md), [Prometheus remote
51
+ write](/src/exporting/prometheus/remote_write/README.md)
52
+- **PostgreSQL**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
53
via [PostgreSQL Prometheus Adapter](https://github.com/CrunchyData/postgresql-prometheus-adapter)
54
-- **Prometheus**: [Prometheus scraper](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/README.md)
55
-- **TimescaleDB**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md),
56
- [netdata-timescale-relay](https://github.com/netdata/netdata/blob/master/src/exporting/TIMESCALE.md)
57
-- **QuasarDB**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
58
-- **SignalFx**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
59
-- **Splunk**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
60
-- **TiKV**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
61
-- **Thanos**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
62
-- **VictoriaMetrics**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
63
-- **Wavefront**: [Prometheus remote write](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
54
+- **Prometheus**: [Prometheus scraper](/src/exporting/prometheus/README.md)
55
+- **TimescaleDB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md),
56
+ [netdata-timescale-relay](/src/exporting/TIMESCALE.md)
57
+- **QuasarDB**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
58
+- **SignalFx**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
59
+- **Splunk**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
60
+- **TiKV**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
61
+- **Thanos**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
62
+- **VictoriaMetrics**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
63
+- **Wavefront**: [Prometheus remote write](/src/exporting/prometheus/remote_write/README.md)
64
65
Can't find your preferred external time-series database? Ask our [community](https://community.netdata.cloud/) for
66
solutions, or file an [issue on
docs/exporting-metrics/enable-an-exporting-connector.md
+14
-14
@@ -1,20 +1,20 @@
1
# Enable an exporting connector
2
3
Now that you found the right connector for your [external time-series
4
-database](https://github.com/netdata/netdata/blob/master/docs/exporting-metrics/README.md#supported-databases), you can now enable the exporting engine and the
4
+database](/docs/exporting-metrics/README.md#supported-databases), you can now enable the exporting engine and the
5
connector itself. We'll walk through the process of enabling the exporting engine itself, followed by two examples using
6
the OpenTSDB and Graphite connectors.
7
8
> When you enable the exporting engine and a connector, the Netdata Agent exports metrics _beginning from the time you
9
> restart its process_, not the entire
10
-> [database of long-term metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
10
+> [database of long-term metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
11
12
Once you understand the process of enabling a connector, you can translate that knowledge to any other connector.
13
14
## Enable the exporting engine
15
16
Use `edit-config` from your
17
-[Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
17
+[Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
18
to open `exporting.conf`:
19
20
```bash
@@ -44,14 +44,14 @@ Replace `my_opentsdb_http_instance` with an instance name of your choice, and ch
44
address or hostname of your OpenTSDB database.
45
46
Restart your Agent with `sudo systemctl restart netdata`, or
47
-the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to begin exporting to your OpenTSDB
47
+the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to begin exporting to your OpenTSDB
48
database. The
49
Netdata Agent exports metrics _beginning from the time the process starts_, and because it exports as metrics are
50
collected, you should start seeing data in your external database after only a few seconds.
51
52
Any further configuration is optional, based on your needs and the configuration of your OpenTSDB database. See the
53
-[OpenTSDB connector doc](https://github.com/netdata/netdata/blob/master/src/exporting/opentsdb/README.md)
54
-and [exporting engine reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md#configuration) for
53
+[OpenTSDB connector doc](/src/exporting/opentsdb/README.md)
54
+and [exporting engine reference](/src/exporting/README.md#configuration) for
55
details.
56
57
## Example: Enable the Graphite connector
@@ -68,28 +68,28 @@ Replace `my_graphite_instance` with an instance name of your choice, and change
68
address or hostname of your Graphite-supported database.
69
70
Restart your Agent with `sudo systemctl restart netdata`, or
71
-the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to begin exporting to your
71
+the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system, to begin exporting to your
72
Graphite-supported database.
73
Because the Agent exports metrics as they're collected, you should start seeing data in your external database after
74
only a few seconds.
75
76
Any further configuration is optional, based on your needs and the configuration of your Graphite-supported database.
77
-See [exporting engine reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md#configuration) for
77
+See [exporting engine reference](/src/exporting/README.md#configuration) for
78
details.
79
80
## What's next?
81
82
If you want to further configure your exporting connectors, see
83
-the [exporting engine reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md#configuration).
83
+the [exporting engine reference](/src/exporting/README.md#configuration).
84
85
For a comprehensive example of using the Graphite connector, read our documentation on
86
-[exporting metrics to Graphite providers](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md). Or, start
87
-[using host labels](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md) on exported metrics.
86
+[exporting metrics to Graphite providers](/src/exporting/graphite/README.md). Or, start
87
+[using host labels](/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md) on exported metrics.
88
89
### Related reference documentation
90
91
-- [Exporting engine reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md)
92
-- [OpenTSDB connector](https://github.com/netdata/netdata/blob/master/src/exporting/opentsdb/README.md)
93
-- [Graphite connector](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md)
91
+- [Exporting engine reference](/src/exporting/README.md)
92
+- [OpenTSDB connector](/src/exporting/opentsdb/README.md)
93
+- [Graphite connector](/src/exporting/graphite/README.md)
94
95
docs/glossary.md
+47
-53
@@ -13,136 +13,130 @@ Use the alphabatized list below to find the answer to your single-term questions
13
14
## A
15
16
-- [**Agent** or **Netdata Agent**](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md): Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices.
16
+- [**Agent** or **Netdata Agent**](/packaging/installer/README.md): Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices.
17
18
-- [**Agent-cloud link** or **ACLK**](https://github.com/netdata/netdata/blob/master/src/aclk/README.md): The Agent-Cloud link (ACLK) is the mechanism responsible for securely connecting a Netdata Agent to your web browser through Netdata Cloud.
18
+- [**Agent-cloud link** or **ACLK**](/src/aclk/README.md): The Agent-Cloud link (ACLK) is the mechanism responsible for securely connecting a Netdata Agent to your web browser through Netdata Cloud.
19
20
-- [**Aggregate Function**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#aggregate-functions-over-time): A function applied When the granularity of the data collected is higher than the plotted points on the chart.
20
+- [**Aggregate Function**](/docs/dashboards-and-charts/netdata-charts.md#aggregate-functions-over-time): A function applied When the granularity of the data collected is higher than the plotted points on the chart.
21
22
-- [**Alerts** (formerly **Alarms**)](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md): With the information that appears on Netdata Cloud and the local dashboard about active alerts, you can configure alerts to match your infrastructure's needs or your team's goals.
22
+- [**Alerts** (formerly **Alarms**)](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md): With the information that appears on Netdata Cloud and the local dashboard about active alerts, you can configure alerts to match your infrastructure's needs or your team's goals.
23
24
-- [**Alarm Entity Type**](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#health-entity-reference): Entity types that are attached to specific charts and use the `alarm` label.
24
+- [**Alarm Entity Type**](/src/health/REFERENCE.md#health-entity-reference): Entity types that are attached to specific charts and use the `alarm` label.
25
26
-- [**Anomaly Advisor**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md): A Netdata feature that lets you focus on potentially anomalous metrics and charts related to a particular highlight window of interest.
26
+- [**Anomaly Advisor**](/docs/dashboards-and-charts/anomaly-advisor-tab.md): A Netdata feature that lets you focus on potentially anomalous metrics and charts related to a particular highlight window of interest.
27
28
## B
29
30
-- [**Bookmarks**](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#manage-spaces): Netdata Cloud's bookmarks put your tools in one accessible place. Bookmarks are shared between all War Rooms in a Space, so any users in your Space will be able to see and use them.
30
+- [**Bookmarks**](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#manage-spaces): Netdata Cloud's bookmarks put your tools in one accessible place. Bookmarks are shared between all War Rooms in a Space, so any users in your Space will be able to see and use them.
31
32
## C
33
34
-- [**Child**](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/README.md): A node, running Netdata, that streams metric data to one or more parent.
34
+- [**Child**](/docs/observability-centralization-points/metrics-centralization-points/README.md): A node, running Netdata, that streams metric data to one or more parent.
35
36
-- [**Cloud** or **Netdata Cloud**](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/README.md): Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alerts from all your nodes in a single web interface.
36
+- [**Cloud** or **Netdata Cloud**](/docs/netdata-cloud/README.md): Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alerts from all your nodes in a single web interface.
37
38
-- [**Collector**](https://github.com/netdata/netdata/blob/master/src/collectors/README.md#collector-architecture-and-terminology): A catch-all term for any Netdata process that gathers metrics from an endpoint.
38
+- [**Collector**](/src/collectors/README.md#collector-architecture-and-terminology): A catch-all term for any Netdata process that gathers metrics from an endpoint.
39
40
- [**Community**](https://community.netdata.cloud/): As a company with a passion and genesis in open-source, we are not just very proud of our community, but we consider our users, fans, and chatters to be an imperative part of the Netdata experience and culture.
41
42
-- [**Context**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#contexts): A way of grouping charts by the types of metrics collected and dimensions displayed. It's kind of like a machine-readable naming and organization scheme.
42
+- [**Context**](/docs/dashboards-and-charts/netdata-charts.md#contexts): A way of grouping charts by the types of metrics collected and dimensions displayed. It's kind of like a machine-readable naming and organization scheme.
43
44
-- [**Custom dashboards**](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md) A dashboard that you can create using simple HTML (no javascript is required for basic dashboards).
44
+- [**Custom dashboards**](/src/web/gui/custom/README.md) A dashboard that you can create using simple HTML (no javascript is required for basic dashboards).
45
46
## D
47
48
-- [**Dashboard**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md): Out-of-the-box visual representation of metrics to provide insight into your infrastructure, its health and performance.
48
+- [**Dashboard**](/docs/dashboards-and-charts/README.md): Out-of-the-box visual representation of metrics to provide insight into your infrastructure, its health and performance.
49
50
-- [**Definition Bar**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md): Bar within a composite chart that provides important information and options about the metrics within the chart.
50
+- [**Definition Bar**](/docs/dashboards-and-charts/netdata-charts.md): Bar within a composite chart that provides important information and options about the metrics within the chart.
51
52
-- [**Dimension**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#dimensions): A dimension is a value that gets shown on a chart.
52
+- [**Dimension**](/docs/dashboards-and-charts/netdata-charts.md#dimensions): A dimension is a value that gets shown on a chart.
53
54
## E
55
56
-- [**External Plugins**](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md): These gather metrics from external processes, such as a webserver or database, and run as independent processes that communicate with the Netdata daemon via pipes.
56
+- [**External Plugins**](/src/collectors/plugins.d/README.md): These gather metrics from external processes, such as a webserver or database, and run as independent processes that communicate with the Netdata daemon via pipes.
57
58
## F
59
60
-- [**Family**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#families): 1. What we consider our Netdata community of users and engineers. 2. A single instance of a hardware or software resource that needs to be displayed separately from similar instances.
60
+- [**Family**](/docs/dashboards-and-charts/netdata-charts.md#families): 1. What we consider our Netdata community of users and engineers. 2. A single instance of a hardware or software resource that needs to be displayed separately from similar instances.
61
62
-- [**Flood Protection**](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#flood-protection): If a node has too many state changes like firing too many alerts or going from reachable to unreachable, Netdata Cloud enables flood protection. As long as a node is in flood protection mode, Netdata Cloud does not send notifications about this node
62
+- [**Flood Protection**](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#flood-protection): If a node has too many state changes like firing too many alerts or going from reachable to unreachable, Netdata Cloud enables flood protection. As long as a node is in flood protection mode, Netdata Cloud does not send notifications about this node
63
64
-- [**Functions** or **Netdata Functions**](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md): Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.
64
+- [**Functions** or **Netdata Functions**](/docs/top-monitoring-netdata-functions.md): Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.
65
66
## G
67
68
-- [**Group by**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#group-by-dimension-node-or-chart): The drop-down on the dimension bar of a composite chart that allows you to group metrics by dimension, node, or chart.
68
+- [**Group by**](/docs/dashboards-and-charts/netdata-charts.md#group-by-dimension-node-or-chart): The drop-down on the dimension bar of a composite chart that allows you to group metrics by dimension, node, or chart.
69
70
-- [**Health Configuration Files**](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#edit-health-configuration-files): Files that you can edit to configure your Agent's health watchdog service.
70
+- [**Health Configuration Files**](/src/health/REFERENCE.md#edit-health-configuration-files): Files that you can edit to configure your Agent's health watchdog service.
71
72
-- [**Health Entity Reference**](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#health-entity-reference):
72
+- [**Health Entity Reference**](/src/health/REFERENCE.md#health-entity-reference):
73
74
-- [**Home** tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/home-tab.md): Tab in Netdata Cloud that provides a predefined dashboard of relevant information about entities in the War Room.
74
+- [**Home** tab](/docs/dashboards-and-charts/home-tab.md): Tab in Netdata Cloud that provides a predefined dashboard of relevant information about entities in the War Room.
75
76
## I
77
78
-- [**Internal plugins**](https://github.com/netdata/netdata/blob/master/src/collectors/README.md#collector-architecture-and-terminology): These gather metrics from `/proc`, `/sys`, and other Linux kernel sources. They are written in `C` and run as threads within the Netdata daemon.
78
+- [**Internal plugins**](/src/collectors/README.md#collector-architecture-and-terminology): These gather metrics from `/proc`, `/sys`, and other Linux kernel sources. They are written in `C` and run as threads within the Netdata daemon.
79
80
## K
81
82
-- [**Kickstart** or **Kickstart Script**](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md): An automatic one-line installation script named 'kickstart.sh' that works on all Linux distributions and macOS.
82
+- [**Kickstart** or **Kickstart Script**](/packaging/installer/methods/kickstart.md): An automatic one-line installation script named 'kickstart.sh' that works on all Linux distributions and macOS.
83
84
-- [**Kubernetes Dashboard** or **Kubernetes Tab**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md): Netdata Cloud features enhanced visualizations for the resource utilization of Kubernetes (k8s) clusters, embedded in the default Overview dashboard.
84
+- [**Kubernetes Dashboard** or **Kubernetes Tab**](/docs/dashboards-and-charts/kubernetes-tab.md): Netdata Cloud features enhanced visualizations for the resource utilization of Kubernetes (k8s) clusters, embedded in the default Overview dashboard.
85
86
## M
87
88
-- [**Metrics Collection**](https://github.com/netdata/netdata/blob/master/src/collectors/README.md): With zero configuration, Netdata auto-detects thousands of data sources upon starting and immediately collects per-second metrics. Netdata can immediately collect metrics from these endpoints thanks to 300+ collectors, which all come pre-installed when you install Netdata.
88
+- [**Metrics Collection**](/src/collectors/README.md): With zero configuration, Netdata auto-detects thousands of data sources upon starting and immediately collects per-second metrics. Netdata can immediately collect metrics from these endpoints thanks to 300+ collectors, which all come pre-installed when you install Netdata.
89
90
-- [**Metric Correlations**](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md): A Netdata feature that lets you quickly find metrics and charts related to a particular window of interest that you want to explore further.
90
+- [**Metric Correlations**](/docs/metric-correlations.md): A Netdata feature that lets you quickly find metrics and charts related to a particular window of interest that you want to explore further.
91
92
-- [**Metrics Exporting**](https://github.com/netdata/netdata/blob/master/docs/exporting-metrics/README.md): Netdata allows you to export metrics to external time-series databases with the exporting engine. This system uses a number of connectors to initiate connections to more than thirty supported databases, including InfluxDB, Prometheus, Graphite, ElasticSearch, and much more.
92
+- [**Metrics Exporting**](/docs/exporting-metrics/README.md): Netdata allows you to export metrics to external time-series databases with the exporting engine. This system uses a number of connectors to initiate connections to more than thirty supported databases, including InfluxDB, Prometheus, Graphite, ElasticSearch, and much more.
93
94
-- [**Metrics Storage**](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md): Upon collection the collected metrics need to be either forwarded, exported or just stored for further treatment. The Agent is capable to store metrics both short and long-term, with or without the usage of non-volatile storage.
94
+- [**Metrics Storage**](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md): Upon collection the collected metrics need to be either forwarded, exported or just stored for further treatment. The Agent is capable to store metrics both short and long-term, with or without the usage of non-volatile storage.
95
96
-- [**Metrics Streaming Replication**](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md): Each node running Netdata can stream the metrics it collects, in real time, to another node. Metric streaming allows you to replicate metrics data across multiple nodes, or centralize all your metrics data into a single time-series database (TSDB).
96
+- [**Metrics Streaming Replication**](/docs/observability-centralization-points/README.md): Each node running Netdata can stream the metrics it collects, in real time, to another node. Metric streaming allows you to replicate metrics data across multiple nodes, or centralize all your metrics data into a single time-series database (TSDB).
97
98
-- [**Module**](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md#enable-and-disable-a-specific-collection-module): A type of collector.
98
+- [**Module**](/src/collectors/REFERENCE.md#enable-and-disable-a-specific-collection-module): A type of collector.
99
100
## N
101
102
- [**Netdata**](https://www.netdata.cloud/): Netdata is a monitoring tool designed by system administrators, DevOps engineers, and developers to collect everything, help you visualize
103
metrics, troubleshoot complex performance problems, and make data interoperable with the rest of your monitoring stack.
104
105
-- [**Netdata Agent** or **Agent**](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md): Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices.
105
+- [**Netdata Agent** or **Agent**](/packaging/installer/README.md): Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices.
106
107
-- [**Netdata Cloud** or **Cloud**](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/README.md): Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alerts from all your nodes in a single web interface.
107
+- [**Netdata Cloud** or **Cloud**](/docs/netdata-cloud/README.md): Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alerts from all your nodes in a single web interface.
108
109
-- [**Netdata Functions** or **Functions**](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md): Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.
110
-
111
-<!-- No link for this keyword - **Netdata Logs** https://github.com/netdata/netdata/blob/master/docs/tasks/miscellaneous/check-netdata-logs.md: The three log files - `error.log`, `access.log` and `debug.log` - used by Netdata -->
112
-
113
-<!-- Here we need to explain Agent notifications and Cloud notifications, not just "notifications"
114
-
115
-- **Notifications** https://github.com/netdata/netdata/blob/master/docs/concepts/health-monitoring/notifications.md: Netdata can send centralized alert notifications to your team whenever a node enters a warning, critical, or unreachable state. By enabling notifications, you ensure no alert, on any node in your infrastructure, goes unnoticed by you or your team. -->
109
+- [**Netdata Functions** or **Functions**](/docs/top-monitoring-netdata-functions.md): Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.
110
111
## O
112
119
-- [**Obsoletion**(of nodes)](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#obsoleting-offline-nodes-from-a-space): Removing nodes from a space.
113
+- [**Obsoletion**(of nodes)](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#obsoleting-offline-nodes-from-a-space): Removing nodes from a space.
114
121
-- [**Orchestrators**](https://github.com/netdata/netdata/blob/master/src/collectors/README.md#collector-architecture-and-terminology): External plugins that run and manage one or more modules. They run as independent processes.
115
+- [**Orchestrators**](/src/collectors/README.md#collector-architecture-and-terminology): External plugins that run and manage one or more modules. They run as independent processes.
116
117
## P
118
125
-- [**Parent**](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/README.md): A node, running Netdata, that receives streamed metric data.
119
+- [**Parent**](/docs/observability-centralization-points/metrics-centralization-points/README.md): A node, running Netdata, that receives streamed metric data.
120
121
## R
122
129
-- [**Registry**](https://github.com/netdata/netdata/blob/master/src/registry/README.md): Registry that allows Netdata to provide unified cross-server dashboards.
123
+- [**Registry**](/src/registry/README.md): Registry that allows Netdata to provide unified cross-server dashboards.
124
131
-- [**Replication Streaming**](https://github.com/netdata/netdata/blob/master/src/streaming/README.md): Streaming configuration where child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
125
+- [**Replication Streaming**](/src/streaming/README.md): Streaming configuration where child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
126
133
-- [**Room** or **War Room**](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
127
+- [**Room** or **War Room**](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
128
129
## S
130
137
-- [**Single Node Dashboard**](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md): A dashboard pre-configured with every installation of the Netdata agent, with thousand of metrics and hundreds of interactive charts that requires no set up.
131
+- [**Single Node Dashboard**](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md): A dashboard pre-configured with every installation of the Netdata agent, with thousand of metrics and hundreds of interactive charts that requires no set up.
132
139
-- [**Space**](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces): A high-level container and virtual collaboration area where you can organize team members, access levels,and the nodes you want to monitor.
133
+- [**Space**](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces): A high-level container and virtual collaboration area where you can organize team members, access levels,and the nodes you want to monitor.
134
135
## T
136
143
-- [**Template Entity Type**](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#entity-types): Entity type that defines rules that apply to all charts of a specific context, and use the template label. Templates help you apply one entity to all disks, all network interfaces, all MySQL databases, and so on.
137
+- [**Template Entity Type**](/src/health/REFERENCE.md#entity-types): Entity type that defines rules that apply to all charts of a specific context, and use the template label. Templates help you apply one entity to all disks, all network interfaces, all MySQL databases, and so on.
138
145
-- [**Tiers**](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiers): Tiering is a mechanism of providing multiple tiers of data with different granularity of metrics (the frequency they are collected and stored, i.e. their resolution).
139
+- [**Tiers**](/src/database/engine/README.md#tiers): Tiering is a mechanism of providing multiple tiers of data with different granularity of metrics (the frequency they are collected and stored, i.e. their resolution).
140
141
## U
142
@@ -151,11 +145,11 @@ even thousands of nodes. There are no actual bottlenecks especially if you retai
145
146
## V
147
154
-- [**Visualizations**](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/visualizations-overview.md): Netdata uses dimensions, contexts, and families to sort your metric data into graphs, charts, and alerts that maximize your understand of your infrastructure and your ability to troubleshoot it, along or on a team.
148
+- [**Visualizations**](/docs/category-overview-pages/visualizations-overview.md): Netdata uses dimensions, contexts, and families to sort your metric data into graphs, charts, and alerts that maximize your understand of your infrastructure and your ability to troubleshoot it, along or on a team.
149
150
## W
151
158
-- [**War Room** or **Room**](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
152
+- [**War Room** or **Room**](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
153
154
## Z
155
docs/guidelines.md
+2
-2
@@ -35,7 +35,7 @@ Check out our [blog](https://github.com/netdata/blog#readme) repo! Any blog subm
35
36
#### Before you get started
37
38
-Anyone interested in contributing significantly to documentation should first read the [Netdata style guide](https://github.com/netdata/netdata/blob/master/docs/developer-and-contributor-corner/style-guide.md) and the [Netdata Community Code of Conduct](https://github.com/netdata/.github/blob/main/CODE_OF_CONDUCT.md).
38
+Anyone interested in contributing significantly to documentation should first read the [Netdata style guide](/docs/developer-and-contributor-corner/style-guide.md) and the [Netdata Community Code of Conduct](https://github.com/netdata/.github/blob/main/CODE_OF_CONDUCT.md).
39
40
Netdata's documentation uses Markdown syntax. If you're not familiar with Markdown, read the [Mastering Markdown](https://guides.github.com/features/mastering-markdown/) guide from GitHub for the basics on creating paragraphs, styled text, lists, tables, and more.
41
@@ -50,7 +50,7 @@ Please ensure that any links to a different documentation resource are fully exp
50
e.g.
51
52
```
53
-[Correct link to this document](https://github.com/netdata/netdata/blob/master/docs/guidelines.md)
53
+[Correct link to this document](/docs/guidelines.md)
54
vs
55
[Incorrect link to this document](https://learn.netdata.cloud/XYZ)
56
```
docs/metric-correlations.md
+2
-2
@@ -8,7 +8,7 @@ Because Metric Correlations uses every available metric from your infrastructure
8
9
## Using Metric Correlations
10
11
-When viewing the [Metrics tab or a single-node dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md), the **Metric Correlations** button appears in the top right corner of the page.
11
+When viewing the [Metrics tab or a single-node dashboard](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md), the **Metric Correlations** button appears in the top right corner of the page.
12
13
To start correlating metrics, click the **Metric Correlations** button, hold the `Alt` key (or `⌘` on macOS), and drag a selection of metrics on a single chart. The selected timeframe needs at least 15 seconds for Metric Correlation to work.
14
@@ -41,7 +41,7 @@ Behind the scenes, Netdata will aggregate the raw data as needed such that arbit
41
42
Unlike other observability agents that only collect raw metrics, Netdata also assigns an [Anomaly Bit](https://github.com/netdata/netdata/tree/master/src/ml#anomaly-bit) in real-time. This bit flags whether a metric is within normal ranges (0) or deviates significantly (1). This built-in anomaly detection allows for the analysis of both the raw data and the anomaly rates.
43
44
-**Note**: Read more [here](https://github.com/netdata/netdata/blob/master/src/ml/README.md) to learn more about the native anomaly detection features within netdata.
44
+**Note**: Read more [here](/src/ml/README.md) to learn more about the native anomaly detection features within netdata.
45
46
- `Metrics` - Run MC on the raw metric values.
47
- `Anomaly Rate` - Run MC on the corresponding anomaly rate for each metric.
docs/netdata-agent/README.md
+3
-3
@@ -65,11 +65,11 @@ stateDiagram-v2
65
66
## Comparison to other observability solutions
67
68
-1. **One moving part**: Other monitoring solution require maintaining metrics exporters, time-series databases, visualization engines. Netdata has everything integrated into one package, even when [Metrics Centralization Points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/README.md) are required, making deployment and maintenance a lot simpler.
68
+1. **One moving part**: Other monitoring solution require maintaining metrics exporters, time-series databases, visualization engines. Netdata has everything integrated into one package, even when [Metrics Centralization Points](/docs/observability-centralization-points/metrics-centralization-points/README.md) are required, making deployment and maintenance a lot simpler.
69
70
2. **Automation**: Netdata is designed to automate most of the process of setting up and running an observability solution. It is designed to instantly provide comprehensive dashboards and fully automated alerts, with zero configuration.
71
72
-3. **High Fidelity Monitoring**: Netdata was born from our need to kill the console for observability. So, it provides metrics and logs in the same granularity and fidelity console tools do, but also comes with tools that go beyond metrics and logs, to provide a holistic view of the monitored infrastructure (e.g. check [Top Monitoring](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md)).
72
+3. **High Fidelity Monitoring**: Netdata was born from our need to kill the console for observability. So, it provides metrics and logs in the same granularity and fidelity console tools do, but also comes with tools that go beyond metrics and logs, to provide a holistic view of the monitored infrastructure (e.g. check [Top Monitoring](/docs/top-monitoring-netdata-functions.md)).
73
74
4. **Minimal impact on monitored systems and applications**: Netdata has been designed to have a minimal impact on the monitored systems and their applications. There are [independent studies](https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf) reporting that Netdata excels in CPU usage, RAM utilization, Execution Time and the impact Netdata has on monitored applications and containers.
75
@@ -79,6 +79,6 @@ stateDiagram-v2
79
80
The Netdata agents (Standalone, Children and Parents) **share the dashboard** of Netdata Cloud. However, when the user is logged-in and the Netdata agent is connected to Netdata Cloud, the following are enabled (which are otherwise disabled):
81
82
-1. **Access to Sensitive Data**: Some data, like systemd-journal logs and several [Top Monitoring](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) features expose sensitive data, like IPs, ports, process command lines and more. To access all these when the dashboard is served directly from a Netdata agent, Netdata Cloud is required to verify that the user accessing the dashboard has the required permissions.
82
+1. **Access to Sensitive Data**: Some data, like systemd-journal logs and several [Top Monitoring](/docs/top-monitoring-netdata-functions.md) features expose sensitive data, like IPs, ports, process command lines and more. To access all these when the dashboard is served directly from a Netdata agent, Netdata Cloud is required to verify that the user accessing the dashboard has the required permissions.
83
84
2. **Dynamic Configuration**: Netdata agents are configured via configuration files, manually or through some provisioning system. The latest Netdata includes a feature to allow users change some of the configuration (collectors, alerts) via the dashboard. This feature is only available to users of paid Netdata Cloud plan.
docs/netdata-agent/backup-and-restore-an-agent.md
+5
-5
@@ -6,7 +6,7 @@ When preparing to backup a Netdata Agent it is worth considering that there are
6
7
| Data type | Description | Location |
8
|---------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
9
-| Agent configuration | Files controlling configuration of the Netdata Agent | [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) |
9
+| Agent configuration | Files controlling configuration of the Netdata Agent | [config directory](/docs/netdata-agent/configuration/README.md) |
10
| Metrics | Database files | /var/cache/netdata |
11
| Identity | Claim token, API key and some other files | /var/lib/netdata |
12
@@ -22,7 +22,7 @@ In this standard scenario, you are backing up your Netdata Agent in case of a no
22
> **Note**
23
> The specific paths may vary depending on installation method, Operating System, and whether it is a Docker/Kubernetes deployment.
24
25
-2. It is recommended that you [stop the Netdata Agent](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/start-stop-restart.md) when backing up the Metrics/database files.
25
+2. It is recommended that you [stop the Netdata Agent](/docs/netdata-agent/start-stop-restart.md) when backing up the Metrics/database files.
26
Backing up the Agent configuration and Identity folders is straightforward as they should not be changing very frequently.
27
28
3. Using a backup tool such as `tar` you will need to run the backup as _root_ or as the _netdata_ user to access all the files in the directories.
@@ -42,9 +42,9 @@ If you want to minimize the gap in metrics caused by stopping the Netdata Agent,
42
43
### Restoring Netdata
44
45
-1. Ensure that the Netdata agent is installed and is [stopped](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
45
+1. Ensure that the Netdata agent is installed and is [stopped](/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
46
47
- If you plan to deploy the Agent and restore a backup on top of it, then you might find it helpful to use the [`--dont-start-it`](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#other-options) option upon installation.
47
+ If you plan to deploy the Agent and restore a backup on top of it, then you might find it helpful to use the [`--dont-start-it`](/packaging/installer/methods/kickstart.md#other-options) option upon installation.
48
49
```
50
wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh && sh /tmp/netdata-kickstart.sh --dont-start-it
@@ -63,4 +63,4 @@ If you want to minimize the gap in metrics caused by stopping the Netdata Agent,
63
sudo tar -xvpzf /path/to/netdata_backup.tar.gz -C /
64
```
65
66
-3. [Start the Netdata agent](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
66
+3. [Start the Netdata agent](/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
docs/netdata-agent/configuration/README.md
+1
-1
@@ -4,7 +4,7 @@ The main Netdata agent configuration is `netdata.conf`.
4
5
## The Netdata config directory
6
7
-On most Linux systems, by using our [recommended one-line installation](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#install-on-linux-with-one-line-installer), the **Netdata config
7
+On most Linux systems, by using our [recommended one-line installation](/packaging/installer/README.md#install-on-linux-with-one-line-installer), the **Netdata config
8
directory** will be `/etc/netdata/`. The config directory contains several configuration files with the `.conf` extension, a
9
few directories, and a shell script named `edit-config`.
10
docs/netdata-agent/configuration/anonymous-telemetry-events.md
+4
-4
@@ -23,7 +23,7 @@ We use the statistics gathered from this information for two purposes:
23
24
Netdata collects usage information via two different channels:
25
26
-- **Agent dashboard**: We use the [PostHog JavaScript integration](https://posthog.com/docs/integrations/js-integration) (with sensitive event attributes overwritten to be anonymized) to send product usage events when you access an [Agent's dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md).
26
+- **Agent dashboard**: We use the [PostHog JavaScript integration](https://posthog.com/docs/integrations/js-integration) (with sensitive event attributes overwritten to be anonymized) to send product usage events when you access an [Agent's dashboard](/docs/dashboards-and-charts/README.md).
27
- **Agent backend**: The `netdata` daemon executes the [`anonymous-statistics.sh`](https://github.com/netdata/netdata/blob/6469cf92724644f5facf343e4bdd76ac0551a418/daemon/anonymous-statistics.sh.in) script when Netdata starts, stops cleanly, or fails.
28
29
You can opt-out from sending anonymous statistics to Netdata through three different [opt-out mechanisms](#opt-out).
@@ -68,7 +68,7 @@ Starting with v1.21, we additionally collect information about:
68
69
- Failures to build the dependencies required to use Cloud features.
70
- Unavailability of Cloud features in an agent.
71
-- Failures to connect to the Cloud in case the [connection process](https://github.com/netdata/netdata/blob/master/src/claim/README.md) has been completed. This includes error codes
71
+- Failures to connect to the Cloud in case the [connection process](/src/claim/README.md) has been completed. This includes error codes
72
to inform the Netdata team about the reason why the connection failed.
73
74
To see exactly what and how is collected, you can review the script template `daemon/anonymous-statistics.sh.in`. The
@@ -85,13 +85,13 @@ installation, including manual, offline, and macOS installations. Create the fil
85
.opt-out-from-anonymous-statistics` from your Netdata configuration directory.
86
87
**Pass the option `--disable-telemetry` to any of the installer scripts in the [installation
88
-docs](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md).** You can append this option during the initial installation or a manual
88
+docs](/packaging/installer/README.md).** You can append this option during the initial installation or a manual
89
update. You can also export the environment variable `DISABLE_TELEMETRY` with a non-zero or non-empty value
90
(e.g: `export DISABLE_TELEMETRY=1`).
91
92
When using Docker, **set your `DISABLE_TELEMETRY` environment variable to `1`.** You can set this variable with the following
93
command: `export DISABLE_TELEMETRY=1`. When creating a container using Netdata's [Docker
94
-image](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md#create-a-new-netdata-agent-container) for the first time, this variable will disable
94
+image](/packaging/docker/README.md#create-a-new-netdata-agent-container) for the first time, this variable will disable
95
the anonymous statistics script inside of the container.
96
97
Each of these opt-out processes does the following:
docs/netdata-agent/configuration/cheatsheet.md
+1
-1
@@ -39,7 +39,7 @@ You are expected to use this method in all following configuration changes.
39
## Metrics collection & retention
40
41
You can tweak your settings in the netdata.conf file.
42
-📄 [Find your netdata.conf file](https://github.com/netdata/netdata/blob/master/src/daemon/config/README.md)
42
+📄 [Find your netdata.conf file](/src/daemon/config/README.md)
43
44
Open a new terminal and navigate to the netdata.conf file. Use the edit-config script to make changes: `sudo ./edit-config netdata.conf`
45
docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md
+19
-19
@@ -22,8 +22,8 @@ The following table summarizes the effect of each optimization on the CPU, RAM a
22
| [Use streaming and replication](#use-streaming-and-replication) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
23
| [Disable unneeded plugins or collectors](#disable-unneeded-plugins-or-collectors) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
24
| [Reduce data collection frequency](#reduce-collection-frequency) | :heavy_check_mark: | | :heavy_check_mark: |
25
-| [Change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) | | :heavy_check_mark: | :heavy_check_mark: |
26
-| [Use a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md) | | :heavy_check_mark: | :heavy_check_mark: |
25
+| [Change how long Netdata stores metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) | | :heavy_check_mark: | :heavy_check_mark: |
26
+| [Use a different metric storage database](/src/database/README.md) | | :heavy_check_mark: | :heavy_check_mark: |
27
| [Disable machine learning](#disable-machine-learning) | :heavy_check_mark: | | |
28
| [Use a reverse proxy](#run-netdata-behind-a-proxy) | :heavy_check_mark: | | |
29
| [Disable/lower gzip compression for the agent dashboard](#disablelower-gzip-compression-for-the-dashboard) | :heavy_check_mark: | | |
@@ -50,7 +50,7 @@ including all its components, should be below 5 - 15% of a single core. For exam
50
0.6% - 1.8% of a total CPU capacity, depending on the CPU characteristics.
51
52
The Netdata Agent runs with the lowest
53
-possible [process scheduling policy](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#netdata-process-scheduling-policy),
53
+possible [process scheduling policy](/src/daemon/README.md#netdata-process-scheduling-policy),
54
which is `nice 19`, and uses the `idle` process scheduler. Together, these settings ensure that the Agent only gets CPU
55
resources when the node has CPU resources to space. If the node reaches 100% CPU utilization, the Agent is stopped first
56
to ensure your applications get any available resources.
@@ -72,8 +72,8 @@ The memory footprint of Netdata is mainly influenced by the number of metrics co
72
To estimate and control memory consumption, you can (either one or a combination of the following actions):
73
74
1. [Disable unneeded plugins or collectors](#disable-unneeded-plugins-or-collectors)
75
-2. [Change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md)
76
-3. [Use a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md).
75
+2. [Change how long Netdata stores metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md)
76
+3. [Use a different metric storage database](/src/database/README.md).
77
78
### Disk footprint and I/O
79
@@ -91,11 +91,11 @@ To optimize your disk footprint in any aspect described below you can:
91
92
To configure retention, you can:
93
94
-1. [Change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
94
+1. [Change how long Netdata stores metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
95
96
To control disk I/O:
97
98
-1. [Use a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md),
98
+1. [Use a different metric storage database](/src/database/README.md),
99
100
101
Minimize deployment impact on the production system by optimizing disk footprint:
@@ -108,7 +108,7 @@ Minimize deployment impact on the production system by optimizing disk footprint
108
109
For all production environments, parent Netdata nodes outside the production infrastructure should be receiving all
110
collected data from children Netdata nodes running on the production infrastructure,
111
-using [streaming and replication](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md).
111
+using [streaming and replication](/docs/observability-centralization-points/README.md).
112
113
### Disable health checks on the child nodes
114
@@ -125,12 +125,12 @@ in `stream.conf`). On the child nodes you should add to `netdata.conf` the follo
125
126
### Use memory mode ram for the child nodes
127
128
-See [using a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md).
128
+See [using a different metric storage database](/src/database/README.md).
129
130
## Disable unneeded plugins or collectors
131
132
If you know that you don't need an [entire plugin or a specific
133
-collector](https://github.com/netdata/netdata/blob/master/src/collectors/README.md#collector-architecture-and-terminology),
133
+collector](/src/collectors/README.md#collector-architecture-and-terminology),
134
you can disable any of them. Keep in mind that if a plugin/collector has nothing to do, it simply shuts down and does
135
not consume system resources. You will only improve the Agent's performance by disabling plugins/collectors that are
136
actively collecting metrics.
@@ -171,7 +171,7 @@ The fastest way to improve the Agent's resource utilization is to reduce how oft
171
### Global
172
173
If you don't need per-second metrics, or if the Netdata Agent uses a lot of CPU even when no one is viewing that node's
174
-dashboard, [configure the Agent](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) to collect
174
+dashboard, [configure the Agent](/docs/netdata-agent/configuration/README.md) to collect
175
metrics less often.
176
177
Open `netdata.conf` and edit the `update every` setting. The default is `1`, meaning that the Agent collects metrics
@@ -191,11 +191,11 @@ seconds, respectively.
191
Every collector and plugin has its own `update every` setting, which you can also change in the `go.d.conf`,
192
`python.d.conf`, or `charts.d.conf` files, or in individual collector configuration files. If the `update
193
every` for an individual collector is less than the global, the Netdata Agent uses the global setting. See
194
-the [collectors configuration reference](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md) for
194
+the [collectors configuration reference](/src/collectors/REFERENCE.md) for
195
details.
196
197
To reduce the frequency of
198
-an [internal_plugin/collector](https://github.com/netdata/netdata/blob/master/src/collectors/README.md#collector-architecture-and-terminology),
198
+an [internal_plugin/collector](/src/collectors/README.md#collector-architecture-and-terminology),
199
open `netdata.conf` and find the appropriate section. For example, to reduce the frequency of the `apps` plugin, which
200
collects and visualizes metrics on application resource utilization:
201
@@ -204,7 +204,7 @@ collects and visualizes metrics on application resource utilization:
204
update every = 5
205
```
206
207
-To [configure an individual collector](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md#configure-a-collector),
207
+To [configure an individual collector](/src/collectors/REFERENCE.md#configure-a-collector),
208
open its specific configuration file with `edit-config` and look for the `update_every` setting. For example, to reduce
209
the frequency of the `nginx` collector, run `sudo ./edit-config go.d/nginx.conf`:
210
@@ -216,13 +216,13 @@ update_every: 10
216
## Lower memory usage for metrics retention
217
218
See how
219
-to [change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
219
+to [change how long Netdata stores metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
220
221
## Use a different metric storage database
222
223
-Consider [using a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md)
223
+Consider [using a different metric storage database](/src/database/README.md)
224
when running Netdata on IoT devices, and for children in a parent-child set up based
225
-on [streaming and replication](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md).
225
+on [streaming and replication](/docs/observability-centralization-points/README.md).
226
227
## Disable machine learning
228
@@ -237,11 +237,11 @@ outside your production infrastructure, or if you have cpu and memory to spare.
237
## Run Netdata behind a proxy
238
239
A dedicated web server like nginx provides more robustness than the Agent's
240
-internal [web server](https://github.com/netdata/netdata/blob/master/src/web/README.md).
240
+internal [web server](/src/web/README.md).
241
Nginx can handle more concurrent connections, reuse idle connections, and use fast gzip compression to reduce payloads.
242
243
For details on installing another web server as a proxy for the local Agent dashboard,
244
-see [reverse proxies](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/README.md).
244
+see [reverse proxies](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/README.md).
245
246
## Disable/lower gzip compression for the dashboard
247
docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md
+4
-4
@@ -1,7 +1,7 @@
1
# Change how long Netdata stores metrics
2
3
The Netdata Agent uses a custom made time-series database (TSDB), named the
4
-[`dbengine`](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md), to store metrics.
4
+[`dbengine`](/src/database/engine/README.md), to store metrics.
5
6
To see the number of metrics stored and the retention in days per tier, use the `/api/v1/dbengine_stats` endpoint.
7
@@ -84,7 +84,7 @@ The DBENGINE memory is related to the number of metrics concurrently being colle
84
on disk in relation with the queries running, and the number of metrics for which retention is maintained.
85
86
The precise analysis of how much memory will be used by the DBENGINE itself is described in
87
-[DBENGINE memory requirements](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#memory-requirements).
87
+[DBENGINE memory requirements](/src/database/engine/README.md#memory-requirements).
88
89
In addition to the DBENGINE, Netdata uses memory for contexts, metric labels (e.g. in a Kubernetes setup),
90
other Netdata structures/processes (e.g. Health) and system overhead.
@@ -156,11 +156,11 @@ setups, all the way to 100% in some edge cases.
156
## Configure metric retention
157
158
Once you have decided how to size each tier, open `netdata.conf` with
159
-[`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf)
159
+[`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf)
160
and make your changes in the `[db]` subsection.
161
162
Save the file and restart the Agent with `sudo systemctl restart netdata`, or
163
-the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
163
+the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
164
for your system, to change the database engine's size.
165
166
## Scaling dedicated parent nodes
docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md
+9
-9
@@ -5,12 +5,12 @@ Netdata allows to organize your observability infrastructure with spaces, war ro
5
6
## Spaces and war rooms
7
8
-[Spaces](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces) are used for organization-level or infrastructure-level
8
+[Spaces](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces) are used for organization-level or infrastructure-level
9
grouping of nodes and people. A node can only appear in a single space, while people can have access to multiple spaces.
10
11
The [war rooms](https://github.com/netdata/netdata/edit/master/docs/cloud/war-rooms.md) in a space bring together nodes and people in
12
collaboration areas. War rooms can also be used for fine-tuned
13
-[role based access control](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md).
13
+[role based access control](/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md).
14
15
## Virtual nodes
16
@@ -85,7 +85,7 @@ sudo ./edit-config netdata.conf
85
```
86
87
Create a new `[host labels]` section defining a new host label and its value for the system in question. Make sure not
88
-to violate any of the [host label naming rules](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/common-configuration-changes.md#organize-nodes-with-host-labels).
88
+to violate any of the [host label naming rules](/docs/netdata-agent/configuration/common-configuration-changes.md#organize-nodes-with-host-labels).
89
90
```conf
91
[host labels]
@@ -139,9 +139,9 @@ child system. It's a vastly simplified way of accessing critical information abo
139
140
> ⚠️ Because automatic labels for child nodes are accessible via API calls, and contain sensitive information like
141
> kernel and operating system versions, you should secure streaming connections with SSL. See the [streaming
142
-> documentation](https://github.com/netdata/netdata/blob/master/src/streaming/README.md#securing-streaming-communications) for details. You may also want to use
143
-> [access lists](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#access-lists) or [expose the API only to LAN/localhost
144
-> connections](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/securing-netdata-agents.md#expose-netdata-only-in-a-private-lan).
142
+> documentation](/src/streaming/README.md#securing-streaming-communications) for details. You may also want to use
143
+> [access lists](/src/web/server/README.md#access-lists) or [expose the API only to LAN/localhost
144
+> connections](/docs/netdata-agent/securing-netdata-agents.md#expose-netdata-only-in-a-private-lan).
145
146
You can also use `_is_parent`, `_is_child`, and any other host labels in both health entities and metrics
147
exporting. Speaking of which...
@@ -192,11 +192,11 @@ Or when ephemeral Docker nodes are involved:
192
```
193
194
Of course, there are many more possibilities for intuitively organizing your systems with host labels. See the [health
195
-documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-host-labels) for more details, and then get creative!
195
+documentation](/src/health/REFERENCE.md#alert-line-host-labels) for more details, and then get creative!
196
197
### Host labels in metrics exporting
198
199
-If you have enabled any metrics exporting via our experimental [exporters](https://github.com/netdata/netdata/blob/master/src/exporting/README.md), any new host
199
+If you have enabled any metrics exporting via our experimental [exporters](/src/exporting/README.md), any new host
200
labels you created manually are sent to the destination database alongside metrics. You can change this behavior by
201
editing `exporting.conf`, and you can even send automatically-generated labels on with exported metrics.
202
@@ -221,7 +221,7 @@ send automatic labels = yes
221
```
222
223
By applying labels to exported metrics, you can more easily parse historical metrics with the labels applied. To learn
224
-more about exporting, read the [documentation](https://github.com/netdata/netdata/blob/master/src/exporting/README.md).
224
+more about exporting, read the [documentation](/src/exporting/README.md).
225
226
## Metric labels
227
docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/README.md
+7
-7
@@ -3,15 +3,15 @@
3
If you need to access a Netdata agent's user interface or API in a production environment we recommend you put Netdata behind
4
another web server and secure access to the dashboard via SSL, user authentication and firewall rules.
5
6
-A dedicated web server also provides more robustness and capabilities than the Agent's [internal web server](https://github.com/netdata/netdata/blob/master/src/web/README.md).
6
+A dedicated web server also provides more robustness and capabilities than the Agent's [internal web server](/src/web/README.md).
7
8
We have documented running behind
9
-[nginx](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md),
10
-[Apache](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md),
11
-[HAProxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md),
12
-[Lighttpd](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md),
13
-[Caddy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md),
14
-and [H2O](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-h2o.md).
9
+[nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md),
10
+[Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md),
11
+[HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md),
12
+[Lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md),
13
+[Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md),
14
+and [H2O](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-h2o.md).
15
If you prefer a different web server, we suggest you follow the documentation for nginx and tell us how you did it
16
by adding your own "Running behind webserverX" document.
17
docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md
+1
-1
@@ -342,7 +342,7 @@ If your apache server is not on localhost, you can set:
342
343
*note: Netdata v1.9+ support `allow connections from`*
344
345
-`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match against the connection IP address.
345
+`allow connections from` accepts [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) to match against the connection IP address.
346
347
## Prevent the double access.log
348
docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-h2o.md
+2
-2
@@ -105,7 +105,7 @@ Using the above, you access Netdata on the backend servers, like this:
105
106
### Encrypt the communication between H2O and Netdata
107
108
-In case Netdata's web server has been [configured to use TLS](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#enabling-tls-support), it is
108
+In case Netdata's web server has been [configured to use TLS](/src/web/server/README.md#enabling-tls-support), it is
109
necessary to specify inside the H2O configuration that the final destination is using TLS. To do this, change the
110
`http://` on the `proxy.reverse.url` line in your H2O configuration with `https://`
111
@@ -173,7 +173,7 @@ If your H2O server is not on localhost, you can set:
173
174
*note: Netdata v1.9+ support `allow connections from`*
175
176
-`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match against
176
+`allow connections from` accepts [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) to match against
177
the connection IP address.
178
179
## Prevent the double access.log
docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md
+2
-2
@@ -164,7 +164,7 @@ Using the above, you access Netdata on the backend servers, like this:
164
165
### Encrypt the communication between Nginx and Netdata
166
167
-In case Netdata's web server has been [configured to use TLS](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#enabling-tls-support), it is
167
+In case Netdata's web server has been [configured to use TLS](/src/web/server/README.md#enabling-tls-support), it is
168
necessary to specify inside the Nginx configuration that the final destination is using TLS. To do this, please, append
169
the following parameters in your `nginx.conf`
170
@@ -236,7 +236,7 @@ If your Nginx server is not on localhost, you can set:
236
237
*note: Netdata v1.9+ support `allow connections from`*
238
239
-`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match against the
239
+`allow connections from` accepts [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) to match against the
240
connection IP address.
241
242
## Prevent the double access.log
docs/netdata-agent/securing-netdata-agents.md
+14
-14
@@ -47,7 +47,7 @@ This is the _recommended method for those who have connected their nodes to Netd
47
metrics using the War Room Overview, Nodes tab, and Cloud dashboards.
48
49
You can disable the local dashboard (and API) but retain the encrypted Agent-Cloud link
50
-([ACLK](https://github.com/netdata/netdata/blob/master/src/aclk/README.md)) that
50
+([ACLK](/src/aclk/README.md)) that
51
allows you to stream metrics on demand from your nodes via the Netdata Cloud interface. This change mitigates all
52
concerns about revealing metrics and system design to the internet at large, while keeping all the functionality you
53
need to view metrics and troubleshoot issues with Netdata Cloud.
@@ -60,12 +60,12 @@ static-threaded` setting, and change it to `none`.
60
mode = none
61
```
62
63
-Save and close the editor, then [restart your Agent](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
63
+Save and close the editor, then [restart your Agent](/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
64
using `sudo systemctl
65
restart netdata`. If you try to visit the local dashboard to `http://NODE:19999` again, the connection will fail because
66
that node no longer serves its local dashboard.
67
68
-> See the [configuration basics doc](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) for details on how to find
68
+> See the [configuration basics doc](/docs/netdata-agent/configuration/README.md) for details on how to find
69
`netdata.conf` and use
70
> `edit-config`.
71
@@ -98,7 +98,7 @@ the internet using multiple hosting providers).
98
## Fine-grained access control
99
100
If you want to keep using the local dashboard, but don't want it exposed to the internet, you can restrict access with
101
-[access lists](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#access-lists). This method also fully
101
+[access lists](/src/web/server/README.md#access-lists). This method also fully
102
retains the ability to stream metrics
103
on-demand through Netdata Cloud.
104
@@ -107,7 +107,7 @@ static IP, only `localhost`, or connections from behind a management LAN.
107
108
By default, this setting is `localhost *`. This setting allows connections from `localhost` in addition to _all_
109
connections, using the `*` wildcard. You can change this setting using Netdata's [simple
110
-patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
110
+patterns](/src/libnetdata/simple_pattern/README.md).
111
112
```conf
113
[web]
@@ -134,9 +134,9 @@ The `allow connections from` setting is global and restricts access to the dashb
134
allow management from = localhost
135
```
136
137
-See the [web server](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#access-lists) docs for additional details
137
+See the [web server](/src/web/server/README.md#access-lists) docs for additional details
138
about access lists. You can take
139
-access lists one step further by [enabling SSL](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#enabling-tls-support) to encrypt data from local
139
+access lists one step further by [enabling SSL](/src/web/server/README.md#enabling-tls-support) to encrypt data from local
140
dashboard in transit. The connection to Netdata Cloud is always secured with TLS.
141
142
## Use an authenticating web server in proxy mode
@@ -144,12 +144,12 @@ dashboard in transit. The connection to Netdata Cloud is always secured with TLS
144
Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with
145
URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers).
146
Instructions are provided on how to set the proxy configuration to have Netdata run behind
147
-[nginx](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md),
148
-[HAproxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md),
149
-[Apache](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md),
150
-[lighthttpd](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md),
151
-[caddy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md), and
152
-[H2O](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-h2o.md).
147
+[nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md),
148
+[HAproxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md),
149
+[Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md),
150
+[lighthttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md),
151
+[caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md), and
152
+[H2O](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-h2o.md).
153
154
## Use Netdata parents as Web Application Firewalls
155
@@ -159,7 +159,7 @@ your production systems from the rest of the world. Netdata
159
Parents receive metric data from Netdata Agents or other Netdata Parents on one side, and serve most queries using their own
160
copy of the data to satisfy dashboard requests on the other side.
161
162
-For more information see [Streaming and replication](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md).
162
+For more information see [Streaming and replication](/docs/observability-centralization-points/README.md).
163
164
## Other methods
165
docs/netdata-agent/sizing-netdata-agents/README.md
+1
-1
@@ -40,7 +40,7 @@ The following guides provide instructions on how to do this.
40
41
Netdata Parents automatically size resource utilization based on the workload they receive. The only possible option for improving query performance is to dedicate more RAM to them, by increasing their caches efficiency.
42
43
-Check [RAM Requirements](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/sizing-netdata-agents/ram-requirements.md) for more information.
43
+Check [RAM Requirements](/docs/netdata-agent/sizing-netdata-agents/ram-requirements.md) for more information.
44
45
## Innovations Netdata has for optimal performance and scalability
46
docs/netdata-agent/sizing-netdata-agents/ram-requirements.md
+1
-1
@@ -8,7 +8,7 @@ Netdata supports memory ballooning and automatically sizes and limits the memory
8
9
With default settings, Netdata should run with 100MB to 200MB of RAM, depending on the number of metrics being collected.
10
11
-This number can be lowered by limiting the number of database tier or switching database modes. For more information check [Disk Requirements and Retention](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/sizing-netdata-agents/disk-requirements-and-retention.md).
11
+This number can be lowered by limiting the number of database tier or switching database modes. For more information check [Disk Requirements and Retention](/docs/netdata-agent/sizing-netdata-agents/disk-requirements-and-retention.md).
12
13
## On Metrics Centralization Points, Netdata Parents
14
docs/netdata-agent/start-stop-restart.md
+2
-2
@@ -1,6 +1,6 @@
1
# Start, stop, or restart the Netdata Agent
2
3
-When you install the Netdata Agent, the [daemon](https://github.com/netdata/netdata/blob/master/src/daemon/README.md) is
3
+When you install the Netdata Agent, the [daemon](/src/daemon/README.md) is
4
configured to start at boot and stop and restart/shutdown.
5
6
You will most often need to _restart_ the Agent to load new or editing configuration files.
@@ -34,7 +34,7 @@ If you start the daemon this way, close it with `sudo killall netdata`.
34
35
## Using `netdatacli`
36
37
-The Netdata Agent also comes with a [CLI tool](https://github.com/netdata/netdata/blob/master/src/cli/README.md) capable of performing shutdowns. Start the Agent back up
37
+The Netdata Agent also comes with a [CLI tool](/src/cli/README.md) capable of performing shutdowns. Start the Agent back up
38
using your preferred method listed above.
39
40
```bash
docs/netdata-agent/versions-and-platforms.md
+1
-1
@@ -67,4 +67,4 @@ Static builds usually miss certain features that require operating-system suppor
67
- systemd-journal features
68
- eBPF related features
69
70
-When platforms are removed from the [Binary Distribution Packages](https://github.com/netdata/netdata/blob/master/packaging/makeself/README.md) list, they default to install or update Netdata to a static build. This may mean that after platforms become EOL, Netdata on them may lose some of its features. We recommend upgrading the operating system before it becomes EOL, to continue using all the features of Netdata.
70
+When platforms are removed from the [Binary Distribution Packages](/packaging/makeself/README.md) list, they default to install or update Netdata to a static build. This may mean that after platforms become EOL, Netdata on them may lose some of its features. We recommend upgrading the operating system before it becomes EOL, to continue using all the features of Netdata.
docs/netdata-cloud/README.md
+3
-3
@@ -113,9 +113,9 @@ However, when there are multiple Netdata agents involved, the queries will be fa
113
114
No. Any or all Netdata agents can be connected to Netdata Cloud.
115
116
-We recommend to create [observability centralization points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md), as required for operational efficiency (ephemeral nodes, teams or services isolation, central control of alerts, production systems performance), security policies (internet isolation), or cost optimization (use existing capacities before allocating new ones).
116
+We recommend to create [observability centralization points](/docs/observability-centralization-points/README.md), as required for operational efficiency (ephemeral nodes, teams or services isolation, central control of alerts, production systems performance), security policies (internet isolation), or cost optimization (use existing capacities before allocating new ones).
117
118
-We suggest to review the [Best Practices for Observability Centralization Points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/best-practices.md).
118
+We suggest to review the [Best Practices for Observability Centralization Points](/docs/observability-centralization-points/best-practices.md).
119
120
## When I have Netdata Parents, do I need to connect Netdata Children to Netdata Cloud too?
121
@@ -129,6 +129,6 @@ Netdata Cloud prefers:
129
130
- The most distant (from the Child) Parent available, when doing metrics visualization queries (since usually these Parents have been added for this purpose).
131
132
-- The closest (to the Child) Parent available, for [Top Monitoring](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) (since top-monitoring provides live data, like the processes running, the list of sockets open, etc). The streaming protocol of Netdata Parents and Children is able to forward such requests to the right child, via the Parents, to respond with live and accurate data.
132
+- The closest (to the Child) Parent available, for [Top Monitoring](/docs/top-monitoring-netdata-functions.md) (since top-monitoring provides live data, like the processes running, the list of sockets open, etc). The streaming protocol of Netdata Parents and Children is able to forward such requests to the right child, via the Parents, to respond with live and accurate data.
133
134
Netdata Children may be connected to Netdata Cloud for high-availability, in case the Netdata Parents are unreachable.
docs/netdata-cloud/authentication-and-authorization/README.md
+2
-2
@@ -20,8 +20,8 @@ To sign in/sign up using Google or GitHub OAuth, visit [Netdata Cloud](https://a
20
21
Netdata integrates with SSO tools, allowing you to control how your team connects and authenticates to Netdata Cloud.
22
23
-For more information, see [Enterprise SSO Authentication](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md).
23
+For more information, see [Enterprise SSO Authentication](/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md).
24
25
## Authorization
26
27
-Once logged in, you can manage role-based access in your space to give each team member the appropriate role. For more information, see [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md).
27
+Once logged in, you can manage role-based access in your space to give each team member the appropriate role. For more information, see [Role-Based Access model](/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md).
docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md
+3
-3
@@ -79,9 +79,9 @@ In more detail, you can find on the following tables which functionalities are a
79
| See all configured notifications on a Space | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
80
| Add new configuration | :heavy_check_mark: | - | - | - | - | - | |
81
| Enable/Disable configuration | :heavy_check_mark: | - | - | - | - | - | |
82
-| Edit configuration | :heavy_check_mark: | - | - | - | - | - | Some exceptions apply depending on [service level](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#available-actions-per-notification-methods-based-on-service-level) |
82
+| Edit configuration | :heavy_check_mark: | - | - | - | - | - | Some exceptions apply depending on [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#available-actions-per-notification-methods-based-on-service-level) |
83
| Delete configuration | :heavy_check_mark: | - | - | - | - | - | |
84
-| Edit personal level notification settings | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | [Manage user notification settings](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-user-notification-settings) |
84
+| Edit personal level notification settings | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | [Manage user notification settings](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-user-notification-settings) |
85
| See space alert notification silencing rules | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | - | |
86
| Add new space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
87
| Enable/Disable space alert notification silencing rule | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
@@ -91,7 +91,7 @@ In more detail, you can find on the following tables which functionalities are a
91
92
> **Note**
93
>
94
-> Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-classification))
94
+> Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-classification))
95
96
### Dashboards
97
docs/netdata-cloud/monitor-your-infrastructure.md
+54
-54
@@ -41,11 +41,11 @@ SRE team for the user-facing SaaS application, and a second IT team for managing
41
don't monitor the same nodes, they can work in separate Spaces and then further organize their nodes into War Rooms.
42
43
Next, set up War Rooms. Netdata Cloud creates dashboards and visualizations based on the nodes added to a given War
44
-Room. You can [organize War Rooms](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#war-room-organization) in any way
44
+Room. You can [organize War Rooms](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#war-room-organization) in any way
45
you want, such as by the application type, for end-to-end application monitoring, or as an incident response tool.
46
47
-Learn more about [Spaces](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces) and [War
48
-Rooms](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms), including how to manage each, in their respective reference
47
+Learn more about [Spaces](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces) and [War
48
+Rooms](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms), including how to manage each, in their respective reference
49
documentation.
50
51
### Invite your team
@@ -55,7 +55,7 @@ inviting others, you can better synchronize with your team or colleagues to unde
55
When something goes wrong, you'll be ready to collaboratively troubleshoot complex performance problems from a single
56
pane of glass.
57
58
-To [invite new users](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team), click on **Invite Users** in the
58
+To [invite new users](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team), click on **Invite Users** in the
59
Space management Area. Choose which War Rooms to add this user to, then click **Send**.
60
61
### See an overview of your infrastructure
@@ -65,28 +65,28 @@ These tabs can be separated into "static", meaning they are by default presented
65
66
#### Static tabs
67
68
-- The default tab for any War Room is the [Home tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/home-tab.md), which gives you an overview of this Space.
68
+- The default tab for any War Room is the [Home tab](/docs/dashboards-and-charts/home-tab.md), which gives you an overview of this Space.
69
Here you can see the number of Nodes claimed, data retention statics, users by role, alerts and more.
70
71
-- The [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md) gives you the ability to see the status (offline or online), host details, alert status and also a short overview of some key metrics from all your nodes at a glance.
71
+- The [Nodes tab](/docs/dashboards-and-charts/nodes-tab.md) gives you the ability to see the status (offline or online), host details, alert status and also a short overview of some key metrics from all your nodes at a glance.
72
73
-- The third and most important tab is the [Metrics tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) which uses composite charts to display real-time metrics from every available node in a given War Room.
73
+- The third and most important tab is the [Metrics tab](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md) which uses composite charts to display real-time metrics from every available node in a given War Room.
74
75
-- [Kubernetes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md) is a logical grouping of charts regarding your Kubernetes clusters. It contains a subset of the charts available in the **Overview tab**.
75
+- [Kubernetes tab](/docs/dashboards-and-charts/kubernetes-tab.md) is a logical grouping of charts regarding your Kubernetes clusters. It contains a subset of the charts available in the **Overview tab**.
76
77
-- The [Dashboards tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md) gives you the ability to have tailored made views of specific/targeted interfaces for your infrastructure using any number of charts from any number of nodes.
77
+- The [Dashboards tab](/docs/dashboards-and-charts/dashboards-tab.md) gives you the ability to have tailored made views of specific/targeted interfaces for your infrastructure using any number of charts from any number of nodes.
78
79
-- The [Alerts tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/alerts-tab.md) provides you with an overview for all the active alerts you receive for the nodes in this War Room, you can also see all the alerts that are configured to be triggered in any given moment.
79
+- The [Alerts tab](/docs/dashboards-and-charts/alerts-tab.md) provides you with an overview for all the active alerts you receive for the nodes in this War Room, you can also see all the alerts that are configured to be triggered in any given moment.
80
81
-- The [Anomalies tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md) is dedicated to the Anomaly Advisor tool.
81
+- The [Anomalies tab](/docs/dashboards-and-charts/anomaly-advisor-tab.md) is dedicated to the Anomaly Advisor tool.
82
83
-- The [Functions tab](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) gives you the ability to visualize functions that the Netdata Agent collectors are able to expose.
83
+- The [Functions tab](/docs/top-monitoring-netdata-functions.md) gives you the ability to visualize functions that the Netdata Agent collectors are able to expose.
84
85
-- The [Feed & events](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/events-feed.md) tab lets you investigate events that occurred in the past, which is invaluable for troubleshooting.
85
+- The [Feed & events](/docs/dashboards-and-charts/events-feed.md) tab lets you investigate events that occurred in the past, which is invaluable for troubleshooting.
86
87
#### Dynamic tabs
88
89
-If you open a [new dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md), jump to a single-node dashboard, or navigate to a dedicated alert page, a new tab will open in War Room bar.
89
+If you open a [new dashboard](/docs/dashboards-and-charts/dashboards-tab.md), jump to a single-node dashboard, or navigate to a dedicated alert page, a new tab will open in War Room bar.
90
91
Tabs can be rearranged with drag-and-drop or closed with the **X** button. Open tabs persist between sessions, so you can always come right back to your preferred setup.
92
@@ -97,7 +97,7 @@ single-node dashboards in Netdata Cloud to drill down on specific issues, scrub
97
historical data, and see like metrics presented meaningfully to help you troubleshoot performance problems.
98
99
Learn more about [interacting with
100
-dashboards and charts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md) to get the most from all of Netdata's real-time
100
+dashboards and charts](/docs/dashboards-and-charts/netdata-charts.md) to get the most from all of Netdata's real-time
101
metrics.
102
103
### Create new dashboards
@@ -109,7 +109,7 @@ from every node in your infrastructure on a single dashboard.
109
111
112
-Read more about [creating new dashboards](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md) for more details about the process and
112
+Read more about [creating new dashboards](/docs/dashboards-and-charts/dashboards-tab.md) for more details about the process and
113
additional tips on best leveraging the feature to help you troubleshoot complex performance problems.
114
115
## Set up your nodes
@@ -136,23 +136,23 @@ cd /etc/netdata
136
sudo ./edit-config netdata.conf
137
```
138
139
-Our [configuration basics doc](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) contains more information about `netdata.conf`, `edit-config`,
139
+Our [configuration basics doc](/docs/netdata-agent/configuration/README.md) contains more information about `netdata.conf`, `edit-config`,
140
along with simple examples to get you familiar with editing your node's configuration.
141
142
-After you've learned the basics, you should [secure your infrastructure's nodes](https://github.com/netdata/netdata/blob/master/docs/security-and-privacy-design/README.md) using
142
+After you've learned the basics, you should [secure your infrastructure's nodes](/docs/security-and-privacy-design/README.md) using
143
one of our recommended methods. These security best practices ensure no untrusted parties gain access to the metrics
144
collected on any of your nodes.
145
146
### Collect metrics from systems and applications
147
148
-Netdata has [300+ pre-installed collectors](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md) that gather thousands of metrics with zero
148
+Netdata has [300+ pre-installed collectors](/src/collectors/COLLECTORS.md) that gather thousands of metrics with zero
149
configuration. Collectors search each of your nodes in default locations and ports to find running applications and
150
gather as many metrics as they can without you having to configure them individually.
151
152
-Most collectors work without configuration, should you want more info, you can read more on [how Netdata's metrics collectors work](https://github.com/netdata/netdata/blob/master/src/collectors/README.md) and the [Collectors configuration reference](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md) documentation.
152
+Most collectors work without configuration, should you want more info, you can read more on [how Netdata's metrics collectors work](/src/collectors/README.md) and the [Collectors configuration reference](/src/collectors/REFERENCE.md) documentation.
153
154
-In addition, find detailed information about which [system](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/system-metrics.md),
155
-[container](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/container-metrics.md), and [application](https://github.com/netdata/netdata/blob/master/docs/collecting-metrics/application-metrics.md) metrics you can
154
+In addition, find detailed information about which [system](/docs/collecting-metrics/system-metrics.md),
155
+[container](/docs/collecting-metrics/container-metrics.md), and [application](/docs/collecting-metrics/application-metrics.md) metrics you can
156
collect from across your infrastructure with Netdata.
157
158
## Netdata Cloud features
@@ -161,62 +161,62 @@ collect from across your infrastructure with Netdata.
161
<Box
162
title="Spaces and War Rooms">
163
<BoxList>
164
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces)" title="Spaces" />
165
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms)" title="War Rooms" />
164
+ <BoxListItemRegexLink to="[](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces)" title="Spaces" />
165
+ <BoxListItemRegexLink to="[](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms)" title="War Rooms" />
166
</BoxList>
167
</Box>
168
<Box
169
title="Dashboards">
170
<BoxList>
171
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md)" title="Metrics tab" />
172
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md)" title="Nodes tab" />
173
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md)" title="Kubernetes" />
174
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md)" title="Create new dashboards" />
171
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md)" title="Metrics tab" />
172
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/nodes-tab.md)" title="Nodes tab" />
173
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/kubernetes-tab.md)" title="Kubernetes" />
174
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/dashboards-tab.md)" title="Create new dashboards" />
175
</BoxList>
176
</Box>
177
<Box
178
title="Alerts and notifications">
179
<BoxList>
180
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/alerts-tab.md#netdata-cloud)" title="View active alerts" />
181
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md)" title="Alert notifications" />
180
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/alerts-tab.md#netdata-cloud)" title="View active alerts" />
181
+ <BoxListItemRegexLink to="[](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md)" title="Alert notifications" />
182
</BoxList>
183
</Box>
184
<Box
185
title="Troubleshooting with Netdata Cloud">
186
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md)" title="Metric Correlations" />
187
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md)" title="Anomaly Advisor" />
188
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/events-feed.md)" title="Events Feed" />
186
+ <BoxListItemRegexLink to="[](/docs/metric-correlations.md)" title="Metric Correlations" />
187
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/anomaly-advisor-tab.md)" title="Anomaly Advisor" />
188
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/events-feed.md)" title="Events Feed" />
189
</Box>
190
<Box
191
title="Management and settings">
192
<BoxList>
193
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/README.md)" title="Sign in with email, Google, GitHub or with an SSO tool" />
194
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team)" title="Invite your team" />
195
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/themes.md)" title="Choose your Netdata Cloud theme" />
196
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md)" title="Role-Based Access" />
197
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-subscription-plans.md)" title="Paid Plans" />
193
+ <BoxListItemRegexLink to="[](/docs/netdata-cloud/authentication-and-authorization/README.md)" title="Sign in with email, Google, GitHub or with an SSO tool" />
194
+ <BoxListItemRegexLink to="[](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team)" title="Invite your team" />
195
+ <BoxListItemRegexLink to="[](/docs/dashboards-and-charts/themes.md)" title="Choose your Netdata Cloud theme" />
196
+ <BoxListItemRegexLink to="[](/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md)" title="Role-Based Access" />
197
+ <BoxListItemRegexLink to="[](/docs/netdata-cloud/netdata-subscription-plans.md)" title="Paid Plans" />
198
</BoxList>
199
</Box>
200
</Grid>
201
202
- Spaces and War Rooms
203
- - [Spaces](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces)
204
- - [War Rooms](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms)
203
+ - [Spaces](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces)
204
+ - [War Rooms](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-war-rooms)
205
- Dashboards
206
- - [Metrics tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md)
207
- - [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md)
208
- - [Kubernetes](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md)
209
- - [Create new dashboards](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md)
206
+ - [Metrics tab](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md)
207
+ - [Nodes tab](/docs/dashboards-and-charts/nodes-tab.md)
208
+ - [Kubernetes](/docs/dashboards-and-charts/kubernetes-tab.md)
209
+ - [Create new dashboards](/docs/dashboards-and-charts/dashboards-tab.md)
210
- Alerts and notifications
211
- - [View active alerts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/alerts-tab.md#netdata-cloud)
212
- - [Alert notifications](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md)
211
+ - [View active alerts](/docs/dashboards-and-charts/alerts-tab.md#netdata-cloud)
212
+ - [Alert notifications](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md)
213
- Troubleshooting with Netdata Cloud
214
- - [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md)
215
- - [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md)
216
- - [Events Feed](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/events-feed.md)
214
+ - [Metric Correlations](/docs/metric-correlations.md)
215
+ - [Anomaly Advisor](/docs/dashboards-and-charts/anomaly-advisor-tab.md)
216
+ - [Events Feed](/docs/dashboards-and-charts/events-feed.md)
217
- Management and settings
218
- - [Sign in with email, Google, GitHub or with an SSO tool](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/README.md)
219
- - [Invite your team](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team)
220
- - [Choose your Netdata Cloud theme](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/themes.md)
221
- - [Role-Based Access](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md)
222
- - [Paid Plans](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-subscription-plans.md)
218
+ - [Sign in with email, Google, GitHub or with an SSO tool](/docs/netdata-cloud/authentication-and-authorization/README.md)
219
+ - [Invite your team](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#invite-your-team)
220
+ - [Choose your Netdata Cloud theme](/docs/dashboards-and-charts/themes.md)
221
+ - [Role-Based Access](/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md)
222
+ - [Paid Plans](/docs/netdata-cloud/netdata-subscription-plans.md)
docs/netdata-cloud/netdata-cloud-on-prem/installation.md
+1
-1
@@ -1,6 +1,6 @@
1
# Netdata Cloud On-Prem Installation
2
3
-This installation guide assumes the prerequisites for installing Netdata Cloud On-Prem as satisfied. For more information please refer to the [requirements documentation](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-cloud-on-prem/README.md#requirements).
3
+This installation guide assumes the prerequisites for installing Netdata Cloud On-Prem as satisfied. For more information please refer to the [requirements documentation](/docs/netdata-cloud/netdata-cloud-on-prem/README.md#requirements).
4
5
## Installation Requirements
6
docs/netdata-cloud/netdata-subscription-plans.md
+1
-1
@@ -29,7 +29,7 @@ Yearly plans require specifying a number of committed nodes, which receive a dis
29
30
## Plan Changes and Credit Balance
31
32
-You can change your plan, billing frequency, or committed nodes at any time. For guidance, see [updating your plan](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/view-plan-and-billing.md#update-a-subscription-plan).
32
+You can change your plan, billing frequency, or committed nodes at any time. For guidance, see [updating your plan](/docs/netdata-cloud/view-plan-and-billing.md#update-a-subscription-plan).
33
34
> **Note**
35
>
docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md
+4
-4
@@ -56,7 +56,7 @@ will open a side tab in which you can:
56
2. _Edit the War Rooms*_, click on the **War rooms** tab to add or remove War Rooms.
57
58
3. _Connect nodes*_, click on **Nodes** tab. Copy the claiming script to your node and run it. See the
59
- [connect to Cloud doc](https://github.com/netdata/netdata/blob/master/src/claim/README.md) for details.
59
+ [connect to Cloud doc](/src/claim/README.md) for details.
60
61
4. _Manage the users*_, click on **Users**.
62
The [invitation doc](#invite-your-team)
@@ -106,7 +106,7 @@ We recommend a few strategies for organizing your War Rooms.
106
107
- **Incident response**
108
You can also create new War Rooms as one of the first steps in your incident response process.
109
- For example, you have a user-facing web app that relies on Apache Pulsar for a message queue, and one of your nodes using the [Pulsar collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/pulsar/README.md) begins reporting a suspiciously low messages rate.
109
+ For example, you have a user-facing web app that relies on Apache Pulsar for a message queue, and one of your nodes using the [Pulsar collector](/src/go/collectors/go.d.plugin/modules/pulsar/README.md) begins reporting a suspiciously low messages rate.
110
You can create a War Room called `$year-$month-$day-pulsar-rate`, add all your Pulsar nodes in addition to nodes they connect to, and begin diagnosing the root cause in a War Room optimized for getting to resolution as fast as possible.
111
112
### Add War Rooms
@@ -158,10 +158,10 @@ You will be prompted to enter the email addresses of the users you want to invit
158
Next, choose the War Rooms you want to invite these users to. Once logged in, these users are not restricted only to
159
these War Rooms. They can be invited to others, or join any that are public.
160
161
-Next, pick a role for the invited user. You can read more about [which roles are available](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md#what-roles-are-available) based on your [subscription plan](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-subscription-plans.md).
161
+Next, pick a role for the invited user. You can read more about [which roles are available](/docs/netdata-cloud/authentication-and-authorization/role-based-access-model.md#what-roles-are-available) based on your [subscription plan](/docs/netdata-cloud/netdata-subscription-plans.md).
162
163
Click the **Send** button to send an email invitation, which will prompt them
164
-to [sign up](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/README.md) and join your Space.
164
+to [sign up](/docs/netdata-cloud/authentication-and-authorization/README.md) and join your Space.
165
166
167
docs/netdata-cloud/versions.md
+1
-1
@@ -16,4 +16,4 @@ For more information check our [Pricing](https://www.netdata.cloud/pricing/) pag
16
17
## On-Prem Version
18
19
-To deploy Netdata Cloud On-premises, take a look at the [related section](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-cloud-on-prem/README.md) on our Documentation.
19
+To deploy Netdata Cloud On-premises, take a look at the [related section](/docs/netdata-cloud/netdata-cloud-on-prem/README.md) on our Documentation.
docs/netdata-cloud/view-plan-and-billing.md
+2
-2
@@ -14,7 +14,7 @@ This section outlines how to view and manage your Space's plan, billing settings
14
1. Navigate to **Space settings** (the cog above your profile icon).
15
2. Select the **Plan & Billing** tab.
16
3. You'll see:
17
- - **Credit** amount, if applicable, usable for future invoices or subscription changes. More on this at [Plan changes and credit balance](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-subscription-plans.md#plan-changes-and-credit-balance).
17
+ - **Credit** amount, if applicable, usable for future invoices or subscription changes. More on this at [Plan changes and credit balance](/docs/netdata-cloud/netdata-subscription-plans.md#plan-changes-and-credit-balance).
18
- **Billing email** linked to your subscription, where all related notifications are sent.
19
- A link to the **Billing options and Invoices** in our billing provider's Customer Portal, where you can:
20
- Manage subscriptions and payment methods.
@@ -33,7 +33,7 @@ This section outlines how to view and manage your Space's plan, billing settings
33
> **Note**
34
>
35
> - Checkout is performed directly if there's an active plan.
36
-> - Plan changes, including downgrades or cancellations, may impact notification settings or user access. More details at [Plan changes and credit balance](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/netdata-subscription-plans.md#plan-changes-and-credit-balance).
36
+> - Plan changes, including downgrades or cancellations, may impact notification settings or user access. More details at [Plan changes and credit balance](/docs/netdata-cloud/netdata-subscription-plans.md#plan-changes-and-credit-balance).
37
38
## FAQ
39
docs/observability-centralization-points/metrics-centralization-points/README.md
+1
-1
@@ -45,4 +45,4 @@ A Cluster is configured as a number of circular **Proxies**, ie. each of the nod
45
46
## Best Practices
47
48
-Refer to [Best Practices for Observability Centralization Points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/best-practices.md).
48
+Refer to [Best Practices for Observability Centralization Points](/docs/observability-centralization-points/best-practices.md).
docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md
+1
-1
@@ -28,7 +28,7 @@ Netdata Children need to maintain a retention only for the time required to swit
28
29
## Restoring a Netdata Parent after maintenance
30
31
-Given the [replication limitations](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/replication-of-past-samples.md#replication-limitations), special care is needed when restoring a Netdata Parent after some long maintenance work on it.
31
+Given the [replication limitations](/docs/observability-centralization-points/metrics-centralization-points/replication-of-past-samples.md#replication-limitations), special care is needed when restoring a Netdata Parent after some long maintenance work on it.
32
33
If the Netdata Children do not have enough retention to replicate the missing data on this Netdata Parent, it is preferable to block access to this Netdata Parent from the Netdata Children, until it replicates the missing data from the other Netdata Parents.
34
docs/observability-centralization-points/metrics-centralization-points/configuration.md
+2
-2
@@ -61,11 +61,11 @@ While encrypting the connection between your parent and child nodes is recommend
61
This example uses self-signed certificates.
62
63
> **Note**
64
-> This section assumes you have read the documentation on [how to edit the Netdata configuration files](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md).
64
+> This section assumes you have read the documentation on [how to edit the Netdata configuration files](/docs/netdata-agent/configuration/README.md).
65
<!-- here we need link to the section that will contain the restarting instructions -->
66
67
1. **Parent node**
68
- To generate an SSL key and certificate using `openssl`, take a look at the related section around [Securing Netdata Agents](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#enable-httpstls-support) in our Documentation.
68
+ To generate an SSL key and certificate using `openssl`, take a look at the related section around [Securing Netdata Agents](/src/web/server/README.md#enable-httpstls-support) in our Documentation.
69
70
2. **Child node**
71
Update `stream.conf` to enable SSL/TLS and allow self-signed certificates. Append ':SSL' to the destination and uncomment 'ssl skip certificate verification'.
docs/observability-centralization-points/metrics-centralization-points/faq.md
+2
-2
@@ -4,7 +4,7 @@
4
5
Netdata Parents generally scale well. According [to our tests](https://blog.netdata.cloud/netdata-vs-prometheus-performance-analysis/) Netdata Parents scale better than Prometheus for the same workload: -35% CPU utilization, -49% Memory Consumption, -12% Network Bandwidth, -98% Disk I/O, -75% Disk footprint.
6
7
-For more information, Check [Sizing Netdata Parents](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md).
7
+For more information, Check [Sizing Netdata Parents](/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md).
8
9
## If I set up a parents cluster, will I be able to have more Child nodes stream to them?
10
@@ -43,7 +43,7 @@ Yes. Function requests will be received by the Parents and forwarded to the Chil
43
44
## If I have a cluster of parents and get one out for maintenance for a few hours, will it have missing data when it returns back online?
45
46
-Check [Restoring a Netdata Parent after maintenance](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md).
46
+Check [Restoring a Netdata Parent after maintenance](/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md).
47
48
## I have a cluster of parents. Which one is used by Netdata Cloud?
49
docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md
+1
-1
@@ -1,3 +1,3 @@
1
# Sizing Netdata Parents
2
3
-To estimate CPU, RAM, and disk requirements for your Netdata Parents, check [sizing Netdata agents](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/sizing-netdata-agents/README.md).
3
+To estimate CPU, RAM, and disk requirements for your Netdata Parents, check [sizing Netdata agents](/docs/netdata-agent/sizing-netdata-agents/README.md).
docs/top-monitoring-netdata-functions.md
+3
-3
@@ -7,7 +7,7 @@ executed on the node/host where the function is made available.
7
8
Collectors besides the metric collection, storing, and/or streaming work are capable of executing specific routines on request. These routines will bring additional information to help you troubleshoot or even trigger some action to happen on the node itself.
9
10
-For more details please check out documentation on how we use our internal collector to get this from the first collector that exposes functions - [plugins.d](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#function).
10
+For more details please check out documentation on how we use our internal collector to get this from the first collector that exposes functions - [plugins.d](/src/collectors/plugins.d/README.md#function).
11
12
## Prerequisites
13
@@ -25,7 +25,7 @@ The following is required to be able to run Functions from Netdata Cloud.
25
| Ipmi-sensors | Readings and status of IPMI sensors. | `ipmi-sensors` | no | [freeipmi](https://github.com/netdata/netdata/tree/master/src/collectors/freeipmi.plugin#readme) |
26
| Mount-points | Disk usage for each mount point, including used and available space, both in terms of percentage and actual bytes, as well as used and available inode counts. | `df` | no | [diskspace](https://github.com/netdata/netdata/tree/master/src/collectors/diskspace.plugin#readme) |
27
| Network-interfaces | Network traffic, packet drop rates, interface states, MTU, speed, and duplex mode for all network interfaces. | `bmon`, `bwm-ng` | no | [proc](https://github.com/netdata/netdata/tree/master/src/collectors/proc.plugin#readme) |
28
-| Processes | Real-time information about the system's resource usage, including CPU utilization, memory consumption, and disk IO for every running process. | `top`, `htop` | yes | [apps](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md) |
28
+| Processes | Real-time information about the system's resource usage, including CPU utilization, memory consumption, and disk IO for every running process. | `top`, `htop` | yes | [apps](/src/collectors/apps.plugin/README.md) |
29
| Systemd-journal | Viewing, exploring and analyzing systemd journal logs. | `journalctl` | yes | [systemd-journal](https://github.com/netdata/netdata/tree/master/src/collectors/systemd-journal.plugin#readme) |
30
| Systemd-list-units | Information about all systemd units, including their active state, description, whether or not they are enabled, and more. | `systemctl list-units` | yes | [systemd-journal](https://github.com/netdata/netdata/tree/master/src/collectors/systemd-journal.plugin#readme) |
31
| Systemd-services | System resource utilization for all running systemd services: CPU, memory, and disk IO. | `systemd-cgtop` | no | [cgroups](https://github.com/netdata/netdata/tree/master/src/collectors/cgroups.plugin#readme) |
@@ -40,7 +40,7 @@ Via streaming, the definitions of functions are transmitted to a parent node, so
40
41
Since these functions are able to execute routines on the node and due to the potential use cases that they can cover, our concern is to ensure no sensitive information or disruptive actions are exposed through the Agent's API.
42
43
-With the communication between the Netdata Agent and Netdata Cloud being through [ACLK](https://github.com/netdata/netdata/blob/master/src/aclk/README.md) this concern is addressed.
43
+With the communication between the Netdata Agent and Netdata Cloud being through [ACLK](/src/aclk/README.md) this concern is addressed.
44
45
## Feedback
46
integrations/cloud-authentication/integrations/oidc.md
+1
-1
@@ -55,7 +55,7 @@ The access settings for your client are the following:
55
56
### SP-initiated SSO
57
58
-If you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
58
+If you start your authentication flow from Netdata sign-in page please check [these steps](/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
59
60
61
### Reference
integrations/cloud-authentication/integrations/okta_sso.md
+1
-1
@@ -50,6 +50,6 @@ Steps needed to be done on Okta Admin Portal:
50
51
### SP-initiated SSO
52
53
-If you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
53
+If you start your authentication flow from Netdata sign-in page please check [these steps](/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
54
55
integrations/cloud-authentication/metadata.yaml
+2
-2
@@ -46,7 +46,7 @@
46
47
### SP-initiated SSO
48
49
- If you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
49
+ If you start your authentication flow from Netdata sign-in page please check [these steps](/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
50
51
- id: 'oidc-authentication'
52
meta:
@@ -98,7 +98,7 @@
98
99
### SP-initiated SSO
100
101
- If you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
101
+ If you start your authentication flow from Netdata sign-in page please check [these steps](/docs/netdata-cloud/authentication-and-authorization/enterprise-sso-authentication.md#from-netdata-sign-up-page).
102
103
104
### Reference
integrations/templates/setup.md
+1
-1
@@ -45,7 +45,7 @@ Configuration for this specific integration is located in the `[[ entry.setup.co
45
[% endif %]
46
47
You can edit the configuration file using the `edit-config` script from the
48
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
48
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
49
50
```bash
51
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
packaging/PLATFORM_SUPPORT.md
+1
-1
@@ -64,7 +64,7 @@ to work on these platforms with minimal user effort.
64
| Amazon Linux | 2023 | x86\_64, AArch64 | |
65
| Amazon Linux | 2 | x86\_64, AArch64 | |
66
| CentOS | 7.x | x86\_64 | |
67
-| Docker | 19.03 or newer | x86\_64, i386, ARMv7, AArch64, POWER8+ | See our [Docker documentation](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md) for more info on using Netdata on Docker |
67
+| Docker | 19.03 or newer | x86\_64, i386, ARMv7, AArch64, POWER8+ | See our [Docker documentation](/packaging/docker/README.md) for more info on using Netdata on Docker |
68
| Debian | 12.x | x86\_64, i386, ARMv7, AArch64 | |
69
| Debian | 11.x | x86\_64, i386, ARMv7, AArch64 | |
70
| Debian | 10.x | x86\_64, i386, ARMv7, AArch64 | |
packaging/VERSIONING_AND_PUBLIC_API.md
+1
-1
@@ -121,7 +121,7 @@ The following special exceptions to the public API exist:
121
guaranteed to be supported for in-place updates for at least two minor versions after the change happens. The
122
new format is not guaranteed to be backwards compatible.
123
- The list of supported platforms is functionally a part of the public API, but our existing [platform support
124
- policy](https://github.com/netdata/netdata/blob/master/packaging/PLATFORM_SUPPORT.md) dictates when and how
124
+ policy](/packaging/PLATFORM_SUPPORT.md) dictates when and how
125
support for specific platforms is added or removed.
126
- The list of components provided as separate packages in our official native packages is considered part of our
127
strictly defined public API, but changes to our packaging that do not alter the functionality of existing installs
packaging/docker/README.md
+2
-2
@@ -294,7 +294,7 @@ volumes:
294
### With SSL/TLS enabled HTTP Proxy
295
296
For a permanent installation on a public server, you
297
-should [secure the Netdata instance](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/securing-netdata-agents.md). This
297
+should [secure the Netdata instance](/docs/netdata-agent/securing-netdata-agents.md). This
298
section contains an example of how to install Netdata with an SSL reverse proxy and basic authentication.
299
300
You can use the following `docker-compose.yml` and Caddyfile files to run Netdata with Docker. Replace the domains and
@@ -369,7 +369,7 @@ to Caddyfile.
369
### With Docker socket proxy
370
371
Deploy a Docker socket proxy that accepts and filters out requests using something like
372
-[HAProxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md) or
372
+[HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md) or
373
[CetusGuard](https://github.com/hectorm/cetusguard) so that it restricts connections to read-only access to
374
the `/containers` endpoint.
375
packaging/installer/README.md
+15
-15
@@ -5,7 +5,7 @@ import TabItem from '@theme/TabItem';
5
6
# Netdata Agent Installation
7
8
-Netdata is very flexible and can be used to monitor all kinds of infrastructure. Read more about possible [Deployment guides](https://github.com/netdata/netdata/blob/master/docs/deployment-guides/README.md) to understand what better suites your needs.
8
+Netdata is very flexible and can be used to monitor all kinds of infrastructure. Read more about possible [Deployment guides](/docs/deployment-guides/README.md) to understand what better suites your needs.
9
10
## Install through Netdata Cloud
11
@@ -20,7 +20,7 @@ To install Netdata in minutes on your platform:
20
2. You will be presented with an empty space, and a prompt to "Connect Nodes" with the install command for each platform
21
3. Select the platform you want to install Netdata to, copy and paste the script into your node's terminal, and run it
22
23
-Upon installation completing successfully, you should be able to see the node live in your Netdata Space and live charts in the Overview tab. [Take a look at our Dashboards and Charts](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md) section to read more about Netdata's features.
23
+Upon installation completing successfully, you should be able to see the node live in your Netdata Space and live charts in the Overview tab. [Take a look at our Dashboards and Charts](/docs/dashboards-and-charts/README.md) section to read more about Netdata's features.
24
25
## Maintaining a Netdata Agent installation
26
@@ -28,19 +28,19 @@ For actions like starting, stopping, restarting, updating and uninstalling the N
28
29
## Configuration
30
31
-If you are looking to configure your Netdata Agent installation, refer to the [respective section in our Documentation](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md).
31
+If you are looking to configure your Netdata Agent installation, refer to the [respective section in our Documentation](/docs/netdata-agent/configuration/README.md).
32
33
## Data collection
34
35
-If Netdata didn't autodetect all the hardware, containers, services, or applications running on your node, you should learn more about [how data collectors work](https://github.com/netdata/netdata/blob/master/src/collectors/README.md). If there's a [supported collector](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md) for metrics you need, [configure the collector](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md) or read about its requirements to configure your endpoint to publish metrics in the correct format and endpoint.
35
+If Netdata didn't autodetect all the hardware, containers, services, or applications running on your node, you should learn more about [how data collectors work](/src/collectors/README.md). If there's a [supported collector](/src/collectors/COLLECTORS.md) for metrics you need, [configure the collector](/src/collectors/REFERENCE.md) or read about its requirements to configure your endpoint to publish metrics in the correct format and endpoint.
36
37
## Alerts & notifications
38
39
-Netdata comes with hundreds of pre-configured alerts, designed by our monitoring gurus in parallel with our open-source community, but you may want to [edit alerts](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) or [enable notifications](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/README.md) to customize your Netdata experience.
39
+Netdata comes with hundreds of pre-configured alerts, designed by our monitoring gurus in parallel with our open-source community, but you may want to [edit alerts](/src/health/REFERENCE.md) or [enable notifications](/docs/alerts-and-notifications/notifications/README.md) to customize your Netdata experience.
40
41
## Make your deployment production ready
42
43
-Go through our [deployment guides](https://github.com/netdata/netdata/blob/master/docs/deployment-guides/README.md), for suggested configuration changes for production deployments.
43
+Go through our [deployment guides](/docs/deployment-guides/README.md), for suggested configuration changes for production deployments.
44
45
## Advanced installation options and troubleshooting
46
@@ -50,14 +50,14 @@ By default, Netdata's installation scripts enable automatic updates for both nig
50
51
If you preferred to update your Netdata agent manually, you can disable automatic updates by using the `--no-updates`
52
option when you install or update Netdata using the [automatic one-line installation
53
-script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
53
+script](/packaging/installer/methods/kickstart.md).
54
55
```bash
56
wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh && sh /tmp/netdata-kickstart.sh --no-updates
57
```
58
59
With automatic updates disabled, you can choose exactly when and how you [update
60
-Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md).
60
+Netdata](/packaging/installer/UPDATE.md).
61
62
#### Network usage of Netdata’s automatic updater
63
@@ -100,7 +100,7 @@ the community helps fix any bugs that might have been introduced in previous rel
100
101
### Anonymous statistics
102
103
-Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self-hosted PostHog instance within the Netdata infrastructure. Read about the information collected, and learn how to-opt, on our [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/anonymous-telemetry-events.md) page.
103
+Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self-hosted PostHog instance within the Netdata infrastructure. Read about the information collected, and learn how to-opt, on our [anonymous statistics](/docs/netdata-agent/configuration/anonymous-telemetry-events.md) page.
104
105
The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
106
_actively_ contributing to Netdata's future.
@@ -122,12 +122,12 @@ There are three potential workarounds for this:
122
affect many projects other than just Netdata, and there are unfortunately a number of other services out there
123
that do not provide IPv6 connectivity, so taking this route is likely to save you time in the future as well.
124
2. If you are using a system that we publish native packages for (see our [platform support
125
- policy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md) for more details),
125
+ policy](/docs/netdata-agent/versions-and-platforms.md) for more details),
126
you can manually set up our native package repositories as outlined in our [native package install
127
- documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/packages.md). Our official
127
+ documentation](/packaging/installer/methods/packages.md). Our official
128
package repositories do provide service over IPv6, so they work without issue on hosts without IPv4 connectivity.
129
3. If neither of the above options work for you, you can still install using our [offline installation
130
- instructions](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md), though
130
+ instructions](/packaging/installer/methods/offline.md), though
131
do note that the offline install source must be prepared from a system with IPv4 connectivity.
132
133
#### Older distributions (Ubuntu 14.04, Debian 8, CentOS 6) and OpenSSL
@@ -144,8 +144,8 @@ man-in-the-middle attacks.
144
#### CentOS 6 and CentOS 8
145
146
To install the Agent on certain CentOS and RHEL systems, you must enable non-default repositories, such as EPEL or
147
-PowerTools, to gather hard dependencies. See the [CentOS 6](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-6x) and
148
-[CentOS 8](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-8x) sections for more information.
147
+PowerTools, to gather hard dependencies. See the [CentOS 6](/packaging/installer/methods/manual.md#centos--rhel-6x) and
148
+[CentOS 8](/packaging/installer/methods/manual.md#centos--rhel-8x) sections for more information.
149
150
#### Access to file is not permitted
151
@@ -179,4 +179,4 @@ both.
179
180
Our current build process has some issues when using certain configurations of the `clang` C compiler on Linux. See [the
181
section on `nonrepresentable section on output`
182
-errors](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
182
+errors](/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
packaging/installer/REINSTALL.md
+5
-5
@@ -8,11 +8,11 @@ Netdata Agent on your node.
8
### Reinstalling with the same install type
9
10
Run the one-line installer script with the `--reinstall` parameter to reinstall the Netdata Agent. This will preserve
11
-any [user configuration](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) in `netdata.conf` or other files, and will keep the same install
11
+any [user configuration](/docs/netdata-agent/configuration/README.md) in `netdata.conf` or other files, and will keep the same install
12
type that was used for the original install.
13
14
If you used any [optional
15
-parameters](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
15
+parameters](/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
16
installation, you need to pass them to the script again during reinstallation. If you cannot remember which options you
17
used, read the contents of the `.environment` file and look for a `REINSTALL_OPTIONS` line. This line contains a list of
18
optional parameters.
@@ -29,7 +29,7 @@ getting a badly broken installation working again. Unlike the regular `--reinsta
29
different install type than the original install used.
30
31
If you used any [optional
32
-parameters](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
32
+parameters](/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) during initial
33
installation, you need to pass them to the script again during reinstallation. If you cannot remember which options you
34
used, read the contents of the `.environment` file and look for a `REINSTALL_OPTIONS` line. This line contains a list of
35
optional parameters.
@@ -59,7 +59,7 @@ When copying these directories back after the reinstall, you may need to update
59
## Troubleshooting
60
61
If you still experience problems with your Netdata Agent installation after following one of these processes, the next
62
-best route is to [uninstall](https://github.com/netdata/netdata/blob/master/packaging/installer/UNINSTALL.md) and then try a fresh installation using the [one-line
63
-installer](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
62
+best route is to [uninstall](/packaging/installer/UNINSTALL.md) and then try a fresh installation using the [one-line
63
+installer](/packaging/installer/methods/kickstart.md).
64
65
You can also post to our [community forums](https://community.netdata.cloud) or create a new [bug report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
packaging/installer/UNINSTALL.md
+1
-1
@@ -3,7 +3,7 @@
3
> ### Note
4
>
5
> If you're having trouble updating Netdata, moving from one installation method to another, or generally having
6
-> issues with your Netdata Agent installation, consider our [reinstalling Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md) instead of removing the Netdata Agent entirely.
6
+> issues with your Netdata Agent installation, consider our [reinstalling Netdata](/packaging/installer/REINSTALL.md) instead of removing the Netdata Agent entirely.
7
8
The recommended method to uninstall Netdata on a system is to use our kickstart installer script with the `--uninstall` option like so:
9
packaging/installer/UPDATE.md
+7
-7
@@ -5,7 +5,7 @@ you installed. If you opted out of automatic updates, you need to update your Ne
5
or stable version. You can also [enable or disable automatic updates on an existing install](#control-automatic-updates).
6
7
> 💡 Looking to reinstall the Netdata Agent to enable a feature, update an Agent that cannot update automatically, or
8
-> troubleshoot an error during the installation process? See our [reinstallation doc](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md)
8
+> troubleshoot an error during the installation process? See our [reinstallation doc](/packaging/installer/REINSTALL.md)
9
> for reinstallation steps.
10
11
Before you update the Netdata Agent, check to see if your Netdata Agent is already up-to-date by clicking on the update
@@ -91,13 +91,13 @@ On such installs, you can update Netdata using your distribution package manager
91
92
The update process outlined above suffers from the same issues that installing on hosts without IPv4
93
connectivity does, and requires similar workarounds. For more details check [the explanation in our install
94
-documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#installs-on-hosts-without-ipv4-connectivity).
94
+documentation](/packaging/installer/README.md#installs-on-hosts-without-ipv4-connectivity).
95
96
### If the kickstart script does not work
97
98
If the above command fails, you can [reinstall
99
-Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md#one-line-installer-script-kickstartsh) to get the latest version. This
100
-also preserves your [configuration](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) in `netdata.conf` or other files just like updating
99
+Netdata](/packaging/installer/REINSTALL.md#one-line-installer-script-kickstartsh) to get the latest version. This
100
+also preserves your [configuration](/docs/netdata-agent/configuration/README.md) in `netdata.conf` or other files just like updating
101
normally would, though you will need to specify any installation options you used originally again.
102
103
## Docker
@@ -121,7 +121,7 @@ docker rm netdata
121
```
122
123
You can now re-create your Netdata container using the `docker` command or a `docker-compose.yml` file. See our [Docker
124
-installation instructions](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md#create-a-new-netdata-agent-container) for details.
124
+installation instructions](/packaging/docker/README.md#create-a-new-netdata-agent-container) for details.
125
126
## macOS
127
@@ -140,7 +140,7 @@ instructions](#updates-for-most-systems) to update Netdata.
140
141
## Manual installation from Git
142
143
-If you installed [Netdata manually from Git](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md), you can run that installer again
143
+If you installed [Netdata manually from Git](/packaging/installer/methods/manual.md), you can run that installer again
144
to update your agent. First, run our automatic requirements installer, which works on many Linux distributions, to
145
ensure your system has the dependencies necessary for new features.
146
@@ -196,7 +196,7 @@ located in the same directory as the main `netdata.conf` file. This file uses PO
196
variables that are used by the updater.
197
198
This configuration file can be edited [using our `edit-config`
199
-script](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md).
199
+script](/docs/netdata-agent/configuration/README.md).
200
201
The following configuration options are currently supported:
202
packaging/installer/methods/ansible.md
+3
-3
@@ -10,7 +10,7 @@ learn_rel_path: "Installation/Install on specific environments"
10
11
# Deploy Netdata with Ansible
12
13
-Netdata's [one-line kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#install-on-linux-with-one-line-installer) is zero-configuration, highly adaptable, and compatible with tons
13
+Netdata's [one-line kickstart](/packaging/installer/README.md#install-on-linux-with-one-line-installer) is zero-configuration, highly adaptable, and compatible with tons
14
of different operating systems and Linux distributions. You can use it on bare metal, VMs, containers, and everything
15
in-between.
16
@@ -105,7 +105,7 @@ two different SSH keys supplied by AWS.
105
106
In order to connect your node(s) to your Space in Netdata Cloud, and see all their metrics in real-time in composite
107
charts or perform [Metric
108
-Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md), you need to set the `claim_token`
108
+Correlations](/docs/metric-correlations.md), you need to set the `claim_token`
109
and `claim_room` variables.
110
111
To find your `claim_token` and `claim_room`, go to Netdata Cloud, then click on your Space's name in the top navigation,
@@ -130,7 +130,7 @@ hostname of the node, the playbook disables that local dashboard by setting `web
130
security boost by not allowing any unwanted access to the local dashboard.
131
132
You can read more about this decision, or other ways you might lock down the local dashboard, in our [node security
133
-doc](https://github.com/netdata/netdata/blob/master/docs/security-and-privacy-design/README.md).
133
+doc](/docs/security-and-privacy-design/README.md).
134
135
> Curious about why Netdata's dashboard is open by default? Read our [blog
136
> post](https://www.netdata.cloud/blog/netdata-agent-dashboard/) on that zero-configuration design decision.
packaging/installer/methods/aws.md
+7
-7
@@ -11,12 +11,12 @@ learn_rel_path: "Installation/Install on specific environments"
11
12
Netdata is fully compatible with Amazon Web Services (AWS).
13
You can install Netdata on cloud instances to monitor the apps/services running there, or use
14
-multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) configuration.
14
+multiple instances in a [parent-child streaming](/src/streaming/README.md) configuration.
15
16
## Recommended installation method
17
18
The best installation method depends on the instance's operating system, distribution, and version. For Linux instances,
19
-we recommend the [`kickstart.sh` automatic installation script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
19
+we recommend the [`kickstart.sh` automatic installation script](/packaging/installer/methods/kickstart.md).
20
21
If you have issues with Netdata after installation, look to the sections below to find the issue you're experiencing,
22
followed by the solution for your provider.
@@ -41,11 +41,11 @@ command from a remote system, and it fails, it's likely that a firewall is block
41
Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports
42
(80/443), which are likely already open on your instance. We have a number of guides available:
43
44
-- [Apache](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
45
-- [Nginx](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
46
-- [Caddy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
47
-- [HAProxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
48
-- [lighttpd](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
44
+- [Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
45
+- [Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
46
+- [Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
47
+- [HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
48
+- [lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
49
50
Sign in to the [AWS console](https://console.aws.amazon.com/) and navigate to the EC2 dashboard. Click on the **Security
51
Groups** link in the navigation, beneath the **Network & Security** heading. Find the Security Group your instance
packaging/installer/methods/azure.md
+7
-7
@@ -11,12 +11,12 @@ learn_rel_path: "Installation/Install on specific environments"
11
12
Netdata is fully compatible with Azure.
13
You can install Netdata on cloud instances to monitor the apps/services running there, or use
14
-multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) configuration.
14
+multiple instances in a [parent-child streaming](/src/streaming/README.md) configuration.
15
16
## Recommended installation method
17
18
The best installation method depends on the instance's operating system, distribution, and version. For Linux instances,
19
-we recommend the [`kickstart.sh` automatic installation script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
19
+we recommend the [`kickstart.sh` automatic installation script](/packaging/installer/methods/kickstart.md).
20
21
If you have issues with Netdata after installation, look to the sections below to find the issue you're experiencing,
22
followed by the solution for your provider.
@@ -41,11 +41,11 @@ command from a remote system, and it fails, it's likely that a firewall is block
41
Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports
42
(80/443), which are likely already open on your instance. We have a number of guides available:
43
44
-- [Apache](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
45
-- [Nginx](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
46
-- [Caddy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
47
-- [HAProxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
48
-- [lighttpd](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
44
+- [Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
45
+- [Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
46
+- [Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
47
+- [HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
48
+- [lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
49
50
Sign in to the [Azure portal](https://portal.azure.com) and open the virtual machine running Netdata. Click on the
51
**Networking** link beneath the **Settings** header, then click on the **Add inbound security rule** button.
packaging/installer/methods/freebsd.md
+3
-3
@@ -28,7 +28,7 @@ Please respond in the affirmative for any relevant prompts during the installati
28
29
## Install Netdata
30
31
-The simplest method is to use the single line [kickstart script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md)
31
+The simplest method is to use the single line [kickstart script](/packaging/installer/methods/kickstart.md)
32
33
If you have a Netdata cloud account then clicking on the **Connect Nodes** button will generate the kickstart command you should use. Use the command from the "Linux" tab, it should look something like this:
34
@@ -90,7 +90,7 @@ You can now access the Netdata dashboard by navigating to `http://NODE:19999`, r
90
91
Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self hosted PostHog instance within the Netdata infrastructure. To read
92
more about the information collected and how to opt-out, check the [anonymous statistics
93
-page](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/anonymous-telemetry-events.md).
93
+page](/docs/netdata-agent/configuration/anonymous-telemetry-events.md).
94
95
## Updating the Agent on FreeBSD
96
If you have not passed the `--auto-update` or `-u` parameter for the installer to enable automatic updating, repeat the last step to update Netdata whenever a new version becomes available.
@@ -134,7 +134,7 @@ The following options are mutually exclusive and specifiy special operations oth
134
- `--uninstall`: Uninstall an existing installation of Netdata. Fails if there is no existing install.
135
- `--claim-only`: If there is an existing install, only try to claim it without attempting to update it. If there is no existing install, install and claim Netdata normally.
136
- `--repositories-only`: Only install repository configuration packages instead of doing a full install of Netdata. Automatically sets --native-only.
137
-- `--prepare-offline-install-source`: Instead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md) for more info.
137
+- `--prepare-offline-install-source`: Instead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](/packaging/installer/methods/offline.md) for more info.
138
139
Additionally, the following environment variables may be used to further customize how the script runs (most users
140
should not need to use special values for any of these):
packaging/installer/methods/gcp.md
+7
-7
@@ -12,12 +12,12 @@ learn_rel_path: "Installation/Install on specific environments"
12
13
Netdata is fully compatible with the Google Cloud Platform (GCP).
14
You can install Netdata on cloud instances to monitor the apps/services running there, or use
15
-multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) configuration.
15
+multiple instances in a [parent-child streaming](/src/streaming/README.md) configuration.
16
17
## Recommended installation method
18
19
The best installation method depends on the instance's operating system, distribution, and version. For Linux instances,
20
-we recommend the [`kickstart.sh` automatic installation script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
20
+we recommend the [`kickstart.sh` automatic installation script](/packaging/installer/methods/kickstart.md).
21
22
If you have issues with Netdata after installation, look to the sections below to find the issue you're experiencing,
23
followed by the solution for your provider.
@@ -42,11 +42,11 @@ command from a remote system, and it fails, it's likely that a firewall is block
42
Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports
43
(80/443), which are likely already open on your instance. We have a number of guides available:
44
45
-- [Apache](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
46
-- [Nginx](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
47
-- [Caddy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
48
-- [HAProxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
49
-- [lighttpd](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
45
+- [Apache](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-apache.md)
46
+- [Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md)
47
+- [Caddy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-caddy.md)
48
+- [HAProxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-haproxy.md)
49
+- [lighttpd](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-lighttpd.md)
50
51
52
To add a firewall rule, go to the [Firewall rules page](https://console.cloud.google.com/networking/firewalls/list) and
packaging/installer/methods/kickstart.md
+7
-7
@@ -15,7 +15,7 @@ This script works on all Linux distributions and macOS environments, by detectin
15
16
> :bulb: Tip
17
>
18
-> If you are unsure whether you want nightly or stable releases, read the [related section](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#nightly-vs-stable-releases) of our Documentation, detailing the pros and cons of each release type.
18
+> If you are unsure whether you want nightly or stable releases, read the [related section](/packaging/installer/README.md#nightly-vs-stable-releases) of our Documentation, detailing the pros and cons of each release type.
19
20
To install Netdata, run the following as your normal user:
21
@@ -70,7 +70,7 @@ You will most often need to _restart_ the Agent to load new or edited configurat
70
> **Note**
71
> Stopping or restarting the Netdata Agent will cause gaps in stored metrics until the `netdata` process initiates collectors and the database engine.
72
>
73
-> You do not need to restart the Netdata Agent between changes to health configuration files, see the relevant section on [reloading health configuration](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#reload-health-configuration).
73
+> You do not need to restart the Netdata Agent between changes to health configuration files, see the relevant section on [reloading health configuration](/src/health/REFERENCE.md#reload-health-configuration).
74
75
### Using `systemctl` or `service`
76
@@ -98,7 +98,7 @@ If you start the daemon this way, close it with `sudo killall netdata`.
98
99
### Shutdown using `netdatacli`
100
101
-The Netdata Agent also comes with a [CLI tool](https://github.com/netdata/netdata/blob/master/src/cli/README.md) capable of performing shutdowns. Start the Agent back up using your preferred method listed above.
101
+The Netdata Agent also comes with a [CLI tool](/src/cli/README.md) capable of performing shutdowns. Start the Agent back up using your preferred method listed above.
102
103
```bash
104
sudo netdatacli shutdown-agent
@@ -242,7 +242,7 @@ By default, the kickstart script will provide a Netdata agent installation that
242
- `--claim-rooms`
243
Specify a comma-separated list of tokens for each War Room this node should appear in.
244
- `--claim-proxy`
245
- Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy. See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy) for details.
245
+ Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy. See [connecting through a proxy](/src/claim/README.md#connect-through-a-proxy) for details.
246
- `--claim-only`
247
If there is an existing install, only try to claim it without attempting to update it. If there is no existing install, install and claim Netdata normally.
248
- `--require-cloud`
@@ -285,7 +285,7 @@ The following options are mutually exclusive and specify special operations othe
285
- `--repositories-only`
286
Only install repository configuration packages instead of doing a full install of Netdata. Automatically sets --native-only.
287
- `--prepare-offline-install-source`
288
- Instead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md) for more info.
288
+ Instead of insallling the agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](/packaging/installer/methods/offline.md) for more info.
289
290
### environment variables
291
@@ -302,7 +302,7 @@ should not need to use special values for any of these):
302
303
## Native packages
304
305
-We publish [official DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/packages.md) for a number of common Linux distributions as part of our releases and nightly
305
+We publish [official DEB/RPM packages](/packaging/installer/methods/packages.md) for a number of common Linux distributions as part of our releases and nightly
306
builds. These packages are available for 64-bit x86 systems. Depending on the distribution and release they may
307
also be available for 32-bit x86, ARMv7, and AArch64 systems. If a native package is available, it will be used as the
308
default installation method. This allows you to handle Netdata updates as part of your usual system update procedure.
@@ -312,7 +312,7 @@ you can do so by adding `--native-only` to the options you pass to the installer
312
313
## Static builds
314
315
-We publish pre-built [static builds](https://github.com/netdata/netdata/blob/master/packaging/makeself/README.md) of Netdata for Linux systems. Currently, these are published for 64-bit x86, ARMv7,
315
+We publish pre-built [static builds](/packaging/makeself/README.md) of Netdata for Linux systems. Currently, these are published for 64-bit x86, ARMv7,
316
AArch64, and POWER8+ hardware. These static builds are able to operate in a mostly self-contained manner and only
317
require a POSIX compliant shell and a supported init system. These static builds install under `/opt/netdata`. If
318
you are on a platform which we provide static builds for but do not provide native packages for, a static build
packaging/installer/methods/kubernetes.md
+3
-3
@@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem';
3
4
# Install Netdata on Kubernetes
5
6
-This document details how to install Netdata on an existing Kubernetes (k8s) cluster, and connect it to Netdata Cloud. Read our [Kubernetes visualizations](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md) documentation, to see what you will get.
6
+This document details how to install Netdata on an existing Kubernetes (k8s) cluster, and connect it to Netdata Cloud. Read our [Kubernetes visualizations](/docs/dashboards-and-charts/kubernetes-tab.md) documentation, to see what you will get.
7
8
The [Netdata Helm chart](https://github.com/netdata/helmchart/blob/master/charts/netdata/README.md) installs one `parent` pod for storing metrics and managing alert notifications, plus an additional
9
`child` pod for every node in the cluster, responsible for collecting metrics from the node, Kubernetes control planes,
@@ -191,10 +191,10 @@ helm upgrade netdata netdata/netdata
191
192
## What's next?
193
194
-[Start Kubernetes monitoring](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md) in Netdata Cloud, which comes with meaningful visualizations out of the box.
194
+[Start Kubernetes monitoring](/docs/dashboards-and-charts/kubernetes-tab.md) in Netdata Cloud, which comes with meaningful visualizations out of the box.
195
196
### Related reference documentation
197
198
-- [Netdata Cloud · Kubernetes monitoring](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/kubernetes-tab.md)
198
+- [Netdata Cloud · Kubernetes monitoring](/docs/dashboards-and-charts/kubernetes-tab.md)
199
- [Netdata Helm chart](https://github.com/netdata/helmchart)
200
- [Netdata service discovery](https://github.com/netdata/agent-service-discovery/)
packaging/installer/methods/macos.md
+9
-9
@@ -9,8 +9,8 @@ learn_rel_path: "Installation/Install on specific environments"
9
# Install Netdata on macOS
10
11
Netdata works on macOS, albeit with some limitations.
12
-The number of charts displaying system metrics is limited, but you can use any of Netdata's [external plugins](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md) to monitor any services you might have installed on your macOS system.
13
-You could also use a macOS system as the parent node in a [streaming configuration](https://github.com/netdata/netdata/blob/master/src/streaming/README.md).
12
+The number of charts displaying system metrics is limited, but you can use any of Netdata's [external plugins](/src/collectors/plugins.d/README.md) to monitor any services you might have installed on your macOS system.
13
+You could also use a macOS system as the parent node in a [streaming configuration](/src/streaming/README.md).
14
15
You can install Netdata in one of the three following ways:
16
@@ -21,12 +21,12 @@ You can install Netdata in one of the three following ways:
21
Each of these installation option requires [Homebrew](https://brew.sh/) for handling dependencies.
22
23
> The Netdata Homebrew package is community-created and -maintained.
24
-> Community-maintained packages _may_ receive support from Netdata, but are only a best-effort affair. Learn more about [Netdata's platform support policy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md).
24
+> Community-maintained packages _may_ receive support from Netdata, but are only a best-effort affair. Learn more about [Netdata's platform support policy](/docs/netdata-agent/versions-and-platforms.md).
25
26
## Install Netdata with our automatic one-line installation script
27
28
**Local Netdata Agent installation**
29
-To install Netdata using our automatic [kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#automatic-one-line-installation-script) open a new terminal and run:
29
+To install Netdata using our automatic [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script) open a new terminal and run:
30
31
```bash
32
curl https://get.netdata.cloud/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh
@@ -35,16 +35,16 @@ The Netdata Agent is installed under `/usr/local/netdata`. Dependencies are hand
35
36
**Automatically connect to Netdata Cloud during installation**
37
38
-The `kickstart.sh` script accepts additional parameters to automatically [connect](https://github.com/netdata/netdata/blob/master/src/claim/README.md) your node to Netdata
38
+The `kickstart.sh` script accepts additional parameters to automatically [connect](/src/claim/README.md) your node to Netdata
39
Cloud immediately after installation. Find the `token` and `rooms` strings by [signing in to Netdata
40
Cloud](https://app.netdata.cloud/sign-in?cloudRoute=/spaces), then clicking on **Connect Nodes** in the [Spaces management
41
-area](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces).
41
+area](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#netdata-cloud-spaces).
42
43
- `--claim-token`: Specify a unique claiming token associated with your Space in Netdata Cloud to be used to connect to the node
44
after the install.
45
- `--claim-rooms`: Specify a comma-separated list of tokens for each War Room this node should appear in.
46
- `--claim-proxy`: Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy.
47
- See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy) for details.
47
+ See [connecting through a proxy](/src/claim/README.md#connect-through-a-proxy) for details.
48
- `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://app.netdata.cloud`.
49
50
For example:
@@ -53,7 +53,7 @@ curl https://get.netdata.cloud/kickstart.sh > /tmp/netdata-kickstart.sh && sh /t
53
```
54
The Netdata Agent is installed under `/usr/local/netdata` on your machine. Your machine will also show up as a node in your Netdata Cloud.
55
56
-If you experience issues while claiming your node, follow the steps in our [Troubleshooting](https://github.com/netdata/netdata/blob/master/src/claim/README.md#troubleshooting) documentation.
56
+If you experience issues while claiming your node, follow the steps in our [Troubleshooting](/src/claim/README.md#troubleshooting) documentation.
57
## Install Netdata via Homebrew
58
59
### For macOS Intel
@@ -90,7 +90,7 @@ We don't recommend installing Netdata from source on macOS, as it can be difficu
90
```
91
92
2. Click **Install** on the Software Update popup window that appears.
93
-3. Use the same terminal session to install some of Netdata's prerequisites using Homebrew. If you don't want to use [Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/README.md), you can omit `cmake`.
93
+3. Use the same terminal session to install some of Netdata's prerequisites using Homebrew. If you don't want to use [Netdata Cloud](/docs/netdata-cloud/README.md), you can omit `cmake`.
94
95
```bash
96
brew install ossp-uuid autoconf automake pkg-config libuv lz4 json-c openssl libtool cmake
packaging/installer/methods/manual.md
+6
-6
@@ -23,7 +23,7 @@ To install the latest git version of Netdata, please follow these 2 steps:
23
## Prepare your system
24
25
Before you begin, make sure that your repo and the repo's submodules are clean from any previous builds and up to date.
26
-Otherwise, [perform a cleanup](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#perform-a-cleanup-in-your-netdata-repo)
26
+Otherwise, [perform a cleanup](/packaging/installer/methods/manual.md#perform-a-cleanup-in-your-netdata-repo)
27
28
Use our automatic requirements installer (_no need to be `root`_), which attempts to find the packages that
29
should be installed on your system to build and run Netdata. It supports a large variety of major Linux distributions
@@ -205,22 +205,22 @@ cd netdata
205
- `--dont-start-it`: Prevent the installer from starting Netdata automatically.
206
- `--stable-channel`: Automatically update only on the release of new major versions.
207
- `--nightly-channel`: Automatically update on every new nightly build.
208
-- `--disable-telemetry`: Opt-out of [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/anonymous-telemetry-events.md) we use to make
208
+- `--disable-telemetry`: Opt-out of [anonymous statistics](/docs/netdata-agent/configuration/anonymous-telemetry-events.md) we use to make
209
Netdata better.
210
- `--no-updates`: Prevent automatic updates of any kind.
211
- `--reinstall`: If an existing install is detected, reinstall instead of trying to update it. Note that this
212
cannot be used to change installation types.
213
-- `--local-files`: Used for [offline installations](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md). Pass four file paths: the Netdata
213
+- `--local-files`: Used for [offline installations](/packaging/installer/methods/offline.md). Pass four file paths: the Netdata
214
tarball, the checksum file, the go.d plugin tarball, and the go.d plugin config tarball, to force kickstart run the
215
process using those files. This option conflicts with the `--stable-channel` option. If you set this _and_
216
`--stable-channel`, Netdata will use the local files.
217
218
### Connect node to Netdata Cloud during installation
219
220
-Unlike the [`kickstart.sh`](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md), the `netdata-installer.sh` script does
221
-not allow you to automatically [connect](https://github.com/netdata/netdata/blob/master/src/claim/README.md) your node to Netdata Cloud immediately after installation.
220
+Unlike the [`kickstart.sh`](/packaging/installer/methods/kickstart.md), the `netdata-installer.sh` script does
221
+not allow you to automatically [connect](/src/claim/README.md) your node to Netdata Cloud immediately after installation.
222
223
-See the [connect to cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md) doc for details on connecting a node with a manual installation of Netdata.
223
+See the [connect to cloud](/src/claim/README.md) doc for details on connecting a node with a manual installation of Netdata.
224
225
### 'nonrepresentable section on output' errors
226
packaging/installer/methods/methods.md
+6
-6
@@ -12,15 +12,15 @@ sidebar_position: 30
12
13
Netdata can be installed:
14
15
-- [As a DEB/RPM package](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/packages.md)
16
-- [As a static binary](https://github.com/netdata/netdata/blob/master/packaging/makeself/README.md)
17
-- [From a git checkout](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md)
18
-- [As a docker container](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md)
15
+- [As a DEB/RPM package](/packaging/installer/methods/packages.md)
16
+- [As a static binary](/packaging/makeself/README.md)
17
+- [From a git checkout](/packaging/installer/methods/manual.md)
18
+- [As a docker container](/packaging/docker/README.md)
19
20
-The [one line installer kickstart.sh](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md)
20
+The [one line installer kickstart.sh](/packaging/installer/methods/kickstart.md)
21
picks the most appropriate method out of the first three for any system
22
and is the recommended installation method, if you don't use containers.
23
24
`kickstart.sh` can also be used for
25
-[offline installation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md),
25
+[offline installation](/packaging/installer/methods/offline.md),
26
suitable for air-gapped systems.
packaging/installer/methods/offline.md
+1
-1
@@ -54,6 +54,6 @@ target system. This can be done in any manner you like, as long as filenames are
54
55
After copying the files, simply run the `install.sh` script located in the
56
offline install source directory. It accepts all the [same options as the kickstart
57
-script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) for further
57
+script](/packaging/installer/methods/kickstart.md#optional-parameters-to-alter-your-installation) for further
58
customization of the installation, though it will default to not enabling automatic updates (as they are not
59
supported on offline installs).
packaging/installer/methods/packages.md
+2
-2
@@ -12,9 +12,9 @@ sidebar_position: 20
12
13
For most common Linux distributions that use either DEB or RPM packages, Netdata provides pre-built native packages
14
for current releases in-line with
15
-our [official platform support policy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md).
15
+our [official platform support policy](/docs/netdata-agent/versions-and-platforms.md).
16
These packages will be used by default when attempting to install on a supported platform using our
17
-[kickstart.sh installer script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
17
+[kickstart.sh installer script](/packaging/installer/methods/kickstart.md).
18
19
When using the kickstart script, you can force usage of native DEB or RPM packages by passing the option
20
`--native-only` when invoking the script. This will cause it to only attempt to use native packages for the install,
packaging/installer/methods/source.md
+1
-1
@@ -13,7 +13,7 @@ sidebar_position: 100
13
These instructions are for advanced users and distribution package
14
maintainers. Unless this describes you, you almost certainly want
15
to follow [our guide for manually installing Netdata from a git
16
-checkout](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md) instead.
16
+checkout](/packaging/installer/methods/manual.md) instead.
17
18
## Required dependencies
19
packaging/installer/methods/synology.md
+1
-1
@@ -18,7 +18,7 @@ learn_rel_path: "Installation/Install on specific environments"
18
19
20
The good news is that our
21
-[one-line installation script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md)
21
+[one-line installation script](/packaging/installer/methods/kickstart.md)
22
works fine if your NAS is one that uses the amd64 architecture. It
23
will install the content into `/opt/netdata`, making future removal safe and simple.
24
packaging/installer/methods/systems.md
+2
-2
@@ -11,8 +11,8 @@ learn_rel_path: "Installation/Install on specific environments"
11
12
This category contains specific instructions for some popular environments.
13
If you have a standard environment that is not yet listed here, just use the
14
-[one line installer kickstart.sh](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md)
14
+[one line installer kickstart.sh](/packaging/installer/methods/kickstart.md)
15
16
If your environment is somewhat old or unusual, check our
17
-[platform support policy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md).
17
+[platform support policy](/docs/netdata-agent/versions-and-platforms.md).
18
packaging/makeself/README.md
+1
-1
@@ -26,7 +26,7 @@ you can do so by adding `--static-only` to the options you pass to the installer
26
## Building a static binary package
27
28
Before you begin, make sure that your repo and the repo's submodules are clean from any previous builds and up to date.
29
-Otherwise, [perform a cleanup](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#perform-a-cleanup-in-your-netdata-repo)
29
+Otherwise, [perform a cleanup](/packaging/installer/methods/manual.md#perform-a-cleanup-in-your-netdata-repo)
30
31
32
To build the static binary 64-bit distribution package, into the root folder on the netdata repo, run:
src/aclk/README.md
+9
-9
@@ -15,7 +15,7 @@ The Cloud App lives at app.netdata.cloud which currently resolves to the followi
15
>This list of IPs can change without notice, we strongly advise you to whitelist following domains `app.netdata.cloud`, `mqtt.netdata.cloud`, if this is not an option in your case always verify the current domain resolution (e.g via the `host` command).
16
17
For a guide to connecting a node using the ACLK, plus additional troubleshooting and reference information, read our [connect to Cloud
18
-documentation](https://github.com/netdata/netdata/blob/master/src/claim/README.md).
18
+documentation](/src/claim/README.md).
19
20
## Data privacy
21
@@ -24,7 +24,7 @@ you. This is why **we don't store any metric data in Netdata Cloud**.
24
25
All the data that you see in the web browser when using Netdata Cloud, is actually streamed directly from the Netdata Agent to the Netdata Cloud dashboard. The data passes through our systems, but it isn't stored.
26
27
-However, to be able to offer the stunning visualizations and advanced functionality of Netdata Cloud, it does store a limited number of _metadata_. Read more about our [security and privacy design](https://github.com/netdata/netdata/blob/master/docs/security-and-privacy-design/README.md).
27
+However, to be able to offer the stunning visualizations and advanced functionality of Netdata Cloud, it does store a limited number of _metadata_. Read more about our [security and privacy design](/docs/security-and-privacy-design/README.md).
28
29
## Enable and configure the ACLK
30
@@ -39,7 +39,7 @@ configuration uses two settings:
39
```
40
41
If your Agent needs to use a proxy to access the internet, you must [set up a proxy for
42
-connecting to cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy).
42
+connecting to cloud](/src/claim/README.md#connect-through-a-proxy).
43
44
You can configure following keys in the `netdata.conf` section `[cloud]`:
45
```
@@ -58,8 +58,8 @@ You have two options if you prefer to disable the ACLK and not use Netdata Cloud
58
### Disable at installation
59
60
You can pass the `--disable-cloud` parameter to the Agent installation when using a kickstart script
61
-([kickstart.sh](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md), or a [manual installation from
62
-Git](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md).
61
+([kickstart.sh](/packaging/installer/methods/kickstart.md), or a [manual installation from
62
+Git](/packaging/installer/methods/manual.md).
63
64
When you pass this parameter, the installer does not download or compile any extra libraries. Once running, the Agent
65
kills the thread responsible for the ACLK and connecting behavior, and behaves as though the ACLK, and thus Netdata Cloud,
@@ -113,12 +113,12 @@ Restart your Agent to disable the ACLK.
113
### Re-enable the ACLK
114
115
If you first disable the ACLK and any Cloud functionality and then decide you would like to use Cloud, you must either
116
-[reinstall Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md) with Cloud enabled or change the runtime setting in your
116
+[reinstall Netdata](/packaging/installer/REINSTALL.md) with Cloud enabled or change the runtime setting in your
117
`cloud.conf` file.
118
119
If you passed `--disable-cloud` to `netdata-installer.sh` during installation, you must
120
-[reinstall](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md) your Agent. Use the same method as before, but pass `--require-cloud` to
121
-the installer. When installation finishes you can [connect your node](https://github.com/netdata/netdata/blob/master/src/claim/README.md#how-to-connect-a-node).
120
+[reinstall](/packaging/installer/REINSTALL.md) your Agent. Use the same method as before, but pass `--require-cloud` to
121
+the installer. When installation finishes you can [connect your node](/src/claim/README.md#how-to-connect-a-node).
122
123
If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf` file, edit the file again and change
124
`enabled` to `yes`:
@@ -128,6 +128,6 @@ If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf`
128
enabled = yes
129
```
130
131
-Restart your Agent and [connect your node](https://github.com/netdata/netdata/blob/master/src/claim/README.md#how-to-connect-a-node).
131
+Restart your Agent and [connect your node](/src/claim/README.md#how-to-connect-a-node).
132
133
src/claim/README.md
+18
-18
@@ -1,7 +1,7 @@
1
# Connect Agent to Cloud
2
3
This guide walks you through the process of securely connecting a Netdata Agent to Netdata Cloud via the encrypted
4
-Agent-Cloud Link ([ACLK](https://github.com/netdata/netdata/blob/master/src/aclk/README.md)).
4
+Agent-Cloud Link ([ACLK](/src/aclk/README.md)).
5
6
When connecting an Agent (also known as a node) to Netdata Cloud, it's essential to complete a verification process.
7
This process ensures that you have the necessary authorization level to manage the node effectively. Verification serves
@@ -36,7 +36,7 @@ There are three main ways to connect your node to Netdata Cloud:
36
right away.
37
- From the [Space Management screen](#manage-space-or-war-room-area): Click "Connect Nodes" to add a new node to your
38
existing Space.
39
-- From the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md): While you can see
39
+- From the [Nodes tab](/docs/dashboards-and-charts/nodes-tab.md): While you can see
40
connected nodes here, the connection process itself happens in the Space Management screen.
41
42
### Empty War Room
@@ -73,7 +73,7 @@ Connecting a Node to a War Room:
73
terminal window. Press Enter to initiate the connection process.
74
75
> Note: When connecting from
76
-> the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md), the room parameter will
76
+> the [Nodes tab](/docs/dashboards-and-charts/nodes-tab.md), the room parameter will
77
> be
78
> set to the current War Room.
79
@@ -105,14 +105,14 @@ Refer to the [Connect an Agent without root privileges section](#connect-an-agen
105
details.
106
107
For in-depth information about the optional parameters `--claim-token`, `--claim-rooms`, and `--claim-url`,
108
-see [Connect node to Netdata Cloud during installation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#connect-node-to-netdata-cloud-during-installation).
108
+see [Connect node to Netdata Cloud during installation](/packaging/installer/methods/kickstart.md#connect-node-to-netdata-cloud-during-installation).
109
110
### Connect an Agent without root privileges
111
112
If you don't have root access, you can still connect your node to Netdata Cloud by following these steps:
113
114
1. Identify the Netdata Agent User: Use the `grep` command to search your `netdata.conf` file which is located at
115
- your [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration.md#the-netdata-config-directory)
115
+ your [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
116
and find the `run as user` setting. This will tell you which user is running the Netdata Agent.
117
```bash
118
grep "run as user" /etc/netdata/netdata.conf
@@ -129,7 +129,7 @@ If you don't have root access, you can still connect your node to Netdata Cloud
129
130
To ensure the **configuration and state information** needed for the Cloud connection is preserved across container
131
restarts, the contents of the `/var/lib/netdata` directory must be persisted. See
132
-our [documentation](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md#recommended-way) for
132
+our [documentation](/packaging/docker/README.md#recommended-way) for
133
details on using persistent volumes.
134
135
<details>
@@ -317,7 +317,7 @@ see the node in your Space after 60 seconds, see the [troubleshooting informatio
317
### Connect an Agent running in macOS
318
319
To connect a node that is running on a macOS environment the script that will be provided to you by Netdata Cloud is
320
-the [kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/macos.md#install-netdata-with-our-automatic-one-line-installation-script)
320
+the [kickstart](/packaging/installer/methods/macos.md#install-netdata-with-our-automatic-one-line-installation-script)
321
script which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata
322
Cloud. It should be similar to:
323
@@ -333,7 +333,7 @@ curl https://get.netdata.cloud/kickstart.sh > /tmp/netdata-kickstart.sh && sh /t
333
### Connect a Kubernetes cluster's parent Netdata pod
334
335
Read
336
-our [Kubernetes installation](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md#deploy-netdata-on-your-kubernetes-cluster)
336
+our [Kubernetes installation](/packaging/installer/methods/kubernetes.md#deploy-netdata-on-your-kubernetes-cluster)
337
for details on connecting a cluster's parent Netdata pod.
338
339
### Connect through a proxy
@@ -363,7 +363,7 @@ For example, a HTTP proxy setting may look like the following:
363
```
364
365
You can now move on to connecting. When you connect with
366
-the [kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#automatic-one-line-installation-script)
366
+the [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script)
367
script, add the `--claim-proxy=` parameter and append the same proxy setting you added to `netdata.conf`.
368
369
```bash
@@ -378,7 +378,7 @@ wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh && sh /
378
### Troubleshooting
379
380
If you're having trouble connecting a node, this may be because
381
-the [ACLK](https://github.com/netdata/netdata/blob/master/src/aclk/README.md) cannot connect to Cloud.
381
+the [ACLK](/src/aclk/README.md) cannot connect to Cloud.
382
383
With the Netdata Agent running, visit `http://NODE:19999/api/v1/info` in your browser, replacing `NODE` with the IP
384
address or hostname of your Agent. The returned JSON contains four keys that will be helpful to diagnose any issues you
@@ -419,7 +419,7 @@ installed Netdata using an unsupported package.
419
> If you are using an unsupported package, such as a third-party `.deb`/`.rpm` package provided by your distribution,
420
> please remove that package and reinstall using
421
>
422
-our [recommended kickstart script](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#install-on-linux-with-one-line-installer).
422
+our [recommended kickstart script](/packaging/installer/README.md#install-on-linux-with-one-line-installer).
423
424
#### kickstart: Failed to write new machine GUID
425
@@ -448,7 +448,7 @@ script.
448
> If you are using an unsupported package, such as a third-party `.deb`/`.rpm` package provided by your distribution,
449
> please remove that package and reinstall using
450
>
451
-our [recommended kickstart script](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#install-on-linux-with-one-line-installer).
451
+our [recommended kickstart script](/packaging/installer/README.md#install-on-linux-with-one-line-installer).
452
453
#### Connecting on older distributions (Ubuntu 14.04, Debian 8, CentOS 6)
454
@@ -458,7 +458,7 @@ versions of OpenSSL cannot perform [hostname validation](https://wiki.openssl.or
458
helps securely encrypt SSL connections.
459
460
We recommend you reinstall Netdata with
461
-a [static build](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md#static-builds),
461
+a [static build](/packaging/installer/methods/kickstart.md#static-builds),
462
which uses an up-to-date version of OpenSSL with hostname validation enabled.
463
464
If you choose to continue using the outdated version of OpenSSL, your node will still connect to Netdata Cloud, albeit
@@ -477,7 +477,7 @@ Additionally, check that the `enabled` setting in `var/lib/netdata/cloud.d/cloud
477
```
478
479
To fix this issue, reinstall Netdata using
480
-your [preferred method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md) and do not add
480
+your [preferred method](/packaging/installer/README.md) and do not add
481
the `--disable-cloud` option.
482
483
#### cloud-available is false / ACLK Available: No
@@ -617,7 +617,7 @@ If in case of some security reason, or other, you need to revoke your previous c
617
can achieve that from the Netdata Cloud UI.
618
619
On any screen where you see the connect the node to Netdata Cloud command you'll see above it, next to
620
-the [updates channel](https://github.com/netdata/netdata/blob/master/docs/netdata-Agent/versions-and-platforms.md), a
620
+the [updates channel](/docs/netdata-Agent/versions-and-platforms.md), a
621
button to **Regenerate token**. This action will invalidate your previous token and generate a fresh new one.
622
623
Only the administrators of a Space in Netdata Cloud can trigger this action.
@@ -630,12 +630,12 @@ Agent's command line tool, and details about the files found in `cloud.d`.
630
### The `cloud.conf` file
631
632
This section defines how and whether your Agent connects to Netdata Cloud
633
-using the [ACLK](https://github.com/netdata/netdata/blob/master/src/aclk/README.md).
633
+using the [ACLK](/src/aclk/README.md).
634
635
| setting | default | info |
636
|:---------------|:----------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
637
| cloud base url | <https://app.netdata.cloud> | The URL for the Netdata Cloud web application. You should not change this. If you want to disable Cloud, change the `enabled` setting. |
638
-| enabled | yes | The runtime option to disable the [Agent-Cloud link](https://github.com/netdata/netdata/blob/master/src/aclk/README.md) and prevent your Agent from connecting to Netdata Cloud. |
638
+| enabled | yes | The runtime option to disable the [Agent-Cloud link](/src/aclk/README.md) and prevent your Agent from connecting to Netdata Cloud. |
639
640
### Claiming script
641
@@ -673,7 +673,7 @@ netdatacli reload-claiming-state
673
This reloads the Agent connection state from disk.
674
675
Our recommendation is to trigger the connection process using
676
-the [kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#automatic-one-line-installation-script)
676
+the [kickstart](/packaging/installer/README.md#automatic-one-line-installation-script)
677
whenever possible.
678
679
### Netdata Agent command line
src/cli/README.md
+1
-1
@@ -33,6 +33,6 @@ dumpconfig
33
Returns the current netdata.conf on stdout.
34
```
35
36
-See also the Netdata daemon [command line options](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#command-line-options).
36
+See also the Netdata daemon [command line options](/src/daemon/README.md#command-line-options).
37
38
src/collectors/COLLECTORS.md
+528
-528
@@ -5,16 +5,16 @@ real-time, interactive charts. The following list includes collectors for both e
5
internal system metrics.
6
7
Learn more
8
-about [how collectors work](https://github.com/netdata/netdata/blob/master/src/collectors/README.md), and
8
+about [how collectors work](/src/collectors/README.md), and
9
then learn how to [enable or
10
-configure](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md#enable-and-disable-a-specific-collection-module) any of the below collectors using the same process.
10
+configure](/src/collectors/REFERENCE.md#enable-and-disable-a-specific-collection-module) any of the below collectors using the same process.
11
12
Some collectors have both Go and Python versions as we continue our effort to migrate all collectors to Go. In these
13
cases, _Netdata always prioritizes the Go version_, and we highly recommend you use the Go versions for the best
14
experience.
15
16
If you want to use a Python version of a collector, you need to
17
-explicitly [disable the Go version](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md#enable-and-disable-a-specific-collection-module),
17
+explicitly [disable the Go version](/src/collectors/REFERENCE.md#enable-and-disable-a-specific-collection-module),
18
and enable the Python version. Netdata then skips the Go version and attempts to load the Python version and its
19
accompanying configuration file.
20
@@ -23,13 +23,13 @@ accompanying configuration file.
23
If you don't see the app/service you'd like to monitor in this list:
24
25
- If your application has a Prometheus endpoint, Netdata can monitor it! Look at our
26
- [generic Prometheus collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/README.md).
26
+ [generic Prometheus collector](/src/go/collectors/go.d.plugin/modules/prometheus/README.md).
27
28
- If your application is instrumented to expose [StatsD](https://blog.netdata.cloud/introduction-to-statsd/) metrics,
29
- see our [generic StatsD collector](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/README.md).
29
+ see our [generic StatsD collector](/src/collectors/statsd.plugin/README.md).
30
31
- If you have data in CSV, JSON, XML or other popular formats, you may be able to use our
32
- [generic structured data (Pandas) collector](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/pandas/README.md),
32
+ [generic structured data (Pandas) collector](/src/collectors/python.d.plugin/pandas/README.md),
33
34
- Check out our [GitHub issues](https://github.com/netdata/netdata/issues). Use the search bar to look for previous
35
discussions about that collector—we may be looking for assistance from users such as yourself!
@@ -38,1157 +38,1157 @@ If you don't see the app/service you'd like to monitor in this list:
38
a [feature request](https://github.com/netdata/netdata/issues/new/choose) on GitHub.
39
40
- If you have basic software development skills, you can add your own plugin
41
- in [Go](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/README.md#how-to-develop-a-collector)
42
- or [Python](https://github.com/netdata/netdata/blob/master/docs/developer-and-contributor-corner/python-collector.md)
41
+ in [Go](/src/go/collectors/go.d.plugin/README.md#how-to-develop-a-collector)
42
+ or [Python](/docs/developer-and-contributor-corner/python-collector.md)
43
44
## Available Data Collection Integrations
45
<!-- AUTOGENERATED PART BY integrations/gen_doc_collector_page.py SCRIPT, DO NOT EDIT MANUALLY -->
46
### APM
47
48
-- [Alamos FE2 server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md)
48
+- [Alamos FE2 server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md)
49
50
-- [Apache Airflow](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md)
50
+- [Apache Airflow](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md)
51
52
-- [Apache Flink](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md)
52
+- [Apache Flink](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md)
53
54
-- [Audisto](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md)
54
+- [Audisto](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md)
55
56
-- [Dependency-Track](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md)
56
+- [Dependency-Track](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md)
57
58
-- [Go applications (EXPVAR)](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/go_expvar/integrations/go_applications_expvar.md)
58
+- [Go applications (EXPVAR)](/src/collectors/python.d.plugin/go_expvar/integrations/go_applications_expvar.md)
59
60
-- [Google Pagespeed](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md)
60
+- [Google Pagespeed](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md)
61
62
-- [IBM AIX systems Njmon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md)
62
+- [IBM AIX systems Njmon](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md)
63
64
-- [JMX](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md)
64
+- [JMX](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md)
65
66
-- [NRPE daemon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md)
66
+- [NRPE daemon](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md)
67
68
-- [Sentry](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md)
68
+- [Sentry](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md)
69
70
-- [Sysload](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md)
70
+- [Sysload](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md)
71
72
-- [VSCode](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md)
72
+- [VSCode](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md)
73
74
-- [YOURLS URL Shortener](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md)
74
+- [YOURLS URL Shortener](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md)
75
76
-- [bpftrace variables](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md)
76
+- [bpftrace variables](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md)
77
78
-- [gpsd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md)
78
+- [gpsd](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md)
79
80
-- [jolokia](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md)
80
+- [jolokia](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md)
81
82
-- [phpDaemon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/phpdaemon/integrations/phpdaemon.md)
82
+- [phpDaemon](/src/go/collectors/go.d.plugin/modules/phpdaemon/integrations/phpdaemon.md)
83
84
### Authentication and Authorization
85
86
-- [Fail2ban](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/fail2ban/integrations/fail2ban.md)
86
+- [Fail2ban](/src/go/collectors/go.d.plugin/modules/fail2ban/integrations/fail2ban.md)
87
88
-- [FreeRADIUS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/freeradius/integrations/freeradius.md)
88
+- [FreeRADIUS](/src/go/collectors/go.d.plugin/modules/freeradius/integrations/freeradius.md)
89
90
-- [HashiCorp Vault secrets](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md)
90
+- [HashiCorp Vault secrets](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md)
91
92
-- [LDAP](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md)
92
+- [LDAP](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md)
93
94
-- [OpenLDAP (community)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md)
94
+- [OpenLDAP (community)](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md)
95
96
-- [OpenLDAP](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/openldap/integrations/openldap.md)
96
+- [OpenLDAP](/src/collectors/python.d.plugin/openldap/integrations/openldap.md)
97
98
-- [RADIUS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md)
98
+- [RADIUS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md)
99
100
-- [SSH](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md)
100
+- [SSH](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md)
101
102
-- [TACACS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md)
102
+- [TACACS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md)
103
104
### Blockchain Servers
105
106
-- [Chia](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md)
106
+- [Chia](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md)
107
108
-- [Crypto exchanges](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md)
108
+- [Crypto exchanges](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md)
109
110
-- [Cryptowatch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md)
110
+- [Cryptowatch](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md)
111
112
-- [Go-ethereum](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/geth/integrations/go-ethereum.md)
112
+- [Go-ethereum](/src/go/collectors/go.d.plugin/modules/geth/integrations/go-ethereum.md)
113
114
-- [Helium miner (validator)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md)
114
+- [Helium miner (validator)](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md)
115
116
-- [IOTA full node](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md)
116
+- [IOTA full node](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md)
117
118
-- [Sia](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md)
118
+- [Sia](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md)
119
120
### CICD Platforms
121
122
-- [Concourse](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md)
122
+- [Concourse](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md)
123
124
-- [GitLab Runner](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md)
124
+- [GitLab Runner](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md)
125
126
-- [Jenkins](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md)
126
+- [Jenkins](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md)
127
128
-- [Puppet](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/puppet/integrations/puppet.md)
128
+- [Puppet](/src/collectors/python.d.plugin/puppet/integrations/puppet.md)
129
130
### Cloud Provider Managed
131
132
-- [AWS EC2 Compute instances](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md)
132
+- [AWS EC2 Compute instances](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md)
133
134
-- [AWS EC2 Spot Instance](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md)
134
+- [AWS EC2 Spot Instance](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md)
135
136
-- [AWS ECS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md)
136
+- [AWS ECS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md)
137
138
-- [AWS Health events](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md)
138
+- [AWS Health events](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md)
139
140
-- [AWS Quota](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md)
140
+- [AWS Quota](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md)
141
142
-- [AWS S3 buckets](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md)
142
+- [AWS S3 buckets](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md)
143
144
-- [AWS SQS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md)
144
+- [AWS SQS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md)
145
146
-- [AWS instance health](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md)
146
+- [AWS instance health](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md)
147
148
-- [Akamai Global Traffic Management](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md)
148
+- [Akamai Global Traffic Management](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md)
149
150
-- [Akami Cloudmonitor](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md)
150
+- [Akami Cloudmonitor](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md)
151
152
-- [Alibaba Cloud](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md)
152
+- [Alibaba Cloud](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md)
153
154
-- [ArvanCloud CDN](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md)
154
+- [ArvanCloud CDN](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md)
155
156
-- [Azure AD App passwords](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md)
156
+- [Azure AD App passwords](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md)
157
158
-- [Azure Elastic Pool SQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md)
158
+- [Azure Elastic Pool SQL](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md)
159
160
-- [Azure Resources](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md)
160
+- [Azure Resources](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md)
161
162
-- [Azure SQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md)
162
+- [Azure SQL](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md)
163
164
-- [Azure Service Bus](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md)
164
+- [Azure Service Bus](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md)
165
166
-- [Azure application](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md)
166
+- [Azure application](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md)
167
168
-- [BigQuery](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md)
168
+- [BigQuery](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md)
169
170
-- [CloudWatch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md)
170
+- [CloudWatch](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md)
171
172
-- [Dell EMC ECS cluster](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md)
172
+- [Dell EMC ECS cluster](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md)
173
174
-- [DigitalOcean](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md)
174
+- [DigitalOcean](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md)
175
176
-- [GCP GCE](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md)
176
+- [GCP GCE](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md)
177
178
-- [GCP Quota](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md)
178
+- [GCP Quota](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md)
179
180
-- [Google Cloud Platform](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md)
180
+- [Google Cloud Platform](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md)
181
182
-- [Google Stackdriver](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md)
182
+- [Google Stackdriver](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md)
183
184
-- [Linode](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md)
184
+- [Linode](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md)
185
186
-- [Lustre metadata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md)
186
+- [Lustre metadata](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md)
187
188
-- [Nextcloud servers](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md)
188
+- [Nextcloud servers](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md)
189
190
-- [OpenStack](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md)
190
+- [OpenStack](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md)
191
192
-- [Zerto](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md)
192
+- [Zerto](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md)
193
194
### Containers and VMs
195
196
-- [Containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/containers.md)
196
+- [Containers](/src/collectors/cgroups.plugin/integrations/containers.md)
197
198
-- [Docker Engine](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/docker_engine/integrations/docker_engine.md)
198
+- [Docker Engine](/src/go/collectors/go.d.plugin/modules/docker_engine/integrations/docker_engine.md)
199
200
-- [Docker Hub repository](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/dockerhub/integrations/docker_hub_repository.md)
200
+- [Docker Hub repository](/src/go/collectors/go.d.plugin/modules/dockerhub/integrations/docker_hub_repository.md)
201
202
-- [Docker](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/docker/integrations/docker.md)
202
+- [Docker](/src/go/collectors/go.d.plugin/modules/docker/integrations/docker.md)
203
204
-- [LXC Containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/lxc_containers.md)
204
+- [LXC Containers](/src/collectors/cgroups.plugin/integrations/lxc_containers.md)
205
206
-- [Libvirt Containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/libvirt_containers.md)
206
+- [Libvirt Containers](/src/collectors/cgroups.plugin/integrations/libvirt_containers.md)
207
208
-- [NSX-T](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md)
208
+- [NSX-T](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md)
209
210
-- [Podman](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md)
210
+- [Podman](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md)
211
212
-- [Proxmox Containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/proxmox_containers.md)
212
+- [Proxmox Containers](/src/collectors/cgroups.plugin/integrations/proxmox_containers.md)
213
214
-- [Proxmox VE](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md)
214
+- [Proxmox VE](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md)
215
216
-- [VMware vCenter Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/vsphere/integrations/vmware_vcenter_server.md)
216
+- [VMware vCenter Server](/src/go/collectors/go.d.plugin/modules/vsphere/integrations/vmware_vcenter_server.md)
217
218
-- [Virtual Machines](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/virtual_machines.md)
218
+- [Virtual Machines](/src/collectors/cgroups.plugin/integrations/virtual_machines.md)
219
220
-- [Xen XCP-ng](https://github.com/netdata/netdata/blob/master/src/collectors/xenstat.plugin/integrations/xen_xcp-ng.md)
220
+- [Xen XCP-ng](/src/collectors/xenstat.plugin/integrations/xen_xcp-ng.md)
221
222
-- [cAdvisor](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md)
222
+- [cAdvisor](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md)
223
224
-- [oVirt Containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/ovirt_containers.md)
224
+- [oVirt Containers](/src/collectors/cgroups.plugin/integrations/ovirt_containers.md)
225
226
-- [vCenter Server Appliance](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/vcsa/integrations/vcenter_server_appliance.md)
226
+- [vCenter Server Appliance](/src/go/collectors/go.d.plugin/modules/vcsa/integrations/vcenter_server_appliance.md)
227
228
### Databases
229
230
-- [4D Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md)
230
+- [4D Server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md)
231
232
-- [AWS RDS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md)
232
+- [AWS RDS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md)
233
234
-- [Cassandra](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/cassandra/integrations/cassandra.md)
234
+- [Cassandra](/src/go/collectors/go.d.plugin/modules/cassandra/integrations/cassandra.md)
235
236
-- [ClickHouse](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clickhouse.md)
236
+- [ClickHouse](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clickhouse.md)
237
238
-- [ClusterControl CMON](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md)
238
+- [ClusterControl CMON](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md)
239
240
-- [CockroachDB](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/cockroachdb/integrations/cockroachdb.md)
240
+- [CockroachDB](/src/go/collectors/go.d.plugin/modules/cockroachdb/integrations/cockroachdb.md)
241
242
-- [CouchDB](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/couchdb/integrations/couchdb.md)
242
+- [CouchDB](/src/go/collectors/go.d.plugin/modules/couchdb/integrations/couchdb.md)
243
244
-- [Couchbase](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/couchbase/integrations/couchbase.md)
244
+- [Couchbase](/src/go/collectors/go.d.plugin/modules/couchbase/integrations/couchbase.md)
245
246
-- [HANA](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md)
246
+- [HANA](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md)
247
248
-- [Hasura GraphQL Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md)
248
+- [Hasura GraphQL Server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md)
249
250
-- [InfluxDB](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md)
250
+- [InfluxDB](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md)
251
252
-- [Machbase](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md)
252
+- [Machbase](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md)
253
254
-- [MariaDB](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/integrations/mariadb.md)
254
+- [MariaDB](/src/go/collectors/go.d.plugin/modules/mysql/integrations/mariadb.md)
255
256
-- [Memcached (community)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md)
256
+- [Memcached (community)](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md)
257
258
-- [Memcached](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/memcached/integrations/memcached.md)
258
+- [Memcached](/src/collectors/python.d.plugin/memcached/integrations/memcached.md)
259
260
-- [MongoDB](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mongodb/integrations/mongodb.md)
260
+- [MongoDB](/src/go/collectors/go.d.plugin/modules/mongodb/integrations/mongodb.md)
261
262
-- [MySQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/integrations/mysql.md)
262
+- [MySQL](/src/go/collectors/go.d.plugin/modules/mysql/integrations/mysql.md)
263
264
-- [ODBC](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md)
264
+- [ODBC](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md)
265
266
-- [Oracle DB (community)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md)
266
+- [Oracle DB (community)](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md)
267
268
-- [Oracle DB](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/oracledb/integrations/oracle_db.md)
268
+- [Oracle DB](/src/collectors/python.d.plugin/oracledb/integrations/oracle_db.md)
269
270
-- [Patroni](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md)
270
+- [Patroni](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md)
271
272
-- [Percona MySQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/mysql/integrations/percona_mysql.md)
272
+- [Percona MySQL](/src/go/collectors/go.d.plugin/modules/mysql/integrations/percona_mysql.md)
273
274
-- [PgBouncer](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/pgbouncer/integrations/pgbouncer.md)
274
+- [PgBouncer](/src/go/collectors/go.d.plugin/modules/pgbouncer/integrations/pgbouncer.md)
275
276
-- [Pgpool-II](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md)
276
+- [Pgpool-II](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md)
277
278
-- [Pika](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/pika/integrations/pika.md)
278
+- [Pika](/src/go/collectors/go.d.plugin/modules/pika/integrations/pika.md)
279
280
-- [PostgreSQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/postgres/integrations/postgresql.md)
280
+- [PostgreSQL](/src/go/collectors/go.d.plugin/modules/postgres/integrations/postgresql.md)
281
282
-- [ProxySQL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/proxysql/integrations/proxysql.md)
282
+- [ProxySQL](/src/go/collectors/go.d.plugin/modules/proxysql/integrations/proxysql.md)
283
284
-- [Redis](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/redis/integrations/redis.md)
284
+- [Redis](/src/go/collectors/go.d.plugin/modules/redis/integrations/redis.md)
285
286
-- [RethinkDB](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/rethinkdbs/integrations/rethinkdb.md)
286
+- [RethinkDB](/src/collectors/python.d.plugin/rethinkdbs/integrations/rethinkdb.md)
287
288
-- [RiakKV](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/riakkv/integrations/riakkv.md)
288
+- [RiakKV](/src/collectors/python.d.plugin/riakkv/integrations/riakkv.md)
289
290
-- [SQL Database agnostic](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md)
290
+- [SQL Database agnostic](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md)
291
292
-- [Vertica](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md)
292
+- [Vertica](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md)
293
294
-- [Warp10](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md)
294
+- [Warp10](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md)
295
296
-- [pgBackRest](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md)
296
+- [pgBackRest](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md)
297
298
### Distributed Computing Systems
299
300
-- [BOINC](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/boinc/integrations/boinc.md)
300
+- [BOINC](/src/collectors/python.d.plugin/boinc/integrations/boinc.md)
301
302
-- [Gearman](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/gearman/integrations/gearman.md)
302
+- [Gearman](/src/collectors/python.d.plugin/gearman/integrations/gearman.md)
303
304
### DNS and DHCP Servers
305
306
-- [Akamai Edge DNS Traffic](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md)
306
+- [Akamai Edge DNS Traffic](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md)
307
308
-- [CoreDNS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/coredns/integrations/coredns.md)
308
+- [CoreDNS](/src/go/collectors/go.d.plugin/modules/coredns/integrations/coredns.md)
309
310
-- [DNS query](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/dnsquery/integrations/dns_query.md)
310
+- [DNS query](/src/go/collectors/go.d.plugin/modules/dnsquery/integrations/dns_query.md)
311
312
-- [DNSBL](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md)
312
+- [DNSBL](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md)
313
314
-- [DNSdist](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/dnsdist/integrations/dnsdist.md)
314
+- [DNSdist](/src/go/collectors/go.d.plugin/modules/dnsdist/integrations/dnsdist.md)
315
316
-- [Dnsmasq DHCP](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md)
316
+- [Dnsmasq DHCP](/src/go/collectors/go.d.plugin/modules/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md)
317
318
-- [Dnsmasq](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/dnsmasq/integrations/dnsmasq.md)
318
+- [Dnsmasq](/src/go/collectors/go.d.plugin/modules/dnsmasq/integrations/dnsmasq.md)
319
320
-- [ISC DHCP](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/isc_dhcpd/integrations/isc_dhcp.md)
320
+- [ISC DHCP](/src/go/collectors/go.d.plugin/modules/isc_dhcpd/integrations/isc_dhcp.md)
321
322
-- [Name Server Daemon](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/nsd/integrations/name_server_daemon.md)
322
+- [Name Server Daemon](/src/collectors/python.d.plugin/nsd/integrations/name_server_daemon.md)
323
324
-- [NextDNS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md)
324
+- [NextDNS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md)
325
326
-- [Pi-hole](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/pihole/integrations/pi-hole.md)
326
+- [Pi-hole](/src/go/collectors/go.d.plugin/modules/pihole/integrations/pi-hole.md)
327
328
-- [PowerDNS Authoritative Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/powerdns/integrations/powerdns_authoritative_server.md)
328
+- [PowerDNS Authoritative Server](/src/go/collectors/go.d.plugin/modules/powerdns/integrations/powerdns_authoritative_server.md)
329
330
-- [PowerDNS Recursor](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/powerdns_recursor/integrations/powerdns_recursor.md)
330
+- [PowerDNS Recursor](/src/go/collectors/go.d.plugin/modules/powerdns_recursor/integrations/powerdns_recursor.md)
331
332
-- [Unbound](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/unbound/integrations/unbound.md)
332
+- [Unbound](/src/go/collectors/go.d.plugin/modules/unbound/integrations/unbound.md)
333
334
### eBPF
335
336
-- [eBPF Cachestat](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_cachestat.md)
336
+- [eBPF Cachestat](/src/collectors/ebpf.plugin/integrations/ebpf_cachestat.md)
337
338
-- [eBPF DCstat](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_dcstat.md)
338
+- [eBPF DCstat](/src/collectors/ebpf.plugin/integrations/ebpf_dcstat.md)
339
340
-- [eBPF Disk](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_disk.md)
340
+- [eBPF Disk](/src/collectors/ebpf.plugin/integrations/ebpf_disk.md)
341
342
-- [eBPF Filedescriptor](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_filedescriptor.md)
342
+- [eBPF Filedescriptor](/src/collectors/ebpf.plugin/integrations/ebpf_filedescriptor.md)
343
344
-- [eBPF Filesystem](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_filesystem.md)
344
+- [eBPF Filesystem](/src/collectors/ebpf.plugin/integrations/ebpf_filesystem.md)
345
346
-- [eBPF Hardirq](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_hardirq.md)
346
+- [eBPF Hardirq](/src/collectors/ebpf.plugin/integrations/ebpf_hardirq.md)
347
348
-- [eBPF MDflush](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_mdflush.md)
348
+- [eBPF MDflush](/src/collectors/ebpf.plugin/integrations/ebpf_mdflush.md)
349
350
-- [eBPF Mount](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_mount.md)
350
+- [eBPF Mount](/src/collectors/ebpf.plugin/integrations/ebpf_mount.md)
351
352
-- [eBPF OOMkill](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_oomkill.md)
352
+- [eBPF OOMkill](/src/collectors/ebpf.plugin/integrations/ebpf_oomkill.md)
353
354
-- [eBPF Process](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_process.md)
354
+- [eBPF Process](/src/collectors/ebpf.plugin/integrations/ebpf_process.md)
355
356
-- [eBPF Processes](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_processes.md)
356
+- [eBPF Processes](/src/collectors/ebpf.plugin/integrations/ebpf_processes.md)
357
358
-- [eBPF SHM](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_shm.md)
358
+- [eBPF SHM](/src/collectors/ebpf.plugin/integrations/ebpf_shm.md)
359
360
-- [eBPF SWAP](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_swap.md)
360
+- [eBPF SWAP](/src/collectors/ebpf.plugin/integrations/ebpf_swap.md)
361
362
-- [eBPF Socket](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_socket.md)
362
+- [eBPF Socket](/src/collectors/ebpf.plugin/integrations/ebpf_socket.md)
363
364
-- [eBPF SoftIRQ](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_softirq.md)
364
+- [eBPF SoftIRQ](/src/collectors/ebpf.plugin/integrations/ebpf_softirq.md)
365
366
-- [eBPF Sync](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_sync.md)
366
+- [eBPF Sync](/src/collectors/ebpf.plugin/integrations/ebpf_sync.md)
367
368
-- [eBPF VFS](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/integrations/ebpf_vfs.md)
368
+- [eBPF VFS](/src/collectors/ebpf.plugin/integrations/ebpf_vfs.md)
369
370
### FreeBSD
371
372
-- [FreeBSD NFS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md)
372
+- [FreeBSD NFS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md)
373
374
-- [FreeBSD RCTL-RACCT](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md)
374
+- [FreeBSD RCTL-RACCT](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md)
375
376
-- [dev.cpu.0.freq](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md)
376
+- [dev.cpu.0.freq](/src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md)
377
378
-- [dev.cpu.temperature](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/dev.cpu.temperature.md)
378
+- [dev.cpu.temperature](/src/collectors/freebsd.plugin/integrations/dev.cpu.temperature.md)
379
380
-- [devstat](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/devstat.md)
380
+- [devstat](/src/collectors/freebsd.plugin/integrations/devstat.md)
381
382
-- [getifaddrs](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/getifaddrs.md)
382
+- [getifaddrs](/src/collectors/freebsd.plugin/integrations/getifaddrs.md)
383
384
-- [getmntinfo](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/getmntinfo.md)
384
+- [getmntinfo](/src/collectors/freebsd.plugin/integrations/getmntinfo.md)
385
386
-- [hw.intrcnt](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/hw.intrcnt.md)
386
+- [hw.intrcnt](/src/collectors/freebsd.plugin/integrations/hw.intrcnt.md)
387
388
-- [ipfw](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/ipfw.md)
388
+- [ipfw](/src/collectors/freebsd.plugin/integrations/ipfw.md)
389
390
-- [kern.cp_time](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/kern.cp_time.md)
390
+- [kern.cp_time](/src/collectors/freebsd.plugin/integrations/kern.cp_time.md)
391
392
-- [kern.ipc.msq](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/kern.ipc.msq.md)
392
+- [kern.ipc.msq](/src/collectors/freebsd.plugin/integrations/kern.ipc.msq.md)
393
394
-- [kern.ipc.sem](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/kern.ipc.sem.md)
394
+- [kern.ipc.sem](/src/collectors/freebsd.plugin/integrations/kern.ipc.sem.md)
395
396
-- [kern.ipc.shm](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md)
396
+- [kern.ipc.shm](/src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md)
397
398
-- [net.inet.icmp.stats](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet.icmp.stats.md)
398
+- [net.inet.icmp.stats](/src/collectors/freebsd.plugin/integrations/net.inet.icmp.stats.md)
399
400
-- [net.inet.ip.stats](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet.ip.stats.md)
400
+- [net.inet.ip.stats](/src/collectors/freebsd.plugin/integrations/net.inet.ip.stats.md)
401
402
-- [net.inet.tcp.states](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet.tcp.states.md)
402
+- [net.inet.tcp.states](/src/collectors/freebsd.plugin/integrations/net.inet.tcp.states.md)
403
404
-- [net.inet.tcp.stats](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet.tcp.stats.md)
404
+- [net.inet.tcp.stats](/src/collectors/freebsd.plugin/integrations/net.inet.tcp.stats.md)
405
406
-- [net.inet.udp.stats](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet.udp.stats.md)
406
+- [net.inet.udp.stats](/src/collectors/freebsd.plugin/integrations/net.inet.udp.stats.md)
407
408
-- [net.inet6.icmp6.stats](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet6.icmp6.stats.md)
408
+- [net.inet6.icmp6.stats](/src/collectors/freebsd.plugin/integrations/net.inet6.icmp6.stats.md)
409
410
-- [net.inet6.ip6.stats](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.inet6.ip6.stats.md)
410
+- [net.inet6.ip6.stats](/src/collectors/freebsd.plugin/integrations/net.inet6.ip6.stats.md)
411
412
-- [net.isr](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/net.isr.md)
412
+- [net.isr](/src/collectors/freebsd.plugin/integrations/net.isr.md)
413
414
-- [system.ram](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/system.ram.md)
414
+- [system.ram](/src/collectors/freebsd.plugin/integrations/system.ram.md)
415
416
-- [uptime](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/uptime.md)
416
+- [uptime](/src/collectors/freebsd.plugin/integrations/uptime.md)
417
418
-- [vm.loadavg](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.loadavg.md)
418
+- [vm.loadavg](/src/collectors/freebsd.plugin/integrations/vm.loadavg.md)
419
420
-- [vm.stats.sys.v_intr](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_intr.md)
420
+- [vm.stats.sys.v_intr](/src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_intr.md)
421
422
-- [vm.stats.sys.v_soft](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_soft.md)
422
+- [vm.stats.sys.v_soft](/src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_soft.md)
423
424
-- [vm.stats.sys.v_swtch](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_swtch.md)
424
+- [vm.stats.sys.v_swtch](/src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_swtch.md)
425
426
-- [vm.stats.vm.v_pgfaults](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_pgfaults.md)
426
+- [vm.stats.vm.v_pgfaults](/src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_pgfaults.md)
427
428
-- [vm.stats.vm.v_swappgs](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_swappgs.md)
428
+- [vm.stats.vm.v_swappgs](/src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_swappgs.md)
429
430
-- [vm.swap_info](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.swap_info.md)
430
+- [vm.swap_info](/src/collectors/freebsd.plugin/integrations/vm.swap_info.md)
431
432
-- [vm.vmtotal](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/vm.vmtotal.md)
432
+- [vm.vmtotal](/src/collectors/freebsd.plugin/integrations/vm.vmtotal.md)
433
434
-- [zfs](https://github.com/netdata/netdata/blob/master/src/collectors/freebsd.plugin/integrations/zfs.md)
434
+- [zfs](/src/collectors/freebsd.plugin/integrations/zfs.md)
435
436
### FTP Servers
437
438
-- [ProFTPD](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md)
438
+- [ProFTPD](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md)
439
440
### Gaming
441
442
-- [BungeeCord](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md)
442
+- [BungeeCord](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md)
443
444
-- [Minecraft](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md)
444
+- [Minecraft](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md)
445
446
-- [OpenRCT2](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md)
446
+- [OpenRCT2](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md)
447
448
-- [SpigotMC](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/spigotmc/integrations/spigotmc.md)
448
+- [SpigotMC](/src/collectors/python.d.plugin/spigotmc/integrations/spigotmc.md)
449
450
-- [Steam](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md)
450
+- [Steam](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md)
451
452
### Generic Data Collection
453
454
-- [Custom Exporter](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md)
454
+- [Custom Exporter](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md)
455
456
-- [Excel spreadsheet](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md)
456
+- [Excel spreadsheet](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md)
457
458
-- [Generic Command Line Output](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md)
458
+- [Generic Command Line Output](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md)
459
460
-- [JetBrains Floating License Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md)
460
+- [JetBrains Floating License Server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md)
461
462
-- [OpenWeatherMap](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md)
462
+- [OpenWeatherMap](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md)
463
464
-- [Pandas](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/pandas/integrations/pandas.md)
464
+- [Pandas](/src/collectors/python.d.plugin/pandas/integrations/pandas.md)
465
466
-- [Prometheus endpoint](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md)
466
+- [Prometheus endpoint](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md)
467
468
-- [SNMP devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/snmp/integrations/snmp_devices.md)
468
+- [SNMP devices](/src/go/collectors/go.d.plugin/modules/snmp/integrations/snmp_devices.md)
469
470
-- [Shell command](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md)
470
+- [Shell command](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md)
471
472
-- [Tankerkoenig API](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md)
472
+- [Tankerkoenig API](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md)
473
474
-- [TwinCAT ADS Web Service](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md)
474
+- [TwinCAT ADS Web Service](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md)
475
476
### Hardware Devices and Sensors
477
478
-- [1-Wire Sensors](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/w1sensor/integrations/1-wire_sensors.md)
478
+- [1-Wire Sensors](/src/collectors/python.d.plugin/w1sensor/integrations/1-wire_sensors.md)
479
480
-- [AM2320](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/am2320/integrations/am2320.md)
480
+- [AM2320](/src/collectors/python.d.plugin/am2320/integrations/am2320.md)
481
482
-- [AMD CPU & GPU](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md)
482
+- [AMD CPU & GPU](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md)
483
484
-- [AMD GPU](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/amd_gpu.md)
484
+- [AMD GPU](/src/collectors/proc.plugin/integrations/amd_gpu.md)
485
486
-- [ARM HWCPipe](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md)
486
+- [ARM HWCPipe](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md)
487
488
-- [CUPS](https://github.com/netdata/netdata/blob/master/src/collectors/cups.plugin/integrations/cups.md)
488
+- [CUPS](/src/collectors/cups.plugin/integrations/cups.md)
489
490
-- [HDD temperature](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/hddtemp/integrations/hdd_temperature.md)
490
+- [HDD temperature](/src/go/collectors/go.d.plugin/modules/hddtemp/integrations/hdd_temperature.md)
491
492
-- [HP iLO](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md)
492
+- [HP iLO](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md)
493
494
-- [IBM CryptoExpress (CEX) cards](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md)
494
+- [IBM CryptoExpress (CEX) cards](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md)
495
496
-- [IBM Z Hardware Management Console](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md)
496
+- [IBM Z Hardware Management Console](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md)
497
498
-- [IPMI (By SoundCloud)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md)
498
+- [IPMI (By SoundCloud)](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md)
499
500
-- [Intel GPU](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/intelgpu/integrations/intel_gpu.md)
500
+- [Intel GPU](/src/go/collectors/go.d.plugin/modules/intelgpu/integrations/intel_gpu.md)
501
502
-- [Intelligent Platform Management Interface (IPMI)](https://github.com/netdata/netdata/blob/master/src/collectors/freeipmi.plugin/integrations/intelligent_platform_management_interface_ipmi.md)
502
+- [Intelligent Platform Management Interface (IPMI)](/src/collectors/freeipmi.plugin/integrations/intelligent_platform_management_interface_ipmi.md)
503
504
-- [Linux Sensors (lm-sensors)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/sensors/integrations/linux_sensors_lm-sensors.md)
504
+- [Linux Sensors (lm-sensors)](/src/go/collectors/go.d.plugin/modules/sensors/integrations/linux_sensors_lm-sensors.md)
505
506
-- [Linux Sensors (sysfs)](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/sensors/integrations/linux_sensors_sysfs.md)
506
+- [Linux Sensors (sysfs)](/src/collectors/charts.d.plugin/sensors/integrations/linux_sensors_sysfs.md)
507
508
-- [NVML](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md)
508
+- [NVML](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md)
509
510
-- [Nvidia GPU](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nvidia_smi/integrations/nvidia_gpu.md)
510
+- [Nvidia GPU](/src/go/collectors/go.d.plugin/modules/nvidia_smi/integrations/nvidia_gpu.md)
511
512
-- [Raritan PDU](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md)
512
+- [Raritan PDU](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md)
513
514
-- [S.M.A.R.T.](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/smartctl/integrations/s.m.a.r.t..md)
514
+- [S.M.A.R.T.](/src/go/collectors/go.d.plugin/modules/smartctl/integrations/s.m.a.r.t..md)
515
516
-- [ServerTech](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md)
516
+- [ServerTech](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md)
517
518
-- [Siemens S7 PLC](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md)
518
+- [Siemens S7 PLC](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md)
519
520
-- [T-Rex NVIDIA GPU Miner](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md)
520
+- [T-Rex NVIDIA GPU Miner](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md)
521
522
### IoT Devices
523
524
-- [Airthings Waveplus air sensor](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md)
524
+- [Airthings Waveplus air sensor](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md)
525
526
-- [Bobcat Miner 300](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md)
526
+- [Bobcat Miner 300](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md)
527
528
-- [Christ Elektronik CLM5IP power panel](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md)
528
+- [Christ Elektronik CLM5IP power panel](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md)
529
530
-- [CraftBeerPi](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md)
530
+- [CraftBeerPi](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md)
531
532
-- [Dutch Electricity Smart Meter](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md)
532
+- [Dutch Electricity Smart Meter](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md)
533
534
-- [Elgato Key Light devices.](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md)
534
+- [Elgato Key Light devices.](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md)
535
536
-- [Energomera smart power meters](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md)
536
+- [Energomera smart power meters](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md)
537
538
-- [Helium hotspot](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md)
538
+- [Helium hotspot](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md)
539
540
-- [Homebridge](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md)
540
+- [Homebridge](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md)
541
542
-- [Homey](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md)
542
+- [Homey](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md)
543
544
-- [Jarvis Standing Desk](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md)
544
+- [Jarvis Standing Desk](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md)
545
546
-- [MP707 USB thermometer](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md)
546
+- [MP707 USB thermometer](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md)
547
548
-- [Modbus protocol](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md)
548
+- [Modbus protocol](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md)
549
550
-- [Monnit Sensors MQTT](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md)
550
+- [Monnit Sensors MQTT](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md)
551
552
-- [Nature Remo E lite devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md)
552
+- [Nature Remo E lite devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md)
553
554
-- [Netatmo sensors](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md)
554
+- [Netatmo sensors](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md)
555
556
-- [OpenHAB](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md)
556
+- [OpenHAB](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md)
557
558
-- [Personal Weather Station](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md)
558
+- [Personal Weather Station](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md)
559
560
-- [Philips Hue](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md)
560
+- [Philips Hue](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md)
561
562
-- [Pimoroni Enviro+](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md)
562
+- [Pimoroni Enviro+](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md)
563
564
-- [Powerpal devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md)
564
+- [Powerpal devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md)
565
566
-- [Radio Thermostat](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md)
566
+- [Radio Thermostat](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md)
567
568
-- [SMA Inverters](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md)
568
+- [SMA Inverters](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md)
569
570
-- [Salicru EQX inverter](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md)
570
+- [Salicru EQX inverter](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md)
571
572
-- [Sense Energy](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md)
572
+- [Sense Energy](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md)
573
574
-- [Shelly humidity sensor](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md)
574
+- [Shelly humidity sensor](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md)
575
576
-- [Smart meters SML](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md)
576
+- [Smart meters SML](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md)
577
578
-- [Solar logging stick](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md)
578
+- [Solar logging stick](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md)
579
580
-- [SolarEdge inverters](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md)
580
+- [SolarEdge inverters](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md)
581
582
-- [Solis Ginlong 5G inverters](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md)
582
+- [Solis Ginlong 5G inverters](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md)
583
584
-- [Sunspec Solar Energy](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md)
584
+- [Sunspec Solar Energy](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md)
585
586
-- [TP-Link P110](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md)
586
+- [TP-Link P110](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md)
587
588
-- [Tado smart heating solution](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md)
588
+- [Tado smart heating solution](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md)
589
590
-- [Tesla Powerwall](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md)
590
+- [Tesla Powerwall](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md)
591
592
-- [Tesla Wall Connector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md)
592
+- [Tesla Wall Connector](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md)
593
594
-- [Tesla vehicle](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md)
594
+- [Tesla vehicle](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md)
595
596
-- [Xiaomi Mi Flora](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md)
596
+- [Xiaomi Mi Flora](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md)
597
598
-- [iqAir AirVisual air quality monitors](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md)
598
+- [iqAir AirVisual air quality monitors](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md)
599
600
### Kubernetes
601
602
-- [Cilium Agent](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md)
602
+- [Cilium Agent](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md)
603
604
-- [Cilium Operator](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md)
604
+- [Cilium Operator](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md)
605
606
-- [Cilium Proxy](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md)
606
+- [Cilium Proxy](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md)
607
608
-- [Kubelet](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubelet/integrations/kubelet.md)
608
+- [Kubelet](/src/go/collectors/go.d.plugin/modules/k8s_kubelet/integrations/kubelet.md)
609
610
-- [Kubeproxy](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/integrations/kubeproxy.md)
610
+- [Kubeproxy](/src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/integrations/kubeproxy.md)
611
612
-- [Kubernetes Cluster Cloud Cost](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md)
612
+- [Kubernetes Cluster Cloud Cost](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md)
613
614
-- [Kubernetes Cluster State](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/k8s_state/integrations/kubernetes_cluster_state.md)
614
+- [Kubernetes Cluster State](/src/go/collectors/go.d.plugin/modules/k8s_state/integrations/kubernetes_cluster_state.md)
615
616
-- [Kubernetes Containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/kubernetes_containers.md)
616
+- [Kubernetes Containers](/src/collectors/cgroups.plugin/integrations/kubernetes_containers.md)
617
618
-- [Rancher](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md)
618
+- [Rancher](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md)
619
620
### Linux Systems
621
622
-- [CPU performance](https://github.com/netdata/netdata/blob/master/src/collectors/perf.plugin/integrations/cpu_performance.md)
622
+- [CPU performance](/src/collectors/perf.plugin/integrations/cpu_performance.md)
623
624
-- [Disk space](https://github.com/netdata/netdata/blob/master/src/collectors/diskspace.plugin/integrations/disk_space.md)
624
+- [Disk space](/src/collectors/diskspace.plugin/integrations/disk_space.md)
625
626
-- [Files and directories](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/filecheck/integrations/files_and_directories.md)
626
+- [Files and directories](/src/go/collectors/go.d.plugin/modules/filecheck/integrations/files_and_directories.md)
627
628
-- [OpenRC](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md)
628
+- [OpenRC](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md)
629
630
#### CPU
631
632
-- [Interrupts](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/interrupts.md)
632
+- [Interrupts](/src/collectors/proc.plugin/integrations/interrupts.md)
633
634
-- [SoftIRQ statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/softirq_statistics.md)
634
+- [SoftIRQ statistics](/src/collectors/proc.plugin/integrations/softirq_statistics.md)
635
636
#### Disk
637
638
-- [Disk Statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/disk_statistics.md)
638
+- [Disk Statistics](/src/collectors/proc.plugin/integrations/disk_statistics.md)
639
640
-- [MD RAID](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/md_raid.md)
640
+- [MD RAID](/src/collectors/proc.plugin/integrations/md_raid.md)
641
642
##### BTRFS
643
644
-- [BTRFS](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/btrfs.md)
644
+- [BTRFS](/src/collectors/proc.plugin/integrations/btrfs.md)
645
646
##### NFS
647
648
-- [NFS Client](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/nfs_client.md)
648
+- [NFS Client](/src/collectors/proc.plugin/integrations/nfs_client.md)
649
650
-- [NFS Server](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/nfs_server.md)
650
+- [NFS Server](/src/collectors/proc.plugin/integrations/nfs_server.md)
651
652
##### ZFS
653
654
-- [ZFS Adaptive Replacement Cache](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/zfs_adaptive_replacement_cache.md)
654
+- [ZFS Adaptive Replacement Cache](/src/collectors/proc.plugin/integrations/zfs_adaptive_replacement_cache.md)
655
656
-- [ZFS Pools](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/zfs_pools.md)
656
+- [ZFS Pools](/src/collectors/proc.plugin/integrations/zfs_pools.md)
657
658
#### Firewall
659
660
-- [Conntrack](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/conntrack.md)
660
+- [Conntrack](/src/collectors/proc.plugin/integrations/conntrack.md)
661
662
-- [Netfilter](https://github.com/netdata/netdata/blob/master/src/collectors/nfacct.plugin/integrations/netfilter.md)
662
+- [Netfilter](/src/collectors/nfacct.plugin/integrations/netfilter.md)
663
664
-- [Synproxy](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/synproxy.md)
664
+- [Synproxy](/src/collectors/proc.plugin/integrations/synproxy.md)
665
666
-- [nftables](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md)
666
+- [nftables](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md)
667
668
#### IPC
669
670
-- [Inter Process Communication](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/inter_process_communication.md)
670
+- [Inter Process Communication](/src/collectors/proc.plugin/integrations/inter_process_communication.md)
671
672
#### Kernel
673
674
-- [Linux kernel SLAB allocator statistics](https://github.com/netdata/netdata/blob/master/src/collectors/slabinfo.plugin/integrations/linux_kernel_slab_allocator_statistics.md)
674
+- [Linux kernel SLAB allocator statistics](/src/collectors/slabinfo.plugin/integrations/linux_kernel_slab_allocator_statistics.md)
675
676
-- [Power Capping](https://github.com/netdata/netdata/blob/master/src/collectors/debugfs.plugin/integrations/power_capping.md)
676
+- [Power Capping](/src/collectors/debugfs.plugin/integrations/power_capping.md)
677
678
#### Memory
679
680
-- [Kernel Same-Page Merging](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/kernel_same-page_merging.md)
680
+- [Kernel Same-Page Merging](/src/collectors/proc.plugin/integrations/kernel_same-page_merging.md)
681
682
-- [Linux ZSwap](https://github.com/netdata/netdata/blob/master/src/collectors/debugfs.plugin/integrations/linux_zswap.md)
682
+- [Linux ZSwap](/src/collectors/debugfs.plugin/integrations/linux_zswap.md)
683
684
-- [Memory Statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/memory_statistics.md)
684
+- [Memory Statistics](/src/collectors/proc.plugin/integrations/memory_statistics.md)
685
686
-- [Memory Usage](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/memory_usage.md)
686
+- [Memory Usage](/src/collectors/proc.plugin/integrations/memory_usage.md)
687
688
-- [Memory modules (DIMMs)](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/memory_modules_dimms.md)
688
+- [Memory modules (DIMMs)](/src/collectors/proc.plugin/integrations/memory_modules_dimms.md)
689
690
-- [Non-Uniform Memory Access](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/non-uniform_memory_access.md)
690
+- [Non-Uniform Memory Access](/src/collectors/proc.plugin/integrations/non-uniform_memory_access.md)
691
692
-- [Page types](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/page_types.md)
692
+- [Page types](/src/collectors/proc.plugin/integrations/page_types.md)
693
694
-- [System Memory Fragmentation](https://github.com/netdata/netdata/blob/master/src/collectors/debugfs.plugin/integrations/system_memory_fragmentation.md)
694
+- [System Memory Fragmentation](/src/collectors/debugfs.plugin/integrations/system_memory_fragmentation.md)
695
696
-- [ZRAM](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/zram.md)
696
+- [ZRAM](/src/collectors/proc.plugin/integrations/zram.md)
697
698
#### Network
699
700
-- [Access Points](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/ap/integrations/access_points.md)
700
+- [Access Points](/src/collectors/charts.d.plugin/ap/integrations/access_points.md)
701
702
-- [IP Virtual Server](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/ip_virtual_server.md)
702
+- [IP Virtual Server](/src/collectors/proc.plugin/integrations/ip_virtual_server.md)
703
704
-- [IPv6 Socket Statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/ipv6_socket_statistics.md)
704
+- [IPv6 Socket Statistics](/src/collectors/proc.plugin/integrations/ipv6_socket_statistics.md)
705
706
-- [InfiniBand](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/infiniband.md)
706
+- [InfiniBand](/src/collectors/proc.plugin/integrations/infiniband.md)
707
708
-- [Network interfaces](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/network_interfaces.md)
708
+- [Network interfaces](/src/collectors/proc.plugin/integrations/network_interfaces.md)
709
710
-- [Network statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/network_statistics.md)
710
+- [Network statistics](/src/collectors/proc.plugin/integrations/network_statistics.md)
711
712
-- [SCTP Statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/sctp_statistics.md)
712
+- [SCTP Statistics](/src/collectors/proc.plugin/integrations/sctp_statistics.md)
713
714
-- [Socket statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/socket_statistics.md)
714
+- [Socket statistics](/src/collectors/proc.plugin/integrations/socket_statistics.md)
715
716
-- [Softnet Statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/softnet_statistics.md)
716
+- [Softnet Statistics](/src/collectors/proc.plugin/integrations/softnet_statistics.md)
717
718
-- [Wireless network interfaces](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/wireless_network_interfaces.md)
718
+- [Wireless network interfaces](/src/collectors/proc.plugin/integrations/wireless_network_interfaces.md)
719
720
-- [tc QoS classes](https://github.com/netdata/netdata/blob/master/src/collectors/tc.plugin/integrations/tc_qos_classes.md)
720
+- [tc QoS classes](/src/collectors/tc.plugin/integrations/tc_qos_classes.md)
721
722
#### Power Supply
723
724
-- [Power Supply](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/power_supply.md)
724
+- [Power Supply](/src/collectors/proc.plugin/integrations/power_supply.md)
725
726
#### Pressure
727
728
-- [Pressure Stall Information](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/pressure_stall_information.md)
728
+- [Pressure Stall Information](/src/collectors/proc.plugin/integrations/pressure_stall_information.md)
729
730
#### System
731
732
-- [Entropy](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/entropy.md)
732
+- [Entropy](/src/collectors/proc.plugin/integrations/entropy.md)
733
734
-- [System Load Average](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/system_load_average.md)
734
+- [System Load Average](/src/collectors/proc.plugin/integrations/system_load_average.md)
735
736
-- [System Uptime](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/system_uptime.md)
736
+- [System Uptime](/src/collectors/proc.plugin/integrations/system_uptime.md)
737
738
-- [System statistics](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/integrations/system_statistics.md)
738
+- [System statistics](/src/collectors/proc.plugin/integrations/system_statistics.md)
739
740
### Logs Servers
741
742
-- [AuthLog](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md)
742
+- [AuthLog](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md)
743
744
-- [Fluentd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/fluentd/integrations/fluentd.md)
744
+- [Fluentd](/src/go/collectors/go.d.plugin/modules/fluentd/integrations/fluentd.md)
745
746
-- [Graylog Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md)
746
+- [Graylog Server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md)
747
748
-- [Logstash](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/logstash/integrations/logstash.md)
748
+- [Logstash](/src/go/collectors/go.d.plugin/modules/logstash/integrations/logstash.md)
749
750
-- [journald](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md)
750
+- [journald](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md)
751
752
-- [loki](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md)
752
+- [loki](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md)
753
754
-- [mtail](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md)
754
+- [mtail](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md)
755
756
### macOS Systems
757
758
-- [Apple Time Machine](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md)
758
+- [Apple Time Machine](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md)
759
760
-- [macOS](https://github.com/netdata/netdata/blob/master/src/collectors/macos.plugin/integrations/macos.md)
760
+- [macOS](/src/collectors/macos.plugin/integrations/macos.md)
761
762
### Mail Servers
763
764
-- [DMARC](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md)
764
+- [DMARC](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md)
765
766
-- [Dovecot](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/dovecot/integrations/dovecot.md)
766
+- [Dovecot](/src/collectors/python.d.plugin/dovecot/integrations/dovecot.md)
767
768
-- [Exim](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/exim/integrations/exim.md)
768
+- [Exim](/src/collectors/python.d.plugin/exim/integrations/exim.md)
769
770
-- [Halon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md)
770
+- [Halon](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md)
771
772
-- [Maildir](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md)
772
+- [Maildir](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md)
773
774
-- [Postfix](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/postfix/integrations/postfix.md)
774
+- [Postfix](/src/collectors/python.d.plugin/postfix/integrations/postfix.md)
775
776
### Media Services
777
778
-- [Discourse](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md)
778
+- [Discourse](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md)
779
780
-- [Icecast](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/icecast/integrations/icecast.md)
780
+- [Icecast](/src/collectors/python.d.plugin/icecast/integrations/icecast.md)
781
782
-- [OBS Studio](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md)
782
+- [OBS Studio](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md)
783
784
-- [RetroShare](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/retroshare/integrations/retroshare.md)
784
+- [RetroShare](/src/collectors/python.d.plugin/retroshare/integrations/retroshare.md)
785
786
-- [SABnzbd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md)
786
+- [SABnzbd](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md)
787
788
-- [Stream](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md)
788
+- [Stream](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md)
789
790
-- [Twitch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md)
790
+- [Twitch](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md)
791
792
-- [Zulip](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md)
792
+- [Zulip](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md)
793
794
### Message Brokers
795
796
-- [ActiveMQ](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/activemq/integrations/activemq.md)
796
+- [ActiveMQ](/src/go/collectors/go.d.plugin/modules/activemq/integrations/activemq.md)
797
798
-- [Apache Pulsar](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/pulsar/integrations/apache_pulsar.md)
798
+- [Apache Pulsar](/src/go/collectors/go.d.plugin/modules/pulsar/integrations/apache_pulsar.md)
799
800
-- [Beanstalk](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/beanstalk/integrations/beanstalk.md)
800
+- [Beanstalk](/src/collectors/python.d.plugin/beanstalk/integrations/beanstalk.md)
801
802
-- [IBM MQ](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md)
802
+- [IBM MQ](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md)
803
804
-- [Kafka Connect](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md)
804
+- [Kafka Connect](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md)
805
806
-- [Kafka ZooKeeper](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md)
806
+- [Kafka ZooKeeper](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md)
807
808
-- [Kafka](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md)
808
+- [Kafka](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md)
809
810
-- [MQTT Blackbox](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md)
810
+- [MQTT Blackbox](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md)
811
812
-- [RabbitMQ](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/rabbitmq/integrations/rabbitmq.md)
812
+- [RabbitMQ](/src/go/collectors/go.d.plugin/modules/rabbitmq/integrations/rabbitmq.md)
813
814
-- [Redis Queue](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md)
814
+- [Redis Queue](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md)
815
816
-- [VerneMQ](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/vernemq/integrations/vernemq.md)
816
+- [VerneMQ](/src/go/collectors/go.d.plugin/modules/vernemq/integrations/vernemq.md)
817
818
-- [XMPP Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md)
818
+- [XMPP Server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md)
819
820
-- [mosquitto](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md)
820
+- [mosquitto](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md)
821
822
### Networking Stack and Network Interfaces
823
824
-- [8430FT modem](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md)
824
+- [8430FT modem](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md)
825
826
-- [A10 ACOS network devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md)
826
+- [A10 ACOS network devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md)
827
828
-- [Andrews & Arnold line status](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md)
828
+- [Andrews & Arnold line status](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md)
829
830
-- [Aruba devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md)
830
+- [Aruba devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md)
831
832
-- [Bird Routing Daemon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md)
832
+- [Bird Routing Daemon](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md)
833
834
-- [Checkpoint device](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md)
834
+- [Checkpoint device](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md)
835
836
-- [Cisco ACI](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md)
836
+- [Cisco ACI](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md)
837
838
-- [Citrix NetScaler](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md)
838
+- [Citrix NetScaler](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md)
839
840
-- [DDWRT Routers](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md)
840
+- [DDWRT Routers](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md)
841
842
-- [FRRouting](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md)
842
+- [FRRouting](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md)
843
844
-- [Fortigate firewall](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md)
844
+- [Fortigate firewall](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md)
845
846
-- [Freifunk network](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md)
846
+- [Freifunk network](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md)
847
848
-- [Fritzbox network devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md)
848
+- [Fritzbox network devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md)
849
850
-- [Hitron CGN series CPE](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md)
850
+- [Hitron CGN series CPE](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md)
851
852
-- [Hitron CODA Cable Modem](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md)
852
+- [Hitron CODA Cable Modem](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md)
853
854
-- [Huawei devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md)
854
+- [Huawei devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md)
855
856
-- [Keepalived](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md)
856
+- [Keepalived](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md)
857
858
-- [Meraki dashboard](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md)
858
+- [Meraki dashboard](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md)
859
860
-- [MikroTik devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md)
860
+- [MikroTik devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md)
861
862
-- [Mikrotik RouterOS devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md)
862
+- [Mikrotik RouterOS devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md)
863
864
-- [NetFlow](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md)
864
+- [NetFlow](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md)
865
866
-- [NetMeter](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md)
866
+- [NetMeter](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md)
867
868
-- [Open vSwitch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md)
868
+- [Open vSwitch](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md)
869
870
-- [OpenROADM devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md)
870
+- [OpenROADM devices](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md)
871
872
-- [RIPE Atlas](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md)
872
+- [RIPE Atlas](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md)
873
874
-- [SONiC NOS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md)
874
+- [SONiC NOS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md)
875
876
-- [SmartRG 808AC Cable Modem](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md)
876
+- [SmartRG 808AC Cable Modem](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md)
877
878
-- [Starlink (SpaceX)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md)
878
+- [Starlink (SpaceX)](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md)
879
880
-- [Traceroute](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md)
880
+- [Traceroute](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md)
881
882
-- [Ubiquiti UFiber OLT](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md)
882
+- [Ubiquiti UFiber OLT](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md)
883
884
-- [Zyxel GS1200-8](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md)
884
+- [Zyxel GS1200-8](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md)
885
886
### Incident Management
887
888
-- [OTRS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md)
888
+- [OTRS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md)
889
890
-- [StatusPage](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md)
890
+- [StatusPage](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md)
891
892
### Observability
893
894
-- [Collectd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md)
894
+- [Collectd](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md)
895
896
-- [Dynatrace](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md)
896
+- [Dynatrace](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md)
897
898
-- [Grafana](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md)
898
+- [Grafana](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md)
899
900
-- [Hubble](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md)
900
+- [Hubble](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md)
901
902
-- [Naemon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md)
902
+- [Naemon](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md)
903
904
-- [Nagios](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md)
904
+- [Nagios](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md)
905
906
-- [New Relic](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md)
906
+- [New Relic](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md)
907
908
### Other
909
910
-- [Example collector](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/example/integrations/example_collector.md)
910
+- [Example collector](/src/collectors/python.d.plugin/example/integrations/example_collector.md)
911
912
-- [GitHub API rate limit](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md)
912
+- [GitHub API rate limit](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md)
913
914
-- [GitHub repository](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md)
914
+- [GitHub repository](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md)
915
916
-- [Netdata Agent alarms](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/alarms/integrations/netdata_agent_alarms.md)
916
+- [Netdata Agent alarms](/src/collectors/python.d.plugin/alarms/integrations/netdata_agent_alarms.md)
917
918
-- [python.d changefinder](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/changefinder/integrations/python.d_changefinder.md)
918
+- [python.d changefinder](/src/collectors/python.d.plugin/changefinder/integrations/python.d_changefinder.md)
919
920
-- [python.d zscores](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/zscores/integrations/python.d_zscores.md)
920
+- [python.d zscores](/src/collectors/python.d.plugin/zscores/integrations/python.d_zscores.md)
921
922
### Processes and System Services
923
924
-- [Applications](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/integrations/applications.md)
924
+- [Applications](/src/collectors/apps.plugin/integrations/applications.md)
925
926
-- [Supervisor](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/supervisord/integrations/supervisor.md)
926
+- [Supervisor](/src/go/collectors/go.d.plugin/modules/supervisord/integrations/supervisor.md)
927
928
-- [User Groups](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/integrations/user_groups.md)
928
+- [User Groups](/src/collectors/apps.plugin/integrations/user_groups.md)
929
930
-- [Users](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/integrations/users.md)
930
+- [Users](/src/collectors/apps.plugin/integrations/users.md)
931
932
### Provisioning Systems
933
934
-- [BOSH](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md)
934
+- [BOSH](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md)
935
936
-- [Cloud Foundry Firehose](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md)
936
+- [Cloud Foundry Firehose](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md)
937
938
-- [Cloud Foundry](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md)
938
+- [Cloud Foundry](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md)
939
940
-- [Spacelift](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md)
940
+- [Spacelift](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md)
941
942
### Search Engines
943
944
-- [Elasticsearch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/elasticsearch/integrations/elasticsearch.md)
944
+- [Elasticsearch](/src/go/collectors/go.d.plugin/modules/elasticsearch/integrations/elasticsearch.md)
945
946
-- [Meilisearch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md)
946
+- [Meilisearch](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md)
947
948
-- [OpenSearch](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/elasticsearch/integrations/opensearch.md)
948
+- [OpenSearch](/src/go/collectors/go.d.plugin/modules/elasticsearch/integrations/opensearch.md)
949
950
-- [Sphinx](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md)
950
+- [Sphinx](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md)
951
952
### Security Systems
953
954
-- [Certificate Transparency](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md)
954
+- [Certificate Transparency](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md)
955
956
-- [ClamAV daemon](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md)
956
+- [ClamAV daemon](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md)
957
958
-- [Clamscan results](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md)
958
+- [Clamscan results](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md)
959
960
-- [Crowdsec](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md)
960
+- [Crowdsec](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md)
961
962
-- [Honeypot](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md)
962
+- [Honeypot](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md)
963
964
-- [Lynis audit reports](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md)
964
+- [Lynis audit reports](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md)
965
966
-- [OpenVAS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md)
966
+- [OpenVAS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md)
967
968
-- [Rspamd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/rspamd/integrations/rspamd.md)
968
+- [Rspamd](/src/go/collectors/go.d.plugin/modules/rspamd/integrations/rspamd.md)
969
970
-- [SSL Certificate](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md)
970
+- [SSL Certificate](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md)
971
972
-- [Suricata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md)
972
+- [Suricata](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md)
973
974
-- [Vault PKI](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md)
974
+- [Vault PKI](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md)
975
976
### Service Discovery / Registry
977
978
-- [Consul](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/consul/integrations/consul.md)
978
+- [Consul](/src/go/collectors/go.d.plugin/modules/consul/integrations/consul.md)
979
980
-- [Kafka Consumer Lag](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md)
980
+- [Kafka Consumer Lag](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md)
981
982
-- [ZooKeeper](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/zookeeper/integrations/zookeeper.md)
982
+- [ZooKeeper](/src/go/collectors/go.d.plugin/modules/zookeeper/integrations/zookeeper.md)
983
984
-- [etcd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md)
984
+- [etcd](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md)
985
986
### Storage, Mount Points and Filesystems
987
988
-- [Adaptec RAID](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/adaptecraid/integrations/adaptec_raid.md)
988
+- [Adaptec RAID](/src/go/collectors/go.d.plugin/modules/adaptecraid/integrations/adaptec_raid.md)
989
990
-- [Altaro Backup](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md)
990
+- [Altaro Backup](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md)
991
992
-- [Borg backup](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md)
992
+- [Borg backup](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md)
993
994
-- [CVMFS clients](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md)
994
+- [CVMFS clients](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md)
995
996
-- [Ceph](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/ceph/integrations/ceph.md)
996
+- [Ceph](/src/collectors/python.d.plugin/ceph/integrations/ceph.md)
997
998
-- [Dell EMC Isilon cluster](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md)
998
+- [Dell EMC Isilon cluster](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md)
999
1000
-- [Dell EMC ScaleIO](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/scaleio/integrations/dell_emc_scaleio.md)
1000
+- [Dell EMC ScaleIO](/src/go/collectors/go.d.plugin/modules/scaleio/integrations/dell_emc_scaleio.md)
1001
1002
-- [Dell EMC XtremIO cluster](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md)
1002
+- [Dell EMC XtremIO cluster](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md)
1003
1004
-- [Dell PowerMax](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md)
1004
+- [Dell PowerMax](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md)
1005
1006
-- [EOS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md)
1006
+- [EOS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md)
1007
1008
-- [Generic storage enclosure tool](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md)
1008
+- [Generic storage enclosure tool](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md)
1009
1010
-- [HDSentinel](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md)
1010
+- [HDSentinel](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md)
1011
1012
-- [HPE Smart Arrays](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/hpssa/integrations/hpe_smart_arrays.md)
1012
+- [HPE Smart Arrays](/src/go/collectors/go.d.plugin/modules/hpssa/integrations/hpe_smart_arrays.md)
1013
1014
-- [Hadoop Distributed File System (HDFS)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/hdfs/integrations/hadoop_distributed_file_system_hdfs.md)
1014
+- [Hadoop Distributed File System (HDFS)](/src/go/collectors/go.d.plugin/modules/hdfs/integrations/hadoop_distributed_file_system_hdfs.md)
1015
1016
-- [IBM Spectrum Virtualize](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md)
1016
+- [IBM Spectrum Virtualize](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md)
1017
1018
-- [IBM Spectrum](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md)
1018
+- [IBM Spectrum](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md)
1019
1020
-- [IPFS](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/ipfs/integrations/ipfs.md)
1020
+- [IPFS](/src/collectors/python.d.plugin/ipfs/integrations/ipfs.md)
1021
1022
-- [LVM logical volumes](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/lvm/integrations/lvm_logical_volumes.md)
1022
+- [LVM logical volumes](/src/go/collectors/go.d.plugin/modules/lvm/integrations/lvm_logical_volumes.md)
1023
1024
-- [Lagerist Disk latency](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md)
1024
+- [Lagerist Disk latency](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md)
1025
1026
-- [MegaCLI MegaRAID](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/megacli/integrations/megacli_megaraid.md)
1026
+- [MegaCLI MegaRAID](/src/go/collectors/go.d.plugin/modules/megacli/integrations/megacli_megaraid.md)
1027
1028
-- [MogileFS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md)
1028
+- [MogileFS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md)
1029
1030
-- [NVMe devices](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nvme/integrations/nvme_devices.md)
1030
+- [NVMe devices](/src/go/collectors/go.d.plugin/modules/nvme/integrations/nvme_devices.md)
1031
1032
-- [NetApp Solidfire](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md)
1032
+- [NetApp Solidfire](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md)
1033
1034
-- [Netapp ONTAP API](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md)
1034
+- [Netapp ONTAP API](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md)
1035
1036
-- [Samba](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/samba/integrations/samba.md)
1036
+- [Samba](/src/collectors/python.d.plugin/samba/integrations/samba.md)
1037
1038
-- [Starwind VSAN VSphere Edition](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md)
1038
+- [Starwind VSAN VSphere Edition](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md)
1039
1040
-- [StoreCLI RAID](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/storcli/integrations/storecli_raid.md)
1040
+- [StoreCLI RAID](/src/go/collectors/go.d.plugin/modules/storcli/integrations/storecli_raid.md)
1041
1042
-- [Storidge](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md)
1042
+- [Storidge](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md)
1043
1044
-- [Synology ActiveBackup](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md)
1044
+- [Synology ActiveBackup](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md)
1045
1046
-- [ZFS Pools](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/zfspool/integrations/zfs_pools.md)
1046
+- [ZFS Pools](/src/go/collectors/go.d.plugin/modules/zfspool/integrations/zfs_pools.md)
1047
1048
### Synthetic Checks
1049
1050
-- [Blackbox](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md)
1050
+- [Blackbox](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md)
1051
1052
-- [Domain expiration date](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/whoisquery/integrations/domain_expiration_date.md)
1052
+- [Domain expiration date](/src/go/collectors/go.d.plugin/modules/whoisquery/integrations/domain_expiration_date.md)
1053
1054
-- [HTTP Endpoints](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
1054
+- [HTTP Endpoints](/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
1055
1056
-- [IOPing](https://github.com/netdata/netdata/blob/master/src/collectors/ioping.plugin/integrations/ioping.md)
1056
+- [IOPing](/src/collectors/ioping.plugin/integrations/ioping.md)
1057
1058
-- [Idle OS Jitter](https://github.com/netdata/netdata/blob/master/src/collectors/idlejitter.plugin/integrations/idle_os_jitter.md)
1058
+- [Idle OS Jitter](/src/collectors/idlejitter.plugin/integrations/idle_os_jitter.md)
1059
1060
-- [Monit](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/monit/integrations/monit.md)
1060
+- [Monit](/src/collectors/python.d.plugin/monit/integrations/monit.md)
1061
1062
-- [Ping](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/ping/integrations/ping.md)
1062
+- [Ping](/src/go/collectors/go.d.plugin/modules/ping/integrations/ping.md)
1063
1064
-- [Pingdom](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md)
1064
+- [Pingdom](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md)
1065
1066
-- [Site 24x7](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md)
1066
+- [Site 24x7](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md)
1067
1068
-- [TCP Endpoints](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/portcheck/integrations/tcp_endpoints.md)
1068
+- [TCP Endpoints](/src/go/collectors/go.d.plugin/modules/portcheck/integrations/tcp_endpoints.md)
1069
1070
-- [Uptimerobot](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md)
1070
+- [Uptimerobot](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md)
1071
1072
-- [X.509 certificate](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/x509check/integrations/x.509_certificate.md)
1072
+- [X.509 certificate](/src/go/collectors/go.d.plugin/modules/x509check/integrations/x.509_certificate.md)
1073
1074
### System Clock and NTP
1075
1076
-- [Chrony](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/chrony/integrations/chrony.md)
1076
+- [Chrony](/src/go/collectors/go.d.plugin/modules/chrony/integrations/chrony.md)
1077
1078
-- [NTPd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/ntpd/integrations/ntpd.md)
1078
+- [NTPd](/src/go/collectors/go.d.plugin/modules/ntpd/integrations/ntpd.md)
1079
1080
-- [Timex](https://github.com/netdata/netdata/blob/master/src/collectors/timex.plugin/integrations/timex.md)
1080
+- [Timex](/src/collectors/timex.plugin/integrations/timex.md)
1081
1082
### Systemd
1083
1084
-- [Systemd Services](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/integrations/systemd_services.md)
1084
+- [Systemd Services](/src/collectors/cgroups.plugin/integrations/systemd_services.md)
1085
1086
-- [Systemd Units](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/systemdunits/integrations/systemd_units.md)
1086
+- [Systemd Units](/src/go/collectors/go.d.plugin/modules/systemdunits/integrations/systemd_units.md)
1087
1088
-- [systemd-logind users](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/logind/integrations/systemd-logind_users.md)
1088
+- [systemd-logind users](/src/go/collectors/go.d.plugin/modules/logind/integrations/systemd-logind_users.md)
1089
1090
### Task Queues
1091
1092
-- [Celery](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md)
1092
+- [Celery](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md)
1093
1094
-- [Mesos](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md)
1094
+- [Mesos](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md)
1095
1096
-- [Slurm](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md)
1096
+- [Slurm](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md)
1097
1098
### Telephony Servers
1099
1100
-- [GTP](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md)
1100
+- [GTP](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md)
1101
1102
-- [Kannel](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md)
1102
+- [Kannel](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md)
1103
1104
-- [OpenSIPS](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/opensips/integrations/opensips.md)
1104
+- [OpenSIPS](/src/collectors/charts.d.plugin/opensips/integrations/opensips.md)
1105
1106
### UPS
1107
1108
-- [APC UPS](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/apcupsd/integrations/apc_ups.md)
1108
+- [APC UPS](/src/collectors/charts.d.plugin/apcupsd/integrations/apc_ups.md)
1109
1110
-- [Eaton UPS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md)
1110
+- [Eaton UPS](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md)
1111
1112
-- [UPS (NUT)](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/upsd/integrations/ups_nut.md)
1112
+- [UPS (NUT)](/src/go/collectors/go.d.plugin/modules/upsd/integrations/ups_nut.md)
1113
1114
### VPNs
1115
1116
-- [Fastd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md)
1116
+- [Fastd](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md)
1117
1118
-- [Libreswan](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/libreswan/integrations/libreswan.md)
1118
+- [Libreswan](/src/collectors/charts.d.plugin/libreswan/integrations/libreswan.md)
1119
1120
-- [OpenVPN status log](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/openvpn_status_log/integrations/openvpn_status_log.md)
1120
+- [OpenVPN status log](/src/go/collectors/go.d.plugin/modules/openvpn_status_log/integrations/openvpn_status_log.md)
1121
1122
-- [OpenVPN](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/openvpn/integrations/openvpn.md)
1122
+- [OpenVPN](/src/go/collectors/go.d.plugin/modules/openvpn/integrations/openvpn.md)
1123
1124
-- [SoftEther VPN Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md)
1124
+- [SoftEther VPN Server](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md)
1125
1126
-- [Speedify CLI](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md)
1126
+- [Speedify CLI](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md)
1127
1128
-- [Tor](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/tor/integrations/tor.md)
1128
+- [Tor](/src/collectors/python.d.plugin/tor/integrations/tor.md)
1129
1130
-- [WireGuard](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/wireguard/integrations/wireguard.md)
1130
+- [WireGuard](/src/go/collectors/go.d.plugin/modules/wireguard/integrations/wireguard.md)
1131
1132
-- [strongSwan](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md)
1132
+- [strongSwan](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md)
1133
1134
### Web Servers and Web Proxies
1135
1136
-- [APIcast](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md)
1136
+- [APIcast](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md)
1137
1138
-- [Apache](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/apache/integrations/apache.md)
1138
+- [Apache](/src/go/collectors/go.d.plugin/modules/apache/integrations/apache.md)
1139
1140
-- [Clash](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md)
1140
+- [Clash](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md)
1141
1142
-- [Cloudflare PCAP](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md)
1142
+- [Cloudflare PCAP](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md)
1143
1144
-- [Envoy](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/envoy/integrations/envoy.md)
1144
+- [Envoy](/src/go/collectors/go.d.plugin/modules/envoy/integrations/envoy.md)
1145
1146
-- [Gobetween](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md)
1146
+- [Gobetween](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md)
1147
1148
-- [HAProxy](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/haproxy/integrations/haproxy.md)
1148
+- [HAProxy](/src/go/collectors/go.d.plugin/modules/haproxy/integrations/haproxy.md)
1149
1150
-- [HHVM](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md)
1150
+- [HHVM](/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md)
1151
1152
-- [HTTPD](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/apache/integrations/httpd.md)
1152
+- [HTTPD](/src/go/collectors/go.d.plugin/modules/apache/integrations/httpd.md)
1153
1154
-- [Lighttpd](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/lighttpd/integrations/lighttpd.md)
1154
+- [Lighttpd](/src/go/collectors/go.d.plugin/modules/lighttpd/integrations/lighttpd.md)
1155
1156
-- [Litespeed](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/litespeed/integrations/litespeed.md)
1156
+- [Litespeed](/src/go/collectors/go.d.plugin/modules/litespeed/integrations/litespeed.md)
1157
1158
-- [NGINX Plus](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nginxplus/integrations/nginx_plus.md)
1158
+- [NGINX Plus](/src/go/collectors/go.d.plugin/modules/nginxplus/integrations/nginx_plus.md)
1159
1160
-- [NGINX VTS](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nginxvts/integrations/nginx_vts.md)
1160
+- [NGINX VTS](/src/go/collectors/go.d.plugin/modules/nginxvts/integrations/nginx_vts.md)
1161
1162
-- [NGINX](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nginx/integrations/nginx.md)
1162
+- [NGINX](/src/go/collectors/go.d.plugin/modules/nginx/integrations/nginx.md)
1163
1164
-- [PHP-FPM](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/phpfpm/integrations/php-fpm.md)
1164
+- [PHP-FPM](/src/go/collectors/go.d.plugin/modules/phpfpm/integrations/php-fpm.md)
1165
1166
-- [Squid log files](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/squidlog/integrations/squid_log_files.md)
1166
+- [Squid log files](/src/go/collectors/go.d.plugin/modules/squidlog/integrations/squid_log_files.md)
1167
1168
-- [Squid](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/squid/integrations/squid.md)
1168
+- [Squid](/src/collectors/python.d.plugin/squid/integrations/squid.md)
1169
1170
-- [Tengine](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/tengine/integrations/tengine.md)
1170
+- [Tengine](/src/go/collectors/go.d.plugin/modules/tengine/integrations/tengine.md)
1171
1172
-- [Tomcat](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/tomcat/integrations/tomcat.md)
1172
+- [Tomcat](/src/collectors/python.d.plugin/tomcat/integrations/tomcat.md)
1173
1174
-- [Traefik](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/traefik/integrations/traefik.md)
1174
+- [Traefik](/src/go/collectors/go.d.plugin/modules/traefik/integrations/traefik.md)
1175
1176
-- [Varnish](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/varnish/integrations/varnish.md)
1176
+- [Varnish](/src/collectors/python.d.plugin/varnish/integrations/varnish.md)
1177
1178
-- [Web server log files](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/integrations/web_server_log_files.md)
1178
+- [Web server log files](/src/go/collectors/go.d.plugin/modules/weblog/integrations/web_server_log_files.md)
1179
1180
-- [uWSGI](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/uwsgi/integrations/uwsgi.md)
1180
+- [uWSGI](/src/collectors/python.d.plugin/uwsgi/integrations/uwsgi.md)
1181
1182
### Windows Systems
1183
1184
-- [Active Directory](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/integrations/active_directory.md)
1184
+- [Active Directory](/src/go/collectors/go.d.plugin/modules/windows/integrations/active_directory.md)
1185
1186
-- [HyperV](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/integrations/hyperv.md)
1186
+- [HyperV](/src/go/collectors/go.d.plugin/modules/windows/integrations/hyperv.md)
1187
1188
-- [MS Exchange](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/integrations/ms_exchange.md)
1188
+- [MS Exchange](/src/go/collectors/go.d.plugin/modules/windows/integrations/ms_exchange.md)
1189
1190
-- [MS SQL Server](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/integrations/ms_sql_server.md)
1190
+- [MS SQL Server](/src/go/collectors/go.d.plugin/modules/windows/integrations/ms_sql_server.md)
1191
1192
-- [NET Framework](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/integrations/net_framework.md)
1192
+- [NET Framework](/src/go/collectors/go.d.plugin/modules/windows/integrations/net_framework.md)
1193
1194
-- [Windows](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/windows/integrations/windows.md)
1194
+- [Windows](/src/go/collectors/go.d.plugin/modules/windows/integrations/windows.md)
src/collectors/README.md
+9
-9
@@ -4,15 +4,15 @@ When Netdata starts, and with zero configuration, it auto-detects thousands of d
4
per-second metrics.
5
6
Netdata can immediately collect metrics from these endpoints thanks to 300+ **collectors**, which all come pre-installed
7
-when you [install Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md).
7
+when you [install Netdata](/packaging/installer/README.md).
8
9
All collectors are **installed by default** with every installation of Netdata. You do not need to install
10
collectors manually to collect metrics from new sources.
11
-See how you can [monitor anything with Netdata](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md).
11
+See how you can [monitor anything with Netdata](/src/collectors/COLLECTORS.md).
12
13
Upon startup, Netdata will **auto-detect** any application or service that has a collector, as long as both the collector
14
and the app/service are configured correctly. If you don't see charts for your application, see
15
-our [collectors' configuration reference](https://github.com/netdata/netdata/blob/master/src/collectors/REFERENCE.md).
15
+our [collectors' configuration reference](/src/collectors/REFERENCE.md).
16
17
## How Netdata's metrics collectors work
18
@@ -23,9 +23,9 @@ Every collector has two primary jobs:
23
24
If the collector finds compatible metrics exposed on the configured endpoint, it begins a per-second collection job. The
25
Netdata Agent gathers these metrics, sends them to the
26
-[database engine for storage](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md)
26
+[database engine for storage](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md)
27
, and immediately
28
-[visualizes them meaningfully](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md)
28
+[visualizes them meaningfully](/docs/dashboards-and-charts/netdata-charts.md)
29
on dashboards.
30
31
Each collector comes with a pre-defined configuration that matches the default setup for that application. This endpoint
@@ -45,18 +45,18 @@ specifics of what a given collector does.
45
- **External** plugins organize collectors that gather metrics from external processes, such as a MySQL database or
46
Nginx web server. They can be written in any language, and the `netdata` daemon spawns them as long-running
47
independent processes. They communicate with the daemon via pipes. All external plugins are managed by
48
- [plugins.d](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md), which provides additional management options.
48
+ [plugins.d](/src/collectors/plugins.d/README.md), which provides additional management options.
49
50
- **Orchestrators** are external plugins that run and manage one or more modules. They run as independent processes.
51
The Go orchestrator is in active development.
52
53
- - [go.d.plugin](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/README.md): An orchestrator for data
53
+ - [go.d.plugin](/src/go/collectors/go.d.plugin/README.md): An orchestrator for data
54
collection modules written in `go`.
55
56
- - [python.d.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md):
56
+ - [python.d.plugin](/src/collectors/python.d.plugin/README.md):
57
An orchestrator for data collection modules written in `python` v2/v3.
58
59
- - [charts.d.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/README.md):
59
+ - [charts.d.plugin](/src/collectors/charts.d.plugin/README.md):
60
An orchestrator for data collection modules written in`bash` v4+.
61
62
- **Modules** are the individual programs controlled by an orchestrator to collect data from a specific application, or type of endpoint.
src/collectors/REFERENCE.md
+7
-7
@@ -9,7 +9,7 @@ learn_rel_path: "Configuration"
9
10
# Collectors configuration reference
11
12
-The list of supported collectors can be found in [the documentation](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md),
12
+The list of supported collectors can be found in [the documentation](/src/collectors/COLLECTORS.md),
13
and on [our website](https://www.netdata.cloud/integrations). The documentation of each collector provides all the
14
necessary configuration options and prerequisites for that collector. In most cases, either the charts are automatically generated
15
without any configuration, or you just fulfil those prerequisites and [configure the collector](#configure-a-collector).
@@ -67,7 +67,7 @@ You can enable/disable of the collection modules supported by `go.d`, `python.d`
67
configuration file of that orchestrator. For example, you can change the behavior of the Go orchestrator, or any of its
68
collectors, by editing `go.d.conf`.
69
70
-Use `edit-config` from your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
70
+Use `edit-config` from your [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
71
to open the orchestrator primary configuration file:
72
73
```bash
@@ -80,7 +80,7 @@ enable/disable it with `yes` and `no` settings. Uncomment any line you change to
80
start.
81
82
After you make your changes, restart the Agent with `sudo systemctl restart netdata`, or the [appropriate
83
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
83
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
84
85
## Configure a collector
86
@@ -93,19 +93,19 @@ metrics, will automatically enable data collection for the application in questi
93
94
When Netdata starts up, each collector searches for exposed metrics on the default endpoint established by that service
95
or application's standard installation procedure. For example,
96
-the [Nginx collector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nginx/README.md) searches at
96
+the [Nginx collector](/src/go/collectors/go.d.plugin/modules/nginx/README.md) searches at
97
`http://127.0.0.1/stub_status` for exposed metrics in the correct format. If an Nginx web server is running and exposes
98
metrics on that endpoint, the collector begins gathering them.
99
100
However, not every node or infrastructure uses standard ports, paths, files, or naming conventions. You may need to
101
enable or configure a collector to gather all available metrics from your systems, containers, or applications.
102
103
-First, [find the collector](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md) you want to edit
103
+First, [find the collector](/src/collectors/COLLECTORS.md) you want to edit
104
and open its documentation. Some software has collectors written in multiple languages. In these cases, you should always
105
pick the collector written in Go.
106
107
Use `edit-config` from your
108
-[Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
108
+[Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory)
109
to open a collector's configuration file. For example, edit the Nginx collector with the following:
110
111
```bash
@@ -118,7 +118,7 @@ configure that collector. Uncomment any line you change to ensure the collector'
118
read it on start.
119
120
After you make your changes, restart the Agent with `sudo systemctl restart netdata`, or the [appropriate
121
-method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
121
+method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
122
123
## Troubleshoot a collector
124
src/collectors/apps.plugin/README.md
+5
-5
@@ -67,8 +67,8 @@ Each of these sections provides the same number of charts:
67
- Network
68
- Sockets open (`apps.sockets`)
69
70
-In addition, if the [eBPF collector](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md) is running, your dashboard will also show an
71
-additional [list of charts](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md#integration-with-appsplugin) using low-level Linux
70
+In addition, if the [eBPF collector](/src/collectors/ebpf.plugin/README.md) is running, your dashboard will also show an
71
+additional [list of charts](/src/collectors/ebpf.plugin/README.md#integration-with-appsplugin) using low-level Linux
72
metrics.
73
74
The above are reported:
@@ -164,10 +164,10 @@ There are a few command line options you can pass to `apps.plugin`. The list of
164
### Integration with eBPF
165
166
If you don't see charts under the **eBPF syscall** or **eBPF net** sections, you should edit your
167
-[`ebpf.d.conf`](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md#configure-the-ebpf-collector) file to ensure the eBPF program is enabled.
167
+[`ebpf.d.conf`](/src/collectors/ebpf.plugin/README.md#configure-the-ebpf-collector) file to ensure the eBPF program is enabled.
168
169
Also see our [guide on troubleshooting apps with eBPF
170
-metrics](https://github.com/netdata/netdata/blob/master/docs/developer-and-contributor-corner/monitor-debug-applications-ebpf.md) for ideas on how to interpret these charts in a
170
+metrics](/docs/developer-and-contributor-corner/monitor-debug-applications-ebpf.md) for ideas on how to interpret these charts in a
171
few scenarios.
172
173
## Permissions
@@ -237,7 +237,7 @@ Examples below for process group `sql`:
237
- Open Pipes 
238
- Open Sockets 
239
240
-For more information about badges check [Generating Badges](https://github.com/netdata/netdata/blob/master/src/web/api/badges/README.md)
240
+For more information about badges check [Generating Badges](/src/web/api/badges/README.md)
241
242
## Comparison with console tools
243
src/collectors/cgroups.plugin/README.md
+2
-2
@@ -78,7 +78,7 @@ currently unsupported when using unified cgroups.
78
### Enabled cgroups
79
80
To provide a sane default, Netdata uses the
81
-following [pattern list](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md):
81
+following [pattern list](/src/libnetdata/simple_pattern/README.md):
82
83
- Checks the pattern against the path of the cgroup
84
@@ -297,4 +297,4 @@ a few errors in error.log complaining about files it cannot find, but immediatel
297
- I/O full pressure
298
299
Network interfaces are monitored by means of
300
-the [proc plugin](https://github.com/netdata/netdata/blob/master/src/collectors/proc.plugin/README.md#monitored-network-interface-metrics).
300
+the [proc plugin](/src/collectors/proc.plugin/README.md#monitored-network-interface-metrics).
src/collectors/charts.d.plugin/README.md
+3
-3
@@ -7,7 +7,7 @@
7
3. It communicates with Netdata via a unidirectional pipe (sending data to the `netdata` daemon)
8
4. Supports any number of data collection **modules**
9
10
-To better understand the guidelines and the API behind our External plugins, please have a look at the [Introduction to External plugins](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md) prior to reading this page.
10
+To better understand the guidelines and the API behind our External plugins, please have a look at the [Introduction to External plugins](/src/collectors/plugins.d/README.md) prior to reading this page.
11
12
13
`charts.d.plugin` has been designed so that the actual script that will do data collection will be permanently in
@@ -17,11 +17,11 @@ memory, collecting data with as little overheads as possible
17
`charts.d.plugin` looks for scripts in `/usr/lib/netdata/charts.d`.
18
The scripts should have the filename suffix: `.chart.sh`.
19
20
-By default, `charts.d.plugin` is not included as part of the install when using [our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/packages.md). You can install it by installing the `netdata-plugin-chartsd` package.
20
+By default, `charts.d.plugin` is not included as part of the install when using [our official native DEB/RPM packages](/packaging/installer/methods/packages.md). You can install it by installing the `netdata-plugin-chartsd` package.
21
22
## Configuration
23
24
-`charts.d.plugin` itself can be [configured](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf)using the configuration file `/etc/netdata/charts.d.conf`. This file is also a BASH script.
24
+`charts.d.plugin` itself can be [configured](/docs/netdata-agent/configuration/README.md#edit-netdataconf)using the configuration file `/etc/netdata/charts.d.conf`. This file is also a BASH script.
25
26
In this file, you can place statements like this:
27
src/collectors/charts.d.plugin/ap/integrations/access_points.md
+2
-2
@@ -85,7 +85,7 @@ There are no alerts configured by default for this integration.
85
86
#### Install charts.d plugin
87
88
-If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
88
+If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
89
90
91
#### `iw` utility.
@@ -101,7 +101,7 @@ The configuration file name for this integration is `charts.d/ap.conf`.
101
102
103
You can edit the configuration file using the `edit-config` script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
106
```bash
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/charts.d.plugin/ap/metadata.yaml
+1
-1
@@ -43,7 +43,7 @@ modules:
43
list:
44
- title: "Install charts.d plugin"
45
description: |
46
- If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
46
+ If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
47
- title: "`iw` utility."
48
description: "Make sure the `iw` utility is installed."
49
configuration:
src/collectors/charts.d.plugin/apcupsd/integrations/apc_ups.md
+2
-2
@@ -103,7 +103,7 @@ The following alerts are available:
103
104
#### Install charts.d plugin
105
106
-If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
106
+If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
107
108
109
#### Required software
@@ -119,7 +119,7 @@ The configuration file name for this integration is `charts.d/apcupsd.conf`.
119
120
121
You can edit the configuration file using the `edit-config` script from the
122
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
122
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
123
124
```bash
125
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/charts.d.plugin/apcupsd/metadata.yaml
+1
-1
@@ -44,7 +44,7 @@ modules:
44
list:
45
- title: "Install charts.d plugin"
46
description: |
47
- If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
47
+ If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
48
- title: "Required software"
49
description: "Make sure the `apcaccess` and `apcupsd` are installed and running."
50
configuration:
src/collectors/charts.d.plugin/libreswan/integrations/libreswan.md
+2
-2
@@ -79,7 +79,7 @@ There are no alerts configured by default for this integration.
79
80
#### Install charts.d plugin
81
82
-If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
82
+If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
83
84
85
#### Permissions to execute `ipsec`
@@ -116,7 +116,7 @@ The configuration file name for this integration is `charts.d/libreswan.conf`.
116
117
118
You can edit the configuration file using the `edit-config` script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
121
```bash
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/charts.d.plugin/libreswan/metadata.yaml
+1
-1
@@ -42,7 +42,7 @@ modules:
42
list:
43
- title: "Install charts.d plugin"
44
description: |
45
- If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
45
+ If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
46
- title: "Permissions to execute `ipsec`"
47
description: |
48
The plugin executes 2 commands to collect all the information it needs:
src/collectors/charts.d.plugin/opensips/integrations/opensips.md
+2
-2
@@ -96,7 +96,7 @@ There are no alerts configured by default for this integration.
96
97
#### Install charts.d plugin
98
99
-If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
99
+If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
100
101
102
#### Required software
@@ -112,7 +112,7 @@ The configuration file name for this integration is `charts.d/opensips.conf`.
112
113
114
You can edit the configuration file using the `edit-config` script from the
115
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
116
117
```bash
118
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/charts.d.plugin/opensips/metadata.yaml
+1
-1
@@ -43,7 +43,7 @@ modules:
43
list:
44
- title: "Install charts.d plugin"
45
description: |
46
- If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
46
+ If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
47
- title: "Required software"
48
description: "The collector requires the `opensipsctl` to be installed."
49
configuration:
src/collectors/charts.d.plugin/sensors/integrations/linux_sensors_sysfs.md
+4
-4
@@ -90,19 +90,19 @@ There are no alerts configured by default for this integration.
90
91
#### Install charts.d plugin
92
93
-If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
93
+If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
94
95
96
#### Enable the sensors collector
97
98
-The `sensors` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `charts.d.conf` file.
98
+The `sensors` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `charts.d.conf` file.
99
100
```bash
101
cd /etc/netdata # Replace this path with your Netdata config directory, if different
102
sudo ./edit-config charts.d.conf
103
```
104
105
-Change the value of the `sensors` setting to `force` and uncomment the line. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
105
+Change the value of the `sensors` setting to `force` and uncomment the line. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
106
107
108
@@ -114,7 +114,7 @@ The configuration file name for this integration is `charts.d/sensors.conf`.
114
115
116
You can edit the configuration file using the `edit-config` script from the
117
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
117
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
119
```bash
120
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/charts.d.plugin/sensors/metadata.yaml
+4
-4
@@ -25,7 +25,7 @@ modules:
25
data_collection:
26
metrics_description: |
27
Use this collector when `lm-sensors` doesn't work on your device (e.g. for RPi temperatures).
28
- For all other cases use the [Python collector](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/sensors), which supports multiple jobs, is more efficient and performs calculations on top of the kernel provided values."
28
+ For all other cases use the [Go collector](/src/go/collectors/go.d.plugin/modules/sensors/README.md), which supports multiple jobs, is more efficient and performs calculations on top of the kernel provided values."
29
method_description: |
30
It will provide charts for all configured system sensors, by reading sensors directly from the kernel.
31
The values graphed are the raw hardware values of the sensors.
@@ -47,17 +47,17 @@ modules:
47
list:
48
- title: "Install charts.d plugin"
49
description: |
50
- If [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
50
+ If [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure `netdata-plugin-chartsd` is installed.
51
- title: "Enable the sensors collector"
52
description: |
53
- The `sensors` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `charts.d.conf` file.
53
+ The `sensors` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `charts.d.conf` file.
54
55
```bash
56
cd /etc/netdata # Replace this path with your Netdata config directory, if different
57
sudo ./edit-config charts.d.conf
58
```
59
60
- Change the value of the `sensors` setting to `force` and uncomment the line. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
60
+ Change the value of the `sensors` setting to `force` and uncomment the line. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
61
configuration:
62
file:
63
name: charts.d/sensors.conf
src/collectors/cups.plugin/integrations/cups.md
+1
-1
@@ -116,7 +116,7 @@ The file format is a modified INI syntax. The general structure is:
116
option3 = some third value
117
```
118
You can edit the configuration file using the `edit-config` script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
121
```bash
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/debugfs.plugin/integrations/linux_zswap.md
+1
-1
@@ -113,7 +113,7 @@ The file format is a modified INI syntax. The general structure is:
113
option3 = some third value
114
```
115
You can edit the configuration file using the `edit-config` script from the
116
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
116
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
117
118
```bash
119
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/debugfs.plugin/integrations/power_capping.md
+1
-1
@@ -107,7 +107,7 @@ The file format is a modified INI syntax. The general structure is:
107
option3 = some third value
108
```
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/debugfs.plugin/integrations/system_memory_fragmentation.md
+1
-1
@@ -111,7 +111,7 @@ The file format is a modified INI syntax. The general structure is:
111
option3 = some third value
112
```
113
You can edit the configuration file using the `edit-config` script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
116
```bash
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/diskspace.plugin/integrations/disk_space.md
+1
-1
@@ -109,7 +109,7 @@ The file format is a modified INI syntax. The general structure is:
109
option3 = some third value
110
```
111
You can edit the configuration file using the `edit-config` script from the
112
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
114
```bash
115
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/README.md
+14
-14
@@ -15,7 +15,7 @@ The Netdata Agent provides many [eBPF](https://ebpf.io/what-is-ebpf/) programs t
15
> ❗ eBPF monitoring only works on Linux systems and with specific Linux kernels, including all kernels newer than `4.11.0`, and all kernels on CentOS 7.6 or later. For kernels older than `4.11.0`, improved support is in active development.
16
17
This document provides comprehensive details about the `ebpf.plugin`.
18
-For hands-on configuration and troubleshooting tips see our [tutorial on troubleshooting apps with eBPF metrics](https://github.com/netdata/netdata/blob/master/docs/developer-and-contributor-corner/monitor-debug-applications-ebpf.md).
18
+For hands-on configuration and troubleshooting tips see our [tutorial on troubleshooting apps with eBPF metrics](/docs/developer-and-contributor-corner/monitor-debug-applications-ebpf.md).
19
20
<figure>
21
<img src="https://user-images.githubusercontent.com/1153921/74746434-ad6a1e00-5222-11ea-858a-a7882617ae02.png" alt="An example of VFS charts, made possible by the eBPF collector plugin" />
@@ -44,12 +44,12 @@ If your Agent is v1.22 or older, you may to enable the collector yourself.
44
45
To enable or disable the entire eBPF collector:
46
47
-1. Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
+1. Navigate to the [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
48
```bash
49
cd /etc/netdata
50
```
51
52
-2. Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit `netdata.conf`.
52
+2. Use the [`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit `netdata.conf`.
53
54
```bash
55
./edit-config netdata.conf
@@ -69,11 +69,11 @@ You can configure the eBPF collector's behavior to fine-tune which metrics you r
69
70
To edit the `ebpf.d.conf`:
71
72
-1. Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
72
+1. Navigate to the [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
73
```bash
74
cd /etc/netdata
75
```
76
-2. Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit [`ebpf.d.conf`](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/ebpf.d.conf).
76
+2. Use the [`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit [`ebpf.d.conf`](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/ebpf.d.conf).
77
78
```bash
79
./edit-config ebpf.d.conf
@@ -103,7 +103,7 @@ accepts the following values:
103
#### Integration with `apps.plugin`
104
105
The eBPF collector also creates charts for each running application through an integration with the
106
-[`apps.plugin`](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md). This integration helps you understand how specific applications
106
+[`apps.plugin`](/src/collectors/apps.plugin/README.md). This integration helps you understand how specific applications
107
interact with the Linux kernel.
108
109
If you want to enable `apps.plugin` integration, change the "apps" setting to "yes".
@@ -116,7 +116,7 @@ If you want to enable `apps.plugin` integration, change the "apps" setting to "y
116
#### Integration with `cgroups.plugin`
117
118
The eBPF collector also creates charts for each cgroup through an integration with the
119
-[`cgroups.plugin`](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md). This integration helps you understand how a specific cgroup
119
+[`cgroups.plugin`](/src/collectors/cgroups.plugin/README.md). This integration helps you understand how a specific cgroup
120
interacts with the Linux kernel.
121
122
The integration with `cgroups.plugin` is disabled by default to avoid creating overhead on your system. If you want to
@@ -236,7 +236,7 @@ Linux metrics:
236
The eBPF collector enables and runs the following eBPF programs by default:
237
238
- `cachestat`: Netdata's eBPF data collector creates charts about the memory page cache. When the integration with
239
- [`apps.plugin`](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md) is enabled, this collector creates charts for the whole host _and_
239
+ [`apps.plugin`](/src/collectors/apps.plugin/README.md) is enabled, this collector creates charts for the whole host _and_
240
for each application.
241
- `fd` : This eBPF program creates charts that show information about calls to open files.
242
- `mount`: This eBPF program creates charts that show calls to syscalls mount(2) and umount(2).
@@ -272,11 +272,11 @@ You can configure each thread of the eBPF data collector. This allows you to ove
272
273
To configure an eBPF thread:
274
275
-1. Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
275
+1. Navigate to the [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
276
```bash
277
cd /etc/netdata
278
```
279
-2. Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit a thread configuration file. The following configuration files are available:
279
+2. Use the [`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit a thread configuration file. The following configuration files are available:
280
281
- `network.conf`: Configuration for the [`network` thread](#network-configuration). This config file overwrites the global options and also
282
lets you specify which network the eBPF collector monitors.
@@ -316,7 +316,7 @@ You can configure the information shown with function `ebpf_socket` using the se
316
317
When you define a `ports` setting, Netdata will collect network metrics for that specific port. For example, if you
318
write `ports = 19999`, Netdata will collect only connections for itself. The `hostnames` setting accepts
319
-[simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). The `ports`, and `ips` settings accept negation (`!`) to deny
319
+[simple patterns](/src/libnetdata/simple_pattern/README.md). The `ports`, and `ips` settings accept negation (`!`) to deny
320
specific values or asterisk alone to define all values.
321
322
In the above example, Netdata will collect metrics for all ports between `1` and `1024`, with the exception of `53` (domain)
@@ -899,7 +899,7 @@ node is experiencing high memory usage and there is no obvious culprit to be fou
899
900
If with these changes you still suspect eBPF using too much memory, and there is no obvious culprit to be found
901
in the `apps.mem` chart, consider testing for high kernel memory usage by [disabling eBPF monitoring](#configuring-ebpfplugin).
902
-Next, [restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) with
902
+Next, [restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) with
903
`sudo systemctl restart netdata` to see if system memory usage (see the `system.ram` chart) has dropped significantly.
904
905
Beginning with `v1.31`, kernel memory usage is configurable via the [`pid table size` setting](#pid-table-size)
@@ -994,7 +994,7 @@ required to run `ebpf.plugin`.
994
995
### ebpf_thread
996
997
-The eBPF plugin has a [function](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) named
997
+The eBPF plugin has a [function](/docs/top-monitoring-netdata-functions.md) named
998
`ebpf_thread` that controls its internal threads and helps to reduce the overhead on host. Using the function you
999
can run the plugin with all threads disabled and enable them only when you want to take a look in specific areas.
1000
@@ -1041,7 +1041,7 @@ dashboard
1041
1042
### ebpf_socket
1043
1044
-The eBPF plugin has a [function](https://github.com/netdata/netdata/blob/master/docs/top-monitoring-netdata-functions.md) named
1044
+The eBPF plugin has a [function](/docs/top-monitoring-netdata-functions.md) named
1045
`ebpf_socket` that shows the current status of open sockets on host.
1046
1047
#### Families
src/collectors/ebpf.plugin/integrations/ebpf_cachestat.md
+1
-1
@@ -146,7 +146,7 @@ The configuration file name for this integration is `ebpf.d/cachestat.conf`.
146
147
148
You can edit the configuration file using the `edit-config` script from the
149
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
149
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
150
151
```bash
152
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_dcstat.md
+1
-1
@@ -144,7 +144,7 @@ The configuration file name for this integration is `ebpf.d/dcstat.conf`.
144
145
146
You can edit the configuration file using the `edit-config` script from the
147
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
148
149
```bash
150
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_disk.md
+1
-1
@@ -110,7 +110,7 @@ The configuration file name for this integration is `ebpf.d/disk.conf`.
110
111
112
You can edit the configuration file using the `edit-config` script from the
113
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
115
```bash
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_filedescriptor.md
+1
-1
@@ -144,7 +144,7 @@ The configuration file name for this integration is `ebpf.d/fd.conf`.
144
145
146
You can edit the configuration file using the `edit-config` script from the
147
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
148
149
```bash
150
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_filesystem.md
+1
-1
@@ -131,7 +131,7 @@ The configuration file name for this integration is `ebpf.d/filesystem.conf`.
131
132
133
You can edit the configuration file using the `edit-config` script from the
134
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
134
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
135
136
```bash
137
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_hardirq.md
+1
-1
@@ -110,7 +110,7 @@ The configuration file name for this integration is `ebpf.d/hardirq.conf`.
110
111
112
You can edit the configuration file using the `edit-config` script from the
113
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
115
```bash
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_mdflush.md
+1
-1
@@ -105,7 +105,7 @@ The configuration file name for this integration is `ebpf.d/mdflush.conf`.
105
106
107
You can edit the configuration file using the `edit-config` script from the
108
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
110
```bash
111
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_mount.md
+1
-1
@@ -111,7 +111,7 @@ The configuration file name for this integration is `ebpf.d/mount.conf`.
111
112
113
You can edit the configuration file using the `edit-config` script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
116
```bash
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_oomkill.md
+1
-1
@@ -127,7 +127,7 @@ The configuration file name for this integration is `ebpf.d/oomkill.conf`.
127
128
129
You can edit the configuration file using the `edit-config` script from the
130
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
130
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
131
132
```bash
133
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_processes.md
+1
-1
@@ -154,7 +154,7 @@ The configuration file name for this integration is `ebpf.d/process.conf`.
154
155
156
You can edit the configuration file using the `edit-config` script from the
157
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
157
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
158
159
```bash
160
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_shm.md
+1
-1
@@ -148,7 +148,7 @@ The configuration file name for this integration is `ebpf.d/shm.conf`.
148
149
150
You can edit the configuration file using the `edit-config` script from the
151
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
151
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
152
153
```bash
154
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_socket.md
+1
-1
@@ -165,7 +165,7 @@ The configuration file name for this integration is `ebpf.d/network.conf`.
165
166
167
You can edit the configuration file using the `edit-config` script from the
168
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
168
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
169
170
```bash
171
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_softirq.md
+1
-1
@@ -110,7 +110,7 @@ The configuration file name for this integration is `ebpf.d/softirq.conf`.
110
111
112
You can edit the configuration file using the `edit-config` script from the
113
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
115
```bash
116
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_swap.md
+1
-1
@@ -137,7 +137,7 @@ The configuration file name for this integration is `ebpf.d/swap.conf`.
137
138
139
You can edit the configuration file using the `edit-config` script from the
140
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
140
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
141
142
```bash
143
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_sync.md
+1
-1
@@ -118,7 +118,7 @@ The configuration file name for this integration is `ebpf.d/sync.conf`.
118
119
120
You can edit the configuration file using the `edit-config` script from the
121
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
122
123
```bash
124
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ebpf.plugin/integrations/ebpf_vfs.md
+1
-1
@@ -179,7 +179,7 @@ The configuration file name for this integration is `ebpf.d/vfs.conf`.
179
180
181
You can edit the configuration file using the `edit-config` script from the
182
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
182
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
183
184
```bash
185
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md
+1
-1
@@ -87,7 +87,7 @@ Configuration for this specific integration is located in the `[plugin:freebsd]`
87
88
89
You can edit the configuration file using the `edit-config` script from the
90
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
90
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
91
92
```bash
93
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/dev.cpu.temperature.md
+1
-1
@@ -96,7 +96,7 @@ The file format is a modified INI syntax. The general structure is:
96
option3 = some third value
97
```
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/devstat.md
+1
-1
@@ -120,7 +120,7 @@ The file format is a modified INI syntax. The general structure is:
120
option3 = some third value
121
```
122
You can edit the configuration file using the `edit-config` script from the
123
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
123
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
125
```bash
126
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/getifaddrs.md
+1
-1
@@ -126,7 +126,7 @@ The file format is a modified INI syntax. The general structure is:
126
option3 = some third value
127
```
128
You can edit the configuration file using the `edit-config` script from the
129
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
130
131
```bash
132
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/getmntinfo.md
+1
-1
@@ -103,7 +103,7 @@ The file format is a modified INI syntax. The general structure is:
103
option3 = some third value
104
```
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/hw.intrcnt.md
+1
-1
@@ -97,7 +97,7 @@ The file format is a modified INI syntax. The general structure is:
97
option3 = some third value
98
```
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/ipfw.md
+1
-1
@@ -100,7 +100,7 @@ The file format is a modified INI syntax. The general structure is:
100
option3 = some third value
101
```
102
You can edit the configuration file using the `edit-config` script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
105
```bash
106
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/kern.cp_time.md
+1
-1
@@ -115,7 +115,7 @@ The file format is a modified INI syntax. The general structure is:
115
option3 = some third value
116
```
117
You can edit the configuration file using the `edit-config` script from the
118
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
120
```bash
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/kern.ipc.msq.md
+1
-1
@@ -98,7 +98,7 @@ The file format is a modified INI syntax. The general structure is:
98
option3 = some third value
99
```
100
You can edit the configuration file using the `edit-config` script from the
101
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
103
```bash
104
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/kern.ipc.sem.md
+1
-1
@@ -103,7 +103,7 @@ The file format is a modified INI syntax. The general structure is:
103
option3 = some third value
104
```
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md
+1
-1
@@ -97,7 +97,7 @@ The file format is a modified INI syntax. The general structure is:
97
option3 = some third value
98
```
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet.icmp.stats.md
+1
-1
@@ -98,7 +98,7 @@ The file format is a modified INI syntax. The general structure is:
98
option3 = some third value
99
```
100
You can edit the configuration file using the `edit-config` script from the
101
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
103
```bash
104
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet.ip.stats.md
+1
-1
@@ -99,7 +99,7 @@ The file format is a modified INI syntax. The general structure is:
99
option3 = some third value
100
```
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet.tcp.states.md
+1
-1
@@ -101,7 +101,7 @@ The file format is a modified INI syntax. The general structure is:
101
option3 = some third value
102
```
103
You can edit the configuration file using the `edit-config` script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
106
```bash
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet.tcp.stats.md
+1
-1
@@ -111,7 +111,7 @@ The file format is a modified INI syntax. The general structure is:
111
option3 = some third value
112
```
113
You can edit the configuration file using the `edit-config` script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
116
```bash
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet.udp.stats.md
+1
-1
@@ -103,7 +103,7 @@ The file format is a modified INI syntax. The general structure is:
103
option3 = some third value
104
```
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet6.icmp6.stats.md
+1
-1
@@ -102,7 +102,7 @@ The file format is a modified INI syntax. The general structure is:
102
option3 = some third value
103
```
104
You can edit the configuration file using the `edit-config` script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
107
```bash
108
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.inet6.ip6.stats.md
+1
-1
@@ -99,7 +99,7 @@ The file format is a modified INI syntax. The general structure is:
99
option3 = some third value
100
```
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/net.isr.md
+1
-1
@@ -115,7 +115,7 @@ The file format is a modified INI syntax. The general structure is:
115
option3 = some third value
116
```
117
You can edit the configuration file using the `edit-config` script from the
118
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
120
```bash
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/system.ram.md
+1
-1
@@ -105,7 +105,7 @@ The file format is a modified INI syntax. The general structure is:
105
option3 = some third value
106
```
107
You can edit the configuration file using the `edit-config` script from the
108
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
110
```bash
111
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/uptime.md
+1
-1
@@ -96,7 +96,7 @@ The file format is a modified INI syntax. The general structure is:
96
option3 = some third value
97
```
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.loadavg.md
+1
-1
@@ -104,7 +104,7 @@ The file format is a modified INI syntax. The general structure is:
104
option3 = some third value
105
```
106
You can edit the configuration file using the `edit-config` script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
109
```bash
110
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_intr.md
+1
-1
@@ -96,7 +96,7 @@ The file format is a modified INI syntax. The general structure is:
96
option3 = some third value
97
```
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_soft.md
+1
-1
@@ -96,7 +96,7 @@ The file format is a modified INI syntax. The general structure is:
96
option3 = some third value
97
```
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.stats.sys.v_swtch.md
+1
-1
@@ -97,7 +97,7 @@ The file format is a modified INI syntax. The general structure is:
97
option3 = some third value
98
```
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_pgfaults.md
+1
-1
@@ -96,7 +96,7 @@ The file format is a modified INI syntax. The general structure is:
96
option3 = some third value
97
```
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.stats.vm.v_swappgs.md
+1
-1
@@ -101,7 +101,7 @@ The file format is a modified INI syntax. The general structure is:
101
option3 = some third value
102
```
103
You can edit the configuration file using the `edit-config` script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
106
```bash
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.swap_info.md
+1
-1
@@ -101,7 +101,7 @@ The file format is a modified INI syntax. The general structure is:
101
option3 = some third value
102
```
103
You can edit the configuration file using the `edit-config` script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
106
```bash
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/vm.vmtotal.md
+1
-1
@@ -103,7 +103,7 @@ The file format is a modified INI syntax. The general structure is:
103
option3 = some third value
104
```
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freebsd.plugin/integrations/zfs.md
+1
-1
@@ -128,7 +128,7 @@ The file format is a modified INI syntax. The general structure is:
128
option3 = some third value
129
```
130
You can edit the configuration file using the `edit-config` script from the
131
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
131
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
132
133
```bash
134
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/freeipmi.plugin/integrations/intelligent_platform_management_interface_ipmi.md
+1
-1
@@ -144,7 +144,7 @@ The file format is a modified INI syntax. The general structure is:
144
option3 = some third value
145
```
146
You can edit the configuration file using the `edit-config` script from the
147
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
148
149
```bash
150
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/idlejitter.plugin/integrations/idle_os_jitter.md
+1
-1
@@ -97,7 +97,7 @@ The file format is a modified INI syntax. The general structure is:
97
option3 = some third value
98
```
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/ioping.plugin/integrations/ioping.md
+1
-1
@@ -95,7 +95,7 @@ The configuration file name for this integration is `ioping.conf`.
95
96
97
You can edit the configuration file using the `edit-config` script from the
98
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
100
```bash
101
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/log2journal/README.md
+2
-2
@@ -522,7 +522,7 @@ journalctl -f --namespace=nginx-logs
522
523
Netdata will automatically pick the new namespace and present it at the list of sources of the dashboard.
524
525
-You can also instruct `systemd-cat-native` to log to a remote system, sending the logs to a `systemd-journal-remote` instance running on another server. Check [the manual of systemd-cat-native](https://github.com/netdata/netdata/blob/master/src/libnetdata/log/systemd-cat-native.md).
525
+You can also instruct `systemd-cat-native` to log to a remote system, sending the logs to a `systemd-journal-remote` instance running on another server. Check [the manual of systemd-cat-native](/src/libnetdata/log/systemd-cat-native.md).
526
527
528
## Performance
@@ -909,4 +909,4 @@ You can find the most common fields at 'man systemd.journal-fields'.
909
910
## `systemd-cat-native` options
911
912
-Read [the manual of systemd-cat-native](https://github.com/netdata/netdata/blob/master/src/libnetdata/log/systemd-cat-native.md).
912
+Read [the manual of systemd-cat-native](/src/libnetdata/log/systemd-cat-native.md).
src/collectors/macos.plugin/integrations/macos.md
+1
-1
@@ -189,7 +189,7 @@ The file format is a modified INI syntax. The general structure is:
189
option3 = some third value
190
```
191
You can edit the configuration file using the `edit-config` script from the
192
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
192
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
193
194
```bash
195
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/nfacct.plugin/integrations/netfilter.md
+1
-1
@@ -107,7 +107,7 @@ The file format is a modified INI syntax. The general structure is:
107
option3 = some third value
108
```
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/perf.plugin/integrations/cpu_performance.md
+4
-4
@@ -97,21 +97,21 @@ There are no alerts configured by default for this integration.
97
98
#### Install perf plugin
99
100
-If you are [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure the `netdata-plugin-perf` package is installed.
100
+If you are [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure the `netdata-plugin-perf` package is installed.
101
102
103
#### Enable the perf plugin
104
105
The plugin is disabled by default because the number of PMUs is usually quite limited and it is not desired to allow Netdata to struggle silently for PMUs, interfering with other performance monitoring software.
106
107
-To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `netdata.conf` file.
107
+To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `netdata.conf` file.
108
109
```bash
110
cd /etc/netdata # Replace this path with your Netdata config directory, if different
111
sudo ./edit-config netdata.conf
112
```
113
114
-Change the value of the `perf` setting to `yes` in the `[plugins]` section. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
114
+Change the value of the `perf` setting to `yes` in the `[plugins]` section. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
115
116
117
@@ -133,7 +133,7 @@ The file format is a modified INI syntax. The general structure is:
133
option3 = some third value
134
```
135
You can edit the configuration file using the `edit-config` script from the
136
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
136
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
137
138
```bash
139
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/perf.plugin/metadata.yaml
+3
-3
@@ -43,19 +43,19 @@ modules:
43
list:
44
- title: Install perf plugin
45
description: |
46
- If you are [using our official native DEB/RPM packages](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure the `netdata-plugin-perf` package is installed.
46
+ If you are [using our official native DEB/RPM packages](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used), make sure the `netdata-plugin-perf` package is installed.
47
- title: Enable the perf plugin
48
description: |
49
The plugin is disabled by default because the number of PMUs is usually quite limited and it is not desired to allow Netdata to struggle silently for PMUs, interfering with other performance monitoring software.
50
51
- To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `netdata.conf` file.
51
+ To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `netdata.conf` file.
52
53
```bash
54
cd /etc/netdata # Replace this path with your Netdata config directory, if different
55
sudo ./edit-config netdata.conf
56
```
57
58
- Change the value of the `perf` setting to `yes` in the `[plugins]` section. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
58
+ Change the value of the `perf` setting to `yes` in the `[plugins]` section. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
59
configuration:
60
file:
61
name: "netdata.conf"
src/collectors/plugins.d/README.md
+14
-14
@@ -16,18 +16,18 @@ from external processes, thus allowing Netdata to use **external plugins**.
16
17
| plugin | language | O/S | description |
18
|:------------------------------------------------------------------------------------------------------:|:--------:|:--------------:|:----------------------------------------------------------------------------------------------------------------------------------------|
19
-| [apps.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/apps.plugin/README.md) | `C` | linux, freebsd | monitors the whole process tree on Linux and FreeBSD and breaks down system resource usage by **process**, **user** and **user group**. |
20
-| [charts.d.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/README.md) | `BASH` | all | a **plugin orchestrator** for data collection modules written in `BASH` v4+. |
21
-| [cups.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/cups.plugin/README.md) | `C` | all | monitors **CUPS** |
22
-| [ebpf.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md) | `C` | linux | monitors different metrics on environments using kernel internal functions. |
23
-| [go.d.plugin](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/README.md) | `GO` | all | collects metrics from the system, applications, or third-party APIs. |
24
-| [ioping.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/ioping.plugin/README.md) | `C` | all | measures disk latency. |
25
-| [freeipmi.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/freeipmi.plugin/README.md) | `C` | linux | collects metrics from enterprise hardware sensors, on Linux servers. |
26
-| [nfacct.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/nfacct.plugin/README.md) | `C` | linux | collects netfilter firewall, connection tracker and accounting metrics using `libmnl` and `libnetfilter_acct`. |
27
-| [xenstat.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/xenstat.plugin/README.md) | `C` | linux | collects XenServer and XCP-ng metrics using `lxenstat`. |
28
-| [perf.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/perf.plugin/README.md) | `C` | linux | collects CPU performance metrics using performance monitoring units (PMU). |
29
-| [python.d.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md) | `python` | all | a **plugin orchestrator** for data collection modules written in `python` v2 or v3 (both are supported). |
30
-| [slabinfo.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/slabinfo.plugin/README.md) | `C` | linux | collects kernel internal cache objects (SLAB) metrics. |
19
+| [apps.plugin](/src/collectors/apps.plugin/README.md) | `C` | linux, freebsd | monitors the whole process tree on Linux and FreeBSD and breaks down system resource usage by **process**, **user** and **user group**. |
20
+| [charts.d.plugin](/src/collectors/charts.d.plugin/README.md) | `BASH` | all | a **plugin orchestrator** for data collection modules written in `BASH` v4+. |
21
+| [cups.plugin](/src/collectors/cups.plugin/README.md) | `C` | all | monitors **CUPS** |
22
+| [ebpf.plugin](/src/collectors/ebpf.plugin/README.md) | `C` | linux | monitors different metrics on environments using kernel internal functions. |
23
+| [go.d.plugin](/src/go/collectors/go.d.plugin/README.md) | `GO` | all | collects metrics from the system, applications, or third-party APIs. |
24
+| [ioping.plugin](/src/collectors/ioping.plugin/README.md) | `C` | all | measures disk latency. |
25
+| [freeipmi.plugin](/src/collectors/freeipmi.plugin/README.md) | `C` | linux | collects metrics from enterprise hardware sensors, on Linux servers. |
26
+| [nfacct.plugin](/src/collectors/nfacct.plugin/README.md) | `C` | linux | collects netfilter firewall, connection tracker and accounting metrics using `libmnl` and `libnetfilter_acct`. |
27
+| [xenstat.plugin](/src/collectors/xenstat.plugin/README.md) | `C` | linux | collects XenServer and XCP-ng metrics using `lxenstat`. |
28
+| [perf.plugin](/src/collectors/perf.plugin/README.md) | `C` | linux | collects CPU performance metrics using performance monitoring units (PMU). |
29
+| [python.d.plugin](/src/collectors/python.d.plugin/README.md) | `python` | all | a **plugin orchestrator** for data collection modules written in `python` v2 or v3 (both are supported). |
30
+| [slabinfo.plugin](/src/collectors/slabinfo.plugin/README.md) | `C` | linux | collects kernel internal cache objects (SLAB) metrics. |
31
32
Plugin orchestrators may also be described as **modular plugins**. They are modular since they accept custom made modules to be included. Writing modules for these plugins is easier than accessing the native Netdata API directly. You will find modules already available for each orchestrator under the directory of the particular modular plugin (e.g. under python.d.plugin for the python orchestrator).
33
Each of these modular plugins has each own methods for defining modules. Please check the examples and their documentation.
@@ -780,12 +780,12 @@ or do not output the line at all.
780
## Modular Plugins
781
782
1. **python**, use `python.d.plugin`, there are many examples in the [python.d
783
- directory](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md)
783
+ directory](/src/collectors/python.d.plugin/README.md)
784
785
python is ideal for Netdata plugins. It is a simple, yet powerful way to collect data, it has a very small memory footprint, although it is not the most CPU efficient way to do it.
786
787
2. **BASH**, use `charts.d.plugin`, there are many examples in the [charts.d
788
- directory](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/README.md)
788
+ directory](/src/collectors/charts.d.plugin/README.md)
789
790
BASH is the simplest scripting language for collecting values. It is the less efficient though in terms of CPU resources. You can use it to collect data quickly, but extensive use of it might use a lot of system resources.
791
src/collectors/proc.plugin/README.md
+2
-2
@@ -402,7 +402,7 @@ You can set the following values for each configuration option:
402
403
There are several alerts defined in `health.d/net.conf`.
404
405
-The tricky ones are `inbound packets dropped` and `inbound packets dropped ratio`. They have quite a strict policy so that they warn users about possible issues. These alerts can be annoying for some network configurations. It is especially true for some bonding configurations if an interface is a child or a bonding interface itself. If it is expected to have a certain number of drops on an interface for a certain network configuration, a separate alert with different triggering thresholds can be created or the existing one can be disabled for this specific interface. It can be done with the help of the [families](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#alert-line-families) line in the alert configuration. For example, if you want to disable the `inbound packets dropped` alert for `eth0`, set `families: !eth0 *` in the alert definition for `template: inbound_packets_dropped`.
405
+The tricky ones are `inbound packets dropped` and `inbound packets dropped ratio`. They have quite a strict policy so that they warn users about possible issues. These alerts can be annoying for some network configurations. It is especially true for some bonding configurations if an interface is a child or a bonding interface itself. If it is expected to have a certain number of drops on an interface for a certain network configuration, a separate alert with different triggering thresholds can be created or the existing one can be disabled for this specific interface. It can be done with the help of the [families](/src/health/REFERENCE.md#alert-line-families) line in the alert configuration. For example, if you want to disable the `inbound packets dropped` alert for `eth0`, set `families: !eth0 *` in the alert definition for `template: inbound_packets_dropped`.
406
407
#### configuration
408
@@ -610,7 +610,7 @@ The `drm` path can be configured if it differs from the default:
610
```
611
612
> [!NOTE]
613
-> Temperature, fan speed, voltage and power metrics for AMD GPUs can be monitored using the [Sensors](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/sensors/README.md) plugin.
613
+> Temperature, fan speed, voltage and power metrics for AMD GPUs can be monitored using the [Sensors](/src/collectors/charts.d.plugin/sensors/README.md) plugin.
614
615
## IPC
616
src/collectors/proc.plugin/integrations/system_statistics.md
+1
-1
@@ -151,7 +151,7 @@ The file format is a modified INI syntax. The general structure is:
151
option3 = some third value
152
```
153
You can edit the configuration file using the `edit-config` script from the
154
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
154
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
155
156
```bash
157
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/profile.plugin/README.md
+1
-1
@@ -12,7 +12,7 @@ A user can specify:
12
13
## Configuration
14
15
-Edit the `netdata.conf` configuration file using [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) from the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory), which is typically at `/etc/netdata`.
15
+Edit the `netdata.conf` configuration file using [`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf) from the [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory), which is typically at `/etc/netdata`.
16
17
Scroll down to the `[plugin:profile]` section to find the available options:
18
src/collectors/python.d.plugin/alarms/integrations/netdata_agent_alarms.md
+1
-1
@@ -87,7 +87,7 @@ The configuration file name for this integration is `python.d/alarms.conf`.
87
88
89
You can edit the configuration file using the `edit-config` script from the
90
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
90
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
91
92
```bash
93
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/alarms/metadata.yaml
+1
-1
@@ -5,7 +5,7 @@ modules:
5
module_name: alarms
6
monitored_instance:
7
name: Netdata Agent alarms
8
- link: https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/alarms/README.md
8
+ link: /src/collectors/python.d.plugin/alarms/README.md
9
categories:
10
- data-collection.other
11
icon_filename: ""
src/collectors/python.d.plugin/am2320/integrations/am2320.md
+1
-1
@@ -107,7 +107,7 @@ The configuration file name for this integration is `python.d/am2320.conf`.
107
108
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/anomalies/README.md
+4
-4
@@ -10,7 +10,7 @@ learn_rel_path: "Integrations/Monitor/Anything"
10
11
# Anomaly detection with Netdata
12
13
-**Note**: Check out the [Netdata Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md) for a more native anomaly detection experience within Netdata.
13
+**Note**: Check out the [Netdata Anomaly Advisor](/docs/dashboards-and-charts/anomaly-advisor-tab.md) for a more native anomaly detection experience within Netdata.
14
15
This collector uses the Python [PyOD](https://pyod.readthedocs.io/en/latest/index.html) library to perform unsupervised [anomaly detection](https://en.wikipedia.org/wiki/Anomaly_detection) on your Netdata charts and/or dimensions.
16
@@ -73,7 +73,7 @@ The configuration for the anomalies collector defines how it will behave on your
73
_**Note**: If you are unsure about any of the below configuration options then it's best to just ignore all this and leave the `anomalies.conf` file alone to begin with. Then you can return to it later if you would like to tune things a bit more once the collector is running for a while and you have a feeling for its performance on your node._
74
75
Edit the `python.d/anomalies.conf` configuration file using `edit-config` from the your agent's [config
76
-directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is usually at `/etc/netdata`.
76
+directory](/docs/netdata-agent/configuration/README.md), which is usually at `/etc/netdata`.
77
78
```bash
79
cd /etc/netdata # Replace this path with your Netdata config directory, if different
@@ -219,7 +219,7 @@ If you would like to go deeper on what exactly the anomalies collector is doing
219
220
## Notes
221
222
-- Python 3 is required as the [`netdata-pandas`](https://github.com/netdata/netdata-pandas) package uses Python async libraries ([asks](https://pypi.org/project/asks/) and [trio](https://pypi.org/project/trio/)) to make asynchronous calls to the [Netdata REST API](https://github.com/netdata/netdata/blob/master/src/web/api/README.md) to get the required data for each chart.
222
+- Python 3 is required as the [`netdata-pandas`](https://github.com/netdata/netdata-pandas) package uses Python async libraries ([asks](https://pypi.org/project/asks/) and [trio](https://pypi.org/project/trio/)) to make asynchronous calls to the [Netdata REST API](/src/web/api/README.md) to get the required data for each chart.
223
- Python 3 is also required for the underlying ML libraries of [numba](https://pypi.org/project/numba/), [scikit-learn](https://pypi.org/project/scikit-learn/), and [PyOD](https://pypi.org/project/pyod/).
224
- It may take a few hours or so (depending on your choice of `train_secs_n`) for the collector to 'settle' into it's typical behaviour in terms of the trained models and probabilities you will see in the normal running of your node.
225
- As this collector does most of the work in Python itself, with [PyOD](https://pyod.readthedocs.io/en/latest/) leveraging [numba](https://numba.pydata.org/) under the hood, you may want to try it out first on a test or development system to get a sense of its performance characteristics on a node similar to where you would like to use it.
@@ -234,7 +234,7 @@ If you would like to go deeper on what exactly the anomalies collector is doing
234
- If you activate this collector on a fresh node, it might take a little while to build up enough data to calculate a realistic and useful model.
235
- Some models like `iforest` can be comparatively expensive (on same n1-standard-2 system above ~2s runtime during predict, ~40s training time, ~50% cpu on both train and predict) so if you would like to use it you might be advised to set a relatively high `update_every` maybe 10, 15 or 30 in `anomalies.conf`.
236
- Setting a higher `train_every_n` and `update_every` is an easy way to devote less resources on the node to anomaly detection. Specifying less charts and a lower `train_n_secs` will also help reduce resources at the expense of covering less charts and maybe a more noisy model if you set `train_n_secs` to be too small for how your node tends to behave.
237
-- If you would like to enable this on a Raspberry Pi, then check out [this guide](https://github.com/netdata/netdata/blob/master/docs/developer-and-contributor-corner/raspberry-pi-anomaly-detection.md) which will guide you through first installing LLVM.
237
+- If you would like to enable this on a Raspberry Pi, then check out [this guide](/docs/developer-and-contributor-corner/raspberry-pi-anomaly-detection.md) which will guide you through first installing LLVM.
238
239
## Useful links and further reading
240
src/collectors/python.d.plugin/beanstalk/integrations/beanstalk.md
+1
-1
@@ -118,7 +118,7 @@ The configuration file name for this integration is `python.d/beanstalk.conf`.
118
119
120
You can edit the configuration file using the `edit-config` script from the
121
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
122
123
```bash
124
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/boinc/integrations/boinc.md
+1
-1
@@ -100,7 +100,7 @@ The configuration file name for this integration is `python.d/boinc.conf`.
100
101
102
You can edit the configuration file using the `edit-config` script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
105
```bash
106
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/ceph/integrations/ceph.md
+1
-1
@@ -116,7 +116,7 @@ The configuration file name for this integration is `python.d/ceph.conf`.
116
117
118
You can edit the configuration file using the `edit-config` script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
121
```bash
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/changefinder/integrations/python.d_changefinder.md
+1
-1
@@ -121,7 +121,7 @@ The configuration file name for this integration is `python.d/changefinder.conf`
121
122
123
You can edit the configuration file using the `edit-config` script from the
124
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
126
```bash
127
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/dovecot/integrations/dovecot.md
+1
-1
@@ -100,7 +100,7 @@ The configuration file name for this integration is `python.d/dovecot.conf`.
100
101
102
You can edit the configuration file using the `edit-config` script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
105
```bash
106
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/example/integrations/example_collector.md
+2
-2
@@ -19,7 +19,7 @@ Module: example
19
20
Example collector that generates some random numbers as metrics.
21
22
-If you want to write your own collector, read our [writing a new Python module](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md#how-to-write-a-new-module) tutorial.
22
+If you want to write your own collector, read our [writing a new Python module](/src/collectors/python.d.plugin/README.md#how-to-write-a-new-module) tutorial.
23
24
25
The `get_data()` function uses `random.randint()` to generate a random number which will be collected as a metric.
@@ -87,7 +87,7 @@ The configuration file name for this integration is `python.d/example.conf`.
87
88
89
You can edit the configuration file using the `edit-config` script from the
90
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
90
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
91
92
```bash
93
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/example/metadata.yaml
+2
-2
@@ -5,7 +5,7 @@ modules:
5
module_name: example
6
monitored_instance:
7
name: Example collector
8
- link: https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/example/README.md
8
+ link: /src/collectors/python.d.plugin/example/README.md
9
categories:
10
- data-collection.other
11
icon_filename: ""
@@ -24,7 +24,7 @@ modules:
24
metrics_description: |
25
Example collector that generates some random numbers as metrics.
26
27
- If you want to write your own collector, read our [writing a new Python module](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md#how-to-write-a-new-module) tutorial.
27
+ If you want to write your own collector, read our [writing a new Python module](/src/collectors/python.d.plugin/README.md#how-to-write-a-new-module) tutorial.
28
method_description: |
29
The `get_data()` function uses `random.randint()` to generate a random number which will be collected as a metric.
30
supported_platforms:
src/collectors/python.d.plugin/exim/integrations/exim.md
+1
-1
@@ -106,7 +106,7 @@ The configuration file name for this integration is `python.d/exim.conf`.
106
107
108
You can edit the configuration file using the `edit-config` script from the
109
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
111
```bash
112
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/gearman/integrations/gearman.md
+1
-1
@@ -106,7 +106,7 @@ The configuration file name for this integration is `python.d/gearman.conf`.
106
107
108
You can edit the configuration file using the `edit-config` script from the
109
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
111
```bash
112
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/go_expvar/integrations/go_applications_expvar.md
+6
-6
@@ -84,14 +84,14 @@ There are no alerts configured by default for this integration.
84
85
#### Enable the go_expvar collector
86
87
-The `go_expvar` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
87
+The `go_expvar` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
88
89
```bash
90
cd /etc/netdata # Replace this path with your Netdata config directory, if different
91
sudo ./edit-config python.d.conf
92
```
93
94
-Change the value of the `go_expvar` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
94
+Change the value of the `go_expvar` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
95
96
97
#### Sample `expvar` usage in a Go application
@@ -172,7 +172,7 @@ The configuration file name for this integration is `python.d/go_expvar.conf`.
172
173
174
You can edit the configuration file using the `edit-config` script from the
175
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
175
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
176
177
```bash
178
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -231,8 +231,8 @@ See [this issue](https://github.com/netdata/netdata/pull/1902#issuecomment-28449
231
232
Please see these two links to the official Netdata documentation for more information about the values:
233
234
-- [External plugins - charts](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#chart)
235
-- [Chart variables](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md#global-variables-order-and-chart)
234
+- [External plugins - charts](/src/collectors/plugins.d/README.md#chart)
235
+- [Chart variables](/src/collectors/python.d.plugin/README.md#global-variables-order-and-chart)
236
237
**Line definitions**
238
@@ -255,7 +255,7 @@ hidden: False
255
```
256
257
Please see the following link for more information about the options and their default values:
258
-[External plugins - dimensions](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#dimension)
258
+[External plugins - dimensions](/src/collectors/plugins.d/README.md#dimension)
259
260
Apart from top-level expvars, this plugin can also parse expvars stored in a multi-level map;
261
All dicts in the resulting JSON document are then flattened to one level.
src/collectors/python.d.plugin/go_expvar/metadata.yaml
+5
-5
@@ -41,14 +41,14 @@ modules:
41
list:
42
- title: "Enable the go_expvar collector"
43
description: |
44
- The `go_expvar` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
44
+ The `go_expvar` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
45
46
```bash
47
cd /etc/netdata # Replace this path with your Netdata config directory, if different
48
sudo ./edit-config python.d.conf
49
```
50
51
- Change the value of the `go_expvar` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
51
+ Change the value of the `go_expvar` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
52
- title: "Sample `expvar` usage in a Go application"
53
description: |
54
The `expvar` package exposes metrics over HTTP and is very easy to use.
@@ -200,8 +200,8 @@ modules:
200
201
Please see these two links to the official Netdata documentation for more information about the values:
202
203
- - [External plugins - charts](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#chart)
204
- - [Chart variables](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/README.md#global-variables-order-and-chart)
203
+ - [External plugins - charts](/src/collectors/plugins.d/README.md#chart)
204
+ - [Chart variables](/src/collectors/python.d.plugin/README.md#global-variables-order-and-chart)
205
206
**Line definitions**
207
@@ -224,7 +224,7 @@ modules:
224
```
225
226
Please see the following link for more information about the options and their default values:
227
- [External plugins - dimensions](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#dimension)
227
+ [External plugins - dimensions](/src/collectors/plugins.d/README.md#dimension)
228
229
Apart from top-level expvars, this plugin can also parse expvars stored in a multi-level map;
230
All dicts in the resulting JSON document are then flattened to one level.
src/collectors/python.d.plugin/haproxy/README.md
+1
-1
@@ -42,7 +42,7 @@ It produces:
42
## Configuration
43
44
Edit the `python.d/haproxy.conf` configuration file using `edit-config` from the Netdata [config
45
-directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
45
+directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
46
47
```bash
48
cd /etc/netdata # Replace this path with your Netdata config directory, if different
src/collectors/python.d.plugin/haproxy/metadata.yaml
+1
-1
@@ -1,5 +1,5 @@
1
# This collector will not appear in documentation, as the go version is preferred,
2
-# https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/haproxy/README.md
2
+# /src/go/collectors/go.d.plugin/modules/haproxy/README.md
3
#
4
#
5
# meta:
src/collectors/python.d.plugin/icecast/integrations/icecast.md
+1
-1
@@ -89,7 +89,7 @@ The configuration file name for this integration is `python.d/icecast.conf`.
89
90
91
You can edit the configuration file using the `edit-config` script from the
92
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
92
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
93
94
```bash
95
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/ipfs/integrations/ipfs.md
+1
-1
@@ -98,7 +98,7 @@ The configuration file name for this integration is `python.d/ipfs.conf`.
98
99
100
You can edit the configuration file using the `edit-config` script from the
101
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
103
```bash
104
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/memcached/integrations/memcached.md
+1
-1
@@ -107,7 +107,7 @@ The configuration file name for this integration is `python.d/memcached.conf`.
107
108
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/monit/integrations/monit.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `python.d/monit.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/nsd/integrations/name_server_daemon.md
+1
-1
@@ -121,7 +121,7 @@ The configuration file name for this integration is `python.d/nsd.conf`.
121
122
123
You can edit the configuration file using the `edit-config` script from the
124
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
126
```bash
127
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/nvidia_smi/README.md
+1
-1
@@ -44,7 +44,7 @@ It produces the following charts:
44
## Configuration
45
46
Edit the `python.d/nvidia_smi.conf` configuration file using `edit-config` from the Netdata [config
47
-directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
47
+directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
48
49
```bash
50
cd /etc/netdata # Replace this path with your Netdata config directory, if different
src/collectors/python.d.plugin/nvidia_smi/metadata.yaml
+1
-1
@@ -1,5 +1,5 @@
1
# This collector will not appear in documentation, as the go version is preferred,
2
-# https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/nvidia_smi/README.md
2
+# /src/go/collectors/go.d.plugin/modules/nvidia_smi/README.md
3
#
4
# meta:
5
# plugin_name: python.d.plugin
src/collectors/python.d.plugin/openldap/integrations/openldap.md
+1
-1
@@ -129,7 +129,7 @@ The configuration file name for this integration is `python.d/openldap.conf`.
129
130
131
You can edit the configuration file using the `edit-config` script from the
132
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
132
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
133
134
```bash
135
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/oracledb/integrations/oracle_db.md
+1
-1
@@ -137,7 +137,7 @@ The configuration file name for this integration is `python.d/oracledb.conf`.
137
138
139
You can edit the configuration file using the `edit-config` script from the
140
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
140
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
141
142
```bash
143
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/pandas/integrations/pandas.md
+3
-3
@@ -109,7 +109,7 @@ The configuration file name for this integration is `python.d/pandas.conf`.
109
110
111
You can edit the configuration file using the `edit-config` script from the
112
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
114
```bash
115
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -136,8 +136,8 @@ Every configuration JOB starts with a `job_name` value which will appear in the
136
| chart_configs | an array of chart configuration dictionaries | [] | yes |
137
| chart_configs.name | name of the chart to be displayed in the dashboard. | None | yes |
138
| chart_configs.title | title of the chart to be displayed in the dashboard. | None | yes |
139
-| chart_configs.family | [family](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#families) of the chart to be displayed in the dashboard. | None | yes |
140
-| chart_configs.context | [context](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#contexts) of the chart to be displayed in the dashboard. | None | yes |
139
+| chart_configs.family | [family](/docs/dashboards-and-charts/netdata-charts.md#families) of the chart to be displayed in the dashboard. | None | yes |
140
+| chart_configs.context | [context](/docs/dashboards-and-charts/netdata-charts.md#contexts) of the chart to be displayed in the dashboard. | None | yes |
141
| chart_configs.type | the type of the chart to be displayed in the dashboard. | None | yes |
142
| chart_configs.units | the units of the chart to be displayed in the dashboard. | None | yes |
143
| chart_configs.df_steps | a series of pandas operations (one per line) that each returns a dataframe. | None | yes |
src/collectors/python.d.plugin/pandas/metadata.yaml
+2
-2
@@ -90,11 +90,11 @@ modules:
90
default_value: None
91
required: true
92
- name: chart_configs.family
93
- description: "[family](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#families) of the chart to be displayed in the dashboard."
93
+ description: "[family](/docs/dashboards-and-charts/netdata-charts.md#families) of the chart to be displayed in the dashboard."
94
default_value: None
95
required: true
96
- name: chart_configs.context
97
- description: "[context](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/netdata-charts.md#contexts) of the chart to be displayed in the dashboard."
97
+ description: "[context](/docs/dashboards-and-charts/netdata-charts.md#contexts) of the chart to be displayed in the dashboard."
98
default_value: None
99
required: true
100
- name: chart_configs.type
src/collectors/python.d.plugin/puppet/integrations/puppet.md
+1
-1
@@ -91,7 +91,7 @@ The configuration file name for this integration is `python.d/puppet.conf`.
91
92
93
You can edit the configuration file using the `edit-config` script from the
94
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
94
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
96
```bash
97
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/rethinkdbs/integrations/rethinkdb.md
+1
-1
@@ -107,7 +107,7 @@ The configuration file name for this integration is `python.d/rethinkdbs.conf`.
107
108
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/retroshare/integrations/retroshare.md
+1
-1
@@ -97,7 +97,7 @@ The configuration file name for this integration is `python.d/retroshare.conf`.
97
98
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/riakkv/integrations/riakkv.md
+1
-1
@@ -127,7 +127,7 @@ The configuration file name for this integration is `python.d/riakkv.conf`.
127
128
129
You can edit the configuration file using the `edit-config` script from the
130
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
130
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
131
132
```bash
133
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/samba/integrations/samba.md
+3
-3
@@ -91,13 +91,13 @@ There are no alerts configured by default for this integration.
91
92
#### Enable the samba collector
93
94
-The `samba` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
94
+The `samba` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
95
96
```bash
97
cd /etc/netdata # Replace this path with your Netdata config directory, if different
98
sudo ./edit-config python.d.conf
99
```
100
-Change the value of the `samba` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
100
+Change the value of the `samba` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
101
102
103
#### Permissions and programs
@@ -143,7 +143,7 @@ The configuration file name for this integration is `python.d/samba.conf`.
143
144
145
You can edit the configuration file using the `edit-config` script from the
146
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
146
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
148
```bash
149
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/samba/metadata.yaml
+2
-2
@@ -46,13 +46,13 @@ modules:
46
list:
47
- title: Enable the samba collector
48
description: |
49
- The `samba` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
49
+ The `samba` collector is disabled by default. To enable it, use `edit-config` from the Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`, to edit the `python.d.conf` file.
50
51
```bash
52
cd /etc/netdata # Replace this path with your Netdata config directory, if different
53
sudo ./edit-config python.d.conf
54
```
55
- Change the value of the `samba` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
55
+ Change the value of the `samba` setting to `yes`. Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate method](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system.
56
- title: Permissions and programs
57
description: |
58
To run the collector you need:
src/collectors/python.d.plugin/spigotmc/integrations/spigotmc.md
+1
-1
@@ -98,7 +98,7 @@ The configuration file name for this integration is `python.d/spigotmc.conf`.
98
99
100
You can edit the configuration file using the `edit-config` script from the
101
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
103
```bash
104
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/squid/integrations/squid.md
+1
-1
@@ -94,7 +94,7 @@ The configuration file name for this integration is `python.d/squid.conf`.
94
95
96
You can edit the configuration file using the `edit-config` script from the
97
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
99
```bash
100
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/tomcat/integrations/tomcat.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `python.d/tomcat.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/tor/integrations/tor.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `python.d/tor.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/traefik/README.md
+1
-1
@@ -51,7 +51,7 @@ It produces:
51
## Configuration
52
53
Edit the `python.d/traefik.conf` configuration file using `edit-config` from the
54
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically
54
+Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically
55
at `/etc/netdata`.
56
57
```bash
src/collectors/python.d.plugin/traefik/metadata.yaml
+1
-1
@@ -1,5 +1,5 @@
1
# This collector will not appear in documentation, as the go version is preferred,
2
-# https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/traefik/README.md
2
+# /src/go/collectors/go.d.plugin/modules/traefik/README.md
3
#
4
# meta:
5
# plugin_name: python.d.plugin
src/collectors/python.d.plugin/uwsgi/integrations/uwsgi.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `python.d/uwsgi.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/varnish/integrations/varnish.md
+1
-1
@@ -138,7 +138,7 @@ The configuration file name for this integration is `python.d/varnish.conf`.
138
139
140
You can edit the configuration file using the `edit-config` script from the
141
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
141
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
142
143
```bash
144
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/w1sensor/integrations/1-wire_sensors.md
+1
-1
@@ -91,7 +91,7 @@ The configuration file name for this integration is `python.d/w1sensor.conf`.
91
92
93
You can edit the configuration file using the `edit-config` script from the
94
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
94
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
96
```bash
97
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/zscores/integrations/python.d_zscores.md
+2
-2
@@ -20,7 +20,7 @@ Module: zscores
20
By using smoothed, rolling [Z-Scores](https://en.wikipedia.org/wiki/Standard_score) for selected metrics or charts you can narrow down your focus and shorten root cause analysis.
21
22
23
-This collector uses the [Netdata rest api](https://github.com/netdata/netdata/blob/master/src/web/api/README.md) to get the `mean` and `stddev`
23
+This collector uses the [Netdata rest api](/src/web/api/README.md) to get the `mean` and `stddev`
24
for each dimension on specified charts over a time range (defined by `train_secs` and `offset_secs`).
25
26
For each dimension it will calculate a Z-Score as `z = (x - mean) / stddev` (clipped at `z_clip`). Scores are then smoothed over
@@ -100,7 +100,7 @@ The configuration file name for this integration is `python.d/zscores.conf`.
100
101
102
You can edit the configuration file using the `edit-config` script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
105
```bash
106
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/python.d.plugin/zscores/metadata.yaml
+1
-1
@@ -27,7 +27,7 @@ modules:
27
metrics_description: |
28
By using smoothed, rolling [Z-Scores](https://en.wikipedia.org/wiki/Standard_score) for selected metrics or charts you can narrow down your focus and shorten root cause analysis.
29
method_description: |
30
- This collector uses the [Netdata rest api](https://github.com/netdata/netdata/blob/master/src/web/api/README.md) to get the `mean` and `stddev`
30
+ This collector uses the [Netdata rest api](/src/web/api/README.md) to get the `mean` and `stddev`
31
for each dimension on specified charts over a time range (defined by `train_secs` and `offset_secs`).
32
33
For each dimension it will calculate a Z-Score as `z = (x - mean) / stddev` (clipped at `z_clip`). Scores are then smoothed over
src/collectors/slabinfo.plugin/integrations/linux_kernel_slab_allocator_statistics.md
+1
-1
@@ -107,7 +107,7 @@ The file format is a modified INI syntax. The general structure is:
107
option3 = some third value
108
```
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/statsd.plugin/README.md
+16
-16
@@ -40,11 +40,11 @@ On synthetic charts, we can have alerts as with any metric and chart.
40
41
- [K6 load testing tool](https://k6.io)
42
- **Description:** k6 is a developer-centric, free and open-source load testing tool built for making performance testing a productive and enjoyable experience.
43
- - [Documentation](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/k6.md)
43
+ - [Documentation](/src/collectors/statsd.plugin/k6.md)
44
- [Configuration](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/k6.conf)
45
- [Asterisk](https://www.asterisk.org/)
46
- **Description:** Asterisk is an Open Source PBX and telephony toolkit.
47
- - [Documentation](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/asterisk.md)
47
+ - [Documentation](/src/collectors/statsd.plugin/asterisk.md)
48
- [Configuration](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/asterisk.conf)
49
50
## Metrics supported by Netdata
@@ -220,7 +220,7 @@ Netdata can visualize StatsD collected metrics in 2 ways:
220
221
### Private metric charts
222
223
-Private charts are controlled with `create private charts for metrics matching = *`. This setting accepts a space-separated list of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). Netdata will create private charts for all metrics **by default**.
223
+Private charts are controlled with `create private charts for metrics matching = *`. This setting accepts a space-separated list of [simple patterns](/src/libnetdata/simple_pattern/README.md). Netdata will create private charts for all metrics **by default**.
224
225
For example, to render charts for all `myapp.*` metrics, except `myapp.*.badmetric`, use:
226
@@ -228,7 +228,7 @@ For example, to render charts for all `myapp.*` metrics, except `myapp.*.badmetr
228
create private charts for metrics matching = !myapp.*.badmetric myapp.*
229
```
230
231
-You can specify Netdata StatsD to have a different `memory mode` than the rest of the Netdata Agent. You can read more about `memory mode` in the [documentation](https://github.com/netdata/netdata/blob/master/src/database/README.md).
231
+You can specify Netdata StatsD to have a different `memory mode` than the rest of the Netdata Agent. You can read more about `memory mode` in the [documentation](/src/database/README.md).
232
233
The default behavior is to use the same settings as the rest of the Netdata Agent. If you wish to change them, edit the following settings:
234
- `private charts memory mode`
@@ -305,7 +305,7 @@ Synthetic charts are organized in
305
- **charts for each application** aka family in Netdata Dashboard.
306
- **StatsD metrics for each chart** /aka charts and context Netdata Dashboard.
307
308
-> You can read more about how the Netdata Agent organizes information in the relevant [documentation](https://github.com/netdata/netdata/blob/master/src/web/README.md)
308
+> You can read more about how the Netdata Agent organizes information in the relevant [documentation](/src/web/README.md)
309
310
For each application you need to create a `.conf` file in `/etc/netdata/statsd.d`.
311
@@ -341,7 +341,7 @@ Using the above configuration `myapp` should get its own section on the dashboar
341
`[app]` starts a new application definition. The supported settings in this section are:
342
343
- `name` defines the name of the app.
344
-- `metrics` is a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). This pattern should match all the possible StatsD metrics that will be participating in the application `myapp`.
344
+- `metrics` is a Netdata [simple pattern](/src/libnetdata/simple_pattern/README.md). This pattern should match all the possible StatsD metrics that will be participating in the application `myapp`.
345
- `private charts = yes|no`, enables or disables private charts for the metrics matched.
346
- `gaps when not collected = yes|no`, enables or disables gaps on the charts of the application in case that no metrics are collected.
347
- `memory mode` sets the memory mode for all charts of the application. The default is the global default for Netdata (not the global default for StatsD private charts). We suggest not to use this (we have commented it out in the example) and let your app use the global default for Netdata, which is our dbengine.
@@ -367,7 +367,7 @@ So, the format is this:
367
dimension = [pattern] METRIC NAME TYPE MULTIPLIER DIVIDER OPTIONS
368
```
369
370
-`pattern` is a keyword. When set, `METRIC` is expected to be a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) that will be used to match all the StatsD metrics to be added to the chart. So, `pattern` automatically matches any number of StatsD metrics, all of which will be added as separate chart dimensions.
370
+`pattern` is a keyword. When set, `METRIC` is expected to be a Netdata [simple pattern](/src/libnetdata/simple_pattern/README.md) that will be used to match all the StatsD metrics to be added to the chart. So, `pattern` automatically matches any number of StatsD metrics, all of which will be added as separate chart dimensions.
371
372
`TYPE`, `MULTIPLIER`, `DIVIDER` and `OPTIONS` are optional.
373
@@ -728,7 +728,7 @@ In general, the process for creating a StatsD collector can be summarized in 2 s
728
729
- Make sure to reload the dashboard tab **after** you start sending data to Netdata.
730
731
-- Create a configuration file for your app using [edit-config](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md): `sudo ./edit-config
731
+- Create a configuration file for your app using [edit-config](/docs/netdata-agent/configuration/README.md): `sudo ./edit-config
732
statsd.d/myapp.conf`
733
734
- Each app will have it's own section in the right-hand menu.
@@ -737,7 +737,7 @@ Now, let's see the above process in detail.
737
738
### Prerequisites
739
740
-- A node with the [Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md) installed.
740
+- A node with the [Netdata](/packaging/installer/README.md) installed.
741
- An application to instrument. For this guide, that will be [k6](https://k6.io/docs/getting-started/installation).
742
743
### Understanding the metrics
@@ -784,8 +784,8 @@ visualize all the available operations.
784
### Create a new StatsD configuration file
785
786
Start by creating a new configuration file under the `statsd.d/` folder in the
787
-[Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
788
-Use [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf)
787
+[Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
788
+Use [`edit-config`](/docs/netdata-agent/configuration/README.md#edit-netdataconf)
789
to create a new file called `k6.conf`.
790
791
```bash=
@@ -832,7 +832,7 @@ Context is a second way to group metrics, when the metrics are of the same natur
832
our case, if we ran several different load testing experiments side-by-side, we could define the same app,
833
but different context (e.g `http_requests.experiment1`, `http_requests.experiment2`).
834
835
-Find more details about family and context in our [documentation](https://github.com/netdata/netdata/blob/master/src/web/README.md#families).
835
+Find more details about family and context in our [documentation](/src/web/README.md#families).
836
837
#### Dimensions
838
@@ -845,10 +845,10 @@ metrics into different charts. This is particularly important, since we decide:
845
The dimension option has this syntax: `dimension = [pattern] METRIC NAME TYPE MULTIPLIER DIVIDER OPTIONS`
846
847
- **pattern**: A keyword that tells the StatsD server the `METRIC` string is actually a
848
- [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
848
+ [simple pattern](/src/libnetdata/simple_pattern/README.md).
849
We don't use simple patterns in the example, but if we wanted to visualize all the `http_req` metrics, we
850
could have a single dimension: `dimension = pattern 'k6.http_req*' last 1 1`. Find detailed examples with
851
- patterns in [dimension patterns](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/README.md#dimension-patterns).
851
+ patterns in [dimension patterns](/src/collectors/statsd.plugin/README.md#dimension-patterns).
852
853
- **METRIC** The id of the metric as it comes from the client. You can easily find this in the private charts above,
854
for example: `k6.http_req_connecting`.
@@ -973,7 +973,7 @@ Note that Netdata will report the rate for metrics and counters, even if k6 or a
973
sends an _absolute_ number. For example, k6 sends absolute HTTP requests with `http_reqs`,
974
but Netdata visualizes that in `requests/second`.
975
976
-To enable this StatsD configuration, [restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
976
+To enable this StatsD configuration, [restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
977
978
### Final touches
979
@@ -981,7 +981,7 @@ At this point, you have used StatsD to gather metrics for k6, creating a whole n
981
Netdata dashboard in the process. Moreover, you can further customize the icon of the particular section,
982
as well as the description for each chart.
983
984
-To edit the section, please follow the Netdata [documentation](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md#customizing-the-local-dashboard).
984
+To edit the section, please follow the Netdata [documentation](/src/web/gui/README.md#customizing-the-local-dashboard).
985
986
While the following configuration will be placed in a new file, as the documentation suggests, it is
987
instructing to use `dashboard_info.js` as a template. Open the file and see how the rest of sections and collectors have been defined.
src/collectors/systemd-journal.plugin/README.md
+1
-1
@@ -457,7 +457,7 @@ For more options and reference to documentation, check `man systemd-journal-remo
457
458
#### _passive_ journal centralization without encryption
459
460
-If you want to setup your own passive journal centralization setup without encryption, [check out guide on it](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/logs-centralization-points-with-systemd-journald/passive-journal-centralization-without-encryption.md).
460
+If you want to setup your own passive journal centralization setup without encryption, [check out guide on it](/docs/observability-centralization-points/logs-centralization-points-with-systemd-journald/passive-journal-centralization-without-encryption.md).
461
462
#### _passive_ journal centralization with encryption using self-signed certificates
463
src/collectors/tc.plugin/integrations/tc_qos_classes.md
+1
-1
@@ -117,7 +117,7 @@ The file format is a modified INI syntax. The general structure is:
117
option3 = some third value
118
```
119
You can edit the configuration file using the `edit-config` script from the
120
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
122
```bash
123
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/timex.plugin/integrations/timex.md
+1
-1
@@ -103,7 +103,7 @@ The file format is a modified INI syntax. The general structure is:
103
option3 = some third value
104
```
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/collectors/xenstat.plugin/integrations/xen_xcp-ng.md
+1
-1
@@ -152,7 +152,7 @@ The file format is a modified INI syntax. The general structure is:
152
option3 = some third value
153
```
154
You can edit the configuration file using the `edit-config` script from the
155
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
155
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
156
157
```bash
158
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/daemon/README.md
+5
-5
@@ -2,7 +2,7 @@
2
3
The Netdata daemon is practically a synonym for the Netdata Agent, as it controls its
4
entire operation. We support various methods to
5
-[start, stop, or restart the daemon](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
5
+[start, stop, or restart the daemon](/packaging/installer/README.md#maintaining-a-netdata-agent-installation).
6
7
This document provides some basic information on the command line options, log files, and how to debug and troubleshoot
8
@@ -113,7 +113,7 @@ The command line options of the Netdata 1.10.0 version are the following:
113
- USR2 Reload health configuration.
114
```
115
116
-You can send commands during runtime via [netdatacli](https://github.com/netdata/netdata/blob/master/src/cli/README.md).
116
+You can send commands during runtime via [netdatacli](/src/cli/README.md).
117
118
## Log files
119
@@ -142,7 +142,7 @@ For most Netdata programs (including standard external plugins shipped by netdat
142
| `ERROR` | Something that might disable a part of netdata.<br/>The log line includes `errno` (if it is not zero). |
143
| `FATAL` | Something prevented a program from running.<br/>The log line includes `errno` (if it is not zero) and the program exited. |
144
145
-The `FATAL` and `ERROR` messages will always appear in the logs, and `INFO`can be filtered using [severity level](https://github.com/netdata/netdata/blob/master/src/daemon/config/README.md#logs-section-options) option.
145
+The `FATAL` and `ERROR` messages will always appear in the logs, and `INFO`can be filtered using [severity level](/src/daemon/config/README.md#logs-section-options) option.
146
147
So, when auto-detection of data collection fail, `ERROR` lines are logged and the relevant modules are disabled, but the
148
program continues to run.
@@ -151,7 +151,7 @@ When a Netdata program cannot run at all, a `FATAL` line is logged.
151
152
### collector.log
153
154
-The `collector.log` is the `stderr` of all [collectors](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md)
154
+The `collector.log` is the `stderr` of all [collectors](/src/collectors/COLLECTORS.md)
155
run by `netdata`.
156
157
So if any process, in the Netdata process tree, writes anything to its standard error,
@@ -281,7 +281,7 @@ all programs), edit `netdata.conf` and set:
281
process nice level = -1
282
```
283
284
-then execute this to [restart Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation):
284
+then execute this to [restart Netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation):
285
286
```sh
287
sudo systemctl restart netdata
src/daemon/config/README.md
+30
-30
@@ -25,24 +25,24 @@ adapt the general behavior of Netdata, in great detail. You can find all these s
25
accessing the URL `https://netdata.server.hostname:19999/netdata.conf`. For example check the configuration file
26
of [netdata.firehol.org](http://netdata.firehol.org/netdata.conf). HTTP access to this file is limited by default to
27
[private IPs](https://en.wikipedia.org/wiki/Private_network), via
28
-the [web server access lists](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#access-lists).
28
+the [web server access lists](/src/web/server/README.md#access-lists).
29
30
`netdata.conf` has sections stated with `[section]`. You will see the following sections:
31
32
-1. `[global]` to [configure](#global-section-options) the [Netdata daemon](https://github.com/netdata/netdata/blob/master/src/daemon/README.md).
32
+1. `[global]` to [configure](#global-section-options) the [Netdata daemon](/src/daemon/README.md).
33
2. `[db]` to [configure](#db-section-options) the database of Netdata.
34
3. `[directories]` to [configure](#directories-section-options) the directories used by Netdata.
35
4. `[logs]` to [configure](#logs-section-options) the Netdata logging.
36
5. `[environment variables]` to [configure](#environment-variables-section-options) the environment variables used
37
Netdata.
38
-6. `[sqlite]` to [configure](#sqlite-section-options) the [Netdata daemon](https://github.com/netdata/netdata/blob/master/src/daemon/README.md) SQLite settings.
39
-7. `[ml]` to configure settings for [machine learning](https://github.com/netdata/netdata/blob/master/src/ml/README.md).
40
-8. `[health]` to [configure](#health-section-options) general settings for [health monitoring](https://github.com/netdata/netdata/blob/master/src/health/README.md).
41
-9. `[web]` to [configure the web server](https://github.com/netdata/netdata/blob/master/src/web/server/README.md).
42
-10. `[registry]` for the [Netdata registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md).
43
-11. `[global statistics]` for the [Netdata registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md).
44
-12. `[statsd]` for the general settings of the [stats.d.plugin](https://github.com/netdata/netdata/blob/master/src/collectors/statsd.plugin/README.md).
45
-13. `[plugins]` to [configure](#plugins-section-options) which [collectors](https://github.com/netdata/netdata/blob/master/src/collectors/README.md) to use and PATH
38
+6. `[sqlite]` to [configure](#sqlite-section-options) the [Netdata daemon](/src/daemon/README.md) SQLite settings.
39
+7. `[ml]` to configure settings for [machine learning](/src/ml/README.md).
40
+8. `[health]` to [configure](#health-section-options) general settings for [health monitoring](/src/health/README.md).
41
+9. `[web]` to [configure the web server](/src/web/server/README.md).
42
+10. `[registry]` for the [Netdata registry](/src/registry/README.md).
43
+11. `[global statistics]` for the [Netdata registry](/src/registry/README.md).
44
+12. `[statsd]` for the general settings of the [stats.d.plugin](/src/collectors/statsd.plugin/README.md).
45
+13. `[plugins]` to [configure](#plugins-section-options) which [collectors](/src/collectors/README.md) to use and PATH
46
settings.
47
14. `[plugin:NAME]` sections for each collector plugin, under the
48
comment [Per plugin configuration](#per-plugin-configuration).
@@ -53,7 +53,7 @@ comment on settings it does not currently use.
53
54
## Applying changes
55
56
-After `netdata.conf` has been modified, Netdata needs to be [restarted](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for
56
+After `netdata.conf` has been modified, Netdata needs to be [restarted](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for
57
changes to apply:
58
59
```bash
@@ -74,10 +74,10 @@ Please note that your data history will be lost if you have modified `history` p
74
75
| setting | default | info |
76
|:----------------------------------:|:-------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
77
-| process scheduling policy | `keep` | See [Netdata process scheduling policy](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#netdata-process-scheduling-policy) |
77
+| process scheduling policy | `keep` | See [Netdata process scheduling policy](/src/daemon/README.md#netdata-process-scheduling-policy) |
78
| OOM score | `0` | |
79
-| glibc malloc arena max for plugins | `1` | See [Virtual memory](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#virtual-memory). |
80
-| glibc malloc arena max for Netdata | `1` | See [Virtual memory](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#virtual-memory). |
79
+| glibc malloc arena max for plugins | `1` | See [Virtual memory](/src/daemon/README.md#virtual-memory). |
80
+| glibc malloc arena max for Netdata | `1` | See [Virtual memory](/src/daemon/README.md#virtual-memory). |
81
| hostname | auto-detected | The hostname of the computer running Netdata. |
82
| host access prefix | empty | This is used in docker environments where /proc, /sys, etc have to be accessed via another path. You may also have to set SYS_PTRACE capability on the docker for this work. Check [issue 43](https://github.com/netdata/netdata/issues/43). |
83
| timezone | auto-detected | The timezone retrieved from the environment variable |
@@ -89,18 +89,18 @@ Please note that your data history will be lost if you have modified `history` p
89
| setting | default | info |
90
|:---------------------------------------------:|:----------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
91
| mode | `dbengine` | `dbengine`: The default for long-term metrics storage with efficient RAM and disk usage. Can be extended with `dbengine page cache size MB` and `dbengine disk space MB`. <br />`ram`: The round-robin database will be temporary and it will be lost when Netdata exits. <br />`alloc`: Similar to `ram`, but can significantly reduce memory usage, when combined with a low retention and does not support KSM. <br />`none`: Disables the database at this host, and disables health monitoring entirely, as that requires a database of metrics. Not to be used together with streaming. |
92
-| retention | `3600` | Used with `mode = ram/alloc`, not the default `mode = dbengine`. This number reflects the number of entries the `netdata` daemon will by default keep in memory for each chart dimension. Check [Memory Requirements](https://github.com/netdata/netdata/blob/master/src/database/README.md) for more information. |
93
-| storage tiers | `3` | The number of storage tiers you want to have in your dbengine. Check the tiering mechanism in the [dbengine's reference](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiering). You can have up to 5 tiers of data (including the _Tier 0_). This number ranges between 1 and 5. |
92
+| retention | `3600` | Used with `mode = ram/alloc`, not the default `mode = dbengine`. This number reflects the number of entries the `netdata` daemon will by default keep in memory for each chart dimension. Check [Memory Requirements](/src/database/README.md) for more information. |
93
+| storage tiers | `3` | The number of storage tiers you want to have in your dbengine. Check the tiering mechanism in the [dbengine's reference](/src/database/engine/README.md#tiering). You can have up to 5 tiers of data (including the _Tier 0_). This number ranges between 1 and 5. |
94
| dbengine page cache size MB | `32` | Determines the amount of RAM in MiB that is dedicated to caching for _Tier 0_ Netdata metric values. |
95
| dbengine tier **`N`** page cache size MB | `32` | Determines the amount of RAM in MiB that is dedicated for caching Netdata metric values of the **`N`** tier. <br /> `N belongs to [1..4]` |
96
| dbengine disk space MB | `256` | Determines the amount of disk space in MiB that is dedicated to storing _Tier 0_ Netdata metric values and all related metadata describing them. This option is available **only for legacy configuration** (`Agent v1.23.2 and prior`). |
97
| dbengine multihost disk space MB | `256` | Same functionality as `dbengine disk space MB`, but includes support for storing metrics streamed to a parent node by its children. Can be used in single-node environments as well. This setting is only for _Tier 0_ metrics. |
98
| dbengine tier **`N`** multihost disk space MB | `256` | Same functionality as `dbengine multihost disk space MB`, but stores metrics of the **`N`** tier (both parent node and its children). Can be used in single-node environments as well. <br /> `N belongs to [1..4]` |
99
-| update every | `1` | The frequency in seconds, for data collection. For more information see the [performance guide](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md). These metrics stored as _Tier 0_ data. Explore the tiering mechanism in the [dbengine's reference](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiering). |
99
+| update every | `1` | The frequency in seconds, for data collection. For more information see the [performance guide](/docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md). These metrics stored as _Tier 0_ data. Explore the tiering mechanism in the [dbengine's reference](/src/database/engine/README.md#tiering). |
100
| dbengine tier **`N`** update every iterations | `60` | The down sampling value of each tier from the previous one. For each Tier, the greater by one Tier has N (equal to 60 by default) less data points of any metric it collects. This setting can take values from `2` up to `255`. <br /> `N belongs to [1..4]` |
101
| dbengine tier **`N`** back fill | `New` | Specifies the strategy of recreating missing data on each Tier from the exact lower Tier. <br /> `New`: Sees the latest point on each Tier and save new points to it only if the exact lower Tier has available points for it's observation window (`dbengine tier N update every iterations` window). <br /> `none`: No back filling is applied. <br /> `N belongs to [1..4]` |
102
-| memory deduplication (ksm) | `yes` | When set to `yes`, Netdata will offer its in-memory round robin database and the dbengine page cache to kernel same page merging (KSM) for deduplication. For more information check [Memory Deduplication - Kernel Same Page Merging - KSM](https://github.com/netdata/netdata/blob/master/src/database/README.md#ksm) |
103
-| cleanup obsolete charts after secs | `3600` | See [monitoring ephemeral containers](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/README.md#monitoring-ephemeral-containers), also sets the timeout for cleaning up obsolete dimensions |
102
+| memory deduplication (ksm) | `yes` | When set to `yes`, Netdata will offer its in-memory round robin database and the dbengine page cache to kernel same page merging (KSM) for deduplication. For more information check [Memory Deduplication - Kernel Same Page Merging - KSM](/src/database/README.md#ksm) |
103
+| cleanup obsolete charts after secs | `3600` | See [monitoring ephemeral containers](/src/collectors/cgroups.plugin/README.md#monitoring-ephemeral-containers), also sets the timeout for cleaning up obsolete dimensions |
104
| gap when lost iterations above | `1` | |
105
| cleanup orphan hosts after secs | `3600` | How long to wait until automatically removing from the DB a remote Netdata host (child) that is no longer sending data. |
106
| enable zero metrics | `no` | Set to `yes` to show charts when all their metrics are zero. |
@@ -115,7 +115,7 @@ Please note that your data history will be lost if you have modified `history` p
115
|:-------------------:|:------------------------------------------------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
116
| config | `/etc/netdata` | The directory configuration files are kept. |
117
| stock config | `/usr/lib/netdata/conf.d` | |
118
-| log | `/var/log/netdata` | The directory in which the [log files](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#log-files) are kept. |
118
+| log | `/var/log/netdata` | The directory in which the [log files](/src/daemon/README.md#log-files) are kept. |
119
| web | `/usr/share/netdata/web` | The directory the web static files are kept. |
120
| cache | `/var/cache/netdata` | The directory the memory database will be stored if and when Netdata exits. Netdata will re-read the database when it will start again, to continue from the same point. |
121
| lib | `/var/lib/netdata` | Contains the alert log and the Netdata instance GUID. |
@@ -124,14 +124,14 @@ Please note that your data history will be lost if you have modified `history` p
124
| plugins | `"/usr/libexec/netdata/plugins.d" "/etc/netdata/custom-plugins.d"` | The directory plugin programs are kept. This setting supports multiple directories, space separated. If any directory path contains spaces, enclose it in single or double quotes. |
125
| health config | `/etc/netdata/health.d` | The directory containing the user alert configuration files, to override the stock configurations |
126
| stock health config | `/usr/lib/netdata/conf.d/health.d` | Contains the stock alert configuration files for each collector |
127
-| registry | `/opt/netdata/var/lib/netdata/registry` | Contains the [registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md) database and GUID that uniquely identifies each Netdata Agent |
127
+| registry | `/opt/netdata/var/lib/netdata/registry` | Contains the [registry](/src/registry/README.md) database and GUID that uniquely identifies each Netdata Agent |
128
129
### [logs] section options
130
131
| setting | default | info |
132
|:----------------------------------:|:-----------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
133
-| debug flags | `0x0000000000000000` | Bitmap of debug options to enable. For more information check [Tracing Options](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#debugging). |
134
-| debug | `/var/log/netdata/debug.log` | The filename to save debug information. This file will not be created if debugging is not enabled. You can also set it to `syslog` to send the debug messages to syslog, or `none` to disable this log. For more information check [Tracing Options](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#debugging). |
133
+| debug flags | `0x0000000000000000` | Bitmap of debug options to enable. For more information check [Tracing Options](/src/daemon/README.md#debugging). |
134
+| debug | `/var/log/netdata/debug.log` | The filename to save debug information. This file will not be created if debugging is not enabled. You can also set it to `syslog` to send the debug messages to syslog, or `none` to disable this log. For more information check [Tracing Options](/src/daemon/README.md#debugging). |
135
| error | `/var/log/netdata/error.log` | The filename to save error messages for Netdata daemon and all plugins (`stderr` is sent here for all Netdata programs, including the plugins). You can also set it to `syslog` to send the errors to syslog, or `none` to disable this log. |
136
| access | `/var/log/netdata/access.log` | The filename to save the log of web clients accessing Netdata charts. You can also set it to `syslog` to send the access log to syslog, or `none` to disable this log. |
137
| facility | `daemon` | A facility keyword is used to specify the type of system that is logging the message. |
@@ -163,9 +163,9 @@ Please note that your data history will be lost if you have modified `history` p
163
This section controls the general behavior of the health monitoring capabilities of Netdata.
164
165
Specific alerts are configured in per-collector config files under the `health.d` directory. For more info, see [health
166
-monitoring](https://github.com/netdata/netdata/blob/master/src/health/README.md).
166
+monitoring](/src/health/README.md).
167
168
-[Alert notifications](https://github.com/netdata/netdata/blob/master/src/health/notifications/README.md) are configured in `health_alarm_notify.conf`.
168
+[Alert notifications](/src/health/notifications/README.md) are configured in `health_alarm_notify.conf`.
169
170
| setting | default | info |
171
|:----------------------------------------------:|:------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -175,11 +175,11 @@ monitoring](https://github.com/netdata/netdata/blob/master/src/health/README.md)
175
| run at least every seconds | `10` | Controls how often all alert conditions should be evaluated. |
176
| postpone alarms during hibernation for seconds | `60` | Prevents false alerts. May need to be increased if you get alerts during hibernation. |
177
| health log history | `432000` | Specifies the history of alert events (in seconds) kept in the agent's sqlite database. |
178
-| enabled alarms | * | Defines which alerts to load from both user and stock directories. This is a [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) list of alert or template names. Can be used to disable specific alerts. For example, `enabled alarms = !oom_kill *` will load all alerts except `oom_kill`. |
178
+| enabled alarms | * | Defines which alerts to load from both user and stock directories. This is a [simple pattern](/src/libnetdata/simple_pattern/README.md) list of alert or template names. Can be used to disable specific alerts. For example, `enabled alarms = !oom_kill *` will load all alerts except `oom_kill`. |
179
180
### [web] section options
181
182
-Refer to the [web server documentation](https://github.com/netdata/netdata/blob/master/src/web/server/README.md)
182
+Refer to the [web server documentation](/src/web/server/README.md)
183
184
### [plugins] section options
185
@@ -199,7 +199,7 @@ Additionally, there will be the following options:
199
### [registry] section options
200
201
To understand what this section is and how it should be configured, please refer to
202
-the [registry documentation](https://github.com/netdata/netdata/blob/master/src/registry/README.md).
202
+the [registry documentation](/src/registry/README.md).
203
204
## Per-plugin configuration
205
@@ -207,7 +207,7 @@ The configuration options for plugins appear in sections following the pattern `
207
208
### Internal plugins
209
210
-Most internal plugins will provide additional options. Check [Internal Plugins](https://github.com/netdata/netdata/blob/master/src/collectors/README.md) for more
210
+Most internal plugins will provide additional options. Check [Internal Plugins](/src/collectors/README.md) for more
211
information.
212
213
Please note, that by default Netdata will enable monitoring metrics for disks, memory, and network only when they are
@@ -223,7 +223,7 @@ External plugins will have only 2 options at `netdata.conf`:
223
224
| setting | default | info |
225
|:---------------:|:--------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
226
-| update every | the value of `[global].update every` setting | The frequency in seconds the plugin should collect values. For more information check the [performance guide](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md). |
226
+| update every | the value of `[global].update every` setting | The frequency in seconds the plugin should collect values. For more information check the [performance guide](/docs/netdata-agent/configuration/optimize-the-netdata-agents-performance.md). |
227
| command options | - | Additional command line options to pass to the plugin. |
228
229
External plugins that need additional configuration may support a dedicated file in `/etc/netdata`. Check their
src/database/README.md
+6
-6
@@ -3,12 +3,12 @@
3
Netdata is fully capable of long-term metrics storage, at per-second granularity, via its default database engine
4
(`dbengine`). But to remain as flexible as possible, Netdata supports several storage options:
5
6
-1. `dbengine`, (the default) data are in database files. The [Database Engine](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md) works like a
6
+1. `dbengine`, (the default) data are in database files. The [Database Engine](/src/database/engine/README.md) works like a
7
traditional database. There is some amount of RAM dedicated to data caching and indexing and the rest of the data
8
reside compressed on disk. The number of history entries is not fixed in this case, but depends on the configured
9
disk space and the effective compression ratio of the data stored. This is the **only mode** that supports changing
10
the data collection update frequency (`update every`) **without losing** the previously stored metrics. For more
11
- details see [here](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md).
11
+ details see [here](/src/database/engine/README.md).
12
13
2. `ram`, data are purely in memory. Data are never saved on disk. This mode uses `mmap()` and supports [KSM](#ksm).
14
@@ -23,13 +23,13 @@ The default mode `[db].mode = dbengine` has been designed to scale for longer re
23
for parent Agents in the _Parent - Child_ setups
24
25
The other available database modes are designed to minimize resource utilization and should only be considered on
26
-[Parent - Child](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md) setups at the children side and only when the
26
+[Parent - Child](/docs/observability-centralization-points/README.md) setups at the children side and only when the
27
resource constraints are very strict.
28
29
So,
30
31
- On a single node setup, use `[db].mode = dbengine`.
32
-- On a [Parent - Child](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md) setup, use `[db].mode = dbengine` on the
32
+- On a [Parent - Child](/docs/observability-centralization-points/README.md) setup, use `[db].mode = dbengine` on the
33
parent to increase retention, and a more resource-efficient mode like, `dbengine` with light retention settings, `ram`, or `none` for the children to minimize resource utilization.
34
35
## Choose your database mode
@@ -48,7 +48,7 @@ Metrics retention is controlled only by the disk space allocated to storing metr
48
CPU required by the agent to query longer timeframes.
49
50
Since Netdata Agents usually run on the edge, on production systems, Netdata Agent **parents** should be considered.
51
-When having a [**parent - child**](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md) setup, the child (the
51
+When having a [**parent - child**](/docs/observability-centralization-points/README.md) setup, the child (the
52
Netdata Agent running on a production system) delegates all of its functions, including longer metrics retention and
53
querying, to the parent node that can dedicate more resources to this task. A single Netdata Agent parent can centralize
54
multiple children Netdata Agents (dozens, hundreds, or even thousands depending on its available resources).
@@ -69,7 +69,7 @@ every 2 seconds. This will **cut in half** both CPU and RAM resources consumed b
69
On very weak devices you might have to use `[db].update every = 5` and `[db].retention = 720` (still 1 hour of data, but
70
1/5 of the CPU and RAM resources).
71
72
-You can also disable [data collection plugins](https://github.com/netdata/netdata/blob/master/src/collectors/README.md) that you don't need. Disabling such plugins will also
72
+You can also disable [data collection plugins](/src/collectors/README.md) that you don't need. Disabling such plugins will also
73
free both CPU and RAM resources.
74
75
## Memory optimizations
src/database/engine/README.md
+1
-1
@@ -114,7 +114,7 @@ When the Netdata Agent starts, during the first data collection of each metric,
114
data from lower tiers, so that the aggregation they provide will be accurate.
115
116
Configuring how the number of tiers and the disk space allocated to each tier is how you can
117
-[change how long netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
117
+[change how long netdata stores metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
118
119
### Data loss
120
src/exporting/README.md
+14
-14
@@ -15,13 +15,13 @@ configuring, and monitoring Netdata's exporting engine, which allows you to send
15
databases.
16
17
For a quick introduction to the exporting engine's features, read our doc on [exporting metrics to time-series
18
-databases](https://github.com/netdata/netdata/blob/master/docs/exporting-metrics/README.md), or jump in to [enabling a connector](https://github.com/netdata/netdata/blob/master/docs/exporting-metrics/enable-an-exporting-connector.md).
18
+databases](/docs/exporting-metrics/README.md), or jump in to [enabling a connector](/docs/exporting-metrics/enable-an-exporting-connector.md).
19
20
The exporting engine has a modular structure and supports metric exporting via multiple exporting connector instances at
21
the same time. You can have different update intervals and filters configured for every exporting connector instance.
22
23
When you enable the exporting engine and a connector, the Netdata Agent exports metrics _beginning from the time you
24
-restart its process_, not the entire [database of long-term metrics](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
24
+restart its process_, not the entire [database of long-term metrics](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md).
25
26
Since Netdata collects thousands of metrics per server per second, which would easily congest any database server when
27
several Netdata servers are sending data to it, Netdata allows sending metrics at a lower frequency, by resampling them.
@@ -34,27 +34,27 @@ X seconds (though, it can send them per second if you need it to).
34
### Integration
35
36
The exporting engine uses a number of connectors to send Netdata metrics to external time-series databases. See our
37
-[list of supported databases](https://github.com/netdata/netdata/blob/master/docs/exporting-metrics/README.md#supported-databases) for information on which
37
+[list of supported databases](/docs/exporting-metrics/README.md#supported-databases) for information on which
38
connector to enable and configure for your database of choice.
39
40
-- [**AWS Kinesis Data Streams**](https://github.com/netdata/netdata/blob/master/src/exporting/aws_kinesis/README.md): Metrics are sent to the service in `JSON`
40
+- [**AWS Kinesis Data Streams**](/src/exporting/aws_kinesis/README.md): Metrics are sent to the service in `JSON`
41
format.
42
-- [**Google Cloud Pub/Sub Service**](https://github.com/netdata/netdata/blob/master/src/exporting/pubsub/README.md): Metrics are sent to the service in `JSON`
42
+- [**Google Cloud Pub/Sub Service**](/src/exporting/pubsub/README.md): Metrics are sent to the service in `JSON`
43
format.
44
-- [**Graphite**](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md): A plaintext interface. Metrics are sent to the database server as
44
+- [**Graphite**](/src/exporting/graphite/README.md): A plaintext interface. Metrics are sent to the database server as
45
`prefix.hostname.chart.dimension`. `prefix` is configured below, `hostname` is the hostname of the machine (can
46
also be configured). Learn more in our guide to [export and visualize Netdata metrics in
47
- Graphite](https://github.com/netdata/netdata/blob/master/src/exporting/graphite/README.md).
48
-- [**JSON** document databases](https://github.com/netdata/netdata/blob/master/src/exporting/json/README.md)
49
-- [**OpenTSDB**](https://github.com/netdata/netdata/blob/master/src/exporting/opentsdb/README.md): Use a plaintext or HTTP interfaces. Metrics are sent to
47
+ Graphite](/src/exporting/graphite/README.md).
48
+- [**JSON** document databases](/src/exporting/json/README.md)
49
+- [**OpenTSDB**](/src/exporting/opentsdb/README.md): Use a plaintext or HTTP interfaces. Metrics are sent to
50
OpenTSDB as `prefix.chart.dimension` with tag `host=hostname`.
51
-- [**MongoDB**](https://github.com/netdata/netdata/blob/master/src/exporting/mongodb/README.md): Metrics are sent to the database in `JSON` format.
52
-- [**Prometheus**](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/README.md): Use an existing Prometheus installation to scrape metrics
51
+- [**MongoDB**](/src/exporting/mongodb/README.md): Metrics are sent to the database in `JSON` format.
52
+- [**Prometheus**](/src/exporting/prometheus/README.md): Use an existing Prometheus installation to scrape metrics
53
from node using the Netdata API.
54
-- [**Prometheus remote write**](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md). A binary snappy-compressed protocol
54
+- [**Prometheus remote write**](/src/exporting/prometheus/remote_write/README.md). A binary snappy-compressed protocol
55
buffer encoding over HTTP. Supports many [storage
56
providers](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage).
57
-- [**TimescaleDB**](https://github.com/netdata/netdata/blob/master/src/exporting/TIMESCALE.md): Use a community-built connector that takes JSON streams from a
57
+- [**TimescaleDB**](/src/exporting/TIMESCALE.md): Use a community-built connector that takes JSON streams from a
58
Netdata client and writes them to a TimescaleDB table.
59
60
### Chart filtering
@@ -295,7 +295,7 @@ Configure individual connectors and override any global settings with the follow
295
Netdata can send metrics to external databases using the TLS/SSL protocol. Unfortunately, some of
296
them does not support encrypted connections, so you will have to configure a reverse proxy to enable
297
HTTPS communication between Netdata and an external database. You can set up a reverse proxy with
298
-[Nginx](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md).
298
+[Nginx](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md).
299
300
## Exporting engine monitoring
301
src/exporting/WALKTHROUGH.md
+2
-2
@@ -57,7 +57,7 @@ command to run (`/bin/bash`) and then chooses the base container images (`centos
57
be sitting inside the shell of the container.
58
59
After we have entered the shell we can install Netdata. This process could not be easier. If you take a look at [this
60
-link](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md), the Netdata devs give us several one-liners to install Netdata. I have not had
60
+link](/packaging/installer/README.md), the Netdata devs give us several one-liners to install Netdata. I have not had
61
any issues with these one liners and their bootstrapping scripts so far (If you guys run into anything do share). Run
62
the following command in your container.
63
@@ -217,7 +217,7 @@ the `chart` dimension. If you'd like you can combine the `chart` and `instance`
217
Let's give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`
218
219
This is the basics of using Prometheus to query Netdata. I'd advise everyone at this point to read [this
220
-page](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/README.md#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
220
+page](/src/exporting/prometheus/README.md#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
221
its internal DB or can send metrics _as-collected_ by specifying the `source=as-collected` URL parameter like so.
222
<http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use
223
this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to
src/exporting/aws_kinesis/integrations/aws_kinesis.md
+1
-1
@@ -50,7 +50,7 @@ The configuration file name for this integration is `exporting.conf`.
50
51
52
You can edit the configuration file using the `edit-config` script from the
53
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
53
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
54
55
```bash
56
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/graphite/integrations/blueflood.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `exporting.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/graphite/integrations/graphite.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `exporting.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/graphite/integrations/influxdb.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `exporting.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/graphite/integrations/kairosdb.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `exporting.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/json/integrations/json.md
+1
-1
@@ -37,7 +37,7 @@ The configuration file name for this integration is `exporting.conf`.
37
38
39
You can edit the configuration file using the `edit-config` script from the
40
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
40
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
42
```bash
43
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/mongodb/integrations/mongodb.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `exporting.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/opentsdb/integrations/opentsdb.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `exporting.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/README.md
+2
-2
@@ -4,7 +4,7 @@ Netdata supports exporting metrics to Prometheus in two ways:
4
5
- You can [configure Prometheus to scrape Netdata metrics](#configure-prometheus-to-scrape-netdata-metrics).
6
7
- - You can [configure Netdata to push metrics to Prometheus](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/remote_write/README.md)
7
+ - You can [configure Netdata to push metrics to Prometheus](/src/exporting/prometheus/remote_write/README.md)
8
, using the Prometheus remote write API.
9
10
## Netdata support for Prometheus
@@ -223,7 +223,7 @@ Netdata can filter the metrics it sends to Prometheus with this setting:
223
```
224
225
This settings accepts a space separated list
226
-of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match the
226
+of [simple patterns](/src/libnetdata/simple_pattern/README.md) to match the
227
**charts** to be sent to Prometheus. Each pattern can use `*` as wildcard, any number of times (e.g `*a*b*c*` is valid).
228
Patterns starting with `!` give a negative match (e.g `!*.bad users.* groups.*` will send all the users and groups
229
except `bad` user and `bad` group). The order is important: the first match (positive or negative) left to right, is
src/exporting/prometheus/integrations/appoptics.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/azure_data_explorer.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/azure_event_hub.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/chronix.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/cortex.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/cratedb.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/elasticsearch.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/gnocchi.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/google_bigquery.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/irondb.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/kafka.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/m3db.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/metricfire.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/new_relic.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/postgresql.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/prometheus_remote_write.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/quasardb.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/splunk_signalfx.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/thanos.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/tikv.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/timescaledb.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/victoriametrics.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/vmware_aria.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/prometheus/integrations/wavefront.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `exporting.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/exporting/pubsub/integrations/google_cloud_pub_sub.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `exporting.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/README.md
+5
-5
@@ -1,7 +1,7 @@
1
<!--
2
title: go.d.plugin
3
description: "go.d.plugin is an external plugin for Netdata, responsible for running individual data collectors written in Go."
4
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/README.md"
4
+custom_edit_url: "/src/go/collectors/go.d.plugin/README.md"
5
sidebar_label: "go.d.plugin"
6
learn_status: "Published"
7
learn_topic_type: "Tasks"
@@ -35,7 +35,7 @@ Go.d.plugin is shipped with Netdata.
35
### Required Linux capabilities
36
37
All capabilities are set automatically during Netdata installation using
38
-the [official installation method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#install-on-linux-with-one-line-installer).
38
+the [official installation method](/packaging/installer/README.md#install-on-linux-with-one-line-installer).
39
No further action required. If you have used a different installation method and need to set the capabilities manually,
40
see the appropriate collector readme.
41
@@ -141,7 +141,7 @@ see the appropriate collector readme.
141
## Configuration
142
143
Edit the `go.d.conf` configuration file using `edit-config` from the
144
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory),
144
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory),
145
which is typically at `/etc/netdata`.
146
147
```bash
@@ -173,7 +173,7 @@ modules:
173
example: yes
174
```
175
176
-Then [restart netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
176
+Then [restart netdata](/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
177
for the change to take effect.
178
179
## Contributing
@@ -184,7 +184,7 @@ contact us in our forums.
184
185
### How to develop a collector
186
187
-Read [how to write a Netdata collector in Go](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/docs/how-to-write-a-module.md).
187
+Read [how to write a Netdata collector in Go](/src/go/collectors/go.d.plugin/docs/how-to-write-a-module.md).
188
189
## Troubleshooting
190
src/go/collectors/go.d.plugin/docs/how-to-write-a-module.md
+5
-5
@@ -1,7 +1,7 @@
1
<!--
2
title: "How to write a Netdata collector in Go"
3
description: "This guide will walk you through the technical implementation of writing a new Netdata collector in Golang, with tips on interfaces, structure, configuration files, and more."
4
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/docs/how-to-write-a-module.md"
4
+custom_edit_url: "/src/go/collectors/go.d.plugin/docs/how-to-write-a-module.md"
5
sidebar_label: "How to write a Netdata collector in Go"
6
learn_status: "Published"
7
learn_topic_type: "Tasks"
@@ -48,10 +48,10 @@ The steps are:
48
developed collector. It will be placed into the `bin` directory (e.g `go.d.plugin/bin`)
49
- Run it in the debug mode `bin/godplugin -d -m <MODULE_NAME>`. This will output the `STDOUT` of the collector, the same
50
output that is sent to the Netdata Agent and is transformed into charts. You can read more about this collector API in
51
- our [documentation](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#external-plugins-api).
51
+ our [documentation](/src/collectors/plugins.d/README.md#external-plugins-api).
52
- If you want to test the collector with the actual Netdata Agent, you need to replace the `go.d.plugin` binary that
53
exists in the Netdata Agent installation directory with the one you just compiled. Once
54
- you [restart](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
54
+ you [restart](/packaging/installer/README.md#maintaining-a-netdata-agent-installation)
55
the Netdata Agent, it will detect and run
56
it, creating all the charts. It is advised not to remove the default `go.d.plugin` binary, but simply rename it
57
to `go.d.plugin.old` so that the Agent doesn't run it, but you can easily rename it back once you are done.
@@ -122,7 +122,7 @@ func (e *Example) Check() bool {
122
### Charts method
123
124
:exclamation: Netdata module
125
-produces [`charts`](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#chart), not
125
+produces [`charts`](/src/collectors/plugins.d/README.md#chart), not
126
raw metrics.
127
128
Use [`agent/module`](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/agent/module/charts.go)
@@ -130,7 +130,7 @@ package to create them,
130
it contains charts and dimensions structs.
131
132
- `Charts` returns
133
- the [charts](https://github.com/netdata/netdata/blob/master/src/collectors/plugins.d/README.md#chart) (`*module.Charts`).
133
+ the [charts](/src/collectors/plugins.d/README.md#chart) (`*module.Charts`).
134
- Called after `Check` and only if `Check` returned `true`.
135
- If it returns `nil`, the job will be disabled
136
- :warning: Make sure not to share returned value between module instances (jobs).
src/go/collectors/go.d.plugin/modules/activemq/integrations/activemq.md
+3
-3
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/activemq.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -113,8 +113,8 @@ The following options can be defined globally: update_every, autodetection_retry
113
| webadmin | Webadmin root path. | admin | yes |
114
| max_queues | Maximum number of concurrently collected queues. | 50 | no |
115
| max_topics | Maximum number of concurrently collected topics. | 50 | no |
116
-| queues_filter | Queues filter. Syntax is [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns). | | no |
117
-| topics_filter | Topics filter. Syntax is [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns). | | no |
116
+| queues_filter | Queues filter. Syntax is [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns). | | no |
117
+| topics_filter | Topics filter. Syntax is [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns). | | no |
118
| username | Username for basic HTTP authentication. | | no |
119
| password | Password for basic HTTP authentication. | | no |
120
| proxy_username | Username for proxy basic HTTP authentication. | | no |
src/go/collectors/go.d.plugin/modules/activemq/metadata.yaml
+2
-2
@@ -83,12 +83,12 @@ modules:
83
required: false
84
- name: queues_filter
85
description: |
86
- Queues filter. Syntax is [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns).
86
+ Queues filter. Syntax is [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns).
87
default_value: ""
88
required: false
89
- name: topics_filter
90
description: |
91
- Topics filter. Syntax is [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns).
91
+ Topics filter. Syntax is [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns).
92
default_value: ""
93
required: false
94
- name: username
src/go/collectors/go.d.plugin/modules/adaptecraid/integrations/adaptec_raid.md
+1
-1
@@ -127,7 +127,7 @@ The configuration file name for this integration is `go.d/adaptec_raid.conf`.
127
128
129
You can edit the configuration file using the `edit-config` script from the
130
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
130
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
131
132
```bash
133
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/apache/integrations/apache.md
+1
-1
@@ -109,7 +109,7 @@ The configuration file name for this integration is `go.d/apache.conf`.
109
110
111
You can edit the configuration file using the `edit-config` script from the
112
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
114
```bash
115
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/apache/integrations/httpd.md
+1
-1
@@ -109,7 +109,7 @@ The configuration file name for this integration is `go.d/apache.conf`.
109
110
111
You can edit the configuration file using the `edit-config` script from the
112
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
113
114
```bash
115
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/bind/README.md
+1
-1
@@ -60,7 +60,7 @@ Per View Statistics (the following set will be added for each bind view):
60
## Configuration
61
62
Edit the `go.d/bind.conf` configuration file using `edit-config` from the
63
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
63
+Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
64
65
```bash
66
cd /etc/netdata # Replace this path with your Netdata config directory
src/go/collectors/go.d.plugin/modules/cassandra/integrations/cassandra.md
+1
-1
@@ -152,7 +152,7 @@ The configuration file name for this integration is `go.d/cassandra.conf`.
152
153
154
You can edit the configuration file using the `edit-config` script from the
155
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
155
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
156
157
```bash
158
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/chrony/integrations/chrony.md
+1
-1
@@ -102,7 +102,7 @@ The configuration file name for this integration is `go.d/chrony.conf`.
102
103
104
You can edit the configuration file using the `edit-config` script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
107
```bash
108
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/cockroachdb/integrations/cockroachdb.md
+1
-1
@@ -155,7 +155,7 @@ The configuration file name for this integration is `go.d/cockroachdb.conf`.
155
156
157
You can edit the configuration file using the `edit-config` script from the
158
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
158
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
159
160
```bash
161
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/consul/integrations/consul.md
+2
-2
@@ -203,7 +203,7 @@ The configuration file name for this integration is `go.d/consul.conf`.
203
204
205
You can edit the configuration file using the `edit-config` script from the
206
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
206
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
207
208
```bash
209
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -223,7 +223,7 @@ The following options can be defined globally: update_every, autodetection_retry
223
| url | Server URL. | http://localhost:8500 | yes |
224
| acl_token | ACL token used in every request. | | no |
225
| max_checks | Checks processing/charting limit. | | no |
226
-| max_filter | Checks processing/charting filter. Uses [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). | | no |
226
+| max_filter | Checks processing/charting filter. Uses [simple patterns](/src/libnetdata/simple_pattern/README.md). | | no |
227
| username | Username for basic HTTP authentication. | | no |
228
| password | Password for basic HTTP authentication. | | no |
229
| proxy_url | Proxy URL. | | no |
src/go/collectors/go.d.plugin/modules/consul/metadata.yaml
+1
-1
@@ -99,7 +99,7 @@ modules:
99
default_value: ""
100
required: false
101
- name: max_filter
102
- description: Checks processing/charting filter. Uses [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
102
+ description: Checks processing/charting filter. Uses [simple patterns](/src/libnetdata/simple_pattern/README.md).
103
default_value: ""
104
required: false
105
- name: username
src/go/collectors/go.d.plugin/modules/coredns/integrations/coredns.md
+1
-1
@@ -138,7 +138,7 @@ The configuration file name for this integration is `go.d/coredns.conf`.
138
139
140
You can edit the configuration file using the `edit-config` script from the
141
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
141
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
142
143
```bash
144
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/couchbase/integrations/couchbase.md
+1
-1
@@ -94,7 +94,7 @@ The configuration file name for this integration is `go.d/couchbase.conf`.
94
95
96
You can edit the configuration file using the `edit-config` script from the
97
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
99
```bash
100
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/couchdb/integrations/couchdb.md
+1
-1
@@ -102,7 +102,7 @@ The configuration file name for this integration is `go.d/couchdb.conf`.
102
103
104
You can edit the configuration file using the `edit-config` script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
107
```bash
108
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/dnsdist/integrations/dnsdist.md
+1
-1
@@ -102,7 +102,7 @@ The configuration file name for this integration is `go.d/dnsdist.conf`.
102
103
104
You can edit the configuration file using the `edit-config` script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
107
```bash
108
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/dnsmasq/integrations/dnsmasq.md
+1
-1
@@ -90,7 +90,7 @@ The configuration file name for this integration is `go.d/dnsmasq.conf`.
90
91
92
You can edit the configuration file using the `edit-config` script from the
93
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
93
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
94
95
```bash
96
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/dnsmasq_dhcp/integrations/dnsmasq_dhcp.md
+1
-1
@@ -117,7 +117,7 @@ The configuration file name for this integration is `go.d/dnsmasq_dhcp.conf`.
117
118
119
You can edit the configuration file using the `edit-config` script from the
120
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
121
122
```bash
123
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/dnsquery/integrations/dns_query.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `go.d/dns_query.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/docker/integrations/docker.md
+1
-1
@@ -122,7 +122,7 @@ The configuration file name for this integration is `go.d/docker.conf`.
122
123
124
You can edit the configuration file using the `edit-config` script from the
125
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
126
127
```bash
128
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/docker_engine/integrations/docker_engine.md
+1
-1
@@ -100,7 +100,7 @@ The configuration file name for this integration is `go.d/docker_engine.conf`.
100
101
102
You can edit the configuration file using the `edit-config` script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
105
```bash
106
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/dockerhub/integrations/docker_hub_repository.md
+1
-1
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/dockerhub.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/elasticsearch/integrations/elasticsearch.md
+1
-1
@@ -194,7 +194,7 @@ The configuration file name for this integration is `go.d/elasticsearch.conf`.
194
195
196
You can edit the configuration file using the `edit-config` script from the
197
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
197
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
198
199
```bash
200
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/elasticsearch/integrations/opensearch.md
+1
-1
@@ -194,7 +194,7 @@ The configuration file name for this integration is `go.d/elasticsearch.conf`.
194
195
196
You can edit the configuration file using the `edit-config` script from the
197
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
197
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
198
199
```bash
200
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/envoy/integrations/envoy.md
+1
-1
@@ -141,7 +141,7 @@ The configuration file name for this integration is `go.d/envoy.conf`.
141
142
143
You can edit the configuration file using the `edit-config` script from the
144
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
144
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
145
146
```bash
147
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/example/README.md
+1
-1
@@ -19,7 +19,7 @@ This module produces example charts with random values. Number of charts, dimens
19
## Configuration
20
21
Edit the `go.d/example.conf` configuration file using `edit-config` from the
22
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
22
+Netdata [config directory](/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.
23
24
```bash
25
cd /etc/netdata # Replace this path with your Netdata config directory
src/go/collectors/go.d.plugin/modules/fail2ban/integrations/fail2ban.md
+1
-1
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/fail2ban.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/filecheck/integrations/files_and_directories.md
+1
-1
@@ -114,7 +114,7 @@ The configuration file name for this integration is `go.d/filecheck.conf`.
114
115
116
You can edit the configuration file using the `edit-config` script from the
117
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
117
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
119
```bash
120
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/fluentd/integrations/fluentd.md
+1
-1
@@ -93,7 +93,7 @@ The configuration file name for this integration is `go.d/fluentd.conf`.
93
94
95
You can edit the configuration file using the `edit-config` script from the
96
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
98
```bash
99
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/freeradius/integrations/freeradius.md
+1
-1
@@ -103,7 +103,7 @@ The configuration file name for this integration is `go.d/freeradius.conf`.
103
104
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/geth/integrations/go-ethereum.md
+1
-1
@@ -103,7 +103,7 @@ The configuration file name for this integration is `go.d/geth.conf`.
103
104
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/haproxy/integrations/haproxy.md
+1
-1
@@ -108,7 +108,7 @@ The configuration file name for this integration is `go.d/haproxy.conf`.
108
109
110
You can edit the configuration file using the `edit-config` script from the
111
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
113
```bash
114
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/hddtemp/integrations/hdd_temperature.md
+1
-1
@@ -100,7 +100,7 @@ The configuration file name for this integration is `go.d/hddtemp.conf`.
100
101
102
You can edit the configuration file using the `edit-config` script from the
103
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
105
```bash
106
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/hdfs/integrations/hadoop_distributed_file_system_hdfs.md
+1
-1
@@ -121,7 +121,7 @@ The configuration file name for this integration is `go.d/hdfs.conf`.
121
122
123
You can edit the configuration file using the `edit-config` script from the
124
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
126
```bash
127
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/hpssa/integrations/hpe_smart_arrays.md
+1
-1
@@ -169,7 +169,7 @@ The configuration file name for this integration is `go.d/ssacli.conf`.
169
170
171
You can edit the configuration file using the `edit-config` script from the
172
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
172
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
173
174
```bash
175
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md
+1
-1
@@ -94,7 +94,7 @@ The configuration file name for this integration is `go.d/httpcheck.conf`.
94
95
96
You can edit the configuration file using the `edit-config` script from the
97
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
99
```bash
100
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/intelgpu/integrations/intel_gpu.md
+1
-1
@@ -111,7 +111,7 @@ The configuration file name for this integration is `go.d/intelgpu.conf`.
111
112
113
You can edit the configuration file using the `edit-config` script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
116
```bash
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/isc_dhcpd/integrations/isc_dhcp.md
+1
-1
@@ -104,7 +104,7 @@ The configuration file name for this integration is `go.d/isc_dhcpd.conf`.
104
105
106
You can edit the configuration file using the `edit-config` script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
109
```bash
110
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/k8s_kubelet/integrations/kubelet.md
+1
-1
@@ -125,7 +125,7 @@ The configuration file name for this integration is `go.d/k8s_kubelet.conf`.
125
126
127
You can edit the configuration file using the `edit-config` script from the
128
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
128
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
129
130
```bash
131
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/k8s_kubeproxy/integrations/kubeproxy.md
+1
-1
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/k8s_kubeproxy.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/k8s_state/integrations/kubernetes_cluster_state.md
+1
-1
@@ -172,7 +172,7 @@ The configuration file name for this integration is `go.d/k8s_state.conf`.
172
173
174
You can edit the configuration file using the `edit-config` script from the
175
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
175
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
176
177
```bash
178
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/lighttpd/integrations/lighttpd.md
+1
-1
@@ -102,7 +102,7 @@ The configuration file name for this integration is `go.d/lighttpd.conf`.
102
103
104
You can edit the configuration file using the `edit-config` script from the
105
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
107
```bash
108
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/litespeed/integrations/litespeed.md
+1
-1
@@ -94,7 +94,7 @@ The configuration file name for this integration is `go.d/litespeed.conf`.
94
95
96
You can edit the configuration file using the `edit-config` script from the
97
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
99
```bash
100
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/logind/integrations/systemd-logind_users.md
+1
-1
@@ -90,7 +90,7 @@ The configuration file name for this integration is `go.d/logind.conf`.
90
91
92
You can edit the configuration file using the `edit-config` script from the
93
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
93
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
94
95
```bash
96
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/logstash/integrations/logstash.md
+1
-1
@@ -115,7 +115,7 @@ The configuration file name for this integration is `go.d/logstatsh.conf`.
115
116
117
You can edit the configuration file using the `edit-config` script from the
118
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
120
```bash
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/lvm/integrations/lvm_logical_volumes.md
+1
-1
@@ -94,7 +94,7 @@ The configuration file name for this integration is `go.d/lvm.conf`.
94
95
96
You can edit the configuration file using the `edit-config` script from the
97
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
99
```bash
100
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/megacli/integrations/megacli_megaraid.md
+1
-1
@@ -147,7 +147,7 @@ The configuration file name for this integration is `go.d/megacli.conf`.
147
148
149
You can edit the configuration file using the `edit-config` script from the
150
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
150
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
151
152
```bash
153
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/mongodb/integrations/mongodb.md
+1
-1
@@ -249,7 +249,7 @@ The configuration file name for this integration is `go.d/mongodb.conf`.
249
250
251
You can edit the configuration file using the `edit-config` script from the
252
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
252
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
253
254
```bash
255
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/mysql/integrations/mariadb.md
+1
-1
@@ -238,7 +238,7 @@ The configuration file name for this integration is `go.d/mysql.conf`.
238
239
240
You can edit the configuration file using the `edit-config` script from the
241
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
241
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
242
243
```bash
244
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/mysql/integrations/mysql.md
+1
-1
@@ -238,7 +238,7 @@ The configuration file name for this integration is `go.d/mysql.conf`.
238
239
240
You can edit the configuration file using the `edit-config` script from the
241
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
241
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
242
243
```bash
244
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/mysql/integrations/percona_mysql.md
+1
-1
@@ -238,7 +238,7 @@ The configuration file name for this integration is `go.d/mysql.conf`.
238
239
240
You can edit the configuration file using the `edit-config` script from the
241
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
241
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
242
243
```bash
244
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/nginx/integrations/nginx.md
+1
-1
@@ -103,7 +103,7 @@ The configuration file name for this integration is `go.d/nginx.conf`.
103
104
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/nginxplus/integrations/nginx_plus.md
+1
-1
@@ -280,7 +280,7 @@ The configuration file name for this integration is `go.d/nginxplus.conf`.
280
281
282
You can edit the configuration file using the `edit-config` script from the
283
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
283
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
284
285
```bash
286
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/nginxvts/integrations/nginx_vts.md
+1
-1
@@ -103,7 +103,7 @@ The configuration file name for this integration is `go.d/nginxvts.conf`.
103
104
105
You can edit the configuration file using the `edit-config` script from the
106
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
106
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
108
```bash
109
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/ntpd/integrations/ntpd.md
+1
-1
@@ -123,7 +123,7 @@ The configuration file name for this integration is `go.d/ntpd.conf`.
123
124
125
You can edit the configuration file using the `edit-config` script from the
126
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
126
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
127
128
```bash
129
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/nvidia_smi/integrations/nvidia_gpu.md
+1
-1
@@ -133,7 +133,7 @@ The configuration file name for this integration is `go.d/nvidia_smi.conf`.
133
134
135
You can edit the configuration file using the `edit-config` script from the
136
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
136
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
137
138
```bash
139
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/nvme/integrations/nvme_devices.md
+1
-1
@@ -115,7 +115,7 @@ The configuration file name for this integration is `go.d/nvme.conf`.
115
116
117
You can edit the configuration file using the `edit-config` script from the
118
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
120
```bash
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/openvpn/integrations/openvpn.md
+1
-1
@@ -116,7 +116,7 @@ The configuration file name for this integration is `go.d/openvpn.conf`.
116
117
118
You can edit the configuration file using the `edit-config` script from the
119
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
120
121
```bash
122
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/openvpn_status_log/integrations/openvpn_status_log.md
+1
-1
@@ -107,7 +107,7 @@ The configuration file name for this integration is `go.d/openvpn_status_log.con
107
108
109
You can edit the configuration file using the `edit-config` script from the
110
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
110
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
112
```bash
113
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/pgbouncer/integrations/pgbouncer.md
+1
-1
@@ -151,7 +151,7 @@ The configuration file name for this integration is `go.d/pgbouncer.conf`.
151
152
153
You can edit the configuration file using the `edit-config` script from the
154
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
154
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
155
156
```bash
157
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/phpdaemon/integrations/phpdaemon.md
+1
-1
@@ -165,7 +165,7 @@ The configuration file name for this integration is `go.d/phpdaemon.conf`.
165
166
167
You can edit the configuration file using the `edit-config` script from the
168
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
168
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
169
170
```bash
171
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/phpfpm/integrations/php-fpm.md
+1
-1
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/phpfpm.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/pihole/integrations/pi-hole.md
+1
-1
@@ -104,7 +104,7 @@ The configuration file name for this integration is `go.d/pihole.conf`.
104
105
106
You can edit the configuration file using the `edit-config` script from the
107
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
107
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
109
```bash
110
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/pika/integrations/pika.md
+1
-1
@@ -112,7 +112,7 @@ The configuration file name for this integration is `go.d/pika.conf`.
112
113
114
You can edit the configuration file using the `edit-config` script from the
115
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
116
117
```bash
118
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/ping/integrations/ping.md
+1
-1
@@ -120,7 +120,7 @@ The configuration file name for this integration is `go.d/ping.conf`.
120
121
122
You can edit the configuration file using the `edit-config` script from the
123
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
123
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
124
125
```bash
126
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/portcheck/integrations/tcp_endpoints.md
+1
-1
@@ -101,7 +101,7 @@ The configuration file name for this integration is `go.d/portcheck.conf`.
101
102
103
You can edit the configuration file using the `edit-config` script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
106
```bash
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/postgres/integrations/postgresql.md
+2
-2
@@ -267,7 +267,7 @@ GRANT pg_monitor TO netdata;
267
```
268
269
After creating the new user, restart the Netdata agent with `sudo systemctl restart netdata`, or
270
-the [appropriate method](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/start-stop-restart.md) for your
270
+the [appropriate method](/docs/netdata-agent/start-stop-restart.md) for your
271
system.
272
273
@@ -280,7 +280,7 @@ The configuration file name for this integration is `go.d/postgres.conf`.
280
281
282
You can edit the configuration file using the `edit-config` script from the
283
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
283
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
284
285
```bash
286
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/postgres/metadata.yaml
+1
-1
@@ -69,7 +69,7 @@ modules:
69
```
70
71
After creating the new user, restart the Netdata agent with `sudo systemctl restart netdata`, or
72
- the [appropriate method](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/start-stop-restart.md) for your
72
+ the [appropriate method](/docs/netdata-agent/start-stop-restart.md) for your
73
system.
74
configuration:
75
file:
src/go/collectors/go.d.plugin/modules/powerdns/integrations/powerdns_authoritative_server.md
+1
-1
@@ -105,7 +105,7 @@ The configuration file name for this integration is `go.d/powerdns.conf`.
105
106
107
You can edit the configuration file using the `edit-config` script from the
108
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
110
```bash
111
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/powerdns_recursor/integrations/powerdns_recursor.md
+1
-1
@@ -108,7 +108,7 @@ The configuration file name for this integration is `go.d/powerdns_recursor.conf
108
109
110
You can edit the configuration file using the `edit-config` script from the
111
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
111
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
112
113
```bash
114
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md
+2
-2
@@ -97,7 +97,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
97
98
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -139,7 +139,7 @@ The following options can be defined globally: update_every, autodetection_retry
139
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
140
141
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
142
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
143
- Option syntax:
144
145
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/clickhouse.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md
+2
-2
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -134,7 +134,7 @@ The following options can be defined globally: update_every, autodetection_retry
134
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
135
136
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
137
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
137
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
138
- Option syntax:
139
140
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md
+2
-2
@@ -97,7 +97,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
97
98
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -139,7 +139,7 @@ The following options can be defined globally: update_every, autodetection_retry
139
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
140
141
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
142
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
143
- Option syntax:
144
145
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md
+2
-2
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -134,7 +134,7 @@ The following options can be defined globally: update_every, autodetection_retry
134
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
135
136
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
137
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
137
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
138
- Option syntax:
139
140
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md
+2
-2
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -134,7 +134,7 @@ The following options can be defined globally: update_every, autodetection_retry
134
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
135
136
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
137
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
137
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
138
- Option syntax:
139
140
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md
+2
-2
@@ -97,7 +97,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
97
98
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -139,7 +139,7 @@ The following options can be defined globally: update_every, autodetection_retry
139
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
140
141
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
142
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
143
- Option syntax:
144
145
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md
+2
-2
@@ -97,7 +97,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
97
98
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -139,7 +139,7 @@ The following options can be defined globally: update_every, autodetection_retry
139
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
140
141
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
142
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
143
- Option syntax:
144
145
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md
+2
-2
@@ -97,7 +97,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
97
98
99
You can edit the configuration file using the `edit-config` script from the
100
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
102
```bash
103
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -139,7 +139,7 @@ The following options can be defined globally: update_every, autodetection_retry
139
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
140
141
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
142
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
143
- Option syntax:
144
145
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md
+2
-2
@@ -92,7 +92,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
92
93
94
You can edit the configuration file using the `edit-config` script from the
95
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
95
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
97
```bash
98
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -134,7 +134,7 @@ The following options can be defined globally: update_every, autodetection_retry
134
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
135
136
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
137
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
137
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
138
- Option syntax:
139
140
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md
+2
-2
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/prometheus.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -138,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry
138
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
139
140
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
141
-- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
141
+- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
142
- Option syntax:
143
144
```yaml
src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml
+1
-1
@@ -75,7 +75,7 @@ modules:
75
This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
76
77
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
78
- - Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
78
+ - Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
79
- Option syntax:
80
81
```yaml
src/go/collectors/go.d.plugin/modules/proxysql/integrations/proxysql.md
+1
-1
@@ -171,7 +171,7 @@ The configuration file name for this integration is `go.d/proxysql.conf`.
171
172
173
You can edit the configuration file using the `edit-config` script from the
174
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
174
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
175
176
```bash
177
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/pulsar/integrations/apache_pulsar.md
+1
-1
@@ -149,7 +149,7 @@ The configuration file name for this integration is `go.d/pulsar.conf`.
149
150
151
You can edit the configuration file using the `edit-config` script from the
152
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
152
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
153
154
```bash
155
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/rabbitmq/integrations/rabbitmq.md
+1
-1
@@ -146,7 +146,7 @@ The configuration file name for this integration is `go.d/rabbitmq.conf`.
146
147
148
You can edit the configuration file using the `edit-config` script from the
149
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
149
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
150
151
```bash
152
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/redis/integrations/redis.md
+1
-1
@@ -129,7 +129,7 @@ The configuration file name for this integration is `go.d/redis.conf`.
129
130
131
You can edit the configuration file using the `edit-config` script from the
132
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
132
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
133
134
```bash
135
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/rspamd/integrations/rspamd.md
+1
-1
@@ -94,7 +94,7 @@ The configuration file name for this integration is `go.d/rspamd.conf`.
94
95
96
You can edit the configuration file using the `edit-config` script from the
97
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
98
99
```bash
100
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/scaleio/integrations/dell_emc_scaleio.md
+1
-1
@@ -144,7 +144,7 @@ The configuration file name for this integration is `go.d/scaleio.conf`.
144
145
146
You can edit the configuration file using the `edit-config` script from the
147
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
147
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
148
149
```bash
150
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/sensors/integrations/linux_sensors_lm-sensors.md
+1
-1
@@ -112,7 +112,7 @@ The configuration file name for this integration is `go.d/sensors.conf`.
112
113
114
You can edit the configuration file using the `edit-config` script from the
115
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
116
117
```bash
118
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/smartctl/integrations/s.m.a.r.t..md
+1
-1
@@ -111,7 +111,7 @@ The configuration file name for this integration is `go.d/smartctl.conf`.
111
112
113
You can edit the configuration file using the `edit-config` script from the
114
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
114
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
116
```bash
117
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/snmp/integrations/snmp_devices.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `go.d/snmp.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/squidlog/integrations/squid_log_files.md
+1
-1
@@ -105,7 +105,7 @@ The configuration file name for this integration is `go.d/squidlog.conf`.
105
106
107
You can edit the configuration file using the `edit-config` script from the
108
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
110
```bash
111
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/storcli/integrations/storecli_raid.md
+1
-1
@@ -148,7 +148,7 @@ The configuration file name for this integration is `go.d/storcli.conf`.
148
149
150
You can edit the configuration file using the `edit-config` script from the
151
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
151
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
152
153
```bash
154
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/supervisord/integrations/supervisor.md
+1
-1
@@ -112,7 +112,7 @@ The configuration file name for this integration is `go.d/supervisord.conf`.
112
113
114
You can edit the configuration file using the `edit-config` script from the
115
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
115
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
116
117
```bash
118
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/systemdunits/integrations/systemd_units.md
+1
-1
@@ -133,7 +133,7 @@ The configuration file name for this integration is `go.d/systemdunits.conf`.
133
134
135
You can edit the configuration file using the `edit-config` script from the
136
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
136
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
137
138
```bash
139
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/tengine/integrations/tengine.md
+1
-1
@@ -99,7 +99,7 @@ The configuration file name for this integration is `go.d/tengine.conf`.
99
100
101
You can edit the configuration file using the `edit-config` script from the
102
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
103
104
```bash
105
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/traefik/integrations/traefik.md
+1
-1
@@ -93,7 +93,7 @@ The configuration file name for this integration is `go.d/traefik.conf`.
93
94
95
You can edit the configuration file using the `edit-config` script from the
96
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
96
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
97
98
```bash
99
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/unbound/integrations/unbound.md
+1
-1
@@ -160,7 +160,7 @@ The configuration file name for this integration is `go.d/unbound.conf`.
160
161
162
You can edit the configuration file using the `edit-config` script from the
163
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
163
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
164
165
```bash
166
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/upsd/integrations/ups_nut.md
+1
-1
@@ -122,7 +122,7 @@ The configuration file name for this integration is `go.d/upsd.conf`.
122
123
124
You can edit the configuration file using the `edit-config` script from the
125
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
125
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
126
127
```bash
128
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/vcsa/integrations/vcenter_server_appliance.md
+1
-1
@@ -149,7 +149,7 @@ The configuration file name for this integration is `go.d/vcsa.conf`.
149
150
151
You can edit the configuration file using the `edit-config` script from the
152
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
152
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
153
154
```bash
155
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/vernemq/integrations/vernemq.md
+1
-1
@@ -179,7 +179,7 @@ The configuration file name for this integration is `go.d/vernemq.conf`.
179
180
181
You can edit the configuration file using the `edit-config` script from the
182
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
182
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
183
184
```bash
185
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/vsphere/integrations/vmware_vcenter_server.md
+3
-3
@@ -186,7 +186,7 @@ The configuration file name for this integration is `go.d/vsphere.conf`.
186
187
188
You can edit the configuration file using the `edit-config` script from the
189
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
189
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
190
191
```bash
192
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
@@ -224,7 +224,7 @@ The following options can be defined globally: update_every, autodetection_retry
224
Metrics of hosts matching the selector will be collected.
225
226
- Include pattern syntax: "/Datacenter pattern/Cluster pattern/Host pattern".
227
-- Match pattern syntax: [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns).
227
+- Match pattern syntax: [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns).
228
- Syntax:
229
230
```yaml
@@ -240,7 +240,7 @@ Metrics of hosts matching the selector will be collected.
240
Metrics of VMs matching the selector will be collected.
241
242
- Include pattern syntax: "/Datacenter pattern/Cluster pattern/Host pattern/VM pattern".
243
-- Match pattern syntax: [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns).
243
+- Match pattern syntax: [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns).
244
- Syntax:
245
246
```yaml
src/go/collectors/go.d.plugin/modules/vsphere/metadata.yaml
+2
-2
@@ -115,7 +115,7 @@ modules:
115
Metrics of hosts matching the selector will be collected.
116
117
- Include pattern syntax: "/Datacenter pattern/Cluster pattern/Host pattern".
118
- - Match pattern syntax: [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns).
118
+ - Match pattern syntax: [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns).
119
- Syntax:
120
121
```yaml
@@ -132,7 +132,7 @@ modules:
132
Metrics of VMs matching the selector will be collected.
133
134
- Include pattern syntax: "/Datacenter pattern/Cluster pattern/Host pattern/VM pattern".
135
- - Match pattern syntax: [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md#simple-patterns).
135
+ - Match pattern syntax: [simple patterns](/src/libnetdata/simple_pattern/README.md#simple-patterns).
136
- Syntax:
137
138
```yaml
src/go/collectors/go.d.plugin/modules/weblog/integrations/web_server_log_files.md
+1
-1
@@ -163,7 +163,7 @@ The configuration file name for this integration is `go.d/web_log.conf`.
163
164
165
You can edit the configuration file using the `edit-config` script from the
166
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
166
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
167
168
```bash
169
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/whoisquery/integrations/domain_expiration_date.md
+1
-1
@@ -96,7 +96,7 @@ The configuration file name for this integration is `go.d/whoisquery.conf`.
96
97
98
You can edit the configuration file using the `edit-config` script from the
99
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
99
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
100
101
```bash
102
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/windows/integrations/active_directory.md
+1
-1
@@ -652,7 +652,7 @@ The configuration file name for this integration is `go.d/windows.conf`.
652
653
654
You can edit the configuration file using the `edit-config` script from the
655
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
655
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
656
657
```bash
658
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/windows/integrations/hyperv.md
+1
-1
@@ -652,7 +652,7 @@ The configuration file name for this integration is `go.d/windows.conf`.
652
653
654
You can edit the configuration file using the `edit-config` script from the
655
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
655
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
656
657
```bash
658
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/windows/integrations/ms_exchange.md
+1
-1
@@ -652,7 +652,7 @@ The configuration file name for this integration is `go.d/windows.conf`.
652
653
654
You can edit the configuration file using the `edit-config` script from the
655
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
655
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
656
657
```bash
658
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/windows/integrations/ms_sql_server.md
+1
-1
@@ -652,7 +652,7 @@ The configuration file name for this integration is `go.d/windows.conf`.
652
653
654
You can edit the configuration file using the `edit-config` script from the
655
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
655
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
656
657
```bash
658
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/windows/integrations/net_framework.md
+1
-1
@@ -652,7 +652,7 @@ The configuration file name for this integration is `go.d/windows.conf`.
652
653
654
You can edit the configuration file using the `edit-config` script from the
655
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
655
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
656
657
```bash
658
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/windows/integrations/windows.md
+1
-1
@@ -652,7 +652,7 @@ The configuration file name for this integration is `go.d/windows.conf`.
652
653
654
You can edit the configuration file using the `edit-config` script from the
655
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
655
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
656
657
```bash
658
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/wireguard/integrations/wireguard.md
+1
-1
@@ -115,7 +115,7 @@ The configuration file name for this integration is `go.d/wireguard.conf`.
115
116
117
You can edit the configuration file using the `edit-config` script from the
118
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
118
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
119
120
```bash
121
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/x509check/integrations/x.509_certificate.md
+1
-1
@@ -98,7 +98,7 @@ The configuration file name for this integration is `go.d/x509check.conf`.
98
99
100
You can edit the configuration file using the `edit-config` script from the
101
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
101
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
102
103
```bash
104
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/zfspool/integrations/zfs_pools.md
+1
-1
@@ -101,7 +101,7 @@ The configuration file name for this integration is `go.d/zfspool.conf`.
101
102
103
You can edit the configuration file using the `edit-config` script from the
104
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
104
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
105
106
```bash
107
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/modules/zookeeper/integrations/zookeeper.md
+1
-1
@@ -105,7 +105,7 @@ The configuration file name for this integration is `go.d/zookeeper.conf`.
105
106
107
You can edit the configuration file using the `edit-config` script from the
108
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
108
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
109
110
```bash
111
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/go/collectors/go.d.plugin/pkg/README.md
+3
-3
@@ -1,6 +1,6 @@
1
<!--
2
title: "Helper Packages"
3
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/README.md"
3
+custom_edit_url: "/src/go/collectors/go.d.plugin/pkg/README.md"
4
sidebar_label: "Helper Packages"
5
learn_status: "Published"
6
learn_rel_path: "Developers/External plugins/go.d.plugin/Helper Packages"
@@ -9,11 +9,11 @@ learn_rel_path: "Developers/External plugins/go.d.plugin/Helper Packages"
9
# Helper Packages
10
11
- if you need IP ranges consider to
12
- use [`iprange`](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/iprange/README.md).
12
+ use [`iprange`](/src/go/collectors/go.d.plugin/pkg/iprange/README.md).
13
- if you parse an application log files, then [`log`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/logs) is
14
handy.
15
- if you need filtering
16
- check [`matcher`](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/matcher/README.md).
16
+ check [`matcher`](/src/go/collectors/go.d.plugin/pkg/matcher/README.md).
17
- if you collect metrics from an HTTP endpoint use [`web`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/web).
18
- if you collect metrics from a prometheus endpoint,
19
then [`prometheus`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/prometheus)
src/go/collectors/go.d.plugin/pkg/iprange/README.md
+1
-1
@@ -1,6 +1,6 @@
1
<!--
2
title: "iprange"
3
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/iprange/README.md"
3
+custom_edit_url: "/src/go/collectors/go.d.plugin/pkg/iprange/README.md"
4
sidebar_label: "iprange"
5
learn_status: "Published"
6
learn_rel_path: "Developers/External plugins/go.d.plugin/Helper Packages"
src/go/collectors/go.d.plugin/pkg/matcher/README.md
+1
-1
@@ -1,6 +1,6 @@
1
<!--
2
title: "matcher"
3
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/matcher/README.md"
3
+custom_edit_url: "/src/go/collectors/go.d.plugin/pkg/matcher/README.md"
4
sidebar_label: "matcher"
5
learn_status: "Published"
6
learn_rel_path: "Developers/External plugins/go.d.plugin/Helper Packages"
src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md
+5
-5
@@ -1,6 +1,6 @@
1
<!--
2
title: "Time series selector"
3
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md"
3
+custom_edit_url: "/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md"
4
sidebar_label: "Time series selector"
5
learn_status: "Published"
6
learn_rel_path: "Developers/External plugins/go.d.plugin/Helper Packages"
@@ -21,7 +21,7 @@ In the simplest form you need to specify only a metric name.
21
<metric_name_pattern> ::= simple pattern
22
```
23
24
-The metric name pattern syntax is [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
24
+The metric name pattern syntax is [simple pattern](/src/libnetdata/simple_pattern/README.md).
25
26
### Examples
27
@@ -58,7 +58,7 @@ It is possible to filter these time series further by appending a comma separate
58
<label_value_pattern> ::= a label value pattern, depends on <op>
59
```
60
61
-The metric name pattern syntax is [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
61
+The metric name pattern syntax is [simple pattern](/src/libnetdata/simple_pattern/README.md).
62
63
Label matching operators:
64
@@ -66,8 +66,8 @@ Label matching operators:
66
- `!=`: Match labels that are not equal to the provided string.
67
- `=~`: Match labels that [regex-match](https://golang.org/pkg/regexp/syntax/) the provided string.
68
- `!~`: Match labels that do not [regex-match](https://golang.org/pkg/regexp/syntax/) the provided string.
69
-- `=*`: Match labels that [simple-pattern-match](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) the provided string.
70
-- `!*`: Match labels that do not [simple-pattern-match](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) the provided string.
69
+- `=*`: Match labels that [simple-pattern-match](/src/libnetdata/simple_pattern/README.md) the provided string.
70
+- `!*`: Match labels that do not [simple-pattern-match](/src/libnetdata/simple_pattern/README.md) the provided string.
71
72
### Examples
73
src/health/README.md
+3
-3
@@ -4,7 +4,7 @@ Netdata offers two ways to receive alert notifications on external integrations.
4
5
Both methods use a node's health alerts to generate the content of a notification.
6
7
-Read our documentation on [configuring alerts](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md) to change the preconfigured thresholds or to create tailored alerts for your infrastructure.
7
+Read our documentation on [configuring alerts](/src/health/REFERENCE.md) to change the preconfigured thresholds or to create tailored alerts for your infrastructure.
8
9
- Netdata Cloud provides centralized alert notifications, utilizing the health status data already sent to Netdata Cloud from connected nodes to send alerts to configured integrations. [Supported integrations](/docs/alerts-&-notifications/notifications/centralized-cloud-notifications) include Amazon SNS, Discord, Slack, Splunk, and others.
10
@@ -12,6 +12,6 @@ Read our documentation on [configuring alerts](https://github.com/netdata/netdat
12
13
The Netdata Agent is a health watchdog for the health and performance of your systems, services, and applications. We've worked closely with our community of DevOps engineers, SREs, and developers to define hundreds of production-ready alerts that work without any configuration.
14
15
-The Agent's health monitoring system is also dynamic and fully customizable. You can write entirely new alerts, tune the pre-configured alerts for every app/service [the Agent collects metrics from](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md), or silence anything you're not interested in. You can even power complex lookups by running statistical algorithms against your metrics.
15
+The Agent's health monitoring system is also dynamic and fully customizable. You can write entirely new alerts, tune the pre-configured alerts for every app/service [the Agent collects metrics from](/src/collectors/COLLECTORS.md), or silence anything you're not interested in. You can even power complex lookups by running statistical algorithms against your metrics.
16
17
-You can [use various alert notification methods](https://github.com/netdata/netdata/blob/master/docs/alerts-and-notifications/notifications/README.md), [customize alerts](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md), and [disable/silence](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#disable-or-silence-alerts) alerts.
17
+You can [use various alert notification methods](/docs/alerts-and-notifications/notifications/README.md), [customize alerts](/src/health/REFERENCE.md), and [disable/silence](/src/health/REFERENCE.md#disable-or-silence-alerts) alerts.
src/health/REFERENCE.md
+23
-23
@@ -4,13 +4,13 @@ Netdata's health watchdog is highly configurable, with support for dynamic thres
4
more. You can tweak any of the existing alerts based on your infrastructure's topology or specific monitoring needs, or
5
create new entities.
6
7
-You can use health alerts in conjunction with any of Netdata's [collectors](https://github.com/netdata/netdata/blob/master/src/collectors/README.md) (see
8
-the [supported collector list](https://github.com/netdata/netdata/blob/master/src/collectors/COLLECTORS.md)) to monitor the health of your systems, containers, and
7
+You can use health alerts in conjunction with any of Netdata's [collectors](/src/collectors/README.md) (see
8
+the [supported collector list](/src/collectors/COLLECTORS.md)) to monitor the health of your systems, containers, and
9
applications in real time.
10
11
While you can see active alerts both on the local dashboard and Netdata Cloud, all health alerts are configured _per
12
node_ via individual Netdata Agents. If you want to deploy a new alert across your
13
-[infrastructure](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/monitor-your-infrastructure.md), you must configure each node with the same health configuration
13
+[infrastructure](/docs/netdata-cloud/monitor-your-infrastructure.md), you must configure each node with the same health configuration
14
files.
15
16
## Reload health configuration
@@ -33,14 +33,14 @@ You can configure the Agent's health watchdog service by editing files in two lo
33
34
- The `[health]` section in `netdata.conf`. By editing the daemon's behavior, you can disable health monitoring
35
altogether, run health checks more or less often, and more. See
36
- [daemon configuration](https://github.com/netdata/netdata/blob/master/src/daemon/config/README.md#health-section-options) for a table of
36
+ [daemon configuration](/src/daemon/config/README.md#health-section-options) for a table of
37
all the available settings, their default values, and what they control.
38
39
- The individual `.conf` files in `health.d/`. These health entity files are organized by the type of metric they are
40
performing calculations on or their associated collector. You should edit these files using the `edit-config`
41
script. For example: `sudo ./edit-config health.d/cpu.conf`.
42
43
-Navigate to your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) and
43
+Navigate to your [Netdata config directory](/docs/netdata-agent/configuration/README.md) and
44
use `edit-config` to make changes to any of these files.
45
46
### Edit individual alerts
@@ -84,7 +84,7 @@ Save the file and [reload Netdata's health configuration](#reload-health-configu
84
## Disable or silence alerts
85
86
Alerts and notifications can be disabled permanently via configuration changes, or temporarily, via the
87
-[health management API](https://github.com/netdata/netdata/blob/master/src/web/api/health/README.md). The
87
+[health management API](/src/web/api/health/README.md). The
88
available options are described below.
89
90
### Disable all alerts
@@ -114,7 +114,7 @@ This action requires that you [reload Netdata's health configuration](#reload-he
114
115
When you need to frequently disable all or some alerts from triggering during certain times (for instance
116
when running backups) you can use the
117
-[health management API](https://github.com/netdata/netdata/blob/master/src/web/api/health/README.md).
117
+[health management API](/src/web/api/health/README.md).
118
The API allows you to issue commands to control the health engine's behavior without changing configuration,
119
or restarting the agent.
120
@@ -122,7 +122,7 @@ or restarting the agent.
122
123
If you want health checks to keep running and alerts to keep getting triggered, but notifications to be
124
suppressed temporarily, you can use the
125
-[health management API](https://github.com/netdata/netdata/blob/master/src/web/api/health/README.md).
125
+[health management API](/src/web/api/health/README.md).
126
The API allows you to issue commands to control the health engine's behavior without changing configuration,
127
or restarting the agent.
128
@@ -134,7 +134,7 @@ your systems, containers, and applications work.
134
Read the [health entity reference](#health-entity-reference) for a full listing of the format,
135
syntax, and functionality of health entities.
136
137
-To write a new health entity into a new file, navigate to your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md),
137
+To write a new health entity into a new file, navigate to your [Netdata config directory](/docs/netdata-agent/configuration/README.md),
138
then use `touch` to create a new file in the `health.d/` directory. Use `edit-config` to start editing the file.
139
140
As an example, let's create a `ram-usage.conf` file.
@@ -223,7 +223,7 @@ Netdata parses the following lines. Beneath the table is an in-depth explanation
223
- The `every` line is **required** if not using `lookup`.
224
- Each entity **must** have at least one of the following lines: `lookup`, `calc`, `warn`, or `crit`.
225
- A few lines use space-separated lists to define how the entity behaves. You can use `*` as a wildcard or prefix with
226
- `!` for a negative match. Order is important, too! See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for
226
+ `!` for a negative match. Order is important, too! See our [simple patterns docs](/src/libnetdata/simple_pattern/README.md) for
227
more examples.
228
- Lines terminated by a `\` are spliced together with the next line. The backslash is removed and the following line is
229
joined with the current one. No space is inserted, so you may split a line anywhere, even in the middle of a word.
@@ -388,9 +388,9 @@ The format is:
388
lookup: METHOD(GROUPING OPTIONS) AFTER [at BEFORE] [every DURATION] [OPTIONS] [of DIMENSIONS]
389
```
390
391
-The full [database query API](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md) is supported. In short:
391
+The full [database query API](/src/web/api/queries/README.md) is supported. In short:
392
393
-- `METHOD` is one of the available [grouping methods](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md#grouping-methods) such as `average`, `min`, `max` etc.
393
+- `METHOD` is one of the available [grouping methods](/src/web/api/queries/README.md#grouping-methods) such as `average`, `min`, `max` etc.
394
This is required.
395
396
- `GROUPING OPTIONS` are optional and can have the form `CONDITION VALUE`, where `CONDITION` is `!=`, `=`, `<=`, `<`, `>`, `>=` and `VALUE` is a number. The `CONDITION` and `VALUE` are required for `countif`, while `VALUE` is used by `percentile`, `trimmed_mean` and `trimmed_median`.
@@ -600,7 +600,7 @@ good idea to tell Netdata to not clear the notification, by using the `no-clear-
600
601
#### Alert line `host labels`
602
603
-Defines the list of labels present on a host. See our [host labels guide](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md) for
603
+Defines the list of labels present on a host. See our [host labels guide](/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts.md) for
604
an explanation of host labels and how to implement them.
605
606
For example, let's suppose that `netdata.conf` is configured with the following labels:
@@ -633,7 +633,7 @@ that will be applied to all hosts installed in the last decade with the followin
633
host labels: installed = 201*
634
```
635
636
-See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for more examples.
636
+See our [simple patterns docs](/src/libnetdata/simple_pattern/README.md) for more examples.
637
638
#### Alert line `chart labels`
639
@@ -662,7 +662,7 @@ chart labels: mount_point=/mnt/disk1 device=sda
662
Will create the alert if the `mount_point` is `/mnt/disk1` and the `device` is `sda`. Furthermore, if a chart label name
663
is specified that does not exist in the chart, the chart won't be matched.
664
665
-See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for more examples.
665
+See our [simple patterns docs](/src/libnetdata/simple_pattern/README.md) for more examples.
666
667
#### Alert line `summary`
668
@@ -808,14 +808,14 @@ You can find all the variables that can be used for a given chart, using
808
Agent dashboard. For example, [variables for the `system.cpu` chart of the
809
registry](https://registry.my-netdata.io/api/v1/alarm_variables?chart=system.cpu).
810
811
-> If you don't know how to find the CHART_NAME, you can read about it [here](https://github.com/netdata/netdata/blob/master/src/web/README.md#charts).
811
+> If you don't know how to find the CHART_NAME, you can read about it [here](/src/web/README.md#charts).
812
813
Netdata supports 3 internal indexes for variables that will be used in health monitoring.
814
815
<details><summary>The variables below can be used in both chart alerts and context templates.</summary>
816
817
Although the `alarm_variables` link shows you variables for a particular chart, the same variables can also be used in
818
-templates for charts belonging to a given [context](https://github.com/netdata/netdata/blob/master/src/web/README.md#contexts). The reason is that all charts of a given
818
+templates for charts belonging to a given [context](/src/web/README.md#contexts). The reason is that all charts of a given
819
context are essentially identical, with the only difference being the family that identifies a particular hardware or software instance.
820
821
</details>
@@ -1048,9 +1048,9 @@ lookup: mean -10s of user
1048
1049
Since [`z = (x - mean) / stddev`](https://en.wikipedia.org/wiki/Standard_score) we create two input alerts, one for `mean` and one for `stddev` and then use them both as inputs in our final `cpu_user_zscore` alert.
1050
1051
-### Example 6 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) based CPU chart alert
1051
+### Example 6 - [Anomaly rate](/src/ml/README.md#anomaly-rate) based CPU chart alert
1052
1053
-Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) averaged across all CPU dimensions is above 5%, critical if it goes above 20%:
1053
+Warning if 5 minute rolling [anomaly rate](/src/ml/README.md#anomaly-rate) averaged across all CPU dimensions is above 5%, critical if it goes above 20%:
1054
1055
```yaml
1056
template: ml_5min_cpu_chart
@@ -1067,9 +1067,9 @@ template: ml_5min_cpu_chart
1067
The `lookup` line will calculate the average anomaly rate across all `system.cpu` dimensions over the last 5 minues. In this case
1068
Netdata will create one alert for the chart.
1069
1070
-### Example 7 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) based node level alert
1070
+### Example 7 - [Anomaly rate](/src/ml/README.md#anomaly-rate) based node level alert
1071
1072
-Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) averaged across all ML enabled dimensions is above 5%, critical if it goes above 20%:
1072
+Warning if 5 minute rolling [anomaly rate](/src/ml/README.md#anomaly-rate) averaged across all ML enabled dimensions is above 5%, critical if it goes above 20%:
1073
1074
```yaml
1075
template: ml_5min_node
@@ -1083,11 +1083,11 @@ template: ml_5min_node
1083
info: rolling 5min anomaly rate for all ML enabled dims
1084
```
1085
1086
-The `lookup` line will use the `anomaly_rate` dimension of the `anomaly_detection.anomaly_rate` ML chart to calculate the average [node level anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#node-anomaly-rate) over the last 5 minutes.
1086
+The `lookup` line will use the `anomaly_rate` dimension of the `anomaly_detection.anomaly_rate` ML chart to calculate the average [node level anomaly rate](/src/ml/README.md#node-anomaly-rate) over the last 5 minutes.
1087
1088
## Troubleshooting
1089
1090
-You can compile Netdata with [debugging](https://github.com/netdata/netdata/blob/master/src/daemon/README.md#debugging) and then set in `netdata.conf`:
1090
+You can compile Netdata with [debugging](/src/daemon/README.md#debugging) and then set in `netdata.conf`:
1091
1092
```yaml
1093
[global]
src/health/guides/apcupsd/apcupsd_last_collected_secs.md
+1
-1
@@ -42,5 +42,5 @@ This alert is related to your American Power Conversion (APC) uninterruptible po
42
43
### Useful resources
44
45
-1. [Netdata - APC UPS monitoring](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/apcupsd/integrations/apc_ups.md)
45
+1. [Netdata - APC UPS monitoring](/src/collectors/charts.d.plugin/apcupsd/integrations/apc_ups.md)
46
2. [`apcupsd` - Power management and control software for APC UPS](https://github.com/apcupsd/apcupsd)
src/health/guides/dbengine/10min_dbengine_global_flushing_errors.md
+1
-1
@@ -9,5 +9,5 @@ faster disks. This alert is triggered in critical state when the number deleted
9
10
### Useful resources
11
12
-[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)
12
+[Read more about Netdata DB engine](/src/database/README.md/engine)
13
src/health/guides/dbengine/10min_dbengine_global_flushing_warnings.md
+1
-1
@@ -11,5 +11,5 @@ This alert is triggered in warn state when the number of `dbengine` dirty pages
11
12
### Useful resources
13
14
-[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)
14
+[Read more about Netdata DB engine](/src/database/README.md/engine)
15
src/health/guides/dbengine/10min_dbengine_global_fs_errors.md
+1
-1
@@ -10,5 +10,5 @@ This alert is triggered in warning state when the number of filesystem errors is
10
11
### Useful resources
12
13
-[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)
13
+[Read more about Netdata DB engine](/src/database/README.md/engine)
14
src/health/guides/dbengine/10min_dbengine_global_io_errors.md
+1
-1
@@ -10,5 +10,5 @@ This alert is triggered in critical state when the number of IO errors is greate
10
11
### Useful resources
12
13
-[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)
13
+[Read more about Netdata DB engine](/src/database/README.md/engine)
14
src/health/guides/entropy/lowest_entropy.md
+1
-1
@@ -4,7 +4,7 @@ This alert presents the minimum amount of entropy in the kernel entropy pool in
4
5
The Netdata Agent checks for the minimum entropy value in the last 5 minutes. The alert gets raised into warning if the value < 100, and cleared if the value > 200.
6
7
-For further information on how our alerts are calculated, please have a look at our [Documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#expressions).
7
+For further information on how our alerts are calculated, please have a look at our [Documentation](/src/health/REFERENCE.md#expressions).
8
9
### What is entropy and why do we need it?
10
src/health/guides/exporting/exporting_last_buffering.md
+1
-1
@@ -26,4 +26,4 @@ This alert is related to the Netdata Exporting engine, which calculates the numb
26
27
### Useful resources
28
29
-1. [Netdata Exporting Reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md)
29
+1. [Netdata Exporting Reference](/src/exporting/README.md)
src/health/guides/exporting/exporting_metrics_sent.md
+1
-1
@@ -43,4 +43,4 @@ To troubleshoot this alert, follow these steps:
43
44
### Useful resources
45
46
-1. [Netdata Exporting Reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md)
46
+1. [Netdata Exporting Reference](/src/exporting/README.md)
src/health/guides/httpcheck/httpcheck_web_service_bad_content.md
+1
-1
@@ -27,4 +27,4 @@ sudo ./edit-config go.d/httpcheck.conf
27
28
### Useful resources
29
30
-1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
\ No newline at end of file
30
+1. [HTTP endpoint monitoring with Netdata](/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
\ No newline at end of file
src/health/guides/httpcheck/httpcheck_web_service_bad_status.md
+1
-1
@@ -18,4 +18,4 @@ root@netdata # curl -v <your_http_endpoint>:<port>/<path>
18
19
### Useful resources
20
21
-1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
21
+1. [HTTP endpoint monitoring with Netdata](/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
src/health/guides/httpcheck/httpcheck_web_service_slow.md
+1
-1
@@ -14,5 +14,5 @@ To troubleshoot this issue, check for:
14
15
### Useful resources
16
17
-1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
17
+1. [HTTP endpoint monitoring with Netdata](/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
18
src/health/guides/httpcheck/httpcheck_web_service_unreachable.md
+1
-1
@@ -30,4 +30,4 @@ To troubleshoot this error, check the following:
30
31
### Useful resources
32
33
-1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
\ No newline at end of file
33
+1. [HTTP endpoint monitoring with Netdata](/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
\ No newline at end of file
src/health/guides/load/load_average_15.md
+1
-1
@@ -4,7 +4,7 @@ This alarm calculates the system `load average` (CPU and I/O demand) over the pe
4
5
The alert gets raised into warning if the metric is 2 times the expected value and cleared if the value is 1.75 times the expected value.
6
7
-For further information on how our alerts are calculated, please have a look at our [Documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#expressions).
7
+For further information on how our alerts are calculated, please have a look at our [Documentation](/src/health/REFERENCE.md#expressions).
8
9
### What does "load average" mean?
10
src/health/guides/load/load_average_5.md
+1
-1
@@ -4,7 +4,7 @@ This alarm calculates the system `load average` (CPU and I/O demand) over the pe
4
5
The alert gets raised into warning if the metric is 4 times the expected value and cleared if the value is 3.5 times the expected value.
6
7
-For further information on how our alerts are calculated, please have a look at our [Documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#expressions).
7
+For further information on how our alerts are calculated, please have a look at our [Documentation](/src/health/REFERENCE.md#expressions).
8
9
10
### What does "load average" mean?
src/health/guides/mdstat/mdstat_nonredundant_last_collected.md
+1
-1
@@ -52,4 +52,4 @@ The md (multiple device) driver is responsible for managing software RAID arrays
52
### Useful resources
53
54
1. [Linux RAID: A Quick Guide](https://www.cyberciti.biz/tips/linux-raid-increase-resync-rebuild-speed.html)
55
-2. [Netdata Agent Configuration Guide](https://github.com/netdata/netdata/blob/master/src/daemon/config/README.md)
55
+2. [Netdata Agent Configuration Guide](/src/daemon/config/README.md)
src/health/guides/ml/ml_1min_node_ar.md
+7
-7
@@ -1,8 +1,8 @@
1
### Understand the alert
2
3
-This alert is triggered when the [node anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md) exceeds the threshold defined in the [alert configuration](https://github.com/netdata/netdata/blob/master/src/health/health.d/ml.conf) over the most recent 1 minute window evaluated.
3
+This alert is triggered when the [node anomaly rate](/src/ml/README.md) exceeds the threshold defined in the [alert configuration](https://github.com/netdata/netdata/blob/master/src/health/health.d/ml.conf) over the most recent 1 minute window evaluated.
4
5
-For example, with the default of `warn: $this > 1`, this means that 1% or more of the metrics collected on the node have across the most recent 1 minute window been flagged as [anomalous](https://github.com/netdata/netdata/blob/master/src/ml/README.md) by Netdata.
5
+For example, with the default of `warn: $this > 1`, this means that 1% or more of the metrics collected on the node have across the most recent 1 minute window been flagged as [anomalous](/src/ml/README.md) by Netdata.
6
7
### Troubleshoot the alert
8
@@ -12,15 +12,15 @@ This alert is a signal that some significant percentage of metrics within your i
12
13
2. **Highlight the area of interest**: Highlight the timeframne of interest where you see an elevated anomaly rate.
14
15
-3. **Check the anomalies tab**: Check the [Anomaly Advisor tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md) to see an ordered list of what metrics were most anomalous in the highlighted window.
15
+3. **Check the anomalies tab**: Check the [Anomaly Advisor tab](/docs/dashboards-and-charts/anomaly-advisor-tab.md) to see an ordered list of what metrics were most anomalous in the highlighted window.
16
17
4. **Press the AR% button on Overview**: You can also press the "[AR%](https://blog.netdata.cloud/anomaly-rates-in-the-menu/)" button on the Overview or single node dashboard to see what parts of the menu have the highest chart anomaly rates. Pressing the AR% button should add some "pills" to each menu item and if you hover over it you will see that chart within each menu section that was most anomalous during the highlighted timeframe.
18
19
-5. **Use Metric Correlations**: Use [metric correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md) to see what metrics may have changed most significantly comparing before to the highlighted timeframe.
19
+5. **Use Metric Correlations**: Use [metric correlations](/docs/metric-correlations.md) to see what metrics may have changed most significantly comparing before to the highlighted timeframe.
20
21
### Useful resources
22
23
-1. [Machine learning (ML) powered anomaly detection](https://github.com/netdata/netdata/blob/master/src/ml/README.md)
24
-2. [Anomaly Advisor tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md)
25
-3. [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md)
23
+1. [Machine learning (ML) powered anomaly detection](/src/ml/README.md)
24
+2. [Anomaly Advisor tab](/docs/dashboards-and-charts/anomaly-advisor-tab.md)
25
+3. [Metric Correlations](/docs/metric-correlations.md)
26
4. [Anomaly Rates in the Menu!](https://blog.netdata.cloud/anomaly-rates-in-the-menu/)
src/health/notifications/README.md
+3
-3
@@ -10,10 +10,10 @@ The default script is `alarm-notify.sh`.
10
>
11
> This file mentions editing configuration files.
12
>
13
-> - To edit configuration files in a safe way, we provide the [`edit config` script](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf)located in your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory) (typically is `/etc/netdata`) that creates the proper file and opens it in an editor automatically.
13
+> - To edit configuration files in a safe way, we provide the [`edit config` script](/docs/netdata-agent/configuration/README.md#edit-netdataconf)located in your [Netdata config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory) (typically is `/etc/netdata`) that creates the proper file and opens it in an editor automatically.
14
> Note that to run the script you need to be inside your Netdata config directory.
15
>
16
-> - Please also note that after most configuration changes you will need to [restart the Agent](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for the changes to take effect.
16
+> - Please also note that after most configuration changes you will need to [restart the Agent](/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for the changes to take effect.
17
>
18
> It is recommended to use this way for configuring Netdata.
19
@@ -113,7 +113,7 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
113
/usr/libexec/netdata/plugins.d/alarm-notify.sh test "ROLE"
114
```
115
116
-If you are [running your own registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md#run-your-own-registry), add `export NETDATA_REGISTRY_URL=[YOUR_URL]` before calling `alarm-notify.sh`.
116
+If you are [running your own registry](/src/registry/README.md#run-your-own-registry), add `export NETDATA_REGISTRY_URL=[YOUR_URL]` before calling `alarm-notify.sh`.
117
118
> If you need to dig even deeper, you can trace the execution with `bash -x`. Note that in test mode, `alarm-notify.sh` calls itself with many more arguments. So first do:
119
>
src/health/notifications/alerta/README.md
+1
-1
@@ -40,7 +40,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
40
41
42
You can edit the configuration file using the `edit-config` script from the
43
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
45
```bash
46
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/awssns/README.md
+1
-1
@@ -57,7 +57,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
57
58
59
You can edit the configuration file using the `edit-config` script from the
60
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
60
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
61
62
```bash
63
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/custom/README.md
+1
-1
@@ -37,7 +37,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
37
38
39
You can edit the configuration file using the `edit-config` script from the
40
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
40
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
42
```bash
43
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/discord/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/dynatrace/README.md
+1
-1
@@ -42,7 +42,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
42
43
44
You can edit the configuration file using the `edit-config` script from the
45
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
45
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
47
```bash
48
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/email/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/flock/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/gotify/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/irc/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/kavenegar/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/matrix/README.md
+1
-1
@@ -40,7 +40,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
40
41
42
You can edit the configuration file using the `edit-config` script from the
43
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
45
```bash
46
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/messagebird/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/msteams/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/ntfy/README.md
+1
-1
@@ -40,7 +40,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
40
41
42
You can edit the configuration file using the `edit-config` script from the
43
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
45
```bash
46
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/opsgenie/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/pagerduty/README.md
+1
-1
@@ -41,7 +41,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
41
42
43
You can edit the configuration file using the `edit-config` script from the
44
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
44
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
45
46
```bash
47
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/prowl/README.md
+1
-1
@@ -44,7 +44,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
44
45
46
You can edit the configuration file using the `edit-config` script from the
47
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
48
49
```bash
50
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/pushbullet/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/pushover/README.md
+1
-1
@@ -42,7 +42,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
42
43
44
You can edit the configuration file using the `edit-config` script from the
45
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
45
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
47
```bash
48
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/rocketchat/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/slack/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/smstools3/README.md
+1
-1
@@ -43,7 +43,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
43
44
45
You can edit the configuration file using the `edit-config` script from the
46
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
46
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
47
48
```bash
49
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/syslog/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/telegram/README.md
+1
-1
@@ -39,7 +39,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
39
40
41
You can edit the configuration file using the `edit-config` script from the
42
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43
44
```bash
45
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/health/notifications/twilio/README.md
+1
-1
@@ -38,7 +38,7 @@ The configuration file name for this integration is `health_alarm_notify.conf`.
38
39
40
You can edit the configuration file using the `edit-config` script from the
41
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
41
+Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
42
43
```bash
44
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
src/libnetdata/ebpf/README.md
+1
-1
@@ -9,5 +9,5 @@ learn_rel_path: "Developers/libnetdata"
9
10
# eBPF library
11
12
-Netdata's eBPF library supports the [eBPF collector](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/README.md).
12
+Netdata's eBPF library supports the [eBPF collector](/src/collectors/ebpf.plugin/README.md).
13
src/libnetdata/procfile/README.md
+1
-1
@@ -32,7 +32,7 @@ For each iteration, the caller:
32
- calls `procfile_readall()` to read updated contents.
33
This call also rewinds (`lseek()` to 0) before reading it.
34
35
- For every file, a [BUFFER](https://github.com/netdata/netdata/blob/master/src/libnetdata/buffer/README.md) is used that is automatically adjusted to fit the entire
35
+ For every file, a [BUFFER](/src/libnetdata/buffer/README.md) is used that is automatically adjusted to fit the entire
36
file contents of the file. So the file is read with a single `read()` call (providing atomicity / consistency when
37
the data are read from the kernel).
38
src/logsmanagement/README.md
+3
-3
@@ -212,7 +212,7 @@ This collector will collect [Apache](https://httpd.apache.org/) and [Nginx](http
212
| :------------: | ------------ |
213
| `log path` | The path to the web server's `access.log`. If set to `auto`, the collector will attempt to auto-discover it, provided the name of the configuration section is either `Apache access.log` or `Nginx access.log`. |
214
| `use inotify` | Select between inotify and file stat watchers (providing `libfluent-bit.so` has been built with inotify support). It defaults to `yes`. Set to `no` if abnormally high CPU usage is observed or if the log source is expected to consistently produce tens of thousands of (unbuffered) logs per second. |
215
-| `log format` | The log format to be used for parsing. Unlike the [`GO weblog`]() module, only the `CSV` parser is supported and it can be configured [in the same way](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md#known-fields) as in the `GO` module. If set to `auto`, the collector will attempt to auto-detect the log format using the same logic explained [here](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/weblog/README.md#log-parser-auto-detection). |
215
+| `log format` | The log format to be used for parsing. Unlike the [`GO weblog`]() module, only the `CSV` parser is supported and it can be configured [in the same way](/src/go/collectors/go.d.plugin/modules/weblog/README.md#known-fields) as in the `GO` module. If set to `auto`, the collector will attempt to auto-detect the log format using the same logic explained [here](/src/go/collectors/go.d.plugin/modules/weblog/README.md#log-parser-auto-detection). |
216
| `verify parsed logs` | If set to `yes`, the parser will attempt to verify that the parsed fields are valid, before extracting metrics from them. If they are invalid (for example, the response code is less than `100`), the `invalid` dimension will be incremented instead. Setting this to `no` will result in a slight performance gain. |
217
| `vhosts chart` | Enable chart showing names of the virtual hosts extracted from the collected logs. |
218
| `ports chart` | Enable chart showing port numbers extracted from the collected logs. |
@@ -380,7 +380,7 @@ Netdata supports 2 incoming streaming configurations:
380
381
For option 1, please refer to the [syslog collector](#collector-configuration-syslog) section. This section will be focused on using option 2.
382
383
-A Netdata agent can be used as a logs aggregation parent to listen to `Forward` messages, using either Unix or network sockets. This option is separate to [Netdata's metrics streaming](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md) and can be used independently of whether that's enabled or not (and it uses a different listening socket too).
383
+A Netdata agent can be used as a logs aggregation parent to listen to `Forward` messages, using either Unix or network sockets. This option is separate to [Netdata's metrics streaming](/docs/observability-centralization-points/README.md) and can be used independently of whether that's enabled or not (and it uses a different listening socket too).
384
385
This setting can be enabled under the `[forward input]` section in `logsmanagement.d.conf`:
386
@@ -658,7 +658,7 @@ If during the Fluent Bit build step you are seeing the following message:
658
```
659
-- Could NOT find Journald (missing: JOURNALD_LIBRARY JOURNALD_INCLUDE_DIR)
660
```
661
-it means that the systemd development libraries are missing from your system. Please see [how to install them alongside other required packages](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md).
661
+it means that the systemd development libraries are missing from your system. Please see [how to install them alongside other required packages](/packaging/installer/methods/manual.md).
662
663
2. I am observing very high CPU usage when monitoring a log source using `flb_tail` or `flb_web_log`.
664
src/ml/README.md
+2
-2
@@ -2,11 +2,11 @@
2
3
In observability, machine learning can be used to detect patterns and anomalies in large datasets, enabling users to identify potential issues before they become critical.
4
5
-At Netdata through understanding what useful insights ML can provide, we created a tool that can improve troubleshooting, reduce mean time to resolution and in many cases prevent issues from escalating. That tool is called the [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md), available at our [Netdata dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md).
5
+At Netdata through understanding what useful insights ML can provide, we created a tool that can improve troubleshooting, reduce mean time to resolution and in many cases prevent issues from escalating. That tool is called the [Anomaly Advisor](/docs/dashboards-and-charts/anomaly-advisor-tab.md), available at our [Netdata dashboard](/docs/dashboards-and-charts/README.md).
6
7
> **Note**
8
>
9
-> If you want to learn how to configure ML on your nodes, check the [ML configuration documentation](https://github.com/netdata/netdata/blob/master/src/ml/ml-configuration.md).
9
+> If you want to learn how to configure ML on your nodes, check the [ML configuration documentation](/src/ml/ml-configuration.md).
10
11
## Design principles
12
src/ml/ml-configuration.md
+4
-4
@@ -1,12 +1,12 @@
1
# ML Configuration
2
3
-Netdata's [Machine Learning](https://github.com/netdata/netdata/blob/master/src/ml/README.md) capabilities are enabled by default.
3
+Netdata's [Machine Learning](/src/ml/README.md) capabilities are enabled by default.
4
5
To enable or disable Machine Learning capabilities on a node:
6
7
-1. [Edit `netdata.conf`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf)
7
+1. [Edit `netdata.conf`](/docs/netdata-agent/configuration/README.md#edit-netdataconf)
8
2. In the `[ml]` section, set `enabled = yes` to enable or `enabled = no` to disable
9
-3. [Restart Netdata](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/start-stop-restart.md)
9
+3. [Restart Netdata](/docs/netdata-agent/start-stop-restart.md)
10
11
Below is a list of all the available configuration params and their default values.
12
@@ -38,7 +38,7 @@ Below is a list of all the available configuration params and their default valu
38
39
If you would like to run ML on a parent instead of at the edge, some configuration options are illustrated below.
40
41
-This example assumes 3 child nodes [streaming](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/README.md) to 1 parent node and illustrates the main ways you might want to configure running ML for the children on the parent, running ML on the children themselves, or even a mix of approaches.
41
+This example assumes 3 child nodes [streaming](/docs/observability-centralization-points/metrics-centralization-points/README.md) to 1 parent node and illustrates the main ways you might want to configure running ML for the children on the parent, running ML on the children themselves, or even a mix of approaches.
42
43
```mermaid
44
flowchart BT
src/registry/README.md
+2
-2
@@ -136,7 +136,7 @@ Netdata v1.9+ support limiting access to the registry from given IPs, like this:
136
allow from = *
137
```
138
139
-`allow from` settings are [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md): string matches that use `*`
139
+`allow from` settings are [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md): string matches that use `*`
140
as wildcard (any number of times) and a `!` prefix for a negative match. So: `allow from = !10.1.2.3 10.*` will allow
141
all IPs in `10.*` except `10.1.2.3`. The order is important: left to right, the first positive or negative match is
142
used.
@@ -183,7 +183,7 @@ Both files are machine readable text files.
183
184
Beginning with `v1.30.0`, when the Netdata Agent's web server processes a request, it delivers the `SameSite=none`
185
and `Secure` cookies. If you have problems accessing the local Agent dashboard or Netdata Cloud, disable these
186
-cookies by [editing `netdata.conf`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf):
186
+cookies by [editing `netdata.conf`](/docs/netdata-agent/configuration/README.md#edit-netdataconf):
187
188
```conf
189
[registry]
src/streaming/README.md
+15
-15
@@ -2,14 +2,14 @@
2
3
This document contains advanced streaming options and suggested deployment options for production.
4
If you haven't already done so, we suggest you first go through the
5
-[quick introduction to streaming](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md)
5
+[quick introduction to streaming](/docs/observability-centralization-points/README.md)
6
, for your first, basic parent child setup.
7
8
## Configuration
9
10
There are two files responsible for configuring Netdata's streaming capabilities: `stream.conf` and `netdata.conf`.
11
12
-From within your Netdata config directory (typically `/etc/netdata`), [use `edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) to
12
+From within your Netdata config directory (typically `/etc/netdata`), [use `edit-config`](/docs/netdata-agent/configuration/README.md) to
13
open either `stream.conf` or `netdata.conf`.
14
15
```
@@ -40,7 +40,7 @@ node**. This file is automatically generated by Netdata the first time it is sta
40
| `api key` | | The `API_KEY` to use as the child node. |
41
| `timeout seconds` | `60` | The timeout to connect and send metrics to a parent. |
42
| `default port` | `19999` | The port to use if `destination` does not specify one. |
43
-| [`send charts matching`](#send-charts-matching) | `*` | A space-separated list of [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to filter which charts are streamed. [Read more →](#send-charts-matching) |
43
+| [`send charts matching`](#send-charts-matching) | `*` | A space-separated list of [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) to filter which charts are streamed. [Read more →](#send-charts-matching) |
44
| `buffer size bytes` | `10485760` | The size of the buffer to use when sending metrics. The default `10485760` equals a buffer of 10MB, which is good for 60 seconds of data. Increase this if you expect latencies higher than that. The buffer is flushed on reconnect. |
45
| `reconnect delay seconds` | `5` | How long to wait until retrying to connect to the parent node. |
46
| `initial clock resync iterations` | `60` | Sync the clock of charts for how many seconds when starting. |
@@ -51,9 +51,9 @@ node**. This file is automatically generated by Netdata the first time it is sta
51
| Setting | Default | Description |
52
|-----------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
53
| `enabled` | `no` | Whether this API KEY enabled or disabled. |
54
-| [`allow from`](#allow-from) | `*` | A space-separated list of [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) matching the IPs of nodes that will stream metrics using this API key. [Read more →](#allow-from) |
54
+| [`allow from`](#allow-from) | `*` | A space-separated list of [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) matching the IPs of nodes that will stream metrics using this API key. [Read more →](#allow-from) |
55
| `default history` | `3600` | The default amount of child metrics history to retain when using the `ram` memory mode. |
56
-| [`default memory mode`](#default-memory-mode) | `ram` | The [database](https://github.com/netdata/netdata/blob/master/src/database/README.md) to use for all nodes using this `API_KEY`. Valid settings are `dbengine`, `ram`, or `none`. [Read more →](#default-memory-mode) |
56
+| [`default memory mode`](#default-memory-mode) | `ram` | The [database](/src/database/README.md) to use for all nodes using this `API_KEY`. Valid settings are `dbengine`, `ram`, or `none`. [Read more →](#default-memory-mode) |
57
| `health enabled by default` | `auto` | Whether alerts and notifications should be enabled for nodes using this `API_KEY`. `auto` enables alerts when the child is connected. `yes` enables alerts always, and `no` disables alerts. |
58
| `default postpone alarms on connect seconds` | `60` | Postpone alerts and notifications for a period of time after the child connects. |
59
| `default health log history` | `432000` | History of health log events (in seconds) kept in the database. |
@@ -88,7 +88,7 @@ To enable TCP streaming to a parent node at `203.0.113.0` on port `20000` and wi
88
89
#### `send charts matching`
90
91
-A space-separated list of [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to filter which charts are streamed.
91
+A space-separated list of [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) to filter which charts are streamed.
92
93
The default is a single wildcard `*`, which streams all charts.
94
@@ -109,7 +109,7 @@ To send all but a few charts, use `!` to create a negative match. To send _all_
109
110
#### `allow from`
111
112
-A space-separated list of [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) matching the IPs of nodes that
112
+A space-separated list of [Netdata simple patterns](/src/libnetdata/simple_pattern/README.md) matching the IPs of nodes that
113
will stream metrics using this API key. The order is important, left to right, as the first positive or negative match is used.
114
115
The default is `*`, which accepts all requests including the `API_KEY`.
@@ -133,7 +133,7 @@ To allow all IPs starting with `10.*`, except `10.1.2.3`:
133
134
#### `default memory mode`
135
136
-The [database](https://github.com/netdata/netdata/blob/master/src/database/README.md) to use for all nodes using this `API_KEY`.
136
+The [database](/src/database/README.md) to use for all nodes using this `API_KEY`.
137
Valid settings are `dbengine`, `ram`, , or `none`.
138
139
- `dbengine`: The default, recommended time-series database (TSDB) for Netdata. Stores recent metrics in memory, then
@@ -143,7 +143,7 @@ Valid settings are `dbengine`, `ram`, , or `none`.
143
- `none`: No database.
144
145
When using `default memory mode = dbengine`, the parent node creates a separate instance of the TSDB to store metrics
146
-from child nodes. The [size of _each_ instance is configurable](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) with the `page
146
+from child nodes. The [size of _each_ instance is configurable](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) with the `page
147
cache size` and `dbengine multihost disk space` settings in the `[global]` section in `netdata.conf`.
148
149
### `netdata.conf`
@@ -151,9 +151,9 @@ cache size` and `dbengine multihost disk space` settings in the `[global]` secti
151
| Setting | Default | Description |
152
|--------------------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
153
| `[global]` section | | |
154
-| `memory mode` | `dbengine` | Determines the [database type](https://github.com/netdata/netdata/blob/master/src/database/README.md) to be used on that node. Other options settings include `none`, and `ram`. `none` disables the database at this host. This also disables alerts and notifications, as those can't run without a database. |
154
+| `memory mode` | `dbengine` | Determines the [database type](/src/database/README.md) to be used on that node. Other options settings include `none`, and `ram`. `none` disables the database at this host. This also disables alerts and notifications, as those can't run without a database. |
155
| `[web]` section | | |
156
-| `mode` | `static-threaded` | Determines the [web server](https://github.com/netdata/netdata/blob/master/src/web/server/README.md) type. The other option is `none`, which disables the dashboard, API, and registry. |
156
+| `mode` | `static-threaded` | Determines the [web server](/src/web/server/README.md) type. The other option is `none`, which disables the dashboard, API, and registry. |
157
| `accept a streaming request every seconds` | `0` | Set a limit on how often a parent node accepts streaming requests from child nodes. `0` equals no limit. If this is set, you may see `... too busy to accept new streaming request. Will be allowed in X secs` in Netdata's `error.log`. |
158
159
### Basic use cases
@@ -287,7 +287,7 @@ Same thing applies with the `[MACHINE_GUID]` configuration.
287
### Securing streaming with TLS/SSL
288
289
Netdata does not activate TLS encryption by default. To encrypt streaming connections, you first need to [enable TLS
290
-support](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#enabling-tls-support) on the parent. With encryption enabled on the receiving side, you
290
+support](/src/web/server/README.md#enabling-tls-support) on the parent. With encryption enabled on the receiving side, you
291
need to instruct the child to use TLS/SSL as well. On the child's `stream.conf`, configure the destination as follows:
292
293
```
@@ -490,8 +490,8 @@ You can monitor the replication process in two ways:
490
491
### Replication history
492
493
-Replication history in [dbengine](https://github.com/netdata/netdata/blob/master/src/database/README.md) mode is limited
494
-by [Tier 0 retention](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md#effect-of-storage-tiers-and-disk-space-on-retention):
493
+Replication history in [dbengine](/src/database/README.md) mode is limited
494
+by [Tier 0 retention](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md#effect-of-storage-tiers-and-disk-space-on-retention):
495
496
- Child instances replicate only Tier 0 data.
497
- Parent instance calculates higher-level tiers using Tier 0 as the basis.
@@ -599,7 +599,7 @@ ERROR : STREAM_SENDER[CHILD HOSTNAME] : STREAM child HOSTNAME [send to PARENT HO
599
Chart data needs to be consistent between child and parent nodes. If there are differences between chart data on
600
a parent and a child, such as gaps in metrics collection, it most often means your child's `memory mode`
601
does not match the parent's. To learn more about the different ways Netdata can store metrics, and thus keep chart
602
-data consistent, read our [memory mode documentation](https://github.com/netdata/netdata/blob/master/src/database/README.md).
602
+data consistent, read our [memory mode documentation](/src/database/README.md).
603
604
### Forbidding access
605
src/web/README.md
+6
-6
@@ -8,15 +8,15 @@ team and the community, but you can also customize them yourself.
8
9
There are two primary ways to view Netdata's dashboards on the agent:
10
11
-1. The [local Agent dashboard](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md) that comes pre-configured with every Netdata installation. You can
11
+1. The [local Agent dashboard](/src/web/gui/README.md) that comes pre-configured with every Netdata installation. You can
12
see it at `http://NODE:19999`, replacing `NODE` with `localhost`, the hostname of your node, or its IP address. You
13
can customize the contents and colors of the standard dashboard [using
14
- JavaScript](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md#customizing-the-local-dashboard).
14
+ JavaScript](/src/web/gui/README.md#customizing-the-local-dashboard).
15
16
2. The [`dashboard.js` JavaScript library](#dashboardjs), which helps you
17
- [customize the standard dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md#customizing-the-local-dashboard)
18
- using JavaScript, or create entirely new [custom dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md)
19
-You can also view all the data Netdata collects through the [REST API v1](https://github.com/netdata/netdata/blob/master/src/web/api/README.md#netdata-rest-api).
17
+ [customize the standard dashboards](/src/web/gui/README.md#customizing-the-local-dashboard)
18
+ using JavaScript, or create entirely new [custom dashboards](/src/web/gui/custom/README.md)
19
+You can also view all the data Netdata collects through the [REST API v1](/src/web/api/README.md#netdata-rest-api).
20
21
## dashboard.js
22
@@ -25,7 +25,7 @@ all the charts and other visualizations that appear on any Netdata dashboard.
25
You need to put `dashboard.js` on any HTML page that's going to render Netdata
26
charts.
27
28
-The [custom dashboards documentation](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md) contains examples of such
28
+The [custom dashboards documentation](/src/web/gui/custom/README.md) contains examples of such
29
custom HTML pages.
30
31
### Generating dashboard.js
src/web/api/badges/README.md
+1
-1
@@ -29,7 +29,7 @@ Similarly, there is [a chart that shows outbound bandwidth per class](http://lon
29
30
The right one is a **volume** calculation. Netdata calculated the total of the last 86.400 seconds (a day) which gives `kilobits`, then divided it by 8 to make it KB, then by 1024 to make it MB and then by 1024 to make it GB. Calculations like this are quite accurate, since for every value collected, every second, Netdata interpolates it to second boundary using microsecond calculations.
31
32
-Let's see a few more badge examples (they come from the [Netdata registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md)):
32
+Let's see a few more badge examples (they come from the [Netdata registry](/src/registry/README.md)):
33
34
- **cpu usage of user `root`** (you can pick any user; 100% = 1 core). This will be `green <10%`, `yellow <20%`, `orange <50%`, `blue <100%` (1 core), `red` otherwise (you define thresholds and colors on the URL).
35
src/web/api/exporters/prometheus/README.md
+1
-1
@@ -9,6 +9,6 @@ learn_rel_path: "Developers/Web/Api/Exporters"
9
10
# Prometheus exporter
11
12
-Read the Prometheus exporter documentation: [Using Netdata with Prometheus](https://github.com/netdata/netdata/blob/master/src/exporting/prometheus/README.md).
12
+Read the Prometheus exporter documentation: [Using Netdata with Prometheus](/src/exporting/prometheus/README.md).
13
14
src/web/api/formatters/README.md
+12
-12
@@ -16,18 +16,18 @@ The following formats are supported:
16
17
| format|module|content type|description|
18
|:----:|:----:|:----------:|:----------|
19
-| `array`|[ssv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/ssv/README.md)|application/json|a JSON array|
20
-| `csv`|[csv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/csv/README.md)|text/plain|a text table, comma separated, with a header line (dimension names) and `\r\n` at the end of the lines|
21
-| `csvjsonarray`|[csv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/csv/README.md)|application/json|a JSON array, with each row as another array (the first row has the dimension names)|
22
-| `datasource`|[json](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/json/README.md)|application/json|a Google Visualization Provider `datasource` javascript callback|
23
-| `datatable`|[json](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/json/README.md)|application/json|a Google `datatable`|
24
-| `html`|[csv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/csv/README.md)|text/html|an html table|
25
-| `json`|[json](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/json/README.md)|application/json|a JSON object|
26
-| `jsonp`|[json](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/json/README.md)|application/json|a JSONP javascript callback|
27
-| `markdown`|[csv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/csv/README.md)|text/plain|a markdown table|
28
-| `ssv`|[ssv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/ssv/README.md)|text/plain|a space separated list of values|
29
-| `ssvcomma`|[ssv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/ssv/README.md)|text/plain|a comma separated list of values|
30
-| `tsv`|[csv](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/csv/README.md)|text/plain|a TAB delimited `csv` (MS Excel flavor)|
19
+| `array`|[ssv](/src/web/api/formatters/ssv/README.md)|application/json|a JSON array|
20
+| `csv`|[csv](/src/web/api/formatters/csv/README.md)|text/plain|a text table, comma separated, with a header line (dimension names) and `\r\n` at the end of the lines|
21
+| `csvjsonarray`|[csv](/src/web/api/formatters/csv/README.md)|application/json|a JSON array, with each row as another array (the first row has the dimension names)|
22
+| `datasource`|[json](/src/web/api/formatters/json/README.md)|application/json|a Google Visualization Provider `datasource` javascript callback|
23
+| `datatable`|[json](/src/web/api/formatters/json/README.md)|application/json|a Google `datatable`|
24
+| `html`|[csv](/src/web/api/formatters/csv/README.md)|text/html|an html table|
25
+| `json`|[json](/src/web/api/formatters/json/README.md)|application/json|a JSON object|
26
+| `jsonp`|[json](/src/web/api/formatters/json/README.md)|application/json|a JSONP javascript callback|
27
+| `markdown`|[csv](/src/web/api/formatters/csv/README.md)|text/plain|a markdown table|
28
+| `ssv`|[ssv](/src/web/api/formatters/ssv/README.md)|text/plain|a space separated list of values|
29
+| `ssvcomma`|[ssv](/src/web/api/formatters/ssv/README.md)|text/plain|a comma separated list of values|
30
+| `tsv`|[csv](/src/web/api/formatters/csv/README.md)|text/plain|a TAB delimited `csv` (MS Excel flavor)|
31
32
For examples of each format, check the relative module documentation.
33
src/web/api/formatters/csv/README.md
+1
-1
@@ -9,7 +9,7 @@ learn_rel_path: "Developers/Web/Api/Formatters"
9
10
# CSV formatter
11
12
-The CSV formatter presents [results of database queries](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md) in the following formats:
12
+The CSV formatter presents [results of database queries](/src/web/api/queries/README.md) in the following formats:
13
14
| format|content type|description|
15
| :----:|:----------:|:----------|
src/web/api/formatters/json/README.md
+1
-1
@@ -9,7 +9,7 @@ learn_rel_path: "Developers/Web/Api/Formatters"
9
10
# JSON formatter
11
12
-The CSV formatter presents [results of database queries](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md) in the following formats:
12
+The CSV formatter presents [results of database queries](/src/web/api/queries/README.md) in the following formats:
13
14
| format | content type | description|
15
|:----:|:----------:|:----------|
src/web/api/formatters/ssv/README.md
+1
-1
@@ -9,7 +9,7 @@ learn_rel_path: "Developers/Web/Api/Formatters"
9
10
# SSV formatter
11
12
-The SSV formatter sums all dimensions in [results of database queries](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md)
12
+The SSV formatter sums all dimensions in [results of database queries](/src/web/api/queries/README.md)
13
to a single value and returns a list of such values showing how it changes through time.
14
15
It supports the following formats:
src/web/api/formatters/value/README.md
+3
-3
@@ -9,7 +9,7 @@ learn_rel_path: "Developers/Web/Api/Formatters"
9
10
# Value formatter
11
12
-The Value formatter presents [results of database queries](https://github.com/netdata/netdata/blob/master/src/web/api/queries/README.md) as a single value.
12
+The Value formatter presents [results of database queries](/src/web/api/queries/README.md) as a single value.
13
14
To calculate the single value to be returned, it sums the values of all dimensions.
15
@@ -22,7 +22,7 @@ The Value formatter respects the following API `&options=`:
22
| `min2max` | yes | to return the delta from the minimum value to the maximum value (across dimensions)|
23
24
The Value formatter is not exposed by the API by itself.
25
-Instead it is used by the [`ssv`](https://github.com/netdata/netdata/blob/master/src/web/api/formatters/ssv/README.md) formatter
26
-and [health monitoring queries](https://github.com/netdata/netdata/blob/master/src/health/README.md).
25
+Instead it is used by the [`ssv`](/src/web/api/formatters/ssv/README.md) formatter
26
+and [health monitoring queries](/src/health/README.md).
27
28
src/web/api/health/README.md
+3
-3
@@ -76,7 +76,7 @@ You can access the API via GET requests, by adding the bearer token to an `Autho
76
curl "http://NODE:19999/api/v1/manage/health?cmd=RESET" -H "X-Auth-Token: Mytoken"
77
```
78
79
-By default access to the health management API is only allowed from `localhost`. Accessing the API from anything else will return a 403 error with the message `You are not allowed to access this resource.`. You can change permissions by editing the `allow management from` variable in `netdata.conf` within the [web] section. See [web server access lists](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#access-lists) for more information.
79
+By default access to the health management API is only allowed from `localhost`. Accessing the API from anything else will return a 403 error with the message `You are not allowed to access this resource.`. You can change permissions by editing the `allow management from` variable in `netdata.conf` within the [web] section. See [web server access lists](/src/web/server/README.md#access-lists) for more information.
80
81
The command `RESET` just returns Netdata to the default operation, with all health checks and notifications enabled.
82
If you've configured and entered your token correctly, you should see the plain text response `All health checks and notifications are enabled`.
@@ -130,7 +130,7 @@ curl "http://NODE:19999/api/v1/manage/health?cmd=SILENCE&context=load" -H "X-Aut
130
131
#### Selection criteria
132
133
-The `selection criteria` are key/value pairs, in the format `key : value`, where value is a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). This means that you can create very powerful selectors (you will rarely need more than one or two).
133
+The `selection criteria` are key/value pairs, in the format `key : value`, where value is a Netdata [simple pattern](/src/libnetdata/simple_pattern/README.md). This means that you can create very powerful selectors (you will rarely need more than one or two).
134
135
The accepted keys for the `selection criteria` are the following:
136
@@ -217,6 +217,6 @@ The file's location is configurable in `netdata.conf`. The default is shown belo
217
218
### Further reading
219
220
-The test script under [tests/health_mgmtapi](https://github.com/netdata/netdata/blob/master/tests/health_mgmtapi/README.md) contains a series of tests that you can either run or read through to understand the various calls and responses better.
220
+The test script under [tests/health_mgmtapi](/tests/health_mgmtapi/README.md) contains a series of tests that you can either run or read through to understand the various calls and responses better.
221
222
src/web/api/queries/README.md
+2
-2
@@ -4,7 +4,7 @@ This document explains in detail the options available to retrieve data from the
4
create custom charts.
5
6
The Netdata database can be queried with the `/api/v1/data` and `/api/v1/badge.svg` REST API methods. The database is also queried from the `lookup` line
7
-in an [alert configuration](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md).
7
+in an [alert configuration](/src/health/REFERENCE.md).
8
9
Every data query accepts the following parameters:
10
@@ -87,7 +87,7 @@ To disable alignment, pass `&options=unaligned` to the query.
87
88
To execute the query, the engine evaluates all dimensions of the chart, one after another.
89
90
-The engine does not evaluate dimensions that do not match the [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md)
90
+The engine does not evaluate dimensions that do not match the [simple pattern](/src/libnetdata/simple_pattern/README.md)
91
given at the `dimensions` parameter, except when `options=percentage` is given (this option
92
requires all the dimensions to be evaluated to find the percentage of each dimension vs to chart
93
total).
src/web/gui/README.md
+10
-10
@@ -1,6 +1,6 @@
1
# Legacy Agent dashboard
2
3
-> ⚠️ You're checking the documentation for the legacy Agent dashboard. For the current version please check [Accessing Netdata Dashboards](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md).
3
+> ⚠️ You're checking the documentation for the legacy Agent dashboard. For the current version please check [Accessing Netdata Dashboards](/docs/dashboards-and-charts/README.md).
4
5
6
The local Netdata Agent dashboard is the heart of Netdata's performance troubleshooting toolkit. You've probably seen it
@@ -10,16 +10,16 @@ before:
10
action](https://user-images.githubusercontent.com/1153921/101513938-fae28380-3939-11eb-9434-8ad86a39be62.gif)
11
12
Learn more about how dashboards work and how they're populated using the `dashboards.js` file in our [web dashboards
13
-overview](https://github.com/netdata/netdata/blob/master/src/web/README.md).
13
+overview](/src/web/README.md).
14
15
By default, Netdata starts a web server for its dashboard at port `19999`. Open up your web browser of choice and
16
navigate to `http://NODE:19999`, replacing `NODE` with the IP address or hostname of your Agent. If installed on localhost,
17
you can access it through `http://localhost:19999`.
18
19
-Netdata uses an [internal, static-threaded web server](https://github.com/netdata/netdata/blob/master/src/web/server/README.md) to host the HTML, CSS, and JavaScript
19
+Netdata uses an [internal, static-threaded web server](/src/web/server/README.md) to host the HTML, CSS, and JavaScript
20
files that make up the local Agent dashboard. You don't have to configure anything to access it, although you can adjust
21
-[your settings](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#other-netdataconf-web-section-options) in the `netdata.conf` file, or run Netdata
22
-behind an [Nginx proxy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md), and so on.
21
+[your settings](/src/web/server/README.md#other-netdataconf-web-section-options) in the `netdata.conf` file, or run Netdata
22
+behind an [Nginx proxy](/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/Running-behind-nginx.md), and so on.
23
24
## Navigating the local dashboard
25
@@ -40,8 +40,8 @@ dashboard](https://user-images.githubusercontent.com/1153921/101509403-f7e59400-
40
41
Netdata is broken up into multiple **sections**, such as **System Overview**,
42
**CPU**, **Disk**, and more. Inside each section you'll find a number of charts,
43
-broken down into [contexts](https://github.com/netdata/netdata/blob/master/src/web/README.md#contexts) and
44
-[families](https://github.com/netdata/netdata/blob/master/src/web/README.md#families).
43
+broken down into [contexts](/src/web/README.md#contexts) and
44
+[families](/src/web/README.md#families).
45
46
An example of the **Memory** section on a Linux desktop system.
47
@@ -69,7 +69,7 @@ Use the calendar to select multiple days. Click on a date to begin the timeframe
69
70
Click **Apply** to re-render all visualizations with new metrics data, or **Clear** to restore the default timeframe.
71
72
-[Increase the metrics retention policy](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) for your node to see more historical
72
+[Increase the metrics retention policy](/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md) for your node to see more historical
73
timeframes.
74
75
### Metrics menus
@@ -80,7 +80,7 @@ section, and menus link to the section they're associated with.
80
81
82
Most metrics menu items will contain several **submenu** entries, which represent any
83
-[families](https://github.com/netdata/netdata/blob/master/src/web/README.md#families) from that section. Netdata automatically
83
+[families](/src/web/README.md#families) from that section. Netdata automatically
84
generates these submenu entries.
85
86
Here's a **Disks** menu with several submenu entries for each disk drive and
@@ -160,4 +160,4 @@ file](https://user-images.githubusercontent.com/1153921/62798924-570e6c80-ba94-1
160
161
## Custom dashboards
162
163
-For information on creating custom dashboards from scratch, see the [custom dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md) guide.
163
+For information on creating custom dashboards from scratch, see the [custom dashboards](/src/web/gui/custom/README.md) guide.
src/web/gui/custom/README.md
+4
-4
@@ -1,7 +1,7 @@
1
# Build new dashboards with HTML
2
3
>❗This feature is only available on v1 dashboards and is not currently supported on v2.
4
-> For more information on the new Custom Dashboards check [this documentation](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/dashboards-tab.md).
4
+> For more information on the new Custom Dashboards check [this documentation](/docs/dashboards-and-charts/dashboards-tab.md).
5
6
You can build dashboards with Netdata charts just with some basic HTML knowledge.
7
@@ -234,7 +234,7 @@ Each chart can get data from a different Netdata server. You can specify the Net
234
></div>
235
```
236
237
-If you have ephemeral monitoring setup ([More info here](https://github.com/netdata/netdata/blob/master/src/streaming/README.md#monitoring-ephemeral-nodes)) and have no
237
+If you have ephemeral monitoring setup ([More info here](/src/streaming/README.md#monitoring-ephemeral-nodes)) and have no
238
direct access to the nodes dashboards, you can use the following:
239
240
```html
@@ -358,7 +358,7 @@ select specific dimensions using this:
358
```
359
360
Netdata supports coma (`,`) or pipe (`|`) separated [simple
361
-patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for dimensions. By default it
361
+patterns](/src/libnetdata/simple_pattern/README.md) for dimensions. By default it
362
searches for both dimension IDs and dimension NAMEs. You can control the target
363
of the match with: `data-append-options="match-ids"` or
364
`data-append-options="match-names"`. Spaces in `data-dimensions=""` are matched
@@ -426,7 +426,7 @@ it, using this:
426
427
### API options
428
429
-You can append Netdata **[REST API v1](https://github.com/netdata/netdata/blob/master/src/web/api/README.md)** data options, using this:
429
+You can append Netdata **[REST API v1](/src/web/api/README.md)** data options, using this:
430
431
```html
432
<div data-netdata="unique.id"
src/web/server/README.md
+10
-10
@@ -9,7 +9,7 @@ This web server respects the `keep-alive` HTTP header to serve multiple HTTP req
9
10
## Configuration
11
12
-From within your Netdata config directory (typically `/etc/netdata`), [use `edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md) to
12
+From within your Netdata config directory (typically `/etc/netdata`), [use `edit-config`](/docs/netdata-agent/configuration/README.md) to
13
open `netdata.conf`.
14
15
```
@@ -26,8 +26,8 @@ Scroll down to the `[web]` section to find the following settings.
26
| `ssl certificate` | `/etc/netdata/ssl/cert.pem` | Declare the location of an SSL certificate to [enable HTTPS](#enable-httpstls-support). |
27
| `tls version` | `1.3` | Choose which TLS version to use. While all versions are allowed (`1` or `1.0`, `1.1`, `1.2` and `1.3`), we recommend `1.3` for the most secure encryption. If left blank, Netdata uses the highest available protocol version on your system. |
28
| `tls ciphers` | `none` | Choose which TLS cipher to use. Options include `TLS_AES_256_GCM_SHA384`, `TLS_CHACHA20_POLY1305_SHA256`, and `TLS_AES_128_GCM_SHA256`. If left blank, Netdata uses the default cipher list for that protocol provided by your TLS implementation. |
29
-| `ses max window` | `15` | See [single exponential smoothing](https://github.com/netdata/netdata/blob/master/src/web/api/queries/ses/README.md). |
30
-| `des max window` | `15` | See [double exponential smoothing](https://github.com/netdata/netdata/blob/master/src/web/api/queries/des/README.md). |
29
+| `ses max window` | `15` | See [single exponential smoothing](/src/web/api/queries/ses/README.md). |
30
+| `des max window` | `15` | See [double exponential smoothing](/src/web/api/queries/des/README.md). |
31
| `mode` | `static-threaded` | Turns on (`static-threaded` or off (`none`) the static-threaded web server. See the [example](#disable-the-web-server) to turn off the web server and disable the dashboard. |
32
| `listen backlog` | `4096` | The port backlog. Check `man 2 listen`. |
33
| `default port` | `19999` | The listen port for the static web server. |
@@ -35,10 +35,10 @@ Scroll down to the `[web]` section to find the following settings.
35
| `web files group` | `netdata` | If this is set, Netdata will check if the file is owned by this group and refuse to serve the file if it's not. |
36
| `disconnect idle clients after seconds` | `60` | The time in seconds to disconnect web clients after being totally idle. |
37
| `timeout for first request` | `60` | How long to wait for a client to send a request before closing the socket. Prevents slow request attacks. |
38
-| `accept a streaming request every seconds` | `0` | Can be used to set a limit on how often a parent node will accept streaming requests from child nodes in a [streaming and replication setup](https://github.com/netdata/netdata/blob/master/src/streaming/README.md). |
39
-| `respect do not track policy` | `no` | If set to `yes`, Netdata will respect the user's browser preferences for [Do Not Track](https://www.eff.org/issues/do-not-track) (DNT) and storing cookies. If DNT is _enabled_ in the browser, and this option is set to `yes`, nodes will not connect to any [registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md). For certain browsers, users must disable DNT and change this option to `yes` for full functionality. |
38
+| `accept a streaming request every seconds` | `0` | Can be used to set a limit on how often a parent node will accept streaming requests from child nodes in a [streaming and replication setup](/src/streaming/README.md). |
39
+| `respect do not track policy` | `no` | If set to `yes`, Netdata will respect the user's browser preferences for [Do Not Track](https://www.eff.org/issues/do-not-track) (DNT) and storing cookies. If DNT is _enabled_ in the browser, and this option is set to `yes`, nodes will not connect to any [registry](/src/registry/README.md). For certain browsers, users must disable DNT and change this option to `yes` for full functionality. |
40
| `x-frame-options response header` | ` ` | Avoid [clickjacking attacks](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options), by ensuring that the content is not embedded into other sites. |
41
-| `allow connections from` | `localhost *` | Declare which IP addresses or full-qualified domain names (FQDNs) are allowed to connect to the web server, including the [dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/README.md) or [HTTP API](https://github.com/netdata/netdata/blob/master/src/web/api/README.md). This is a global setting with higher priority to any of the ones below. |
41
+| `allow connections from` | `localhost *` | Declare which IP addresses or full-qualified domain names (FQDNs) are allowed to connect to the web server, including the [dashboard](/docs/dashboards-and-charts/README.md) or [HTTP API](/src/web/api/README.md). This is a global setting with higher priority to any of the ones below. |
42
| `allow connections by dns` | `heuristic` | See the [access list examples](#access-lists) for details on using `allow` settings. |
43
| `allow dashboard from` | `localhost *` | |
44
| `allow dashboard by dns` | `heuristic` | |
@@ -55,7 +55,7 @@ Scroll down to the `[web]` section to find the following settings.
55
| `gzip compression level` | `3` | Valid settings are 1 (fastest) to 9 (best ratio). |
56
| `web server threads` | ` ` | How many processor threads the web server is allowed. The default is system-specific, the minimum of `6` or the number of CPU cores. |
57
| `web server max sockets` | ` ` | Available sockets. The default is system-specific, automatically adjusted to 50% of the max number of open files Netdata is allowed to use (via `/etc/security/limits.conf` or systemd), to allow enough file descriptors to be available for data collection. |
58
-| `custom dashboard_info.js` | ` ` | Specifies the location of a custom `dashboard.js` file. See [customizing the standard dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/customize.md#customize-the-standard-dashboard) for details. |
58
+| `custom dashboard_info.js` | ` ` | Specifies the location of a custom `dashboard.js` file. See [customizing the standard dashboard](/docs/developer-and-contributor-corner/customize.md#customize-the-standard-dashboard) for details. |
59
60
## Examples
61
@@ -95,7 +95,7 @@ Using the above, Netdata will bind to:
95
- IPv4 127.0.0.1 at port 19999 (port was used from `default port`). Only the UI (dashboard) and the read API will be accessible on this port. Both HTTP and HTTPS requests will be accepted.
96
- IPv4 10.1.1.1 at port 19998. The management API and `netdata.conf` will be accessible on this port.
97
- All the IPs `hostname` resolves to (both IPv4 and IPv6 depending on the resolved IPs) at port 19997. Only badges will be accessible on this port.
98
-- All IPv6 IPs at port 19996. Only metric streaming requests from other Netdata agents will be accepted on this port. Only encrypted streams will be allowed (i.e. child nodes also need to be [configured for TLS](https://github.com/netdata/netdata/blob/master/src/streaming/README.md).
98
+- All IPv6 IPs at port 19996. Only metric streaming requests from other Netdata agents will be accepted on this port. Only encrypted streams will be allowed (i.e. child nodes also need to be [configured for TLS](/src/streaming/README.md).
99
- All the IPs `localhost` resolves to (both IPv4 and IPv6 depending the resolved IPs) at port 19996. This port will only accept registry API requests.
100
- All IPv4 and IPv6 IPs at port `http` as set in `/etc/services`. Only the UI (dashboard) and the read API will be accessible on this port.
101
- Unix domain socket `/run/netdata/netdata.sock`. All requests are serviceable on this socket. Note that in some OSs like Fedora, every service sees a different `/tmp`, so don't create a Unix socket under `/tmp`. `/run` or `/var/run` is suggested.
@@ -182,7 +182,7 @@ Example:
182
bind to = *=dashboard|registry|badges|management|streaming|netdata.conf^SSL=force
183
```
184
185
-For information how to configure the child to use TLS, check [securing the communication](https://github.com/netdata/netdata/blob/master/src/streaming/README.md#securing-streaming-communications) in the streaming documentation. There you will find additional details on the expected behavior for client and server nodes, when their respective TLS options are enabled.
185
+For information how to configure the child to use TLS, check [securing the communication](/src/streaming/README.md#securing-streaming-communications) in the streaming documentation. There you will find additional details on the expected behavior for client and server nodes, when their respective TLS options are enabled.
186
187
When we define the use of SSL in a Netdata agent for different ports, Netdata will apply the behavior specified on each port. For example, using the configuration line below:
188
@@ -238,7 +238,7 @@ Netdata supports access lists in `netdata.conf`:
238
- `allow netdata.conf from` checks the IP to allow `http://netdata.host:19999/netdata.conf`.
239
The IPs listed are all the private IPv4 addresses, including link local IPv6 addresses. Keep in mind that connections to Netdata API ports are filtered by `allow connections from`. So, IPs allowed by `allow netdata.conf from` should also be allowed by `allow connections from`.
240
241
-- `allow management from` checks the IPs to allow API management calls. Management via the API is currently supported for [health](https://github.com/netdata/netdata/blob/master/src/web/api/health/README.md#health-management-api)
241
+- `allow management from` checks the IPs to allow API management calls. Management via the API is currently supported for [health](/src/web/api/health/README.md#health-management-api)
242
243
In order to check the FQDN of the connection without opening the Netdata agent to DNS-spoofing, a reverse-dns record
244
must be setup for the connecting host. At connection time the reverse-dns of the peer IP address is resolved, and
tests/health_mgmtapi/README.md
+1
-1
@@ -9,7 +9,7 @@ learn_rel_path: "Developers"
9
10
# Health command API tester
11
12
-The directory `tests/health_cmdapi` contains the test script `health-cmdapi-test.sh` for the [health command API](https://github.com/netdata/netdata/blob/master/src/web/api/health/README.md).
12
+The directory `tests/health_cmdapi` contains the test script `health-cmdapi-test.sh` for the [health command API](/src/web/api/health/README.md).
13
14
The script can be executed with options to prepare the system for the tests, run them and restore the system to its previous state.
15