diff --git a/BREAKING_CHANGES.md b/BREAKING_CHANGES.md
index 20d055621a..3399cb61f3 100644
--- a/BREAKING_CHANGES.md
+++ b/BREAKING_CHANGES.md
@@ -8,4 +8,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/BREAKING_CHANGES
- remove deprecated bash modules (`apache`, `cpu_apps`, `cpufreq`, `exim`, `hddtemp`, `load_average`, `mem_apps`, `mysql`, `nginx`, `phpfpm`, `postfix`, `squid`, `tomcat`) [[#7962](https://github.com/netdata/netdata/pull/7962)]
-[](<>)
+
diff --git a/BUILD.md b/BUILD.md
index 049c86d3f5..83f7e9945e 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -362,4 +362,4 @@ Some smaller miscellaneous suggestions:
* [header checks in CMake](https://stackoverflow.com/questions/647892/how-to-check-header-files-and-library-functions-in-cmake-like-it-is-done-in-auto)
* [how to write platform checks](https://gitlab.kitware.com/cmake/community/wikis/doc/tutorials/How-To-Write-Platform-Checks)
-[](<>)
+
diff --git a/README.md b/README.md
index a1f7933a7a..b979e60847 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,6 @@
<a href="https://travis-ci.com/netdata/netdata"><img src="https://travis-ci.com/netdata/netdata.svg?branch=master" alt="Build status"></a>
<a href="https://bestpractices.coreinfrastructure.org/projects/2231"><img src="https://bestpractices.coreinfrastructure.org/projects/2231/badge" alt="CII Best Practices"></a>
<a href="https://www.gnu.org/licenses/gpl-3.0"><img src="https://img.shields.io/badge/License-GPL%20v3%2B-blue.svg" alt="License: GPL v3+"></a>
- <a href="<>"><img src="https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Freadme&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3" alt="analytics"></a>
<br />
<a href="https://codeclimate.com/github/netdata/netdata"><img src="https://codeclimate.com/github/netdata/netdata/badges/gpa.svg" alt="Code Climate"></a>
<a href="https://www.codacy.com/app/netdata/netdata?utm_source=github.com&utm_medium=referral&utm_content=netdata/netdata&utm_campaign=Badge_Grade"><img src="https://api.codacy.com/project/badge/Grade/a994873f30d045b9b4b83606c3eb3498" alt="Codacy"></a>
diff --git a/REDISTRIBUTED.md b/REDISTRIBUTED.md
index fb256b5fce..0b62d54b56 100644
--- a/REDISTRIBUTED.md
+++ b/REDISTRIBUTED.md
@@ -180,4 +180,4 @@ connectivity is not available.
Copyright 2015, Benedikt Schmitt [Unlicense License](https://unlicense.org/)
-[](<>)
+
diff --git a/aclk/README.md b/aclk/README.md
index 870314be47..09c0d2920f 100644
--- a/aclk/README.md
+++ b/aclk/README.md
@@ -134,4 +134,4 @@ If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf`
Restart your Agent and [connect your node](/claim/README.md#how-to-connect-a-node).
-[](<>)
+
diff --git a/backends/README.md b/backends/README.md
index 8d53fd664e..62d68b3cc7 100644
--- a/backends/README.md
+++ b/backends/README.md
@@ -233,4 +233,4 @@ Netdata adds 4 alarms:
-[](<>)
+
diff --git a/backends/TIMESCALE.md b/backends/TIMESCALE.md
index 05a3c3b470..34f052c940 100644
--- a/backends/TIMESCALE.md
+++ b/backends/TIMESCALE.md
@@ -54,4 +54,4 @@ blog](https://blog.timescale.com/blog/writing-it-metrics-from-netdata-to-timesca
Thank you to Mahlon, Rune, TimescaleDB, and the members of the Netdata community that requested and then built this
backend connection between Netdata and TimescaleDB!
-[](<>)
+
diff --git a/backends/WALKTHROUGH.md b/backends/WALKTHROUGH.md
index bb38e7c1c6..881c6bf7c8 100644
--- a/backends/WALKTHROUGH.md
+++ b/backends/WALKTHROUGH.md
@@ -255,4 +255,4 @@ achieved you do not have to think about the monitoring system until Prometheus c
happens there are options presented in the Prometheus documentation for solving this. Hope this was helpful, happy
monitoring.
-[](<>)
+
diff --git a/backends/aws_kinesis/README.md b/backends/aws_kinesis/README.md
index a2b682517e..d20d7f8f9e 100644
--- a/backends/aws_kinesis/README.md
+++ b/backends/aws_kinesis/README.md
@@ -50,4 +50,4 @@ Alternatively, AWS credentials can be set for the `netdata` user using AWS SDK f
A partition key for every record is computed automatically by Netdata with the purpose to distribute records across
available shards evenly.
-[](<>)
+
diff --git a/backends/mongodb/README.md b/backends/mongodb/README.md
index 7c7996e1be..27229e59d9 100644
--- a/backends/mongodb/README.md
+++ b/backends/mongodb/README.md
@@ -38,4 +38,4 @@ collection = your_collection_name
The default socket timeout depends on the backend update interval. The timeout is 500 ms shorter than the interval (but
not less than 1000 ms). You can alter the timeout using the `sockettimeoutms` MongoDB URI option.
-[](<>)
+
diff --git a/backends/opentsdb/README.md b/backends/opentsdb/README.md
index 5ba7b12c58..0fa8e62f44 100644
--- a/backends/opentsdb/README.md
+++ b/backends/opentsdb/README.md
@@ -35,4 +35,3 @@ After your proxy is configured, make the following changes to `netdata.conf`:
In this example, we used the port `8082` for our reverse proxy. If your reverse proxy listens on a different port,
change the `destination = localhost:8082` line accordingly.
-[]()
diff --git a/backends/prometheus/README.md b/backends/prometheus/README.md
index a0460d1d8e..5022ecd251 100644
--- a/backends/prometheus/README.md
+++ b/backends/prometheus/README.md
@@ -454,4 +454,4 @@ through a web proxy, or when multiple prometheus servers are NATed to a single I
`&server=NAME` to the URL. This `NAME` is used by Netdata to uniquely identify each prometheus server and keep track of
its last access time.
-[](<>)
+
diff --git a/backends/prometheus/remote_write/README.md b/backends/prometheus/remote_write/README.md
index b83575e100..c6749091fe 100644
--- a/backends/prometheus/remote_write/README.md
+++ b/backends/prometheus/remote_write/README.md
@@ -38,4 +38,4 @@ buffer size on failures.
The remote write backend does not support `buffer on failures`
-[](<>)
+
diff --git a/build_external/README.md b/build_external/README.md
index 6a1e30a574..d68e4d0f10 100644
--- a/build_external/README.md
+++ b/build_external/README.md
@@ -125,4 +125,4 @@ Notes:
* There is not yet a good way to configure the target agent container from the docker-compose command line.
* Several other containers should be in this compose (a paho client, tshark etc).
-[]()
+
diff --git a/claim/README.md b/claim/README.md
index d7b6ba1cb5..72f32bb617 100644
--- a/claim/README.md
+++ b/claim/README.md
@@ -548,4 +548,4 @@ Rooms you added that node to.
The user can also put the Cloud endpoint's full certificate chain in `cloud.d/cloud_fullchain.pem` so that the Agent
can trust the endpoint if necessary.
-[](<>)
+
diff --git a/cli/README.md b/cli/README.md
index 6eb121be5f..75a90b08a2 100644
--- a/cli/README.md
+++ b/cli/README.md
@@ -37,4 +37,4 @@ aclk-state [json]
Those commands are the same that can be sent to netdata via [signals](/daemon/README.md#command-line-options).
-[](<>)
+
diff --git a/collectors/COLLECTORS.md b/collectors/COLLECTORS.md
index 19790c4244..c40768bef1 100644
--- a/collectors/COLLECTORS.md
+++ b/collectors/COLLECTORS.md
@@ -540,4 +540,4 @@ default. To use a third-party collector, visit their GitHub/documentation page a
- [charts.d example](charts.d.plugin/example/README.md): An example `charts.d` collector.
- [python.d example](python.d.plugin/example/README.md): An example `python.d` collector.
-[](<>)
+
diff --git a/collectors/README.md b/collectors/README.md
index e9cce42b39..863a7b0621 100644
--- a/collectors/README.md
+++ b/collectors/README.md
@@ -46,4 +46,4 @@ long-term metrics storage, by archiving metrics to like Graphite, Prometheus, Mo
**[Exporting](/exporting/README.md)**: An experimental refactoring of our backends system with a modular system and
support for exporting metrics to multiple systems simultaneously.
-[](<>)
+
diff --git a/collectors/REFERENCE.md b/collectors/REFERENCE.md
index fc9ed366d3..bd267c5c6f 100644
--- a/collectors/REFERENCE.md
+++ b/collectors/REFERENCE.md
@@ -179,4 +179,3 @@ through this, is to examine what other similar plugins do.
You can add custom collectors by following the [external plugins documentation](/collectors/plugins.d/README.md).
-[]()
diff --git a/collectors/apps.plugin/README.md b/collectors/apps.plugin/README.md
index a85c07898d..76821695a1 100644
--- a/collectors/apps.plugin/README.md
+++ b/collectors/apps.plugin/README.md
@@ -396,4 +396,4 @@ if you sum the CPU utilization of all processes, you might have more CPU time th
total cpu time of the system. Netdata solves this, by adapting the per process cpu utilization to
the total of the system. [Netdata adds charts that document this normalization](https://london.my-netdata.io/default.html#menu_netdata_submenu_apps_plugin).
-[](<>)
+
diff --git a/collectors/cgroups.plugin/README.md b/collectors/cgroups.plugin/README.md
index 86776d6e0e..d74ef000e9 100644
--- a/collectors/cgroups.plugin/README.md
+++ b/collectors/cgroups.plugin/README.md
@@ -284,4 +284,4 @@ So, when a network interface or container stops, Netdata might log a few errors
Network interfaces are monitored by means of the [proc plugin](/collectors/proc.plugin/README.md#monitored-network-interface-metrics).
-[](<>)
+
diff --git a/collectors/charts.d.plugin/README.md b/collectors/charts.d.plugin/README.md
index 4a7911a603..06f4af1ece 100644
--- a/collectors/charts.d.plugin/README.md
+++ b/collectors/charts.d.plugin/README.md
@@ -195,4 +195,4 @@ This is what you need to do:
Execute the above in this order, since Netdata will (by default) attempt to start new plugins soon after they are
created in `/usr/libexec/netdata/plugins.d/`.
-[](<>)
+
diff --git a/collectors/charts.d.plugin/ap/README.md b/collectors/charts.d.plugin/ap/README.md
index 35a00d65d4..a7953a5414 100644
--- a/collectors/charts.d.plugin/ap/README.md
+++ b/collectors/charts.d.plugin/ap/README.md
@@ -96,4 +96,4 @@ You can only set `ap_update_every=NUMBER` to change the data collection frequenc
The plugin is able to auto-detect if you are running access points on your linux box.
-[](<>)
+
diff --git a/collectors/charts.d.plugin/apcupsd/README.md b/collectors/charts.d.plugin/apcupsd/README.md
index b5b41e84d4..f1aebf97ca 100644
--- a/collectors/charts.d.plugin/apcupsd/README.md
+++ b/collectors/charts.d.plugin/apcupsd/README.md
@@ -18,4 +18,4 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
sudo ./edit-config charts.d/apcupsd.conf
```
-[](<>)
+
diff --git a/collectors/charts.d.plugin/example/README.md b/collectors/charts.d.plugin/example/README.md
index c3dfd2c001..77446b2702 100644
--- a/collectors/charts.d.plugin/example/README.md
+++ b/collectors/charts.d.plugin/example/README.md
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/chart
If you want to understand how charts.d data collector functions, check out the [charts.d example](https://raw.githubusercontent.com/netdata/netdata/master/collectors/charts.d.plugin/example/example.chart.sh).
-[](<>)
+
diff --git a/collectors/charts.d.plugin/libreswan/README.md b/collectors/charts.d.plugin/libreswan/README.md
index b1c1f05e43..41c4e24c93 100644
--- a/collectors/charts.d.plugin/libreswan/README.md
+++ b/collectors/charts.d.plugin/libreswan/README.md
@@ -53,4 +53,4 @@ Make sure the path `/sbin/ipsec` matches your setup (execute `which ipsec` to fi
---
-[](<>)
+
diff --git a/collectors/charts.d.plugin/nut/README.md b/collectors/charts.d.plugin/nut/README.md
index 3f9c5f0a25..69d7622cd2 100644
--- a/collectors/charts.d.plugin/nut/README.md
+++ b/collectors/charts.d.plugin/nut/README.md
@@ -71,4 +71,4 @@ nut_update_every=2
---
-[](<>)
+
diff --git a/collectors/charts.d.plugin/opensips/README.md b/collectors/charts.d.plugin/opensips/README.md
index 7575a1dad6..b08d19232b 100644
--- a/collectors/charts.d.plugin/opensips/README.md
+++ b/collectors/charts.d.plugin/opensips/README.md
@@ -16,4 +16,4 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
sudo ./edit-config charts.d/opensips.conf
```
-[](<>)
+
diff --git a/collectors/charts.d.plugin/sensors/README.md b/collectors/charts.d.plugin/sensors/README.md
index 2a1cdb6765..ab7a8b6606 100644
--- a/collectors/charts.d.plugin/sensors/README.md
+++ b/collectors/charts.d.plugin/sensors/README.md
@@ -81,4 +81,4 @@ sensors_excluded=()
---
-[](<>)
+
diff --git a/collectors/checks.plugin/README.md b/collectors/checks.plugin/README.md
index 5f1a6b912b..6e2cf5dea7 100644
--- a/collectors/checks.plugin/README.md
+++ b/collectors/checks.plugin/README.md
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/check
A debugging plugin (by default it is disabled)
-[](<>)
+
diff --git a/collectors/cups.plugin/README.md b/collectors/cups.plugin/README.md
index 373602dca1..e3d2e1661b 100644
--- a/collectors/cups.plugin/README.md
+++ b/collectors/cups.plugin/README.md
@@ -59,4 +59,4 @@ For each destination the plugin provides these charts:
At the moment only job status pending, processing, and held are reported because we do not have a method to collect stopped, canceled, aborted and completed jobs which scales.
-[]()
+
diff --git a/collectors/diskspace.plugin/README.md b/collectors/diskspace.plugin/README.md
index a8b41c861d..c037a0b167 100644
--- a/collectors/diskspace.plugin/README.md
+++ b/collectors/diskspace.plugin/README.md
@@ -40,4 +40,4 @@ Charts can be enabled/disabled for every mount separately:
> for disks performance monitoring, see the `proc` plugin, [here](/collectors/proc.plugin/README.md#monitoring-disks)
-[](<>)
+
diff --git a/collectors/ebpf.plugin/README.md b/collectors/ebpf.plugin/README.md
index babcd5206b..e0b74a575a 100644
--- a/collectors/ebpf.plugin/README.md
+++ b/collectors/ebpf.plugin/README.md
@@ -899,4 +899,4 @@ shows how the lockdown module impacts `ebpf.plugin` based on the selected option
If you or your distribution compiled the kernel with the last combination, your system cannot load shared libraries
required to run `ebpf.plugin`.
-[](<>)
+
diff --git a/collectors/fping.plugin/README.md b/collectors/fping.plugin/README.md
index 4aca2a9de3..626edf5d0e 100644
--- a/collectors/fping.plugin/README.md
+++ b/collectors/fping.plugin/README.md
@@ -99,4 +99,4 @@ That's it. Netdata will detect the new plugin and start it.
You can name the new plugin any name you like.
Just make sure the plugin and the configuration file have the same name.
-[](<>)
+
diff --git a/collectors/freebsd.plugin/README.md b/collectors/freebsd.plugin/README.md
index 1b519a6594..9a97a7ece6 100644
--- a/collectors/freebsd.plugin/README.md
+++ b/collectors/freebsd.plugin/README.md
@@ -9,4 +9,4 @@ Collects resource usage and performance data on FreeBSD systems
By default, Netdata will enable monitoring metrics for disks, memory, and network only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Use `yes` instead of `auto` in plugin configuration sections to enable these charts permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
-[](<>)
+
diff --git a/collectors/freeipmi.plugin/README.md b/collectors/freeipmi.plugin/README.md
index 3ff6f4099b..13958784ea 100644
--- a/collectors/freeipmi.plugin/README.md
+++ b/collectors/freeipmi.plugin/README.md
@@ -191,4 +191,4 @@ If you need to disable IPMI for Netdata, edit `/etc/netdata/netdata.conf` and se
freeipmi = no
```
-[](<>)
+
diff --git a/collectors/idlejitter.plugin/README.md b/collectors/idlejitter.plugin/README.md
index 40436d33c0..5a92d53177 100644
--- a/collectors/idlejitter.plugin/README.md
+++ b/collectors/idlejitter.plugin/README.md
@@ -29,4 +29,4 @@ idlejitter.plugin generates the idlejitter chart which measures CPU idle jitter
This chart is available without any configuration.
-[](<>)
+
diff --git a/collectors/ioping.plugin/README.md b/collectors/ioping.plugin/README.md
index 08b0ce8b15..c4c3695c54 100644
--- a/collectors/ioping.plugin/README.md
+++ b/collectors/ioping.plugin/README.md
@@ -83,4 +83,4 @@ That's it. Netdata will detect the new plugin and start it.
You can name the new plugin any name you like.
Just make sure the plugin and the configuration file have the same name.
-[](<>)
+
diff --git a/collectors/macos.plugin/README.md b/collectors/macos.plugin/README.md
index 800eb0e85e..92bbf1eb1c 100644
--- a/collectors/macos.plugin/README.md
+++ b/collectors/macos.plugin/README.md
@@ -9,4 +9,4 @@ Collects resource usage and performance data on macOS systems
By default, Netdata will enable monitoring metrics for disks, memory, and network only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Use `yes` instead of `auto` in plugin configuration sections to enable these charts permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
-[](<>)
+
diff --git a/collectors/nfacct.plugin/README.md b/collectors/nfacct.plugin/README.md
index 1bd8a46e8f..81f21ccfd1 100644
--- a/collectors/nfacct.plugin/README.md
+++ b/collectors/nfacct.plugin/README.md
@@ -51,4 +51,4 @@ sudo /usr/libexec/netdata/plugins.d/nfacct.plugin 1 debug
You will get verbose output on what the plugin does.
-[](<>)
+
diff --git a/collectors/node.d.plugin/README.md b/collectors/node.d.plugin/README.md
index 8db80d85be..4c5f278bd6 100644
--- a/collectors/node.d.plugin/README.md
+++ b/collectors/node.d.plugin/README.md
@@ -233,4 +233,4 @@ The `service` object defines a set of functions to allow you send information to
_FIXME: document an operational node.d.plugin data collector - the best example is the
[snmp collector](https://raw.githubusercontent.com/netdata/netdata/master/collectors/node.d.plugin/snmp/snmp.node.js)_
-[](<>)
+
diff --git a/collectors/node.d.plugin/fronius/README.md b/collectors/node.d.plugin/fronius/README.md
index 746737d0b9..fdb56a0d36 100644
--- a/collectors/node.d.plugin/fronius/README.md
+++ b/collectors/node.d.plugin/fronius/README.md
@@ -132,4 +132,4 @@ The output of /solar_api/v1/GetPowerFlowRealtimeData.fcgi looks like this:
}
```
-[](<>)
+
diff --git a/collectors/node.d.plugin/named/README.md b/collectors/node.d.plugin/named/README.md
index acd03f6871..f1018bd380 100644
--- a/collectors/node.d.plugin/named/README.md
+++ b/collectors/node.d.plugin/named/README.md
@@ -345,4 +345,4 @@ Verify it works by running the following command (the collector is written in no
curl "http://localhost:8888/json/v1/server"
```
-[](<>)
+
diff --git a/collectors/node.d.plugin/sma_webbox/README.md b/collectors/node.d.plugin/sma_webbox/README.md
index 99e093b708..db5b97aab1 100644
--- a/collectors/node.d.plugin/sma_webbox/README.md
+++ b/collectors/node.d.plugin/sma_webbox/README.md
@@ -30,4 +30,4 @@ The module supports any number of name servers:
}
```
-[](<>)
+
diff --git a/collectors/node.d.plugin/snmp/README.md b/collectors/node.d.plugin/snmp/README.md
index df6d7eacab..2df94c7b5d 100644
--- a/collectors/node.d.plugin/snmp/README.md
+++ b/collectors/node.d.plugin/snmp/README.md
@@ -442,4 +442,4 @@ This switch has a very slow SNMP processors. To respond, it needs about 8 second
}
```
-[](<>)
+
diff --git a/collectors/node.d.plugin/stiebeleltron/README.md b/collectors/node.d.plugin/stiebeleltron/README.md
index 59bbf703c4..0982578dc1 100644
--- a/collectors/node.d.plugin/stiebeleltron/README.md
+++ b/collectors/node.d.plugin/stiebeleltron/README.md
@@ -522,4 +522,4 @@ The charts are being generated using the configuration below. So if your install
}
```
-[](<>)
+
diff --git a/collectors/perf.plugin/README.md b/collectors/perf.plugin/README.md
index ccd185cedb..a7a87aca27 100644
--- a/collectors/perf.plugin/README.md
+++ b/collectors/perf.plugin/README.md
@@ -77,4 +77,4 @@ sudo /usr/libexec/netdata/plugins.d/perf.plugin 1 all debug
You will get verbose output on what the plugin does.
-[](<>)
+
diff --git a/collectors/plugins.d/README.md b/collectors/plugins.d/README.md
index c166e11e36..033beaa4f9 100644
--- a/collectors/plugins.d/README.md
+++ b/collectors/plugins.d/README.md
@@ -481,4 +481,4 @@ There are a few rules for writing plugins properly:
4. If possible, try to autodetect if your plugin should be enabled, without any configuration.
-[](<>)
+
diff --git a/collectors/proc.plugin/README.md b/collectors/proc.plugin/README.md
index a9ce2dfa55..32e2112afd 100644
--- a/collectors/proc.plugin/README.md
+++ b/collectors/proc.plugin/README.md
@@ -604,4 +604,4 @@ As far as the message queue charts are dynamic, sane limits are applied for the
# max dimensions in memory allowed = 50
```
-[](<>)
+
diff --git a/collectors/python.d.plugin/README.md b/collectors/python.d.plugin/README.md
index 9170350fb8..16266ab7ed 100644
--- a/collectors/python.d.plugin/README.md
+++ b/collectors/python.d.plugin/README.md
@@ -270,4 +270,4 @@ At minimum, to be buildable and testable, the PR needs to include:
- Optionally, chart information in `web/gui/dashboard_info.js`. This generally involves specifying a name and icon for the section, and may include descriptions for the section or individual charts.
- Optionally, some default alarm configurations for your collector in `health/health.d/<module_name>.conf` and a line adding `<module_name>.conf` in `health/Makefile.am`.
-[](<>)
+
diff --git a/collectors/python.d.plugin/adaptec_raid/README.md b/collectors/python.d.plugin/adaptec_raid/README.md
index 4e99508b32..da5d13b16a 100644
--- a/collectors/python.d.plugin/adaptec_raid/README.md
+++ b/collectors/python.d.plugin/adaptec_raid/README.md
@@ -77,4 +77,4 @@ sudo ./edit-config python.d/adaptec_raid.conf
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/alarms/README.md b/collectors/python.d.plugin/alarms/README.md
index 3f2a8176e4..cd5e1b8178 100644
--- a/collectors/python.d.plugin/alarms/README.md
+++ b/collectors/python.d.plugin/alarms/README.md
@@ -56,5 +56,3 @@ local:
```
It will default to pulling all alarms at each time step from the Netdata rest api at `http://127.0.0.1:19999/api/v1/alarms?all`
-
-[]()
diff --git a/collectors/python.d.plugin/am2320/README.md b/collectors/python.d.plugin/am2320/README.md
index 14ddaa735d..3503d7c172 100644
--- a/collectors/python.d.plugin/am2320/README.md
+++ b/collectors/python.d.plugin/am2320/README.md
@@ -51,4 +51,3 @@ Software install:
- restart the netdata service.
- check the dashboard.
-[]()
diff --git a/collectors/python.d.plugin/anomalies/README.md b/collectors/python.d.plugin/anomalies/README.md
index 3552053eec..32e79a82fb 100644
--- a/collectors/python.d.plugin/anomalies/README.md
+++ b/collectors/python.d.plugin/anomalies/README.md
@@ -241,4 +241,3 @@ If you would like to go deeper on what exactly the anomalies collector is doing
- Good [blog post](https://www.anodot.com/blog/what-is-anomaly-detection/) from Anodot on time series anomaly detection. Anodot also have some great whitepapers in this space too that some may find useful.
- Novelty and outlier detection in the [scikit-learn documentation](https://scikit-learn.org/stable/modules/outlier_detection.html).
-[]()
diff --git a/collectors/python.d.plugin/apache/README.md b/collectors/python.d.plugin/apache/README.md
index d27525095f..c6086835fb 100644
--- a/collectors/python.d.plugin/apache/README.md
+++ b/collectors/python.d.plugin/apache/README.md
@@ -79,4 +79,4 @@ Without configuration, module attempts to connect to `http://localhost/server-st
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/beanstalk/README.md b/collectors/python.d.plugin/beanstalk/README.md
index 24315adb4f..3b632597e1 100644
--- a/collectors/python.d.plugin/beanstalk/README.md
+++ b/collectors/python.d.plugin/beanstalk/README.md
@@ -130,4 +130,4 @@ If no configuration is given, module will attempt to connect to beanstalkd on `1
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/bind_rndc/README.md b/collectors/python.d.plugin/bind_rndc/README.md
index 2832575dd9..2d747f81bd 100644
--- a/collectors/python.d.plugin/bind_rndc/README.md
+++ b/collectors/python.d.plugin/bind_rndc/README.md
@@ -76,4 +76,4 @@ If no configuration is given, module will attempt to read named.stats file at `
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/boinc/README.md b/collectors/python.d.plugin/boinc/README.md
index bd509c9004..4da2d52bfb 100644
--- a/collectors/python.d.plugin/boinc/README.md
+++ b/collectors/python.d.plugin/boinc/README.md
@@ -38,4 +38,4 @@ remote:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/ceph/README.md b/collectors/python.d.plugin/ceph/README.md
index 5d671f2aaa..b75ba6d4f6 100644
--- a/collectors/python.d.plugin/ceph/README.md
+++ b/collectors/python.d.plugin/ceph/README.md
@@ -45,4 +45,4 @@ local:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/changefinder/README.md b/collectors/python.d.plugin/changefinder/README.md
index 051639d1e5..7ec3a2539d 100644
--- a/collectors/python.d.plugin/changefinder/README.md
+++ b/collectors/python.d.plugin/changefinder/README.md
@@ -215,4 +215,3 @@ sudo su -s /bin/bash netdata
- Novelty and outlier detection in
the [scikit-learn documentation](https://scikit-learn.org/stable/modules/outlier_detection.html).
-[]()
diff --git a/collectors/python.d.plugin/chrony/README.md b/collectors/python.d.plugin/chrony/README.md
index 4681b4f6d5..3093ec3f92 100644
--- a/collectors/python.d.plugin/chrony/README.md
+++ b/collectors/python.d.plugin/chrony/README.md
@@ -58,4 +58,4 @@ local:
Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
method](/docs/configure/start-stop-restart.md) for your system, to finish configuring the `chrony` collector.
-[](<>)
+
diff --git a/collectors/python.d.plugin/couchdb/README.md b/collectors/python.d.plugin/couchdb/README.md
index 896bbdd31a..d359c8f7c8 100644
--- a/collectors/python.d.plugin/couchdb/README.md
+++ b/collectors/python.d.plugin/couchdb/README.md
@@ -50,4 +50,4 @@ local:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/dns_query_time/README.md b/collectors/python.d.plugin/dns_query_time/README.md
index e1fde74716..365e22560e 100644
--- a/collectors/python.d.plugin/dns_query_time/README.md
+++ b/collectors/python.d.plugin/dns_query_time/README.md
@@ -26,4 +26,4 @@ sudo ./edit-config python.d/dns_query_time.conf
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/dnsdist/README.md b/collectors/python.d.plugin/dnsdist/README.md
index 7c279efafa..95b2efae09 100644
--- a/collectors/python.d.plugin/dnsdist/README.md
+++ b/collectors/python.d.plugin/dnsdist/README.md
@@ -69,4 +69,4 @@ localhost:
X-API-Key: 'dnsdist-api-key'
```
-[](<>)
+
diff --git a/collectors/python.d.plugin/dockerd/README.md b/collectors/python.d.plugin/dockerd/README.md
index 178bae2cc7..6470a7c0be 100644
--- a/collectors/python.d.plugin/dockerd/README.md
+++ b/collectors/python.d.plugin/dockerd/README.md
@@ -43,4 +43,4 @@ sudo ./edit-config python.d/dockerd.conf
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/dovecot/README.md b/collectors/python.d.plugin/dovecot/README.md
index 730b64257b..e6bbf0d743 100644
--- a/collectors/python.d.plugin/dovecot/README.md
+++ b/collectors/python.d.plugin/dovecot/README.md
@@ -102,4 +102,4 @@ If no configuration is given, module will attempt to connect to dovecot using un
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/elasticsearch/README.md b/collectors/python.d.plugin/elasticsearch/README.md
index cf1834c5a8..a98eddf51a 100644
--- a/collectors/python.d.plugin/elasticsearch/README.md
+++ b/collectors/python.d.plugin/elasticsearch/README.md
@@ -91,4 +91,4 @@ If no configuration is given, module will try to connect to `http://127.0.0.1:92
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/energid/README.md b/collectors/python.d.plugin/energid/README.md
index 60c829fed9..73e39ae148 100644
--- a/collectors/python.d.plugin/energid/README.md
+++ b/collectors/python.d.plugin/energid/README.md
@@ -74,4 +74,4 @@ bitcoin:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/example/README.md b/collectors/python.d.plugin/example/README.md
index b1c21ecbcc..0b80aa9ea8 100644
--- a/collectors/python.d.plugin/example/README.md
+++ b/collectors/python.d.plugin/example/README.md
@@ -11,4 +11,4 @@ Netdata provides an [example python data collection module](https://github.com/n
If you want to write your own collector, read our [writing a new Python module](/collectors/python.d.plugin/README.md#how-to-write-a-new-module) tutorial.
-[](<>)
+
diff --git a/collectors/python.d.plugin/exim/README.md b/collectors/python.d.plugin/exim/README.md
index 240aa7bedd..92b2d7a5b1 100644
--- a/collectors/python.d.plugin/exim/README.md
+++ b/collectors/python.d.plugin/exim/README.md
@@ -38,4 +38,4 @@ Configuration is not needed.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/fail2ban/README.md b/collectors/python.d.plugin/fail2ban/README.md
index 90a59dce07..be09e1857a 100644
--- a/collectors/python.d.plugin/fail2ban/README.md
+++ b/collectors/python.d.plugin/fail2ban/README.md
@@ -79,4 +79,4 @@ at `/etc/fail2ban/jail.local`. If conf file is not found default jail is `ssh`.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/freeradius/README.md b/collectors/python.d.plugin/freeradius/README.md
index 2993c8952f..d5ec464b5f 100644
--- a/collectors/python.d.plugin/freeradius/README.md
+++ b/collectors/python.d.plugin/freeradius/README.md
@@ -87,4 +87,4 @@ and restart/reload your FREERADIUS server.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/gearman/README.md b/collectors/python.d.plugin/gearman/README.md
index b9fc914bf7..34ea584abf 100644
--- a/collectors/python.d.plugin/gearman/README.md
+++ b/collectors/python.d.plugin/gearman/README.md
@@ -48,4 +48,3 @@ localhost:
When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:4730`.
-[]()
diff --git a/collectors/python.d.plugin/go_expvar/README.md b/collectors/python.d.plugin/go_expvar/README.md
index a73610e7a1..feb150dd95 100644
--- a/collectors/python.d.plugin/go_expvar/README.md
+++ b/collectors/python.d.plugin/go_expvar/README.md
@@ -316,4 +316,4 @@ The images below show how do the final charts in Netdata look.
-[](<>)
+
diff --git a/collectors/python.d.plugin/haproxy/README.md b/collectors/python.d.plugin/haproxy/README.md
index 33d34f1ad2..4eb962e24e 100644
--- a/collectors/python.d.plugin/haproxy/README.md
+++ b/collectors/python.d.plugin/haproxy/README.md
@@ -64,4 +64,4 @@ If no configuration is given, module will fail to run.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/hddtemp/README.md b/collectors/python.d.plugin/hddtemp/README.md
index aaaf214219..d8aba62d2e 100644
--- a/collectors/python.d.plugin/hddtemp/README.md
+++ b/collectors/python.d.plugin/hddtemp/README.md
@@ -35,4 +35,4 @@ If no configuration is given, module will attempt to connect to hddtemp daemon o
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/hpssa/README.md b/collectors/python.d.plugin/hpssa/README.md
index 69c8d8a33c..c1d2182799 100644
--- a/collectors/python.d.plugin/hpssa/README.md
+++ b/collectors/python.d.plugin/hpssa/README.md
@@ -81,4 +81,3 @@ ssacli_path: /usr/sbin/ssacli
Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
method](/docs/configure/start-stop-restart.md) for your system.
-[]()
diff --git a/collectors/python.d.plugin/httpcheck/README.md b/collectors/python.d.plugin/httpcheck/README.md
index 59c60f5443..101b96e3e2 100644
--- a/collectors/python.d.plugin/httpcheck/README.md
+++ b/collectors/python.d.plugin/httpcheck/README.md
@@ -56,4 +56,4 @@ server:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/icecast/README.md b/collectors/python.d.plugin/icecast/README.md
index 90cdaa5dc1..c122f76a38 100644
--- a/collectors/python.d.plugin/icecast/README.md
+++ b/collectors/python.d.plugin/icecast/README.md
@@ -41,4 +41,4 @@ Without configuration, module attempts to connect to `http://localhost:8443/stat
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/ipfs/README.md b/collectors/python.d.plugin/ipfs/README.md
index 4d3b0ecbe1..3a7c436326 100644
--- a/collectors/python.d.plugin/ipfs/README.md
+++ b/collectors/python.d.plugin/ipfs/README.md
@@ -48,4 +48,4 @@ remote:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/isc_dhcpd/README.md b/collectors/python.d.plugin/isc_dhcpd/README.md
index 5830bd63ef..712943d99a 100644
--- a/collectors/python.d.plugin/isc_dhcpd/README.md
+++ b/collectors/python.d.plugin/isc_dhcpd/README.md
@@ -54,4 +54,4 @@ The module will not work If no configuration is given.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/litespeed/README.md b/collectors/python.d.plugin/litespeed/README.md
index 2225773b77..b58b23d7eb 100644
--- a/collectors/python.d.plugin/litespeed/README.md
+++ b/collectors/python.d.plugin/litespeed/README.md
@@ -69,4 +69,4 @@ If no configuration is given, module will use "/tmp/lshttpd/".
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/logind/README.md b/collectors/python.d.plugin/logind/README.md
index 3e2d4c1907..442d388d0f 100644
--- a/collectors/python.d.plugin/logind/README.md
+++ b/collectors/python.d.plugin/logind/README.md
@@ -83,4 +83,4 @@ sudo ./edit-config python.d/logind.conf
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/megacli/README.md b/collectors/python.d.plugin/megacli/README.md
index e411c4c112..3c99c3de83 100644
--- a/collectors/python.d.plugin/megacli/README.md
+++ b/collectors/python.d.plugin/megacli/README.md
@@ -83,4 +83,4 @@ do_battery: yes
Save the file and restart the Netdata Agent with `sudo systemctl restart netdata`, or the [appropriate
method](/docs/configure/start-stop-restart.md) for your system.
-[](<>)
+
diff --git a/collectors/python.d.plugin/memcached/README.md b/collectors/python.d.plugin/memcached/README.md
index abd93fd01e..19139ee922 100644
--- a/collectors/python.d.plugin/memcached/README.md
+++ b/collectors/python.d.plugin/memcached/README.md
@@ -96,4 +96,4 @@ If no configuration is given, module will attempt to connect to memcached instan
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/mongodb/README.md b/collectors/python.d.plugin/mongodb/README.md
index e122736ac0..b6dd9c5f4c 100644
--- a/collectors/python.d.plugin/mongodb/README.md
+++ b/collectors/python.d.plugin/mongodb/README.md
@@ -207,4 +207,4 @@ If no configuration is given, module will attempt to connect to mongodb daemon o
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/monit/README.md b/collectors/python.d.plugin/monit/README.md
index fe13896879..13960256b6 100644
--- a/collectors/python.d.plugin/monit/README.md
+++ b/collectors/python.d.plugin/monit/README.md
@@ -49,4 +49,4 @@ If no configuration is given, module will attempt to connect to monit as `http:/
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/mysql/README.md b/collectors/python.d.plugin/mysql/README.md
index 63d2c1e53c..1ba794adfe 100644
--- a/collectors/python.d.plugin/mysql/README.md
+++ b/collectors/python.d.plugin/mysql/README.md
@@ -393,4 +393,4 @@ page](https://mariadb.com/kb/en/library/user-statistics/)
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/nginx/README.md b/collectors/python.d.plugin/nginx/README.md
index b55b01e7c0..34f63cc52d 100644
--- a/collectors/python.d.plugin/nginx/README.md
+++ b/collectors/python.d.plugin/nginx/README.md
@@ -62,4 +62,4 @@ Without configuration, module attempts to connect to `http://localhost/stub_stat
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/nginx_plus/README.md b/collectors/python.d.plugin/nginx_plus/README.md
index 2580740c36..489ac9c2a3 100644
--- a/collectors/python.d.plugin/nginx_plus/README.md
+++ b/collectors/python.d.plugin/nginx_plus/README.md
@@ -162,4 +162,4 @@ Without configuration, module fail to start.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/nsd/README.md b/collectors/python.d.plugin/nsd/README.md
index 1e7b240e7b..e5183aeb7b 100644
--- a/collectors/python.d.plugin/nsd/README.md
+++ b/collectors/python.d.plugin/nsd/README.md
@@ -65,4 +65,4 @@ Configuration is not needed.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/ntpd/README.md b/collectors/python.d.plugin/ntpd/README.md
index 0b08f12b89..9832707bd0 100644
--- a/collectors/python.d.plugin/ntpd/README.md
+++ b/collectors/python.d.plugin/ntpd/README.md
@@ -87,4 +87,4 @@ If no configuration is given, module will attempt to connect to `ntpd` on `::1:1
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/nvidia_smi/README.md b/collectors/python.d.plugin/nvidia_smi/README.md
index f8ce824df9..fb613064cb 100644
--- a/collectors/python.d.plugin/nvidia_smi/README.md
+++ b/collectors/python.d.plugin/nvidia_smi/README.md
@@ -61,4 +61,4 @@ poll_seconds : 1
exclude_zero_memory_users : yes
```
-[](<>)
+
diff --git a/collectors/python.d.plugin/openldap/README.md b/collectors/python.d.plugin/openldap/README.md
index 4942d0f399..b0cd1db42d 100644
--- a/collectors/python.d.plugin/openldap/README.md
+++ b/collectors/python.d.plugin/openldap/README.md
@@ -76,4 +76,4 @@ openldap:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/oracledb/README.md b/collectors/python.d.plugin/oracledb/README.md
index d61c7d2ad0..88024f8c54 100644
--- a/collectors/python.d.plugin/oracledb/README.md
+++ b/collectors/python.d.plugin/oracledb/README.md
@@ -94,4 +94,4 @@ remote:
All parameters are required. Without them module will fail to start.
-[](<>)
+
diff --git a/collectors/python.d.plugin/ovpn_status_log/README.md b/collectors/python.d.plugin/ovpn_status_log/README.md
index 8fa8cb833f..374d1910e2 100644
--- a/collectors/python.d.plugin/ovpn_status_log/README.md
+++ b/collectors/python.d.plugin/ovpn_status_log/README.md
@@ -47,4 +47,4 @@ default
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/phpfpm/README.md b/collectors/python.d.plugin/phpfpm/README.md
index 9d0dbb5805..fe81971b23 100644
--- a/collectors/python.d.plugin/phpfpm/README.md
+++ b/collectors/python.d.plugin/phpfpm/README.md
@@ -48,4 +48,4 @@ Without configuration, module attempts to connect to `http://localhost/status`
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/portcheck/README.md b/collectors/python.d.plugin/portcheck/README.md
index 35521b2adf..845fa5b90e 100644
--- a/collectors/python.d.plugin/portcheck/README.md
+++ b/collectors/python.d.plugin/portcheck/README.md
@@ -49,4 +49,4 @@ server:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/postfix/README.md b/collectors/python.d.plugin/postfix/README.md
index 53073ea8de..ac16962a5b 100644
--- a/collectors/python.d.plugin/postfix/README.md
+++ b/collectors/python.d.plugin/postfix/README.md
@@ -24,4 +24,4 @@ Configuration is not needed.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/postgres/README.md b/collectors/python.d.plugin/postgres/README.md
index 0515ec57c0..224b76ff52 100644
--- a/collectors/python.d.plugin/postgres/README.md
+++ b/collectors/python.d.plugin/postgres/README.md
@@ -115,4 +115,4 @@ tcp:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/powerdns/README.md b/collectors/python.d.plugin/powerdns/README.md
index 610a665dee..02449e68e8 100644
--- a/collectors/python.d.plugin/powerdns/README.md
+++ b/collectors/python.d.plugin/powerdns/README.md
@@ -101,4 +101,4 @@ local:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/proxysql/README.md b/collectors/python.d.plugin/proxysql/README.md
index f1b369a446..8c6a394f12 100644
--- a/collectors/python.d.plugin/proxysql/README.md
+++ b/collectors/python.d.plugin/proxysql/README.md
@@ -103,4 +103,4 @@ If no configuration is given, module will fail to run.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/puppet/README.md b/collectors/python.d.plugin/puppet/README.md
index 9b7c0a2c38..1b06d181b1 100644
--- a/collectors/python.d.plugin/puppet/README.md
+++ b/collectors/python.d.plugin/puppet/README.md
@@ -64,4 +64,4 @@ When no configuration is given, module uses `https://fqdn.example.com:8140`.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/rabbitmq/README.md b/collectors/python.d.plugin/rabbitmq/README.md
index 2130a7b3a4..607e32c7f1 100644
--- a/collectors/python.d.plugin/rabbitmq/README.md
+++ b/collectors/python.d.plugin/rabbitmq/README.md
@@ -113,4 +113,4 @@ socket:
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/redis/README.md b/collectors/python.d.plugin/redis/README.md
index 9fab56c333..319827100b 100644
--- a/collectors/python.d.plugin/redis/README.md
+++ b/collectors/python.d.plugin/redis/README.md
@@ -61,4 +61,4 @@ When no configuration file is found, module tries to connect to TCP/IP socket: `
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/rethinkdbs/README.md b/collectors/python.d.plugin/rethinkdbs/README.md
index 85cebd96a5..d3fa3553ae 100644
--- a/collectors/python.d.plugin/rethinkdbs/README.md
+++ b/collectors/python.d.plugin/rethinkdbs/README.md
@@ -50,4 +50,4 @@ When no configuration file is found, module tries to connect to `127.0.0.1:28015
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/retroshare/README.md b/collectors/python.d.plugin/retroshare/README.md
index d8bd3a9143..297df9fca7 100644
--- a/collectors/python.d.plugin/retroshare/README.md
+++ b/collectors/python.d.plugin/retroshare/README.md
@@ -44,4 +44,4 @@ remote:
```
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/riakkv/README.md b/collectors/python.d.plugin/riakkv/README.md
index d0ea9a1379..fe62c67189 100644
--- a/collectors/python.d.plugin/riakkv/README.md
+++ b/collectors/python.d.plugin/riakkv/README.md
@@ -124,5 +124,3 @@ With no explicit configuration given, the module will attempt to connect to
The default update frequency for the plugin is set to 2 seconds as Riak
internally updates the metrics every second. If we were to update the metrics
every second, the resulting graph would contain odd jitter.
-
-[]()
diff --git a/collectors/python.d.plugin/samba/README.md b/collectors/python.d.plugin/samba/README.md
index 04cb7dcf73..767df12de9 100644
--- a/collectors/python.d.plugin/samba/README.md
+++ b/collectors/python.d.plugin/samba/README.md
@@ -118,4 +118,4 @@ sudo ./edit-config python.d/samba.conf
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/sensors/README.md b/collectors/python.d.plugin/sensors/README.md
index 5d29348441..1495893176 100644
--- a/collectors/python.d.plugin/sensors/README.md
+++ b/collectors/python.d.plugin/sensors/README.md
@@ -28,4 +28,4 @@ Please join this discussion for help.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/smartd_log/README.md b/collectors/python.d.plugin/smartd_log/README.md
index a1b41f4089..eef34ce437 100644
--- a/collectors/python.d.plugin/smartd_log/README.md
+++ b/collectors/python.d.plugin/smartd_log/README.md
@@ -122,4 +122,4 @@ If no configuration is given, module will attempt to read log files in `/var/log
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/spigotmc/README.md b/collectors/python.d.plugin/spigotmc/README.md
index 9b297f6399..06483188b8 100644
--- a/collectors/python.d.plugin/spigotmc/README.md
+++ b/collectors/python.d.plugin/spigotmc/README.md
@@ -35,4 +35,4 @@ By default, a connection to port 25575 on the local system is attempted with an
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/springboot/README.md b/collectors/python.d.plugin/springboot/README.md
index f38e8bf05a..cdbc9a9003 100644
--- a/collectors/python.d.plugin/springboot/README.md
+++ b/collectors/python.d.plugin/springboot/README.md
@@ -142,4 +142,4 @@ Please check
[springboot.conf](https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/springboot/springboot.conf)
for more examples.
-[](<>)
+
diff --git a/collectors/python.d.plugin/squid/README.md b/collectors/python.d.plugin/squid/README.md
index e3ed4e0dfa..c29b69a198 100644
--- a/collectors/python.d.plugin/squid/README.md
+++ b/collectors/python.d.plugin/squid/README.md
@@ -55,4 +55,4 @@ Without any configuration module will try to autodetect where squid presents its
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/tomcat/README.md b/collectors/python.d.plugin/tomcat/README.md
index f9f2ffe312..b7525b88ac 100644
--- a/collectors/python.d.plugin/tomcat/README.md
+++ b/collectors/python.d.plugin/tomcat/README.md
@@ -50,4 +50,4 @@ So it will probably fail.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/tor/README.md b/collectors/python.d.plugin/tor/README.md
index 192a86a37a..3e7b8997ac 100644
--- a/collectors/python.d.plugin/tor/README.md
+++ b/collectors/python.d.plugin/tor/README.md
@@ -61,4 +61,4 @@ Without configuration, module attempts to connect to `127.0.0.1:9051`.
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/traefik/README.md b/collectors/python.d.plugin/traefik/README.md
index 2a1dd77aab..251cdf2e49 100644
--- a/collectors/python.d.plugin/traefik/README.md
+++ b/collectors/python.d.plugin/traefik/README.md
@@ -71,4 +71,4 @@ Without configuration, module attempts to connect to `http://localhost:8080/heal
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/uwsgi/README.md b/collectors/python.d.plugin/uwsgi/README.md
index f564821a19..58db1a41a2 100644
--- a/collectors/python.d.plugin/uwsgi/README.md
+++ b/collectors/python.d.plugin/uwsgi/README.md
@@ -49,4 +49,4 @@ localhost:
When no configuration file is found, module tries to connect to TCP/IP socket: `localhost:1717`.
-[](<>)
+
diff --git a/collectors/python.d.plugin/varnish/README.md b/collectors/python.d.plugin/varnish/README.md
index cb29738f55..018905f06e 100644
--- a/collectors/python.d.plugin/varnish/README.md
+++ b/collectors/python.d.plugin/varnish/README.md
@@ -62,4 +62,4 @@ The name of the `varnishd` instance to get logs from. If not specified, the host
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/w1sensor/README.md b/collectors/python.d.plugin/w1sensor/README.md
index 31facef77b..b6d2b2d630 100644
--- a/collectors/python.d.plugin/w1sensor/README.md
+++ b/collectors/python.d.plugin/w1sensor/README.md
@@ -25,4 +25,4 @@ sudo ./edit-config python.d/w1sensor.conf
---
-[](<>)
+
diff --git a/collectors/python.d.plugin/web_log/README.md b/collectors/python.d.plugin/web_log/README.md
index 8bbb9a83a3..552d56e90f 100644
--- a/collectors/python.d.plugin/web_log/README.md
+++ b/collectors/python.d.plugin/web_log/README.md
@@ -216,4 +216,4 @@ The column `minimum requests` state the minimum number of requests required for
Netdata alarms are user-configurable. Sample config files can be found under directory `health/health.d` of the [Netdata GitHub repository](https://github.com/netdata/netdata/).
-[](<>)
+
diff --git a/collectors/slabinfo.plugin/README.md b/collectors/slabinfo.plugin/README.md
index 21d83c999b..2f49046609 100644
--- a/collectors/slabinfo.plugin/README.md
+++ b/collectors/slabinfo.plugin/README.md
@@ -26,4 +26,4 @@ In the following screenshot, you can clearly see a `find` done on a ext4 filesys
-[](<>)
+
diff --git a/collectors/statsd.plugin/README.md b/collectors/statsd.plugin/README.md
index 1d1c8ab70d..4acd24bb56 100644
--- a/collectors/statsd.plugin/README.md
+++ b/collectors/statsd.plugin/README.md
@@ -611,4 +611,4 @@ The function is smart enough to call `nc` just once and pass all the metrics to
If you have gotten thus far, make sure to check out our [community forums](https://community.netdata.cloud) to share your experience using Netdata with StatsD.
-[](<>)
+
diff --git a/collectors/tc.plugin/README.md b/collectors/tc.plugin/README.md
index 480076087e..32c20f4904 100644
--- a/collectors/tc.plugin/README.md
+++ b/collectors/tc.plugin/README.md
@@ -202,4 +202,4 @@ Finally, create `/etc/netdata/tc-qos-helper.conf` with this content:
Please note, that by default Netdata will enable monitoring metrics only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Set `yes` for a chart instead of `auto` to enable it permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
-[](<>)
+
diff --git a/collectors/timex.plugin/README.md b/collectors/timex.plugin/README.md
index 79947441f9..e5c6a1dede 100644
--- a/collectors/timex.plugin/README.md
+++ b/collectors/timex.plugin/README.md
@@ -26,4 +26,4 @@ Scroll down to the `[plugin:timex]` section to find the available options:
# time offset = yes
```
-[](<>)
+
diff --git a/collectors/xenstat.plugin/README.md b/collectors/xenstat.plugin/README.md
index 61be271d99..8cbe086fc1 100644
--- a/collectors/xenstat.plugin/README.md
+++ b/collectors/xenstat.plugin/README.md
@@ -50,4 +50,4 @@ sudo /usr/libexec/netdata/plugins.d/xenstat.plugin 1 debug
You will get verbose output on what the plugin does.
-[](<>)
+
diff --git a/contrib/README.md b/contrib/README.md
index e253efa993..36abd3b102 100644
--- a/contrib/README.md
+++ b/contrib/README.md
@@ -58,4 +58,4 @@ source is to remove the current package from your system, then
install the new package. Upgrading on wheezy is known to not
work cleanly; Jessie may behave as expected.
-[](<>)
+
diff --git a/contrib/sles11/README.md b/contrib/sles11/README.md
index 4cdf7e9f91..30d0261312 100644
--- a/contrib/sles11/README.md
+++ b/contrib/sles11/README.md
@@ -14,4 +14,4 @@ changes and additions for sles 11 backport, namely:
- crude hack of notification script to work with bash 3 (email and syslog only, one destination,
see comments at the top)
-[](<>)
+
diff --git a/daemon/README.md b/daemon/README.md
index 1ea865f899..1557ca0c87 100644
--- a/daemon/README.md
+++ b/daemon/README.md
@@ -551,4 +551,4 @@ valgrind $(which netdata) -D
Netdata will start and it will be a lot slower. Now reproduce the crash and `valgrind` will dump on your console the
stack trace. Open a new github issue and post the output.
-[](<>)
+
diff --git a/daemon/config/README.md b/daemon/config/README.md
index cc755af78a..4d9c3d8bbb 100644
--- a/daemon/config/README.md
+++ b/daemon/config/README.md
@@ -227,4 +227,4 @@ multiplying the value of `out` by -1, Netdata creates the negative values seen i
-[](<>)
+
diff --git a/database/README.md b/database/README.md
index 9fef705803..a8bb21e4ed 100644
--- a/database/README.md
+++ b/database/README.md
@@ -212,4 +212,4 @@ Netdata will create charts for kernel memory de-duplication performance, like th
-[](<>)
+
diff --git a/database/engine/README.md b/database/engine/README.md
index a782716f0c..7defcce9de 100644
--- a/database/engine/README.md
+++ b/database/engine/README.md
@@ -256,4 +256,4 @@ and generate a read load of 1.7M/sec, whereas in the CPU-bound scenario the read
Consequently, there is a significant degree of interference by the reader threads, that slow down the writer threads.
This is also possible because the interference effects are greater than the SSD impact on data generation throughput.
-[](<>)
+
diff --git a/diagrams/data_structures/README.md b/diagrams/data_structures/README.md
index 27705c5489..12ea1afa28 100644
--- a/diagrams/data_structures/README.md
+++ b/diagrams/data_structures/README.md
@@ -15,4 +15,4 @@ These are the main internal data structures of `netdata`. Created with `draw.io`
-[](<>)
+
diff --git a/docs/Add-more-charts-to-netdata.md b/docs/Add-more-charts-to-netdata.md
index 44aa1abad3..6090644e38 100644
--- a/docs/Add-more-charts-to-netdata.md
+++ b/docs/Add-more-charts-to-netdata.md
@@ -11,5 +11,3 @@ This file has been deprecated. Please see our [collectors docs](/collectors/READ
See the [list of supported collectors](/collectors/COLLECTORS.md) to see all the sources Netdata can collect metrics
from.
-
-[]()
diff --git a/docs/Demo-Sites.md b/docs/Demo-Sites.md
index 5c0369c150..e6e8eb3dca 100644
--- a/docs/Demo-Sites.md
+++ b/docs/Demo-Sites.md
@@ -22,4 +22,4 @@ You can also view live demos of Netdata at **[https://www.netdata.cloud](https:/
Netdata dashboards are mobile- and touch-friendly.
-[](<>)
+
diff --git a/docs/Donations-netdata-has-received.md b/docs/Donations-netdata-has-received.md
index df6c040bab..a8623c5dbf 100644
--- a/docs/Donations-netdata-has-received.md
+++ b/docs/Donations-netdata-has-received.md
@@ -26,4 +26,4 @@ Thank you!
Please contact me at costa@tsaousis.gr.
-[](<>)
+
diff --git a/docs/README.md b/docs/README.md
index 47950f3889..e3b9156176 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -14,4 +14,4 @@ perfect.
Now get out there and build an exceptional infrastructure.
-[](<>)
+
diff --git a/docs/Running-behind-apache.md b/docs/Running-behind-apache.md
index de95f55ead..989c51fc7b 100644
--- a/docs/Running-behind-apache.md
+++ b/docs/Running-behind-apache.md
@@ -368,4 +368,4 @@ Make sure the requests reach Netdata, by examining `/var/log/netdata/access.log`
1. if the requests do not reach Netdata, your apache does not forward them.
2. if the requests reach Netdata but the URLs are wrong, you have not re-written them properly.
-[](<>)
+
diff --git a/docs/Running-behind-caddy.md b/docs/Running-behind-caddy.md
index a20fd0535b..0282d0750f 100644
--- a/docs/Running-behind-caddy.md
+++ b/docs/Running-behind-caddy.md
@@ -31,4 +31,4 @@ You would also need to instruct Netdata to listen only to `127.0.0.1` or `::1`.
To limit access to Netdata only from localhost, set `bind socket to IP = 127.0.0.1` or `bind socket to IP = ::1` in `/etc/netdata/netdata.conf`.
-[](<>)
+
diff --git a/docs/Running-behind-haproxy.md b/docs/Running-behind-haproxy.md
index d4b09f85c7..74ca0a7889 100644
--- a/docs/Running-behind-haproxy.md
+++ b/docs/Running-behind-haproxy.md
@@ -290,4 +290,4 @@ backend netdata_backend
http-request set-header Connection "keep-alive"
```
-[](<>)
+
diff --git a/docs/Running-behind-lighttpd.md b/docs/Running-behind-lighttpd.md
index 1e86f334f9..2623560e15 100644
--- a/docs/Running-behind-lighttpd.md
+++ b/docs/Running-behind-lighttpd.md
@@ -68,4 +68,4 @@ You would also need to instruct Netdata to listen only to `127.0.0.1` or `::1`.
To limit access to Netdata only from localhost, set `bind socket to IP = 127.0.0.1` or `bind socket to IP = ::1` in `/etc/netdata/netdata.conf`.
-[](<>)
+
diff --git a/docs/Running-behind-nginx.md b/docs/Running-behind-nginx.md
index 83720039e5..0cb16309a1 100644
--- a/docs/Running-behind-nginx.md
+++ b/docs/Running-behind-nginx.md
@@ -267,4 +267,4 @@ If you get an 502 Bad Gateway error you might check your Nginx error log:
If you see something like the above, chances are high that SELinux prevents nginx from connecting to the backend server. To fix that, just use this policy: `setsebool -P httpd_can_network_connect true`.
-[](<>)
+
diff --git a/docs/a-github-star-is-important.md b/docs/a-github-star-is-important.md
index d309d3928a..22659ea6f5 100644
--- a/docs/a-github-star-is-important.md
+++ b/docs/a-github-star-is-important.md
@@ -21,4 +21,4 @@ Thank you!
Costa Tsaousis
-[](<>)
+
diff --git a/docs/agent-cloud.md b/docs/agent-cloud.md
index fcec10af89..ed54325c35 100644
--- a/docs/agent-cloud.md
+++ b/docs/agent-cloud.md
@@ -75,5 +75,3 @@ about how you might want to use or configure Cloud, we recommend the following:
onboarding and connect your first nodes.
- Better understand how agents connect securely to the Cloud with [connect agent to Cloud](/claim/README.md) and [Agent-Cloud
link](/aclk/README.md) documentation.
-
-[]()
diff --git a/docs/anonymous-statistics.md b/docs/anonymous-statistics.md
index c00e4b8205..5351ec8561 100644
--- a/docs/anonymous-statistics.md
+++ b/docs/anonymous-statistics.md
@@ -106,4 +106,3 @@ Prior to v1.29.4 we used Google Analytics to capture this information. This led
While we migrate fully away from Google Analytics to PostHog there maybe be a small period of time where we run both in parallel before we remove all Google Analytics related code. This is to ensure we can fully test and validate the Netdata PostHog implementation before fully defaulting to it.
-[]()
diff --git a/docs/collect/application-metrics.md b/docs/collect/application-metrics.md
index 4fb9ed6abb..5af58b1057 100644
--- a/docs/collect/application-metrics.md
+++ b/docs/collect/application-metrics.md
@@ -77,4 +77,4 @@ Collecting all the available metrics on your nodes, and across your entire infra
puzzle. Next, learn more about Netdata's famous real-time visualizations by [seeing an overview of your
infrastructure](/docs/visualize/overview-infrastructure.md) using Netdata Cloud.
-[](<>)
+
diff --git a/docs/collect/container-metrics.md b/docs/collect/container-metrics.md
index b5bb9da01c..5d145362ef 100644
--- a/docs/collect/container-metrics.md
+++ b/docs/collect/container-metrics.md
@@ -96,4 +96,4 @@ brokers, and more. See more in the [application metrics doc](/docs/collect/appli
If you already have all the information you need about collecting metrics, move into Netdata's meaningful visualizations
with [seeing an overview of your infrastructure](/docs/visualize/overview-infrastructure.md) using Netdata Cloud.
-[](<>)
+
diff --git a/docs/collect/enable-configure.md b/docs/collect/enable-configure.md
index 584d237157..19e680c21b 100644
--- a/docs/collect/enable-configure.md
+++ b/docs/collect/enable-configure.md
@@ -65,4 +65,4 @@ Netdata's visualization features. [See an overview of your infrastructure](/docs
using Netdata Cloud, or learn how to [interact with dashboards and
charts](/docs/visualize/interact-dashboards-charts.md).
-[](<>)
+
diff --git a/docs/collect/how-collectors-work.md b/docs/collect/how-collectors-work.md
index b4a6c8796a..983de35a81 100644
--- a/docs/collect/how-collectors-work.md
+++ b/docs/collect/how-collectors-work.md
@@ -77,4 +77,4 @@ your infrastructure.
See our [collectors reference](/collectors/REFERENCE.md) for detailed information on Netdata's collector architecture,
troubleshooting a collector, developing a custom collector, and more.
-[](<>)
+
diff --git a/docs/collect/system-metrics.md b/docs/collect/system-metrics.md
index 14e2cc2aa3..6233028946 100644
--- a/docs/collect/system-metrics.md
+++ b/docs/collect/system-metrics.md
@@ -63,4 +63,4 @@ should investigate Netdata's container compatibility if you use them heavily in
If you don't use containers, skip ahead to collecting [application metrics](/docs/collect/application-metrics.md) with
Netdata.
-[](<>)
+
diff --git a/docs/contributing/contributing-documentation.md b/docs/contributing/contributing-documentation.md
index 76fc609d5f..68b861d406 100644
--- a/docs/contributing/contributing-documentation.md
+++ b/docs/contributing/contributing-documentation.md
@@ -106,4 +106,4 @@ specific sections and ask for additional information or other fixes.
After merging your PR, the Netdata team rebuilds the [documentation site](https://learn.netdata.cloud) to publish the
changed documentation.
-[](<>)
+
diff --git a/docs/contributing/style-guide.md b/docs/contributing/style-guide.md
index 025b45f64f..2af58d54ae 100644
--- a/docs/contributing/style-guide.md
+++ b/docs/contributing/style-guide.md
@@ -489,4 +489,4 @@ The following tables describe the standard spelling, capitalization, and usage o
| **preconfigured** | The concept that many of Netdata's features come with sane defaults that users don't need to configure to find [immediate value](/docs/overview/why-netdata.md#simple-to-deploy). |
| **real time**/**real-time** | Use _real time_ as a noun phrase, most often with _in_: _Netdata collects metrics in real time_. Use _real-time_ as an adjective: _Netdata collects real-time metrics from hundreds of supported applications and services. |
-[](<>)
+
diff --git a/docs/export/enable-connector.md b/docs/export/enable-connector.md
index 1ddecfd2cd..a914a114ae 100644
--- a/docs/export/enable-connector.md
+++ b/docs/export/enable-connector.md
@@ -92,4 +92,4 @@ labels](/docs/guides/using-host-labels.md) on exported metrics.
- [OpenTSDB connector](/exporting/opentsdb/README.md)
- [Graphite connector](/exporting/graphite/README.md)
-[](<>)
+
diff --git a/docs/export/external-databases.md b/docs/export/external-databases.md
index 6f7f488b63..00d849f402 100644
--- a/docs/export/external-databases.md
+++ b/docs/export/external-databases.md
@@ -87,4 +87,4 @@ Graphite_](/docs/guides/export/export-netdata-metrics-graphite.md).
- [Exporting engine reference](/exporting/README.md)
- [Backends reference (deprecated)](/backends/README.md)
-[](<>)
+
diff --git a/docs/guides/collect-apache-nginx-web-logs.md b/docs/guides/collect-apache-nginx-web-logs.md
index 1ffa9d3b6b..0298e1d433 100644
--- a/docs/guides/collect-apache-nginx-web-logs.md
+++ b/docs/guides/collect-apache-nginx-web-logs.md
@@ -159,4 +159,4 @@ into powerful real-time tools for keeping your servers happy.
Don't forget to give GitHub user [Wing924](https://github.com/Wing924) a big 👍 for his hard work in starting up the Go
refactoring effort.
-[](<>)
+
diff --git a/docs/guides/collect-unbound-metrics.md b/docs/guides/collect-unbound-metrics.md
index 5709c872cc..8edcab102b 100644
--- a/docs/guides/collect-unbound-metrics.md
+++ b/docs/guides/collect-unbound-metrics.md
@@ -137,4 +137,4 @@ for improvement or refinement based on real-world use cases. Feel free to [file
issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) with your
thoughts.
-[](<>)
+
diff --git a/docs/guides/deploy/ansible.md b/docs/guides/deploy/ansible.md
index f7bf514e2a..7e5532b62b 100644
--- a/docs/guides/deploy/ansible.md
+++ b/docs/guides/deploy/ansible.md
@@ -171,4 +171,4 @@ provisioning/infrastructure as code software, such as Chef or Puppet, in our [co
repo](https://github.com/netdata/community). Anyone is able to fork the repo and submit a PR, either to improve this
playbook, extend it, or create an entirely new experience for deploying Netdata across entire infrastructure.
-[](<>)
+
diff --git a/docs/guides/export/export-netdata-metrics-graphite.md b/docs/guides/export/export-netdata-metrics-graphite.md
index 37d2fdb50f..007c30f8b2 100644
--- a/docs/guides/export/export-netdata-metrics-graphite.md
+++ b/docs/guides/export/export-netdata-metrics-graphite.md
@@ -180,4 +180,4 @@ often.
For full details about each configuration option and what it does, see the [exporting reference
guide](/exporting/README.md).
-[](<>)
+
diff --git a/docs/guides/longer-metrics-storage.md b/docs/guides/longer-metrics-storage.md
index b682125f5c..85edb55ee2 100644
--- a/docs/guides/longer-metrics-storage.md
+++ b/docs/guides/longer-metrics-storage.md
@@ -157,4 +157,4 @@ charts](/web/README.md#using-charts).
And if you'd now like to reduce Netdata's resource usage, view our [performance
guide](/docs/guides/configure/performance.md) for our best practices on optimization.
-[](<>)
+
diff --git a/docs/guides/monitor-cockroachdb.md b/docs/guides/monitor-cockroachdb.md
index 3272378367..46dd2535e2 100644
--- a/docs/guides/monitor-cockroachdb.md
+++ b/docs/guides/monitor-cockroachdb.md
@@ -133,4 +133,4 @@ Also, be sure to check out these useful resources:
- [Monitor CockroachDB with
Prometheus](https://www.cockroachlabs.com/docs/stable/monitor-cockroachdb-with-prometheus.html)
-[](<>)
+
diff --git a/docs/guides/monitor-hadoop-cluster.md b/docs/guides/monitor-hadoop-cluster.md
index 69f2bc8e31..62403f8976 100644
--- a/docs/guides/monitor-hadoop-cluster.md
+++ b/docs/guides/monitor-hadoop-cluster.md
@@ -200,4 +200,4 @@ issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cnee
file](https://github.com/netdata/go.d.plugin/blob/master/config/go.d/zookeeper.conf) to understand how to configure
global options or per-job options, timeouts, TLS certificates, and more.
-[](<>)
+
diff --git a/docs/guides/monitor/dimension-templates.md b/docs/guides/monitor/dimension-templates.md
index 7cbe7959cb..539127366c 100644
--- a/docs/guides/monitor/dimension-templates.md
+++ b/docs/guides/monitor/dimension-templates.md
@@ -173,4 +173,4 @@ Or, at the very least, simplify your configuration files.
For information about other advanced features in Netdata's health monitoring toolkit, check out our [health
documentation](/health/README.md). And if you have some cool alarms you built using dimension templates,
-[](<>)
+
diff --git a/docs/guides/monitor/kubernetes-k8s-netdata.md b/docs/guides/monitor/kubernetes-k8s-netdata.md
index bd893ede6d..5cfefe8923 100644
--- a/docs/guides/monitor/kubernetes-k8s-netdata.md
+++ b/docs/guides/monitor/kubernetes-k8s-netdata.md
@@ -251,4 +251,4 @@ clusters of all sizes.
collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/k8s_kubeproxy)
- [Netdata Agent · `cgroups.plugin`](/collectors/cgroups.plugin/README.md)
-[](<>)
+
diff --git a/docs/guides/monitor/lamp-stack.md b/docs/guides/monitor/lamp-stack.md
index 4fe0defb01..595d64400f 100644
--- a/docs/guides/monitor/lamp-stack.md
+++ b/docs/guides/monitor/lamp-stack.md
@@ -244,4 +244,3 @@ source of issues faster with [Metric Correlations](https://learn.netdata.cloud/d
- [Netdata Agent · MySQL data collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql)
- [Netdata Agent · PHP-FPM data collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/phpfpm)
-[](<>)
\ No newline at end of file
diff --git a/docs/guides/monitor/pi-hole-raspberry-pi.md b/docs/guides/monitor/pi-hole-raspberry-pi.md
index 9dc60d3af4..721ba2a8ff 100644
--- a/docs/guides/monitor/pi-hole-raspberry-pi.md
+++ b/docs/guides/monitor/pi-hole-raspberry-pi.md
@@ -159,4 +159,4 @@ troubleshooting the health of your systems and services.
If you have any questions about using Netdata to monitor your Raspberry Pi, Pi-hole, or any other applications, head on
over to our [community forum](https://community.netdata.cloud/).
-[](<>)
+
diff --git a/docs/guides/monitor/process.md b/docs/guides/monitor/process.md
index d322035b12..2f46d7abc4 100644
--- a/docs/guides/monitor/process.md
+++ b/docs/guides/monitor/process.md
@@ -298,4 +298,4 @@ frameworks.
- [Netdata Agent · Dashboards](/web/README.md#dimensions)
- [Netdata Agent · MySQL collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql)
-[](<>)
+
diff --git a/docs/guides/monitor/raspberry-pi-anomaly-detection.md b/docs/guides/monitor/raspberry-pi-anomaly-detection.md
index 029dfcbc71..73f57cd04c 100644
--- a/docs/guides/monitor/raspberry-pi-anomaly-detection.md
+++ b/docs/guides/monitor/raspberry-pi-anomaly-detection.md
@@ -122,4 +122,4 @@ feedback on our [community forum](https://community.netdata.cloud/t/anomalies-co
- [Netdata Agent · Get Netdata](/docs/get-started.mdx)
- [Netdata Agent · Anomalies collector](/collectors/python.d.plugin/anomalies/README.md)
-[](<>)
+
diff --git a/docs/guides/monitor/statsd.md b/docs/guides/monitor/statsd.md
index 214b488f20..3e2f0f85c9 100644
--- a/docs/guides/monitor/statsd.md
+++ b/docs/guides/monitor/statsd.md
@@ -295,4 +295,4 @@ Netdata allows you easily visualize any StatsD metric without any configuration,
- [Netdata Agent · StatsD](/collectors/statsd.plugin/README.md)
-[](<>)
+
diff --git a/docs/guides/monitor/stop-notifications-alarms.md b/docs/guides/monitor/stop-notifications-alarms.md
index ad054d5c79..a8b73a86ac 100644
--- a/docs/guides/monitor/stop-notifications-alarms.md
+++ b/docs/guides/monitor/stop-notifications-alarms.md
@@ -89,4 +89,4 @@ You can also use Netdata's [Health Management API](/web/api/health/README.md#hea
checks and notifications while Netdata runs. With this API, you can disable health checks during a maintenance window or
backup process, for example.
-[](<>)
+
diff --git a/docs/guides/monitor/visualize-monitor-anomalies.md b/docs/guides/monitor/visualize-monitor-anomalies.md
index 9eace52325..1f8c2c8f8d 100644
--- a/docs/guides/monitor/visualize-monitor-anomalies.md
+++ b/docs/guides/monitor/visualize-monitor-anomalies.md
@@ -139,4 +139,4 @@ that works well for monitoring some other popular application, like MySQL, Postg
- [Netdata Agent · Anomalies collector](/collectors/python.d.plugin/anomalies/README.md)
- [Netdata Cloud · Build new dashboards](https://learn.netdata.cloud/docs/cloud/visualize/dashboards)
-[](<>)
+
diff --git a/docs/guides/python-collector.md b/docs/guides/python-collector.md
index c3784194ab..f93c724bf0 100644
--- a/docs/guides/python-collector.md
+++ b/docs/guides/python-collector.md
@@ -483,4 +483,4 @@ Now we you ready to start developing our Netdata python Collector and share it w
production-grade collectors.
- Celebrate! You have contributed to an open-source project with hundreds of thousands of users!
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-00.md b/docs/guides/step-by-step/step-00.md
index 3cb85ceda4..ab68fe741c 100644
--- a/docs/guides/step-by-step/step-00.md
+++ b/docs/guides/step-by-step/step-00.md
@@ -117,4 +117,4 @@ MongoDB, TimescaleDB, and others.
Run Netdata behind an Nginx proxy to improve performance, and enable TLS/HTTPS for better security.
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-01.md b/docs/guides/step-by-step/step-01.md
index cdcfcd7a2d..f5430e3a67 100644
--- a/docs/guides/step-by-step/step-01.md
+++ b/docs/guides/step-by-step/step-01.md
@@ -153,4 +153,4 @@ get right into that dashboard you've heard so much about.
[Next: Get to know Netdata's dashboard →](step-02.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-02.md b/docs/guides/step-by-step/step-02.md
index c87712c9a4..4b802ffd67 100644
--- a/docs/guides/step-by-step/step-02.md
+++ b/docs/guides/step-by-step/step-02.md
@@ -205,4 +205,4 @@ Next, you'll learn how to monitor multiple nodes through the dashboard.
[Next: Monitor more than one system with Netdata →](step-03.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-03.md b/docs/guides/step-by-step/step-03.md
index a2f37beebf..c1d283ba01 100644
--- a/docs/guides/step-by-step/step-03.md
+++ b/docs/guides/step-by-step/step-03.md
@@ -88,4 +88,4 @@ customize your Netdata experience to your exact infrastructure and the informati
[Next: The basics of configuring Netdata →](step-04.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-04.md b/docs/guides/step-by-step/step-04.md
index 41431b1d03..37b4245bef 100644
--- a/docs/guides/step-by-step/step-04.md
+++ b/docs/guides/step-by-step/step-04.md
@@ -141,4 +141,4 @@ choosing.
[Next: Health monitoring alarms and notifications →](step-05.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-05.md b/docs/guides/step-by-step/step-05.md
index c0b6226182..3cd8c5dbc8 100644
--- a/docs/guides/step-by-step/step-05.md
+++ b/docs/guides/step-by-step/step-05.md
@@ -347,4 +347,4 @@ from hundreds of services with almost no configuration on your part. Onward!
[Next: Collect metrics from more services and apps →](step-06.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-06.md b/docs/guides/step-by-step/step-06.md
index 618886076b..89a8cb7329 100644
--- a/docs/guides/step-by-step/step-06.md
+++ b/docs/guides/step-by-step/step-06.md
@@ -119,4 +119,4 @@ the dashboard to learn more about some of its more advanced features.
[Next: Netdata's dashboard in depth →](step-07.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-07.md b/docs/guides/step-by-step/step-07.md
index f2f665575c..17a02cd465 100644
--- a/docs/guides/step-by-step/step-07.md
+++ b/docs/guides/step-by-step/step-07.md
@@ -111,4 +111,4 @@ Next, you'll learn how to build your first custom dashboard!
[Next: Build your first custom dashboard →](step-08.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-08.md b/docs/guides/step-by-step/step-08.md
index 76a1b07750..e9c0f902c4 100644
--- a/docs/guides/step-by-step/step-08.md
+++ b/docs/guides/step-by-step/step-08.md
@@ -392,4 +392,4 @@ Next, you'll learn how to store long-term historical metrics in Netdata!
[Next: Long-term metrics storage →](/docs/guides/step-by-step/step-09.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-09.md b/docs/guides/step-by-step/step-09.md
index 6e29d84c52..6333dfe694 100644
--- a/docs/guides/step-by-step/step-09.md
+++ b/docs/guides/step-by-step/step-09.md
@@ -159,4 +159,4 @@ our Netdata dashboard.
[Next: Set up a proxy →](/docs/guides/step-by-step/step-10.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-10.md b/docs/guides/step-by-step/step-10.md
index d1c065c513..456b598555 100644
--- a/docs/guides/step-by-step/step-10.md
+++ b/docs/guides/step-by-step/step-10.md
@@ -229,4 +229,4 @@ For some celebratory emoji and a clap on the back, head on over to our final ste
[Next: The end. →](step-99.md)
-[](<>)
+
diff --git a/docs/guides/step-by-step/step-99.md b/docs/guides/step-by-step/step-99.md
index 0d5b2c1afd..58902fee73 100644
--- a/docs/guides/step-by-step/step-99.md
+++ b/docs/guides/step-by-step/step-99.md
@@ -48,4 +48,4 @@ If that feels like too much possibility to you, why not one of these options:
We can't wait to see what you monitor next! Bon voyage! ⛵
-[](<>)
+
diff --git a/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md b/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
index 688e7d296b..3ebca54253 100644
--- a/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+++ b/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
@@ -267,4 +267,4 @@ we'd love to hear them: [info@netdata.cloud](mailto:info@netdata.cloud).
Happy troubleshooting!
-[](<>)
+
diff --git a/docs/guides/using-host-labels.md b/docs/guides/using-host-labels.md
index d3a51bea6b..edb85ecfa9 100644
--- a/docs/guides/using-host-labels.md
+++ b/docs/guides/using-host-labels.md
@@ -209,4 +209,4 @@ If you have issues or questions around using host labels, don't hesitate to [fil
issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) on GitHub. We're
excited to make host labels even more valuable to our users, which we can only do with your input.
-[](<>)
+
diff --git a/docs/monitor/configure-alarms.md b/docs/monitor/configure-alarms.md
index 563e615608..ac45811526 100644
--- a/docs/monitor/configure-alarms.md
+++ b/docs/monitor/configure-alarms.md
@@ -145,4 +145,4 @@ state.
To build complex, dynamic alarms, read our guide on [dimension templates](/docs/guides/monitor/dimension-templates.md).
-[](<>)
+
diff --git a/docs/monitor/enable-notifications.md b/docs/monitor/enable-notifications.md
index d0ff04d99d..8cf6979723 100644
--- a/docs/monitor/enable-notifications.md
+++ b/docs/monitor/enable-notifications.md
@@ -144,4 +144,4 @@ architecture](/docs/store/distributed-data-architecture.md) for the best-in-clas
- [Netdata Cloud · Alarm notifications](https://learn.netdata.cloud/docs/cloud/alerts-notifications/notifications)
- [Netdata Agent · Notifications](/health/notifications/README.md)
-[](<>)
+
diff --git a/docs/monitor/view-active-alarms.md b/docs/monitor/view-active-alarms.md
index 99169c2c8c..be21826831 100644
--- a/docs/monitor/view-active-alarms.md
+++ b/docs/monitor/view-active-alarms.md
@@ -72,4 +72,4 @@ If you're happy with the pre-configured alarms, skip ahead to [enable
notifications](/docs/monitor/enable-notifications.md) to use Netdata Cloud's centralized alarm notifications and/or
per-node notifications to endpoints like Slack, PagerDuty, Twilio, and more.
-[](<>)
+
diff --git a/docs/netdata-for-IoT.md b/docs/netdata-for-IoT.md
index 77b95229fd..35d770537e 100644
--- a/docs/netdata-for-IoT.md
+++ b/docs/netdata-for-IoT.md
@@ -71,4 +71,4 @@ Then restart Netdata. You will get this:
-[](<>)
+
diff --git a/docs/netdata-security.md b/docs/netdata-security.md
index bb4ac30c42..41f5c40b12 100644
--- a/docs/netdata-security.md
+++ b/docs/netdata-security.md
@@ -226,4 +226,4 @@ _actively_ contributing to Netdata's future.
| `/var/lib/netdata`|user `netdata`<br/>group `netdata`|dirs `0750`<br/>files `0660`|reads, writes, creates, deletes|**Netdata permanent database files**<br/>Netdata stores here the registry data, health alarm log db, etc.|
| `/var/log/netdata`|user `netdata`<br/>group `root`|dirs `0755`<br/>files `0644`|writes, creates|**Netdata log files**<br/>all the Netdata applications, logs their errors or other informational messages to files in this directory. These files should be log rotated.|
-[](<>)
+
diff --git a/docs/overview/netdata-monitoring-stack.md b/docs/overview/netdata-monitoring-stack.md
index 3a954f055a..ae9252272b 100644
--- a/docs/overview/netdata-monitoring-stack.md
+++ b/docs/overview/netdata-monitoring-stack.md
@@ -59,4 +59,4 @@ charts, or use Netdata's health watchdog to send notifications whenever an anoma
Whether you're using Netdata standalone or as part of a larger monitoring stack, the next step is the same: [**Get
Netdata**](/docs/get-started.mdx).
-[](<>)
+
diff --git a/docs/overview/what-is-netdata.md b/docs/overview/what-is-netdata.md
index 37f974ad84..3df1d949bf 100644
--- a/docs/overview/what-is-netdata.md
+++ b/docs/overview/what-is-netdata.md
@@ -71,4 +71,4 @@ case:
Learn more about [why you should use Netdata](/docs/overview/why-netdata.md), or [how Netdata works with your existing
monitoring stack](/docs/overview/netdata-monitoring-stack.md).
-[](<>)
+
diff --git a/docs/overview/why-netdata.md b/docs/overview/why-netdata.md
index 27a30a4c6a..9a308f25cd 100644
--- a/docs/overview/why-netdata.md
+++ b/docs/overview/why-netdata.md
@@ -60,4 +60,4 @@ Whether you already have a monitoring stack you want to integrate Netdata into,
ground-up, you should read more on how Netdata can work either [standalone or as an interoperable part of a monitoring
stack](/docs/overview/netdata-monitoring-stack.md).
-[](<>)
+
diff --git a/docs/quickstart/infrastructure.md b/docs/quickstart/infrastructure.md
index ea803cf136..9db66c0529 100644
--- a/docs/quickstart/infrastructure.md
+++ b/docs/quickstart/infrastructure.md
@@ -182,4 +182,4 @@ To change how the Netdata Agent runs on each node, dig in to configuration files
GitHub](https://learn.netdata.cloud/docs/cloud/manage/sign-in)
- [Netdata Cloud · Nodes view](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
-[](<>)
+
diff --git a/docs/quickstart/single-node.md b/docs/quickstart/single-node.md
index ab98a83897..7855a48768 100644
--- a/docs/quickstart/single-node.md
+++ b/docs/quickstart/single-node.md
@@ -89,4 +89,4 @@ out some of Netdata's other visualization and health monitoring features:
- [Export metrics](/docs/export/external-databases.md) to an external time-series database to use Netdata alongside
other monitoring and troubleshooting tools.
-[](<>)
+
diff --git a/docs/store/change-metrics-storage.md b/docs/store/change-metrics-storage.md
index 2ed026c5c1..99760e8d37 100644
--- a/docs/store/change-metrics-storage.md
+++ b/docs/store/change-metrics-storage.md
@@ -74,4 +74,4 @@ further analysis, visualization, or correlation with other tools.
- [Netdata Agent · Database engine](/database/engine/README.md)
-[](<>)
+
diff --git a/docs/store/distributed-data-architecture.md b/docs/store/distributed-data-architecture.md
index 0ec5c14206..c834d710ad 100644
--- a/docs/store/distributed-data-architecture.md
+++ b/docs/store/distributed-data-architecture.md
@@ -68,4 +68,4 @@ You can configure the Netdata Agent to store days, weeks, or months worth of dis
resources required to retain your desired amount of metrics, and expand or contract the database by editing a single
setting.
-[](<>)
+
diff --git a/docs/visualize/create-dashboards.md b/docs/visualize/create-dashboards.md
index 91a8dccccc..696cd1a747 100644
--- a/docs/visualize/create-dashboards.md
+++ b/docs/visualize/create-dashboards.md
@@ -61,4 +61,4 @@ While it's useful to see real-time metrics on flexible dashboards, you need ways
strikes. Every Netdata Agent comes with a health watchdog that uses [alarms](/docs/monitor/configure-alarms.md) and
[notifications](/docs/monitor/enable-notifications.md) to notify you of issues seconds after they strike.
-[](<>)
+
diff --git a/docs/visualize/interact-dashboards-charts.md b/docs/visualize/interact-dashboards-charts.md
index c5b4c1b629..5dbbf19ab4 100644
--- a/docs/visualize/interact-dashboards-charts.md
+++ b/docs/visualize/interact-dashboards-charts.md
@@ -128,4 +128,4 @@ to get informed when something goes wrong in your infrastructure.
- [Netdata Cloud · Nodes](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
- [Netdata Cloud · Build new dashboards](https://learn.netdata.cloud/docs/cloud/visualize/dashboards)
-[](<>)
+
diff --git a/docs/visualize/overview-infrastructure.md b/docs/visualize/overview-infrastructure.md
index 288bfc515f..4edbb0f3ad 100644
--- a/docs/visualize/overview-infrastructure.md
+++ b/docs/visualize/overview-infrastructure.md
@@ -108,4 +108,4 @@ visualizations_](/docs/guides/monitor/kubernetes-k8s-netdata.md), for a full wal
- [Netdata Cloud · Nodes view](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
- [Netdata Cloud · Kubernetes visualizations](https://learn.netdata.cloud/docs/cloud/visualize/kubernetes)
-[](<>)
+
diff --git a/docs/why-netdata/1s-granularity.md b/docs/why-netdata/1s-granularity.md
index a2cc65b8f4..4fc7fab2d2 100644
--- a/docs/why-netdata/1s-granularity.md
+++ b/docs/why-netdata/1s-granularity.md
@@ -56,4 +56,4 @@ Netdata has been designed to:
So, for Netdata 1s granularity is easy, the natural outcome...
-[](<>)
+
diff --git a/docs/why-netdata/README.md b/docs/why-netdata/README.md
index 39cda51e23..c482ee9441 100644
--- a/docs/why-netdata/README.md
+++ b/docs/why-netdata/README.md
@@ -32,4 +32,4 @@ Netdata's helps us troubleshoot slowdowns without touching the console.
So, everything is a bit different.
-[](<>)
+
diff --git a/docs/why-netdata/immediate-results.md b/docs/why-netdata/immediate-results.md
index ba7c7d684a..b35aa53818 100644
--- a/docs/why-netdata/immediate-results.md
+++ b/docs/why-netdata/immediate-results.md
@@ -43,4 +43,4 @@ Netdata:
- Does not introduce any query languages or any other technology to be learned. Of course some familiarity with the tool is required, but nothing too complicated.
- Includes all the community expertise and experience for monitoring systems and applications.
-[](<>)
+
diff --git a/docs/why-netdata/meaningful-presentation.md b/docs/why-netdata/meaningful-presentation.md
index 64d83b4f62..fc670e33f1 100644
--- a/docs/why-netdata/meaningful-presentation.md
+++ b/docs/why-netdata/meaningful-presentation.md
@@ -65,4 +65,4 @@ But it simplifies everything else. Data collection, metrics database and visuali
Netdata goes a step further, by enriching the dashboard with information that is useful for most people. So, to improve clarity and help users be more effective, Netdata includes right in the dashboard the community knowledge and expertise about the metrics. So, that Netdata users can focus on solving their infrastructure problem, not on the technicalities of data collection and visualization.
-[](<>)
+
diff --git a/docs/why-netdata/unlimited-metrics.md b/docs/why-netdata/unlimited-metrics.md
index 8e50062c7d..b79a4ede3f 100644
--- a/docs/why-netdata/unlimited-metrics.md
+++ b/docs/why-netdata/unlimited-metrics.md
@@ -46,4 +46,4 @@ Due to Netdata's distributed nature, the number of metrics collected does not ha
Of course, since Netdata is also about [meaningful presentation](meaningful-presentation.md), the number of metrics makes Netdata development slower. We, the Netdata developers, need to have a good understanding of the metrics before adding them into Netdata. We need to organize the metrics, add information related to them, configure alarms for them, so that you, the Netdata users, will have the best out-of-the-box experience and all the information required to kill the console for troubleshooting slowdowns.
-[](<>)
+
diff --git a/exporting/README.md b/exporting/README.md
index 18f56fbb6a..84627a2e38 100644
--- a/exporting/README.md
+++ b/exporting/README.md
@@ -311,4 +311,4 @@ Netdata adds 3 alarms:
-[](<>)
+
diff --git a/exporting/TIMESCALE.md b/exporting/TIMESCALE.md
index c98003ed4d..b1bd720f00 100644
--- a/exporting/TIMESCALE.md
+++ b/exporting/TIMESCALE.md
@@ -66,4 +66,4 @@ blog](https://blog.timescale.com/blog/writing-it-metrics-from-netdata-to-timesca
Thank you to Mahlon, Rune, TimescaleDB, and the members of the Netdata community that requested and then built this
exporting connection between Netdata and TimescaleDB!
-[](<>)
+
diff --git a/exporting/WALKTHROUGH.md b/exporting/WALKTHROUGH.md
index d6ede8235b..0612b298a7 100644
--- a/exporting/WALKTHROUGH.md
+++ b/exporting/WALKTHROUGH.md
@@ -263,4 +263,4 @@ achieved you do not have to think about the monitoring system until Prometheus c
happens there are options presented in the Prometheus documentation for solving this. Hope this was helpful, happy
monitoring.
-[](<>)
+
diff --git a/exporting/aws_kinesis/README.md b/exporting/aws_kinesis/README.md
index 299fec5817..29dd3438ec 100644
--- a/exporting/aws_kinesis/README.md
+++ b/exporting/aws_kinesis/README.md
@@ -55,4 +55,4 @@ Alternatively, you can set AWS credentials for the `netdata` user using AWS SDK
Netdata automatically computes a partition key for every record with the purpose to distribute records across
available shards evenly.
-[](<>)
+
diff --git a/exporting/graphite/README.md b/exporting/graphite/README.md
index d755e09345..6c96c78c92 100644
--- a/exporting/graphite/README.md
+++ b/exporting/graphite/README.md
@@ -32,4 +32,4 @@ Add `:http` or `:https` modifiers to the connector type if you need to use other
The Graphite connector is further configurable using additional settings. See the [exporting reference
doc](/exporting/README.md#options) for details.
-[](<>)
+
diff --git a/exporting/json/README.md b/exporting/json/README.md
index 7cce463e20..d129ffbd79 100644
--- a/exporting/json/README.md
+++ b/exporting/json/README.md
@@ -32,4 +32,4 @@ Add `:http` or `:https` modifiers to the connector type if you need to use other
The JSON connector is further configurable using additional settings. See the [exporting reference
doc](/exporting/README.md#options) for details.
-[](<>)
+
diff --git a/exporting/mongodb/README.md b/exporting/mongodb/README.md
index 2934f38c52..b10d547164 100644
--- a/exporting/mongodb/README.md
+++ b/exporting/mongodb/README.md
@@ -35,4 +35,4 @@ You can find more information about the `destination` string URI format in the M
The default socket timeout depends on the exporting connector update interval. The timeout is 500 ms shorter than the
interval (but not less than 1000 ms). You can alter the timeout using the `sockettimeoutms` MongoDB URI option.
-[](<>)
+
diff --git a/exporting/opentsdb/README.md b/exporting/opentsdb/README.md
index 0ca6d2449c..c9b1ab95a9 100644
--- a/exporting/opentsdb/README.md
+++ b/exporting/opentsdb/README.md
@@ -32,4 +32,4 @@ Add `:http` or `:https` modifiers to the connector type if you need to use other
The OpenTSDB connector is further configurable using additional settings. See the [exporting reference
doc](/exporting/README.md#options) for details.
-[](<>)
+
diff --git a/exporting/prometheus/README.md b/exporting/prometheus/README.md
index ceb778a430..5c15ca580c 100644
--- a/exporting/prometheus/README.md
+++ b/exporting/prometheus/README.md
@@ -458,4 +458,4 @@ through a web proxy, or when multiple Prometheus servers are NATed to a single I
`&server=NAME` to the URL. This `NAME` is used by Netdata to uniquely identify each Prometheus server and keep track of
its last access time.
-[](<>)
+
diff --git a/exporting/prometheus/remote_write/README.md b/exporting/prometheus/remote_write/README.md
index ce379063e9..54c5d65881 100644
--- a/exporting/prometheus/remote_write/README.md
+++ b/exporting/prometheus/remote_write/README.md
@@ -55,4 +55,4 @@ buffer size on failures.
The remote write exporting connector does not support `buffer on failures`
-[](<>)
+
diff --git a/exporting/pubsub/README.md b/exporting/pubsub/README.md
index 73b6a2031a..2f9ac83d44 100644
--- a/exporting/pubsub/README.md
+++ b/exporting/pubsub/README.md
@@ -35,4 +35,4 @@ Next, create the credentials JSON file by following Google Cloud's [authenticati
`chmod 400 google_cloud_credentials.json; chown netdata google_cloud_credentials.json`. Set the `credentials file`
option to the full path of the file.
-[](<>)
+
diff --git a/health/QUICKSTART.md b/health/QUICKSTART.md
index bc91caf7c5..d1e63167c5 100644
--- a/health/QUICKSTART.md
+++ b/health/QUICKSTART.md
@@ -140,4 +140,4 @@ Or, get guided insights into specific health configurations with our [health gui
Finally, move on to Netdata's [notification system](/health/notifications/README.md) to learn more about how Netdata can
let you know when the health of your systems or apps goes awry.
-[](<>)
+
diff --git a/health/README.md b/health/README.md
index 37f09e8486..2b1caf5486 100644
--- a/health/README.md
+++ b/health/README.md
@@ -35,4 +35,4 @@ content.
**[Notifications](/health/notifications/README.md)**: Get notified about ongoing alarms from your Agents via your
favorite platform(s), such as Slack, Discord, PagerDuty, email, and much more.
-[](<>)
+
diff --git a/health/REFERENCE.md b/health/REFERENCE.md
index 4feb782d6c..42aa2ef3f7 100644
--- a/health/REFERENCE.md
+++ b/health/REFERENCE.md
@@ -913,4 +913,4 @@ to temporary disable notifications (for instance when running backups triggers a
notifications are runtime. The health checks can be controlled at runtime via the [health management
api](/web/api/health/README.md).
-[](<>)
+
diff --git a/health/notifications/README.md b/health/notifications/README.md
index 53541981da..0bd6c7649e 100644
--- a/health/notifications/README.md
+++ b/health/notifications/README.md
@@ -83,4 +83,4 @@ bash -x /usr/libexec/netdata/plugins.d/alarm-notify.sh test
```
Then look in the output for the alarm-notify.sh calls and run the one you want to trace with `bash -x`.
-[](<>)
+
diff --git a/health/notifications/alerta/README.md b/health/notifications/alerta/README.md
index 85a0cd488f..9603aae01f 100644
--- a/health/notifications/alerta/README.md
+++ b/health/notifications/alerta/README.md
@@ -78,4 +78,4 @@ We can test alarms using the standard approach:
For more information see the [Alerta documentation](https://docs.alerta.io)
-[](<>)
+
diff --git a/health/notifications/awssns/README.md b/health/notifications/awssns/README.md
index c682513792..f5368ab2ca 100644
--- a/health/notifications/awssns/README.md
+++ b/health/notifications/awssns/README.md
@@ -40,4 +40,4 @@ Notes:
- If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration. This variable supports all the same variables you can use in custom notifications.
- While Amazon SNS supports sending differently formatted messages for different delivery methods, Netdata does not currently support this functionality.
-[](<>)
+
diff --git a/health/notifications/custom/README.md b/health/notifications/custom/README.md
index bcb09ef533..edc42623d5 100644
--- a/health/notifications/custom/README.md
+++ b/health/notifications/custom/README.md
@@ -89,4 +89,4 @@ The following are more human friendly:
- `${severity}` like "Escalated to CRITICAL", "Recovered from WARNING"
- `${raised_for}` like "(alarm was raised for 10 minutes)"
-[](<>)
+
diff --git a/health/notifications/discord/README.md b/health/notifications/discord/README.md
index 1650d9cec5..568d03bc33 100644
--- a/health/notifications/discord/README.md
+++ b/health/notifications/discord/README.md
@@ -47,4 +47,4 @@ role_recipients_discord[webmaster]="marketing development"
The keywords `systems`, `databases`, `marketing`, `development` are discordapp.com channels (they should already exist within your discord server).
-[](<>)
+
diff --git a/health/notifications/dynatrace/README.md b/health/notifications/dynatrace/README.md
index cc82ee78d7..3f8ad85b6d 100644
--- a/health/notifications/dynatrace/README.md
+++ b/health/notifications/dynatrace/README.md
@@ -32,5 +32,3 @@ The default value is `CUSTOM_INFO`.
This is a required parameter.
6. Specify the annotation type. This is the source of the Dynatrace event. Put whatever it fits you, for example,
_Netdata Alarm_, which is also the default value.
-
-[]()
diff --git a/health/notifications/email/README.md b/health/notifications/email/README.md
index 82786fca16..3dc84dd408 100644
--- a/health/notifications/email/README.md
+++ b/health/notifications/email/README.md
@@ -74,4 +74,4 @@ sendmail="/usr/bin/msmtp"
chmod 600 ~/.msmtprc
```
-[](<>)
+
diff --git a/health/notifications/flock/README.md b/health/notifications/flock/README.md
index b24ecdb254..b9e0025b31 100644
--- a/health/notifications/flock/README.md
+++ b/health/notifications/flock/README.md
@@ -34,4 +34,4 @@ FLOCK_WEBHOOK_URL="https://api.flock.com/hooks/sendMessage/XXXXXXXXXXXXXXXXXXXXX
DEFAULT_RECIPIENT_FLOCK="alarms"
```
-[](<>)
+
diff --git a/health/notifications/hangouts/README.md b/health/notifications/hangouts/README.md
index 886abfc430..7554b39cd9 100644
--- a/health/notifications/hangouts/README.md
+++ b/health/notifications/hangouts/README.md
@@ -52,4 +52,4 @@ You can define multiple rooms like this: `sysadmin devops alarms|critical`.
The keywords `sysadmin`, `devops`, and `alarms` are Hangouts rooms.
-[](<>)
+
diff --git a/health/notifications/irc/README.md b/health/notifications/irc/README.md
index e7f22e1fd0..21c998d11b 100644
--- a/health/notifications/irc/README.md
+++ b/health/notifications/irc/README.md
@@ -75,4 +75,4 @@ role_recipients_irc[webmaster]="#networking-alarms"
The keywords `#user-alarms`, `#networking-alarms`, `#system-alarms`, `#databases-alarms` are irc channels which belong to the specified IRC network.
-[](<>)
+
diff --git a/health/notifications/kavenegar/README.md b/health/notifications/kavenegar/README.md
index b59799fc2f..6123eb9013 100644
--- a/health/notifications/kavenegar/README.md
+++ b/health/notifications/kavenegar/README.md
@@ -43,4 +43,4 @@ KAVENEGAR_SENDER=""
DEFAULT_RECIPIENT_KAVENEGAR=""
```
-[](<>)
+
diff --git a/health/notifications/matrix/README.md b/health/notifications/matrix/README.md
index ea22b4a8a1..8eeecf55d3 100644
--- a/health/notifications/matrix/README.md
+++ b/health/notifications/matrix/README.md
@@ -55,4 +55,4 @@ MATRIX_ACCESSTOKEN="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
DEFAULT_RECIPIENT_MATRIX="!XXXXXXXXXXXX:matrix.org"
```
-[](<>)
+
diff --git a/health/notifications/messagebird/README.md b/health/notifications/messagebird/README.md
index 8e3d1a5b39..f70e86c68a 100644
--- a/health/notifications/messagebird/README.md
+++ b/health/notifications/messagebird/README.md
@@ -42,4 +42,4 @@ MESSAGEBIRD_NUMBER="XXXXXXX"
DEFAULT_RECIPIENT_MESSAGEBIRD="XXXXXXX"
```
-[](<>)
+
diff --git a/health/notifications/msteams/README.md b/health/notifications/msteams/README.md
index 3ff5de68dd..14dbe75116 100644
--- a/health/notifications/msteams/README.md
+++ b/health/notifications/msteams/README.md
@@ -42,4 +42,4 @@ role_recipients_msteams[dba]="YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
role_recipients_msteams[webmaster]="ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ"
```
-[](<>)
+
diff --git a/health/notifications/opsgenie/README.md b/health/notifications/opsgenie/README.md
index 10b9f5242c..640fcd42ac 100644
--- a/health/notifications/opsgenie/README.md
+++ b/health/notifications/opsgenie/README.md
@@ -59,4 +59,4 @@ message:
You can find more details about the Opsgenie error codes in their [response
docs](https://docs.opsgenie.com/docs/response).
-[](<>)
+
diff --git a/health/notifications/prowl/README.md b/health/notifications/prowl/README.md
index 7c60de2704..dc136820ce 100644
--- a/health/notifications/prowl/README.md
+++ b/health/notifications/prowl/README.md
@@ -25,5 +25,3 @@ the Prowl website after registering.
Once you have an API key, simply specify that as a recipient for Prowl
notifications.
-
-[]()
diff --git a/health/notifications/pushbullet/README.md b/health/notifications/pushbullet/README.md
index 7c2f6774e0..194050bc13 100644
--- a/health/notifications/pushbullet/README.md
+++ b/health/notifications/pushbullet/README.md
@@ -47,4 +47,4 @@ PUSHBULLET_ACCESS_TOKEN="o.Sometokenhere"
DEFAULT_RECIPIENT_PUSHBULLET="admin1@example.com admin3@somemail.com #examplechanneltag #anotherchanneltag"
```
-[](<>)
+
diff --git a/health/notifications/pushover/README.md b/health/notifications/pushover/README.md
index 3ba97fbc3e..1e50f7140d 100644
--- a/health/notifications/pushover/README.md
+++ b/health/notifications/pushover/README.md
@@ -20,4 +20,4 @@ pushover.net notifications look like this:
-[](<>)
+
diff --git a/health/notifications/rocketchat/README.md b/health/notifications/rocketchat/README.md
index a54f5826c0..96d6160b2d 100644
--- a/health/notifications/rocketchat/README.md
+++ b/health/notifications/rocketchat/README.md
@@ -49,4 +49,4 @@ role_recipients_rocketchat[webmaster]="marketing development"
The keywords `systems`, `databases`, `marketing`, `development` are RocketChat channels (they should already exist).
Both public and private channels can be used, even if they differ from the channel configured in your RocketChat incoming webhook.
-[](<>)
+
diff --git a/health/notifications/slack/README.md b/health/notifications/slack/README.md
index e338e9af00..ad36ce34aa 100644
--- a/health/notifications/slack/README.md
+++ b/health/notifications/slack/README.md
@@ -47,4 +47,4 @@ role_recipients_slack[dba]="databases systems"
role_recipients_slack[webmaster]="marketing development"
```
-[](<>)
+
diff --git a/health/notifications/smstools3/README.md b/health/notifications/smstools3/README.md
index 6d90e702a5..6618dfa180 100644
--- a/health/notifications/smstools3/README.md
+++ b/health/notifications/smstools3/README.md
@@ -41,4 +41,4 @@ Netdata uses the script `sendsms` that is installed by `smstools3` and just pass
sendsms=""
```
-[](<>)
+
diff --git a/health/notifications/stackpulse/README.md b/health/notifications/stackpulse/README.md
index 4c44954abb..c478fd5848 100644
--- a/health/notifications/stackpulse/README.md
+++ b/health/notifications/stackpulse/README.md
@@ -78,4 +78,4 @@ access the **TRIGGER** tab to define the scenarios used to trigger the event. Th
For more details how to create a scenario, take a look at the [StackPulse documentation](https://docs.stackpulse.io).
-[](<>)
+
diff --git a/health/notifications/syslog/README.md b/health/notifications/syslog/README.md
index 360f6844d3..8b7863a1a0 100644
--- a/health/notifications/syslog/README.md
+++ b/health/notifications/syslog/README.md
@@ -31,4 +31,4 @@ The `facility` and `level` are the standard syslog facility and level options, f
You can configure sending directly to remote log servers by specifying a host (and optionally a port). However, this has a somewhat high overhead, so it is much preferred to use your local syslog daemon to handle the forwarding of messages to remote systems (pretty much all of them allow at least simple forwarding, and most of the really popular ones support complex queueing and routing of messages to remote log servers).
-[](<>)
+
diff --git a/health/notifications/telegram/README.md b/health/notifications/telegram/README.md
index c1c6f2a4ee..2a2ed56232 100644
--- a/health/notifications/telegram/README.md
+++ b/health/notifications/telegram/README.md
@@ -42,4 +42,4 @@ Telegram messages look like this:
-[](<>)
+
diff --git a/health/notifications/twilio/README.md b/health/notifications/twilio/README.md
index b36d40b994..b563c66c1c 100644
--- a/health/notifications/twilio/README.md
+++ b/health/notifications/twilio/README.md
@@ -44,4 +44,4 @@ TWILIO_NUMBER="xxxxxxxxxxx"
DEFAULT_RECIPIENT_TWILIO="+15555555555"
```
-[](<>)
+
diff --git a/health/notifications/web/README.md b/health/notifications/web/README.md
index 9e4918603f..185843af55 100644
--- a/health/notifications/web/README.md
+++ b/health/notifications/web/README.md
@@ -10,4 +10,4 @@ The Netdata dashboard shows HTML notifications, when it is open.
Such web notifications look like this:
-[](<>)
+
diff --git a/libnetdata/README.md b/libnetdata/README.md
index cdb199f519..fe0690d687 100644
--- a/libnetdata/README.md
+++ b/libnetdata/README.md
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/READM
`libnetdata` is a collection of library code that is used by all Netdata `C` programs.
-[](<>)
+
diff --git a/libnetdata/adaptive_resortable_list/README.md b/libnetdata/adaptive_resortable_list/README.md
index 74e379a925..9eb942bc88 100644
--- a/libnetdata/adaptive_resortable_list/README.md
+++ b/libnetdata/adaptive_resortable_list/README.md
@@ -96,4 +96,4 @@ Compared to unoptimized code (test No 1: 4.6sec):
Do not use ARL if the a name/keyword may appear more than once in the
source data.
-[](<>)
+
diff --git a/libnetdata/avl/README.md b/libnetdata/avl/README.md
index 2097be57f3..36392bd79f 100644
--- a/libnetdata/avl/README.md
+++ b/libnetdata/avl/README.md
@@ -14,4 +14,4 @@ use any memory allocations and their memory footprint is optimized
In addition to the above, this version of AVL, provides versions using locks
and traversal functions.
-[](<>)
+
diff --git a/libnetdata/buffer/README.md b/libnetdata/buffer/README.md
index 5a9d7b023d..07259ebba8 100644
--- a/libnetdata/buffer/README.md
+++ b/libnetdata/buffer/README.md
@@ -14,4 +14,4 @@ is just a lookup (it does not traverse the string).
Netdata uses `BUFFER`s for preparing web responses and buffering data to be sent upstream or
to backend databases.
-[](<>)
+
diff --git a/libnetdata/circular_buffer/README.md b/libnetdata/circular_buffer/README.md
index d36c05f5a1..4482173d7f 100644
--- a/libnetdata/circular_buffer/README.md
+++ b/libnetdata/circular_buffer/README.md
@@ -8,5 +8,3 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/circu
`struct circular_buffer` is an adaptive circular buffer. It will start at an initial size
and grow up to a maximum size as it fills. Two indices within the structure track the current
`read` and `write` position for data.
-
-[]()
diff --git a/libnetdata/clocks/README.md b/libnetdata/clocks/README.md
index e53b86a616..3a7ce55f9f 100644
--- a/libnetdata/clocks/README.md
+++ b/libnetdata/clocks/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/clocks/README.md
-->
-[](<>)
+
diff --git a/libnetdata/config/README.md b/libnetdata/config/README.md
index a71f1ee181..2eccf7a211 100644
--- a/libnetdata/config/README.md
+++ b/libnetdata/config/README.md
@@ -51,4 +51,4 @@ When you get the configuration file from the server, there will be a
comment above all `name = value` pairs the server does not use.
So you know that whatever you wrote there, is not used.
-[](<>)
+
diff --git a/libnetdata/dictionary/README.md b/libnetdata/dictionary/README.md
index 234ff18454..6049c7f66d 100644
--- a/libnetdata/dictionary/README.md
+++ b/libnetdata/dictionary/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/dictionary/README.md
-->
-[](<>)
+
diff --git a/libnetdata/ebpf/README.md b/libnetdata/ebpf/README.md
index 09c6607d97..534867f317 100644
--- a/libnetdata/ebpf/README.md
+++ b/libnetdata/ebpf/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/ebpf/README.md
-->
-[](<>)
+
diff --git a/libnetdata/eval/README.md b/libnetdata/eval/README.md
index 72b4089a98..8b13789179 100644
--- a/libnetdata/eval/README.md
+++ b/libnetdata/eval/README.md
@@ -1 +1 @@
-[](<>)
+
diff --git a/libnetdata/json/README.md b/libnetdata/json/README.md
index 79a48e2406..2e04b8b6bc 100644
--- a/libnetdata/json/README.md
+++ b/libnetdata/json/README.md
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/json/
`json` contains a parser for json strings, based on `jsmn` (<https://github.com/zserge/jsmn>), but case you have installed the JSON-C library, the installation script will prefer it, you can also force its use with `--enable-jsonc` in the compilation time.
-[](<>)
+
diff --git a/libnetdata/locks/README.md b/libnetdata/locks/README.md
index b525c97f08..a83f1b6476 100644
--- a/libnetdata/locks/README.md
+++ b/libnetdata/locks/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/locks/README.md
-->
-[](<>)
+
diff --git a/libnetdata/log/README.md b/libnetdata/log/README.md
index c0d7a340cf..a767dd4465 100644
--- a/libnetdata/log/README.md
+++ b/libnetdata/log/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/log/README.md
-->
-[](<>)
+
diff --git a/libnetdata/popen/README.md b/libnetdata/popen/README.md
index e51e2059be..db4aefaedd 100644
--- a/libnetdata/popen/README.md
+++ b/libnetdata/popen/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/popen/README.md
-->
-[](<>)
+
diff --git a/libnetdata/procfile/README.md b/libnetdata/procfile/README.md
index 3eeb1e2057..65638030d4 100644
--- a/libnetdata/procfile/README.md
+++ b/libnetdata/procfile/README.md
@@ -64,4 +64,4 @@ and the data are inside the processor's caches.
This library is extensively used in Netdata and its plugins.
-[](<>)
+
diff --git a/libnetdata/simple_pattern/README.md b/libnetdata/simple_pattern/README.md
index a90759c3a6..cb377f84ed 100644
--- a/libnetdata/simple_pattern/README.md
+++ b/libnetdata/simple_pattern/README.md
@@ -40,4 +40,4 @@ Netdata stops processing to the first positive or negative match
(left to right). If it is not matched by either positive or negative
patterns, it is denied at the end.
-[](<>)
+
diff --git a/libnetdata/socket/README.md b/libnetdata/socket/README.md
index 6736f13bdb..70bfd3441a 100644
--- a/libnetdata/socket/README.md
+++ b/libnetdata/socket/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/socket/README.md
-->
-[](<>)
+
diff --git a/libnetdata/statistical/README.md b/libnetdata/statistical/README.md
index ee1faba22e..f254081d28 100644
--- a/libnetdata/statistical/README.md
+++ b/libnetdata/statistical/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/statistical/README.md
-->
-[](<>)
+
diff --git a/libnetdata/storage_number/README.md b/libnetdata/storage_number/README.md
index 295b3d6e76..4cd19a98bc 100644
--- a/libnetdata/storage_number/README.md
+++ b/libnetdata/storage_number/README.md
@@ -14,4 +14,4 @@ have less decimal precision) and 3 bits for flags.
This provides an extremely optimized memory footprint with just 0.0001% max accuracy loss.
-[](<>)
+
diff --git a/libnetdata/threads/README.md b/libnetdata/threads/README.md
index 377da5ea3f..75ab11b1ea 100644
--- a/libnetdata/threads/README.md
+++ b/libnetdata/threads/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/threads/README.md
-->
-[](<>)
+
diff --git a/libnetdata/url/README.md b/libnetdata/url/README.md
index 4a95547a5d..bd289d955b 100644
--- a/libnetdata/url/README.md
+++ b/libnetdata/url/README.md
@@ -2,4 +2,4 @@
custom_edit_url: https://github.com/netdata/netdata/edit/master/libnetdata/url/README.md
-->
-[](<>)
+
diff --git a/packaging/docker/README.md b/packaging/docker/README.md
index 0052bebe13..dcce9a4a1b 100644
--- a/packaging/docker/README.md
+++ b/packaging/docker/README.md
@@ -489,4 +489,4 @@ Once you have contacted the Netdata owners to setup you up on Github and Travis,
Having followed these instructions, your forked repository should be all set up for integration with Travis CI. Happy
testing!
-[](<>)
+
diff --git a/packaging/installer/README.md b/packaging/installer/README.md
index f2f826edb9..34f1a8a3d6 100644
--- a/packaging/installer/README.md
+++ b/packaging/installer/README.md
@@ -220,4 +220,4 @@ Our current build process has some issues when using certain configurations of t
section on `nonrepresentable section on output`
errors](/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
-[](<>)
+
diff --git a/packaging/installer/REINSTALL.md b/packaging/installer/REINSTALL.md
index 1398551df6..ddfc8bcb5f 100644
--- a/packaging/installer/REINSTALL.md
+++ b/packaging/installer/REINSTALL.md
@@ -33,4 +33,4 @@ installer](/packaging/installer/methods/kickstart.md).
You can also post to our [community forums](https://community.netdata.cloud/c/support/13) or create a new [bug
report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
-[](<>)
+
diff --git a/packaging/installer/UNINSTALL.md b/packaging/installer/UNINSTALL.md
index c18a1bfc81..87c76ca651 100644
--- a/packaging/installer/UNINSTALL.md
+++ b/packaging/installer/UNINSTALL.md
@@ -51,4 +51,4 @@ The default `environment_file` is `/etc/netdata/.environment`.
> Note: This uninstallation method assumes previous installation with `netdata-installer.sh` or the kickstart script.
> Currently using it when Netdata was installed by a package manager can work or cause unexpected results.
-[](<>)
+
diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md
index 8230d00cdb..fbe7f57579 100644
--- a/packaging/installer/UPDATE.md
+++ b/packaging/installer/UPDATE.md
@@ -117,4 +117,4 @@ sudo ./netdata-installer.sh
> ⚠️ If you installed Netdata with any optional parameters, such as `--no-updates` to disable automatic updates, and
> want to retain those settings, you need to set them again during this process.
-[](<>)
+
diff --git a/packaging/installer/methods/cloud-providers.md b/packaging/installer/methods/cloud-providers.md
index 08c0ed9da2..bc5c9aae25 100644
--- a/packaging/installer/methods/cloud-providers.md
+++ b/packaging/installer/methods/cloud-providers.md
@@ -123,4 +123,4 @@ Name: Netdata
Click **Add** to apply your new inbound security rule.
-[](<>)
+
diff --git a/packaging/installer/methods/freebsd.md b/packaging/installer/methods/freebsd.md
index 8b62570664..13f5b1529f 100644
--- a/packaging/installer/methods/freebsd.md
+++ b/packaging/installer/methods/freebsd.md
@@ -105,4 +105,4 @@ The `netdata-updater.sh` script will update your Agent.
| `--zlib-is-really-here` or `--libs-are-really-here` | If you get errors about missing zlib or libuuid but you know it is available, you might have a broken pkg-config. Use this option to proceed without checking pkg-config|
|`--disable-telemetry` | Use this flag to opt-out from our anonymous telemetry program. (DISABLE_TELEMETRY=1)|
-[](<>)
+
diff --git a/packaging/installer/methods/freenas.md b/packaging/installer/methods/freenas.md
index a0dafdff87..a69f1e3fb3 100644
--- a/packaging/installer/methods/freenas.md
+++ b/packaging/installer/methods/freenas.md
@@ -21,4 +21,4 @@ To start the Netdata service:
service netdata start
```
-[](<>)
+
diff --git a/packaging/installer/methods/kickstart.md b/packaging/installer/methods/kickstart.md
index 5f4344c348..02655e8e4e 100644
--- a/packaging/installer/methods/kickstart.md
+++ b/packaging/installer/methods/kickstart.md
@@ -152,4 +152,4 @@ Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which
solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
external databases, and more.
-[](<>)
+
diff --git a/packaging/installer/methods/kubernetes.md b/packaging/installer/methods/kubernetes.md
index f128506656..216703a334 100644
--- a/packaging/installer/methods/kubernetes.md
+++ b/packaging/installer/methods/kubernetes.md
@@ -194,4 +194,4 @@ utilization metrics, and application metrics.
- [Netdata Helm chart](https://github.com/netdata/helmchart)
- [Netdata service discovery](https://github.com/netdata/agent-service-discovery/)
-[](<>)
+
diff --git a/packaging/installer/methods/macos.md b/packaging/installer/methods/macos.md
index 2df21da7cc..1ff5da6b44 100644
--- a/packaging/installer/methods/macos.md
+++ b/packaging/installer/methods/macos.md
@@ -108,4 +108,4 @@ When you're finished with installation, check out our [single-node](/docs/quicks
Or, skip straight to [configuring the Netdata Agent](/docs/configure/nodes.md).
-[](<>)
+
diff --git a/packaging/installer/methods/manual.md b/packaging/installer/methods/manual.md
index 6d88fbd8e5..aaf1451df7 100644
--- a/packaging/installer/methods/manual.md
+++ b/packaging/installer/methods/manual.md
@@ -244,4 +244,4 @@ Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which
solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
external databases, and more.
-[](<>)
+
diff --git a/packaging/installer/methods/offline.md b/packaging/installer/methods/offline.md
index c978dd6130..53390c71b1 100644
--- a/packaging/installer/methods/offline.md
+++ b/packaging/installer/methods/offline.md
@@ -86,5 +86,3 @@ Or, skip straight to [configuring the Netdata Agent](/docs/configure/nodes.md).
Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which is structured based on actions and
solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
external databases, and more.
-
-[]()
diff --git a/packaging/installer/methods/pfsense.md b/packaging/installer/methods/pfsense.md
index 6d9de76064..f0d730036c 100644
--- a/packaging/installer/methods/pfsense.md
+++ b/packaging/installer/methods/pfsense.md
@@ -81,4 +81,4 @@ workaround from <https://redmine.pfsense.org/issues/6643>
**Note:** In pfSense, the Netdata configuration files are located under `/usr/local/etc/netdata`.
-[](<>)
+
diff --git a/packaging/installer/methods/source.md b/packaging/installer/methods/source.md
index 737ea166aa..a25323f0cf 100644
--- a/packaging/installer/methods/source.md
+++ b/packaging/installer/methods/source.md
@@ -234,4 +234,4 @@ repository](https://github.com/netdata/kernel-collector/blob/master/README.md),
which outlines both the required dependencies, as well as multiple
options for building the code.
-[](<>)
+
diff --git a/packaging/installer/methods/synology.md b/packaging/installer/methods/synology.md
index 8e55924c17..ed68880a01 100644
--- a/packaging/installer/methods/synology.md
+++ b/packaging/installer/methods/synology.md
@@ -58,4 +58,4 @@ installed. You'll have to do this manually:
3. Make sure `/etc/rc.netdata` is executable: `chmod 0755 /etc/rc.netdata`.
-[](<>)
+
diff --git a/packaging/maintainers/README.md b/packaging/maintainers/README.md
index 903c37d5f6..249436d6be 100644
--- a/packaging/maintainers/README.md
+++ b/packaging/maintainers/README.md
@@ -83,4 +83,4 @@ This page tracks the package maintainers for Netdata, for various operating syst
[](https://repology.org/metapackage/netdata/versions)
-[](<>)
+
diff --git a/packaging/makeself/README.md b/packaging/makeself/README.md
index c898a94049..055b6c18bd 100644
--- a/packaging/makeself/README.md
+++ b/packaging/makeself/README.md
@@ -51,4 +51,4 @@ To stop Netdata while it runs under `valgrind`, press Control-C on the console.
> If you omit the parameter `--undef-value-errors=no` to valgrind, you will get hundreds of errors about conditional jumps that depend on uninitialized values. This is normal. Valgrind has heuristics to prevent it from printing such errors for system libraries, but for the static Netdata binary, all the required libraries are built into Netdata. So, valgrind cannot apply its heuristics and prints them.
-[](<>)
+
diff --git a/parser/README.md b/parser/README.md
index 50d55e3d63..c01972df63 100644
--- a/parser/README.md
+++ b/parser/README.md
@@ -145,5 +145,3 @@ Output
Returns
- none
-
-[]()
diff --git a/registry/README.md b/registry/README.md
index 1544a57d1d..df618ffc58 100644
--- a/registry/README.md
+++ b/registry/README.md
@@ -211,4 +211,4 @@ ERROR 409: Cannot ACCESS netdata registry: https://registry.my-netdata.io respon
This error is printed on your web browser console (press F12 on your browser to see it).
-[](<>)
+
diff --git a/streaming/README.md b/streaming/README.md
index 71c1dc289b..b10c4a5db4 100644
--- a/streaming/README.md
+++ b/streaming/README.md
@@ -727,4 +727,4 @@ file descriptor given is not a valid stream
After logging this error, Netdata will close the stream.
-[](<>)
+
diff --git a/tests/README.md b/tests/README.md
index 256b482cfa..5f51e2dfdf 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -145,4 +145,4 @@ The karma and node.d runners can be integrated in Travis (AFAIK), but that is ou
Note: Karma is for browser-testing. On a build server, no GUI or browser might by available, unless browsers support headless mode.
-[](<>)
+
diff --git a/tests/health_mgmtapi/README.md b/tests/health_mgmtapi/README.md
index 1a4b2b146b..e19b612a52 100644
--- a/tests/health_mgmtapi/README.md
+++ b/tests/health_mgmtapi/README.md
@@ -12,4 +12,4 @@ The script can be executed with options to prepare the system for the tests, run
It depends on the management API being accessible on localhost:19999 and on the responses to the api/v1/alarms?all requests being functional.
It also requires read access to the management API key that is usually under `/var/lib/netdata/netdata.api.key` (`@varlibdir_POST@/netdata.api.key`).
-[](<>)
+
diff --git a/web/README.md b/web/README.md
index 6a7aa68ffa..7093ca18f7 100644
--- a/web/README.md
+++ b/web/README.md
@@ -232,5 +232,3 @@ make
If you make any changes to the `src` directory when developing Netdata, you
should regenerate the `dashboard.js` file before you commit to the Netdata
repository.
-
-[]()
diff --git a/web/api/README.md b/web/api/README.md
index 1cc3439c22..89a9530027 100644
--- a/web/api/README.md
+++ b/web/api/README.md
@@ -11,4 +11,4 @@ The complete documentation of the Netdata API is available at the **[Swagger Edi
If your prefer it over the Swagger Editor, you can also use **[Swagger UI](https://registry.my-netdata.io/swagger/#!/default/get_data)**. This however does not provide all the information available.
-[](<>)
+
diff --git a/web/api/badges/README.md b/web/api/badges/README.md
index b5fc534684..601eae479b 100644
--- a/web/api/badges/README.md
+++ b/web/api/badges/README.md
@@ -360,4 +360,4 @@ You can refresh them from your browser console though. Press F12 to open the web
var len = document.images.length; while(len--) { document.images[len].src = document.images[len].src.replace(/\?cacheBuster=\d*/, "") + "?cacheBuster=" + new Date().getTime().toString(); };
```
-[](<>)
+
diff --git a/web/api/exporters/README.md b/web/api/exporters/README.md
index 4019647440..1d517a91e4 100644
--- a/web/api/exporters/README.md
+++ b/web/api/exporters/README.md
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/web/api/exporter
TBD
-[](<>)
+
diff --git a/web/api/exporters/prometheus/README.md b/web/api/exporters/prometheus/README.md
index 48b85555e4..cf7e2caa8d 100644
--- a/web/api/exporters/prometheus/README.md
+++ b/web/api/exporters/prometheus/README.md
@@ -7,4 +7,4 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/web/api/exporter
Read the Prometheus exporter documentation: [Using Netdata with Prometheus](/exporting/prometheus/README.md).
-[](<>)
+
diff --git a/web/api/exporters/shell/README.md b/web/api/exporters/shell/README.md
index 9d44a37070..a41326c9d2 100644
--- a/web/api/exporters/shell/README.md
+++ b/web/api/exporters/shell/README.md
@@ -66,4 +66,4 @@ NETDATA_${chart_id^^}_${dimension_id^^}="${value}"
The value is rounded to the closest integer, since shell script cannot process decimal numbers.
-[](<>)
+
diff --git a/web/api/formatters/README.md b/web/api/formatters/README.md
index 1fd2b30294..3e67ac6ee2 100644
--- a/web/api/formatters/README.md
+++ b/web/api/formatters/README.md
@@ -75,4 +75,4 @@ For example, to download a CSV file with CPU utilization of the last hour,
This is done by appending `&tqx=outFileName:FILENAME` to any data query.
The output will be in the format given with `&format=`.
-[](<>)
+
diff --git a/web/api/formatters/csv/README.md b/web/api/formatters/csv/README.md
index 2a859e2498..df7c11efa6 100644
--- a/web/api/formatters/csv/README.md
+++ b/web/api/formatters/csv/README.md
@@ -141,4 +141,4 @@ And this is how it looks when formatted:
| 2018-10-27 03:44:00 | 7026.9852167 |
| 2018-10-27 03:43:00 | 205.9904794 |
-[](<>)
+
diff --git a/web/api/formatters/json/README.md b/web/api/formatters/json/README.md
index 685a3f2dfa..a0f8108e73 100644
--- a/web/api/formatters/json/README.md
+++ b/web/api/formatters/json/README.md
@@ -153,4 +153,4 @@ google.visualization.Query.setResponse({version:'0.6',reqId:'0',status:'ok',sig:
}});
```
-[](<>)
+
diff --git a/web/api/formatters/ssv/README.md b/web/api/formatters/ssv/README.md
index d439949a58..d9e193d66e 100644
--- a/web/api/formatters/ssv/README.md
+++ b/web/api/formatters/ssv/README.md
@@ -56,4 +56,4 @@ in a JSON array:
[278,258,268,239,259,260,243,266,278,318,264,258]
```
-[](<>)
+
diff --git a/web/api/formatters/value/README.md b/web/api/formatters/value/README.md
index 21c937080f..a51e32de76 100644
--- a/web/api/formatters/value/README.md
+++ b/web/api/formatters/value/README.md
@@ -21,4 +21,4 @@ The Value formatter is not exposed by the API by itself.
Instead it is used by the [`ssv`](/web/api/formatters/ssv/README.md) formatter
and [health monitoring queries](/health/README.md).
-[](<>)
+
diff --git a/web/api/health/README.md b/web/api/health/README.md
index b6e8b5c234..9ec8f31c01 100644
--- a/web/api/health/README.md
+++ b/web/api/health/README.md
@@ -222,4 +222,4 @@ The file's location is configurable in `netdata.conf`. The default is shown belo
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.
-[](<>)
+
diff --git a/web/api/queries/README.md b/web/api/queries/README.md
index 31ec496558..44cdd05b41 100644
--- a/web/api/queries/README.md
+++ b/web/api/queries/README.md
@@ -173,4 +173,4 @@ So, the proper way to query the database is to also set at least `after`. The fo
When you keep calling this URL, you will see that it returns one new value every 10 seconds, and the timestamp always ends with zero. Similarly, if you say `points=1&after=-5` it will always return timestamps ending with 0 or 5.
-[](<>)
+
diff --git a/web/api/queries/average/README.md b/web/api/queries/average/README.md
index f32a67571d..b8d4ba7e76 100644
--- a/web/api/queries/average/README.md
+++ b/web/api/queries/average/README.md
@@ -43,4 +43,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Average>.
-[](<>)
+
diff --git a/web/api/queries/des/README.md b/web/api/queries/des/README.md
index 5505de5a69..33c5f1a0cc 100644
--- a/web/api/queries/des/README.md
+++ b/web/api/queries/des/README.md
@@ -70,4 +70,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Exponential_smoothing>.
-[](<>)
+
diff --git a/web/api/queries/incremental_sum/README.md b/web/api/queries/incremental_sum/README.md
index e5f3dfc0cc..44301172e3 100644
--- a/web/api/queries/incremental_sum/README.md
+++ b/web/api/queries/incremental_sum/README.md
@@ -38,4 +38,4 @@ Examining last 1 minute `successful` web server responses:
- none
-[](<>)
+
diff --git a/web/api/queries/max/README.md b/web/api/queries/max/README.md
index 32b1d434cb..48da7cf087 100644
--- a/web/api/queries/max/README.md
+++ b/web/api/queries/max/README.md
@@ -35,4 +35,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Sample_maximum_and_minimum>.
-[](<>)
+
diff --git a/web/api/queries/median/README.md b/web/api/queries/median/README.md
index 25ce8b8d6d..bb7d4c66be 100644
--- a/web/api/queries/median/README.md
+++ b/web/api/queries/median/README.md
@@ -42,4 +42,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Median>.
-[](<>)
+
diff --git a/web/api/queries/min/README.md b/web/api/queries/min/README.md
index 69ef4ea127..495523c047 100644
--- a/web/api/queries/min/README.md
+++ b/web/api/queries/min/README.md
@@ -35,4 +35,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Sample_maximum_and_minimum>.
-[](<>)
+
diff --git a/web/api/queries/ses/README.md b/web/api/queries/ses/README.md
index c279701358..b835b8120b 100644
--- a/web/api/queries/ses/README.md
+++ b/web/api/queries/ses/README.md
@@ -58,4 +58,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Moving_average#exponential-moving-average>
- <https://en.wikipedia.org/wiki/Exponential_smoothing>.
-[](<>)
+
diff --git a/web/api/queries/stddev/README.md b/web/api/queries/stddev/README.md
index 7cd7d62af0..2fca47d5e4 100644
--- a/web/api/queries/stddev/README.md
+++ b/web/api/queries/stddev/README.md
@@ -90,4 +90,4 @@ Examining last 1 minute `successful` web server responses:
Check <https://en.wikipedia.org/wiki/Coefficient_of_variation>.
-[](<>)
+
diff --git a/web/api/queries/sum/README.md b/web/api/queries/sum/README.md
index aeace0a168..d4465bd826 100644
--- a/web/api/queries/sum/README.md
+++ b/web/api/queries/sum/README.md
@@ -38,4 +38,4 @@ Examining last 1 minute `successful` web server responses:
- <https://en.wikipedia.org/wiki/Summation>.
-[](<>)
+
diff --git a/web/gui/README.md b/web/gui/README.md
index 166cea7b2a..69db6becbc 100644
--- a/web/gui/README.md
+++ b/web/gui/README.md
@@ -165,5 +165,3 @@ file](https://user-images.githubusercontent.com/1153921/62798924-570e6c80-ba94-1
For information on creating custom dashboards from scratch, see the [custom dashboards](/web/gui/custom/README.md) or
[Atlassian Confluence dashboards](/web/gui/confluence/README.md) guides.
-
-[]()
diff --git a/web/gui/confluence/README.md b/web/gui/confluence/README.md
index 2e929e7d14..64dacdf38d 100644
--- a/web/gui/confluence/README.md
+++ b/web/gui/confluence/README.md
@@ -1016,4 +1016,4 @@ NETDATA.options.current.eliminate_zero_dimensions = false;
</div>
```
-[](<>)
+
diff --git a/web/gui/custom/README.md b/web/gui/custom/README.md
index a646e4b5c4..5ec87c5af9 100644
--- a/web/gui/custom/README.md
+++ b/web/gui/custom/README.md
@@ -602,4 +602,3 @@ to 50.
-[]()
diff --git a/web/server/README.md b/web/server/README.md
index dc447118e2..445c17db6e 100644
--- a/web/server/README.md
+++ b/web/server/README.md
@@ -242,4 +242,4 @@ If you publish your Netdata to the internet, you may want to apply some protecti
4. Run the `netdata` process with a low process scheduling priority (the default is the lowest)
5. If possible, proxy Netdata via a full featured web server (nginx, apache, etc)
-[](<>)
+
diff --git a/web/server/static/README.md b/web/server/static/README.md
index e095f2ef3e..6a83b70db4 100644
--- a/web/server/static/README.md
+++ b/web/server/static/README.md
@@ -14,4 +14,4 @@ Each thread uses non-blocking I/O so it can serve any number of web requests in
This web server respects the `keep-alive` HTTP header to serve multiple HTTP requests via the same connection.
-[](<>)
+