fix broken links and links pointing to Learn (#17675)

2025-04-10 08:07:34 +00:00 · 2024-05-16 12:54:02 +03:00 · 2024-05-16 12:54:02 +03:00 · 9e236258a5
commit 9e236258a5
parent 6860a57a95
77 changed files with 114 additions and 484 deletions
--- a/README.md
+++ b/README.md
@ -13,7 +13,7 @@
 <p align="center">
  <a href="https://github.com/netdata/netdata/"><img src="https://img.shields.io/github/stars/netdata/netdata?style=social" alt="GitHub Stars"></a>
  <br />
-  <a href="https://app.netdata.cloud/spaces/netdata-demo?utm_campaign=github_readme_demo_badge"><img src="https://img.shields.io/badge/Live Demo-green" alt="Live Demo"></a>
+  <a href="https://app.netdata.cloud/spaces/netdata-demo?utm_campaign=github_readme_demo_badge"><img src="https://img.shields.io/badge/Live%20Demo-green" alt="Live Demo"></a>
  <a href="https://github.com/netdata/netdata/releases/latest"><img src="https://img.shields.io/github/release/netdata/netdata.svg" alt="Latest release"></a>
  <a href="https://github.com/netdata/netdata-nightlies/releases/latest"><img src="https://img.shields.io/github/release/netdata/netdata-nightlies.svg" alt="Latest nightly build"></a>
  <br />
@ -256,7 +256,7 @@ Check the [systemd-journal plugin of Netdata](https://github.com/netdata/netdata
   Netdata can be installed on all Linux, macOS, and FreeBSD systems. We provide binary packages for the most popular operating systems and package managers.

   - Install on [Ubuntu, Debian CentOS, Fedora, Suse, Red Hat, Arch, Alpine, Gentoo, even BusyBox](https://learn.netdata.cloud/docs/installing/one-line-installer-for-all-linux-systems).
-   - Install with [Docker](https://learn.netdata.cloud/docs/installing/docker).<br/>
+   - Install with [Docker](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md).<br/>
     Netdata is a [Verified Publisher on DockerHub](https://hub.docker.com/r/netdata/netdata) and our users enjoy free unlimited DockerHub pulls :heart_eyes:.
   - Install on [MacOS](https://learn.netdata.cloud/docs/installing/macos) :metal:.
   - Install on [FreeBSD](https://learn.netdata.cloud/docs/installing/freebsd) and [pfSense](https://learn.netdata.cloud/docs/installing/pfsense).
@ -429,7 +429,7 @@ Of course it is! We do our best to ensure it is!
 We understand that Netdata is a software piece that is installed on millions of production systems across the world. So, it is important for us, Netdata to be as secure as possible:

  - We follow the [Open Source Security Foundation](https://bestpractices.coreinfrastructure.org/en/projects/2231) best practices.
-  - We have given great attention to detail when it comes to security design. Check out our [security design](https://learn.netdata.cloud/docs/architecture/security-and-privacy-design).
+  - We have given great attention to detail when it comes to security design. Check out our [security design](https://github.com/netdata/netdata/blob/master/docs/security-and-privacy-design/README.md).
  - Netdata is a popular open-source project and is frequently tested by many security analysts.
  - Check also our [security policies and advisories published so far](https://github.com/netdata/netdata/security).

--- a/docs/alerts-and-notifications/creating-alerts-with-netdata-alerts-configuration-manager.md
+++ b/docs/alerts-and-notifications/creating-alerts-with-netdata-alerts-configuration-manager.md
@ -42,4 +42,4 @@ You can read more about the different options in the [Alerts reference documenta

 - **Alert Template Name**: Provide a unique name for the alert.
 - **Alert Template Description**: Offer a brief explanation of what the alert monitors.
- **Alert Summary**: Create a custom title for alert notifications, which can be integrated with centralized notification systems available [here](https://learn.netdata.cloud/docs/alerting/notifications/centralized-cloud-notifications).
+- **Alert Summary**: Create a custom title for alert notifications, which can be integrated with centralized notification systems available [here](https://learn.netdata.cloud/docs/alerts-&-notifications/notifications/centralized-cloud-notifications).
--- a/docs/deployment-guides/deployment-strategies.md
+++ b/docs/deployment-guides/deployment-strategies.md
@ -58,7 +58,7 @@ On the child node, edit `netdata.conf` by using the edit-config script: `/etc/ne

 ```yaml
 [db]
-    # https://learn.netdata.cloud/docs/agent/database
+    # https://github.com/netdata/netdata/blob/master/src/database/README.md
    # none = no retention, ram = some retention in ram
    mode = ram
    # The retention in seconds.
--- a/packaging/installer/REINSTALL.md
+++ b/packaging/installer/REINSTALL.md
@ -62,5 +62,4 @@ If you still experience problems with your Netdata Agent installation after foll
 best route is to [uninstall](https://github.com/netdata/netdata/blob/master/packaging/installer/UNINSTALL.md) and then try a fresh installation using the [one-line
 installer](https://github.com/netdata/netdata/blob/master/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).
+You can also post to our [community forums](https://community.netdata.cloud) or create a new [bug report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml).
--- a/packaging/installer/UPDATE.md
+++ b/packaging/installer/UPDATE.md
@ -132,7 +132,7 @@ brew upgrade netdata
 ```

 Homebrew downloads the latest Netdata via the
-[formulae](https://github.com/Homebrew/homebrew-core/blob/master/Formula/netdata.rb), ensures all dependencies are met,
+[formulae](https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/netdata.rb), ensures all dependencies are met,
 and updates Netdata via reinstallation.

 If you instead installed Netdata using our one-line installation script, you can use our [regular update
--- a/packaging/installer/methods/freebsd.md
+++ b/packaging/installer/methods/freebsd.md
@ -28,7 +28,7 @@ Please respond in the affirmative for any relevant prompts during the installati

 ## Install Netdata

-The simplest method is to use the single line [kickstart script](https://learn.netdata.cloud/docs/agent/packaging/installer/methods/kickstart)
+The simplest method is to use the single line [kickstart script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md)

 If you have a Netdata cloud account then clicking on the **Connect Nodes** button will generate the kickstart command you should use. Use the command from the "Linux" tab, it should look something like this:

--- a/packaging/installer/methods/manual.md
+++ b/packaging/installer/methods/manual.md
@ -40,7 +40,7 @@ and other operating systems and is regularly tested. You can find this tool [her
    -   Please note that for RHEL/CentOS you need
        [EPEL](http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/).
        In addition, RHEL/CentOS version 6 also need
-        [OKay](https://okay.com.mx/blog-news/rpm-repositories-for-centos-6-and-7.html) for package libuv version 1.
+        [OKay](https://okay.com.mx) for package libuv version 1.
    -   CentOS 8 / RHEL 8 requires a bit of extra work. See the dedicated section below.

 -   **SUSE** Linux and its derivatives (including **openSUSE**)
@ -140,7 +140,7 @@ required if manually installing packages.
 CentOS 6.x:

 - Enable the EPEL repo
- Enable the additional repo from [okay.network](https://okay.network/blog-news/rpm-repositories-for-centos-6-and-7.html)
+- Enable the additional repo from [okay.network](https://okay.network)

 And install the minimum required dependencies.

@ -154,7 +154,7 @@ CentOS 8.x:

 - Enable the PowerTools repo
 - Enable the EPEL repo
- Enable the Extra repo from [OKAY](https://okay.network/blog-news/rpm-repositories-for-centos-6-and-7.html)
+- Enable the Extra repo from [OKAY](https://okay.network)

 And install the minimum required dependencies:

--- a/packaging/installer/methods/packages.md
+++ b/packaging/installer/methods/packages.md
@ -8,7 +8,7 @@ learn_rel_path: "Installation/Installation methods"
 sidebar_position: 20
 -->

-# Install Netdata using native DEB/RPM packages.
+# Install Netdata using native DEB/RPM packages

 For most common Linux distributions that use either DEB or RPM packages, Netdata provides pre-built native packages
 for current releases in-line with
@ -20,8 +20,6 @@ When using the kickstart script, you can force usage of native DEB or RPM packag
 `--native-only` when invoking the script. This will cause it to only attempt to use native packages for the install,
 and fail if it cannot do so.

-
-
 > ### Note
 >
 > In July 2022, we switched hosting of our native packages from Package Cloud to self-hosted repositories.
@ -31,10 +29,9 @@ and fail if it cannot do so.
 > When selecting a repository configuration package, note that the version 2 packages provide configuration for
 > our self-hosted repositories, and then version 1 packages provide configuration for Package Cloud.

+## Manual setup of RPM packages

-## Manual setup of RPM packages.
-
-Netdata’s official RPM repositories are hosted at https://repo.netdata.cloud/repos. We provide four groups of
+Netdata’s official RPM repositories are hosted at <https://repo.netdata.cloud/repos>. We provide four groups of
 repositories at that top level:

 - `stable`: Contains packages for stable releases of the Netdata Agent.
@ -55,14 +52,14 @@ Under each of those directories is a directory for each supported release of tha
 directory for each supported CPU architecture which contains the actual repository.

 For example, for stable release packages for RHEL 9 on 64-bit x86, the full URL for the repository would be
-https://repo.netdata.cloud/repos/stable/el/9/x86_64/
+<https://repo.netdata.cloud/repos/stable/el/9/x86_64/>

 Our RPM packages and repository metadata are signed using a GPG key with a user name of ‘Netdatabot’. The
 current key fingerprint is `6588FDD7B14721FE7C3115E6F9177B5265F56346`. The associated public key can be fetched from
 `https://repo.netdata.cloud/netdatabot.gpg.key`.

 If you are explicitly configuring a system to use our repositories, the recommended setup is to download the
-appropriate repository configuration package from https://repo.netdata.cloud/repos/repoconfig and install it
+appropriate repository configuration package from <https://repo.netdata.cloud/repos/repoconfig> and install it
 directly on the target system using the system package manager. This will ensure any packages needed to use the
 repository are also installed, and will help enable a seamless transition if we ever need to change our infrastructure.

@ -73,9 +70,9 @@ repository are also installed, and will help enable a seamless transition if we
 > repository _should_ be pulled in automatically by our repository config packages, but if it is not you may need
 > to manually install `epel-release` to be able to successfully install the Netdata packages.

-## Manual setup of DEB packages.
+## Manual setup of DEB packages

-Netdata’s official DEB repositories are hosted at https://repo.netdata.cloud/repos. We provide four groups of
+Netdata’s official DEB repositories are hosted at <https://repo.netdata.cloud/repos>. We provide four groups of
 repositories at that top level:

 - `stable`: Contains packages for stable releases of the Netdata Agent.
@ -105,7 +102,7 @@ current key fingerprint is `6588FDD7B14721FE7C3115E6F9177B5265F56346`. The assoc
 `https://repo.netdata.cloud/netdatabot.gpg.key`.

 If you are explicitly configuring a system to use our repositories, the recommended setup is to download the
-appropriate repository configuration package from https://repo.netdata.cloud/repos/repoconfig and install it
+appropriate repository configuration package from <https://repo.netdata.cloud/repos/repoconfig> and install it
 directly on the target system using the system package manager. This will ensure any packages needed to use the
 repository are also installed, and will help enable a seamless transition if we ever need to change our infrastructure.

--- a/packaging/maintainers/README.md
+++ b/packaging/maintainers/README.md
@ -33,7 +33,7 @@ This page tracks the package maintainers for Netdata, for various operating syst

 | System | URL | Core Developer | Package Maintainer
 |:-:|:-:|:-:|:-:|
-| macOS Homebrew Formula|[link](https://github.com/Homebrew/homebrew-core/blob/master/Formula/netdata.rb)|@vlvkobal|@rickard-von-essen
+| macOS Homebrew Formula|[link](https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/netdata.rb)|@vlvkobal|@rickard-von-essen

 ---

@ -48,7 +48,6 @@ This page tracks the package maintainers for Netdata, for various operating syst

 | Embedded Linux | Netdata Version | Maintainer | Related URL |
 | :-: | :-: | :-: | :-- |
-| ASUSTOR NAS | ? | William Lin | https://www.asustor.com/apps/app_detail?id=532 |
 | OpenWRT | Release | @nitroshift | [openwrt package](https://github.com/openwrt/packages/tree/master/admin/netdata) |
 | ReadyNAS | Release | @NAStools | https://github.com/nastools/netdata |
 | QNAP | Release | QNAP_Stephane | https://forum.qnap.com/viewtopic.php?t=121518 |
--- a/src/claim/README.md
+++ b/src/claim/README.md
@ -73,7 +73,7 @@ Connecting a Node to a War Room:
   terminal window. Press Enter to initiate the connection process.

 > Note: When connecting from
-> the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboard/nodes-tab.md), the room parameter will
+> the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/nodes-tab.md), the room parameter will
 > be
 > set to the current War Room.

--- a/src/collectors/COLLECTORS.md
+++ b/src/collectors/COLLECTORS.md
@ -441,8 +441,6 @@ If you don't see the app/service you'd like to monitor in this list:

 - [BungeeCord](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md)

- [CS:GO](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cs:go.md)
-
 - [Minecraft](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md)

 - [OpenRCT2](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md)
--- a/src/collectors/cgroups.plugin/README.md
+++ b/src/collectors/cgroups.plugin/README.md
@ -106,7 +106,7 @@ The whole point for the additional pattern list, is to limit the number of times
 pattern list, the script might be called thousands of times, depending on the number of cgroups available in the system.

 The above pattern list is matched against the path of the cgroup. For matched cgroups, Netdata calls the
-script [cgroup-name.sh](https://raw.githubusercontent.com/netdata/netdata/master/src/collectors/cgroups.plugin/cgroup-name.sh)
+script [cgroup-name.sh](https://github.com/netdata/netdata/blob/master/src/collectors/cgroups.plugin/cgroup-name.sh.in)
 to get its name. This script queries `docker`, `kubectl`, `podman`, or applies heuristics to find give a name for the
 cgroup.

--- a/src/collectors/charts.d.plugin/ap/metadata.yaml
+++ b/src/collectors/charts.d.plugin/ap/metadata.yaml
@ -5,7 +5,7 @@ modules:
      module_name: ap
      monitored_instance:
        name: Access Points
-        link: "https://learn.netdata.cloud/docs/data-collection/networking-stack-and-network-interfaces/linux-access-points"
+        link: ""
        categories:
          - data-collection.linux-systems.network-metrics
        icon_filename: "network-wired.svg"
--- a/src/collectors/ebpf.plugin/README.md
+++ b/src/collectors/ebpf.plugin/README.md
@ -44,12 +44,12 @@ If your Agent is v1.22 or older, you may to enable the collector yourself.

 To enable or disable the entire eBPF collector: 

-1.  Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory).
+1.  Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
    ```bash
    cd /etc/netdata
    ```

-2.  Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) script to edit `netdata.conf`.
+2.  Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit `netdata.conf`.

    ```bash
    ./edit-config netdata.conf
@ -69,11 +69,11 @@ You can configure the eBPF collector's behavior to fine-tune which metrics you r

 To edit the `ebpf.d.conf`:

-1.  Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory).
+1.  Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
    ```bash
    cd /etc/netdata
    ```
-2.  Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) script to edit [`ebpf.d.conf`](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/ebpf.d.conf).
+2.  Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit [`ebpf.d.conf`](https://github.com/netdata/netdata/blob/master/src/collectors/ebpf.plugin/ebpf.d.conf).

    ```bash
    ./edit-config ebpf.d.conf
@ -272,11 +272,11 @@ You can configure each thread of the eBPF data collector. This allows you to ove

 To configure an eBPF thread:

-1.  Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory).
+1.  Navigate to the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
    ```bash
    cd /etc/netdata
    ```
-2.  Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) script to edit a thread configuration file. The following configuration files are available:
+2.  Use the [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) script to edit a thread configuration file. The following configuration files are available:

    -   `network.conf`: Configuration for the [`network` thread](#network-configuration). This config file overwrites the global options and also
        lets you specify which network the eBPF collector monitors.
--- a/src/collectors/profile.plugin/README.md
+++ b/src/collectors/profile.plugin/README.md
@ -12,7 +12,7 @@ A user can specify:

 ## Configuration

-Edit the `netdata.conf` configuration file using [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) from the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory), which is typically at `/etc/netdata`.
+Edit the `netdata.conf` configuration file using [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) from the [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory), which is typically at `/etc/netdata`.

 Scroll down to the `[plugin:profile]` section to find the available options:

--- a/src/collectors/python.d.plugin/anomalies/README.md
+++ b/src/collectors/python.d.plugin/anomalies/README.md
@ -68,12 +68,12 @@ sudo ./edit-config python.d.conf
 sudo systemctl restart netdata
 ```

-The configuration for the anomalies collector defines how it will behave on your system and might take some experimentation with over time to set it optimally for your node. Out of the box, the config comes with some [sane defaults](https://www.netdata.cloud/blog/redefining-monitoring-netdata/) to get you started that try to balance the flexibility and power of the ML models with the goal of being as cheap as possible in term of cost on the node resources. 
+The configuration for the anomalies collector defines how it will behave on your system and might take some experimentation with over time to set it optimally for your node. Out of the box, the config comes with some [sane defaults](https://www.netdata.cloud/blog/redefining-monitoring-with-netdata/) to get you started that try to balance the flexibility and power of the ML models with the goal of being as cheap as possible in term of cost on the node resources. 

 _**Note**: If you are unsure about any of the below configuration options then it's best to just ignore all this and leave the `anomalies.conf` file alone to begin with. Then you can return to it later if you would like to tune things a bit more once the collector is running for a while and you have a feeling for its performance on your node._

 Edit the `python.d/anomalies.conf` configuration file using `edit-config` from the your agent's [config
-directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md), which is usually at `/etc/netdata`.
+directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is usually at `/etc/netdata`.

 ```bash
 cd /etc/netdata   # Replace this path with your Netdata config directory, if different
--- a/src/collectors/python.d.plugin/haproxy/README.md
+++ b/src/collectors/python.d.plugin/haproxy/README.md
@ -42,7 +42,7 @@ It produces:
 ## Configuration

 Edit the `python.d/haproxy.conf` configuration file using `edit-config` from the Netdata [config
-directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md), which is typically at `/etc/netdata`.
+directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.

 ```bash
 cd /etc/netdata   # Replace this path with your Netdata config directory, if different
--- a/src/collectors/python.d.plugin/nvidia_smi/README.md
+++ b/src/collectors/python.d.plugin/nvidia_smi/README.md
@ -44,7 +44,7 @@ It produces the following charts:
 ## Configuration

 Edit the `python.d/nvidia_smi.conf` configuration file using `edit-config` from the Netdata [config
-directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md), which is typically at `/etc/netdata`.
+directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.

 ```bash
 cd /etc/netdata   # Replace this path with your Netdata config directory, if different
--- a/src/collectors/python.d.plugin/traefik/README.md
+++ b/src/collectors/python.d.plugin/traefik/README.md
@ -51,7 +51,7 @@ It produces:
 ## Configuration

 Edit the `python.d/traefik.conf` configuration file using `edit-config` from the
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md), which is typically
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically
 at `/etc/netdata`.

 ```bash
--- a/src/collectors/statsd.plugin/README.md
+++ b/src/collectors/statsd.plugin/README.md
@ -728,7 +728,7 @@ In general, the process for creating a StatsD collector can be summarized in 2 s

    - Make sure to reload the dashboard tab **after** you start sending data to Netdata.

- Create a configuration file for your app using [edit-config](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md): `sudo ./edit-config
+- Create a configuration file for your app using [edit-config](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md): `sudo ./edit-config
  statsd.d/myapp.conf`

    - Each app will have it's own section in the right-hand menu.
@ -784,8 +784,8 @@ visualize all the available operations.
 ### Create a new StatsD configuration file

 Start by creating a new configuration file under the `statsd.d/` folder in the 
-[Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#the-netdata-config-directory). 
-Use [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) 
+[Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory). 
+Use [`edit-config`](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#edit-netdataconf) 
 to create a new file called `k6.conf`.

 ```bash=
--- a/src/exporting/json/metadata.yaml
+++ b/src/exporting/json/metadata.yaml
@ -3,7 +3,7 @@
 id: 'export-json'
 meta:
  name: 'JSON'
-  link: 'https://learn.netdata.cloud/docs/exporting/json-document-databases'
+  link: ''
  categories:
    - export
  icon_filename: 'json.svg'
--- a/src/go/collectors/go.d.plugin/README.md
+++ b/src/go/collectors/go.d.plugin/README.md
@ -69,7 +69,6 @@ see the appropriate collector readme.
 | [docker_engine](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/docker_engine)           |         Docker Engine         |
 | [dockerhub](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/dockerhub)                   |          Docker Hub           |
 | [elasticsearch](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/elasticsearch)           |   Elasticsearch/OpenSearch    |
-| [energid](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/energid)                       |          Energi Core          |
 | [envoy](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/envoy)                           |             Envoy             |
 | [example](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/example)                       |               -               |
 | [fail2ban](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/fail2ban)                     |        Fail2Ban Jails         |
--- a/src/go/collectors/go.d.plugin/modules/bind/README.md
+++ b/src/go/collectors/go.d.plugin/modules/bind/README.md
@ -60,7 +60,7 @@ Per View Statistics (the following set will be added for each bind view):
 ## Configuration

 Edit the `go.d/bind.conf` configuration file using `edit-config` from the
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md), which is typically at `/etc/netdata`.
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.

 ```bash
 cd /etc/netdata # Replace this path with your Netdata config directory
--- a/src/go/collectors/go.d.plugin/modules/example/README.md
+++ b/src/go/collectors/go.d.plugin/modules/example/README.md
@ -19,7 +19,7 @@ This module produces example charts with random values. Number of charts, dimens
 ## Configuration

 Edit the `go.d/example.conf` configuration file using `edit-config` from the
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md), which is typically at `/etc/netdata`.
+Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md), which is typically at `/etc/netdata`.

 ```bash
 cd /etc/netdata # Replace this path with your Netdata config directory
--- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md
+++ b/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md
@ -24,7 +24,7 @@ Module: prometheus
 Keep tabs on Azure resources vital metrics for efficient cloud management and cost optimization.


-Metrics are gathered by periodically sending HTTP requests to [Azure Resources Exporter](https://github.com/FXinnovation/azure-resources-exporter).
+Metrics are gathered by periodically sending HTTP requests to [Azure Resources Exporter](https://github.com/FXinnovation/azure_metrics_exporter).


 This collector is supported on all platforms.
@ -84,7 +84,7 @@ There are no alerts configured by default for this integration.

 #### Install Exporter

-Install [Azure Resources Exporter](https://github.com/FXinnovation/azure-resources-exporter) by following the instructions mentioned in the exporter README.
+Install [Azure Resources Exporter](https://github.com/FXinnovation/azure_metrics_exporter) by following the instructions mentioned in the exporter README.



--- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/csgo.md
+++ b/src/go/collectors/go.d.plugin/modules/prometheus/integrations/csgo.md
@ -1,291 +0,0 @@
-<!--startmeta
-custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/csgo.md"
-meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml"
-sidebar_label: "CS:GO"
-learn_status: "Published"
-learn_rel_path: "Collecting Metrics/Gaming"
-most_popular: False
-message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE"
-endmeta-->
-
-# CS:GO
-
-
-<img src="https://netdata.cloud/img/csgo.svg" width="150"/>
-
-
-Plugin: go.d.plugin
-Module: prometheus
-
-<img src="https://img.shields.io/badge/maintained%20by-Community-blue" />
-
-## Overview
-
-Monitor Counter-Strike: Global Offensive server metrics for improved game performance and management.
-
-
-Metrics are gathered by periodically sending HTTP requests to [CS:GO Exporter](https://github.com/kinduff/csgo_exporter).
-
-
-This collector is supported on all platforms.
-
-This collector supports collecting metrics from multiple instances of this integration, including remote instances.
-
-
-### Default Behavior
-
-#### Auto-Detection
-
-By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations).
-The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf).
-
-
-#### Limits
-
-The default configuration for this integration does not impose any limits on data collection.
-
-#### Performance Impact
-
-The default configuration for this integration is not expected to impose a significant performance impact on the system.
-
-
-## Metrics
-
-This collector has built-in grouping logic based on the [type of metrics](https://prometheus.io/docs/concepts/metric_types/).
-
-| Metric                    | Chart                                     | Dimension(s)         | Algorithm   |
-|---------------------------|-------------------------------------------|----------------------|-------------|
-| Gauge                     | for each label set                        | one, the metric name | absolute    |
-| Counter                   | for each label set                        | one, the metric name | incremental |
-| Summary (quantiles)       | for each label set (excluding 'quantile') | for each quantile    | absolute    |
-| Summary (sum and count)   | for each label set                        | the metric name      | incremental |
-| Histogram (buckets)       | for each label set (excluding 'le')       | for each bucket      | incremental |
-| Histogram (sum and count) | for each label set                        | the metric name      | incremental |
-
-Untyped metrics (have no '# TYPE') processing:
-
- As Counter or Gauge depending on pattern match when 'fallback_type' is used.
- As Counter if it has suffix '_total'.
- As Summary if it has 'quantile' label.
- As Histogram if it has 'le' label.
-
-**The rest are ignored**.
-
-
-
-## Alerts
-
-There are no alerts configured by default for this integration.
-
-
-## Setup
-
-### Prerequisites
-
-#### Install Exporter
-
-Install [CS:GO Exporter](https://github.com/kinduff/csgo_exporter) by following the instructions mentioned in the exporter README.
-
-
-
-### Configuration
-
-#### File
-
-The configuration file name for this integration is `go.d/prometheus.conf`.
-
-
-You can edit the configuration file using the `edit-config` script from the
-Netdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
-
-```bash
-cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
-sudo ./edit-config go.d/prometheus.conf
-```
-#### Options
-
-The following options can be defined globally: update_every, autodetection_retry.
-
-
-<details><summary>Config options</summary>
-
-| Name | Description | Default | Required |
-|:----|:-----------|:-------|:--------:|
-| update_every | Data collection frequency. | 10 | no |
-| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |
-| url | Server URL. |  | yes |
-| selector | Time series selector (filter). |  | no |
-| fallback_type | Time series selector (filter). |  | no |
-| max_time_series | Global time series limit. If an endpoint returns number of time series > limit the data is not processed. | 2000 | no |
-| max_time_series_per_metric | Time series per metric (metric name) limit. Metrics with number of time series > limit are skipped. | 200 | no |
-| timeout | HTTP request timeout. | 10 | no |
-| username | Username for basic HTTP authentication. |  | no |
-| password | Password for basic HTTP authentication. |  | no |
-| proxy_url | Proxy URL. |  | no |
-| proxy_username | Username for proxy basic HTTP authentication. |  | no |
-| proxy_password | Password for proxy basic HTTP authentication. |  | no |
-| method | HTTP request method. | GET | no |
-| body | HTTP request body. |  | no |
-| headers | HTTP request headers. |  | no |
-| not_follow_redirects | Redirect handling policy. Controls whether the client follows redirects. | no | no |
-| tls_skip_verify | Server certificate chain and hostname validation policy. Controls whether the client performs this check. | no | no |
-| tls_ca | Certification authority that the client uses when verifying the server's certificates. |  | no |
-| tls_cert | Client TLS certificate. |  | no |
-| tls_key | Client TLS key. |  | no |
-
-##### selector
-
-This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.
-
- Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
- Pattern syntax: [selector](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md).
- Option syntax:
-
-```yaml
-selector:
-  allow:
-    - pattern1
-    - pattern2
-  deny:
-    - pattern3
-    - pattern4
-```
-
-
-##### fallback_type
-
-This option allows you to process Untyped metrics as Counter or Gauge instead of ignoring them.
-
- Metric name pattern syntax: [shell file name pattern](https://golang.org/pkg/path/filepath/#Match).
- Option syntax:
-
-```yaml
-fallback_type:
-  counter:
-    - metric_name_pattern1
-    - metric_name_pattern2
-  gauge:
-    - metric_name_pattern3
-    - metric_name_pattern4
-```
-
-
-</details>
-
-#### Examples
-
-##### Basic
-
-> **Note**: Change the port of the monitored application on which it provides metrics.
-
-A basic example configuration.
-
-
-```yaml
-jobs:
-  - name: local
-    url: http://127.0.0.1:9090/metrics
-
-```
-##### Read metrics from a file
-
-An example configuration to read metrics from a file.
-
-<details><summary>Config</summary>
-
-```yaml
-# use "file://" scheme
-jobs:
-  - name: myapp
-    url: file:///opt/metrics/myapp/metrics.txt
-
-```
-</details>
-
-##### HTTP authentication
-
-> **Note**: Change the port of the monitored application on which it provides metrics.
-
-Basic HTTP authentication.
-
-
-<details><summary>Config</summary>
-
-```yaml
-jobs:
-  - name: local
-    url: http://127.0.0.1:9090/metrics
-    username: username
-    password: password
-
-```
-</details>
-
-##### HTTPS with self-signed certificate
-
-> **Note**: Change the port of the monitored application on which it provides metrics.
-
-Do not validate server certificate chain and hostname.
-
-
-<details><summary>Config</summary>
-
-```yaml
-jobs:
-  - name: local
-    url: https://127.0.0.1:9090/metrics
-    tls_skip_verify: yes
-
-```
-</details>
-
-##### Multi-instance
-
-> **Note**: When you define multiple jobs, their names must be unique.
-> **Note**: Change the port of the monitored application on which it provides metrics.
-
-Collecting metrics from local and remote instances.
-
-
-<details><summary>Config</summary>
-
-```yaml
-jobs:
-  - name: local
-    url: http://127.0.0.1:9090/metrics
-
-  - name: remote
-    url: http://192.0.2.1:9090/metrics
-
-```
-</details>
-
-
-
-## Troubleshooting
-
-### Debug Mode
-
-To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output
-should give you clues as to why the collector isn't working.
-
- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on
-  your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`.
-
-  ```bash
-  cd /usr/libexec/netdata/plugins.d/
-  ```
-
- Switch to the `netdata` user.
-
-  ```bash
-  sudo -u netdata -s
-  ```
-
- Run the `go.d.plugin` to debug the collector:
-
-  ```bash
-  ./go.d.plugin -d -m prometheus
-  ```
-
-
--- a/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml
+++ b/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml
@ -682,7 +682,7 @@ modules:
      community: true
      monitored_instance:
        name: Azure Resources
-        link: https://github.com/FXinnovation/azure-resources-exporter
+        link: https://github.com/FXinnovation/azure_metrics_exporter
        icon_filename: azure.png
        categories:
          - data-collection.cloud-provider-managed
@ -696,14 +696,14 @@ modules:
        metrics_description: |
          Keep tabs on Azure resources vital metrics for efficient cloud management and cost optimization.
        method_description: |
-          Metrics are gathered by periodically sending HTTP requests to [Azure Resources Exporter](https://github.com/FXinnovation/azure-resources-exporter).
+          Metrics are gathered by periodically sending HTTP requests to [Azure Resources Exporter](https://github.com/FXinnovation/azure_metrics_exporter).
    setup:
      <<: *setup
      prerequisites:
        list:
          - title: Install Exporter
            description: |
-              Install [Azure Resources Exporter](https://github.com/FXinnovation/azure-resources-exporter) by following the instructions mentioned in the exporter README.
+              Install [Azure Resources Exporter](https://github.com/FXinnovation/azure_metrics_exporter) by following the instructions mentioned in the exporter README.
  - <<: *module
    meta:
      <<: *meta
@ -4192,33 +4192,6 @@ modules:
          - title: Install Exporter
            description: |
              Install [Cryptowat Exporter](https://github.com/nbarrientos/cryptowat_exporter) by following the instructions mentioned in the exporter README.
-  - <<: *module
-    meta:
-      <<: *meta
-      id: collector-go.d.plugin-prometheus-csgo
-      most_popular: false
-      community: true
-      monitored_instance:
-        name: CS:GO
-        link: https://github.com/kinduff/csgo_exporter
-        icon_filename: csgo.svg
-        categories:
-          - data-collection.gaming
-      keywords: []
-    overview:
-      <<: *overview
-      data_collection:
-        metrics_description: |
-          Monitor Counter-Strike: Global Offensive server metrics for improved game performance and management.
-        method_description: |
-          Metrics are gathered by periodically sending HTTP requests to [CS:GO Exporter](https://github.com/kinduff/csgo_exporter).
-    setup:
-      <<: *setup
-      prerequisites:
-        list:
-          - title: Install Exporter
-            description: |
-              Install [CS:GO Exporter](https://github.com/kinduff/csgo_exporter) by following the instructions mentioned in the exporter README.
  - <<: *module
    meta:
      <<: *meta
--- a/src/go/collectors/go.d.plugin/pkg/README.md
+++ b/src/go/collectors/go.d.plugin/pkg/README.md
@ -17,6 +17,6 @@ learn_rel_path: "Developers/External plugins/go.d.plugin/Helper Packages"
 - if you collect metrics from an HTTP endpoint use [`web`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/web).
 - if you collect metrics from a prometheus endpoint,
  then [`prometheus`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/prometheus)
-  and [`web`](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/web/README.md) is what you need.
- [`tlscfg`](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/tlscfg/README.md) provides TLS support.
- [`stm`](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/pkg/stm/README.md) helps you to convert any struct to a `map[string]int64`.
+  and [`web`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/web) is what you need.
+- [`tlscfg`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/tlscfg) provides TLS support.
+- [`stm`](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/pkg/stm) helps you to convert any struct to a `map[string]int64`.
--- a/src/health/guides/apcupsd/apcupsd_last_collected_secs.md
+++ b/src/health/guides/apcupsd/apcupsd_last_collected_secs.md
@ -42,5 +42,5 @@ This alert is related to your American Power Conversion (APC) uninterruptible po

 ### Useful resources

-1. [Netdata - APC UPS monitoring](https://learn.netdata.cloud/docs/data-collection/ups/apc-ups)
+1. [Netdata - APC UPS monitoring](https://github.com/netdata/netdata/blob/master/src/collectors/charts.d.plugin/apcupsd/integrations/apc_ups.md)
 2. [`apcupsd` - Power management and control software for APC UPS](https://github.com/apcupsd/apcupsd)
--- a/src/health/guides/boinc/boinc_total_tasks.md
+++ b/src/health/guides/boinc/boinc_total_tasks.md
@ -24,8 +24,6 @@ This alert monitors the average number of total tasks for the BOINC system over
   sudo /etc/init.d/boinc-client restart
   ```

-2. For other operating systems or custom installations, refer to the BOINC's documentation for restarting the client: https://boinc.berkeley.edu/wiki/Stop_or_restart_BOINC
-
 #### Check system resources

 BOINC tasks may fail or slow down if there is not enough system resources (CPU, RAM, or Disk Space) available. Monitor your system performance using tools like `top`, `free`, and `df`, and make adjustments if necessary to ensure that BOINC has enough resources to complete tasks.
--- a/src/health/guides/boinc/boinc_upload_errors.md
+++ b/src/health/guides/boinc/boinc_upload_errors.md
@ -18,7 +18,7 @@ This alert indicates that your BOINC node is experiencing an increase in the ave

 4. Inspect BOINC client logs

-   Consult the BOINC client logs to gain insight into the upload errors. The logs can be found in the client's data directory. Refer to the [BOINC log file documentation](https://boinc.berkeley.edu/wiki/Log_Files) for more information on how to read and analyze the logs.
+   Consult the BOINC client logs to gain insight into the upload errors. The logs can be found in the client's data directory.

 5. Contact project support

--- a/src/health/guides/cockroachdb/cockroachdb_unavailable_ranges.md
+++ b/src/health/guides/cockroachdb/cockroachdb_unavailable_ranges.md
@ -44,7 +44,7 @@ This alert indicates that there are unavailable ranges in your CockroachDB clust

 6. Consider rebalancing the cluster

-   Rebalancing the cluster can help distribute the load more evenly across nodes and reduce the number of unavailable ranges. See the [CockroachDB documentation](https://www.cockroachlabs.com/docs/stable/training/manual-rebalancing.html) for more information on manual rebalancing.
+   Rebalancing the cluster can help distribute the load more evenly across nodes and reduce the number of unavailable ranges. See the [CockroachDB documentation](https://www.cockroachlabs.com/docs/stable/demo-replication-and-rebalancing.html) for more information on manual rebalancing.

 ### Useful resources

--- a/src/health/guides/dbengine/10min_dbengine_global_flushing_errors.md
+++ b/src/health/guides/dbengine/10min_dbengine_global_flushing_errors.md
@ -9,5 +9,5 @@ faster disks. This alert is triggered in critical state when the number deleted

 ### Useful resources

-[Read more about Netdata DB engine](https://learn.netdata.cloud/docs/agent/database/engine)
+[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)

--- a/src/health/guides/dbengine/10min_dbengine_global_flushing_warnings.md
+++ b/src/health/guides/dbengine/10min_dbengine_global_flushing_warnings.md
@ -11,5 +11,5 @@ This alert is triggered in warn state when the number of `dbengine` dirty pages

 ### Useful resources

-[Read more about Netdata DB engine](https://learn.netdata.cloud/docs/agent/database/engine)
+[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)

--- a/src/health/guides/dbengine/10min_dbengine_global_fs_errors.md
+++ b/src/health/guides/dbengine/10min_dbengine_global_fs_errors.md
@ -10,5 +10,5 @@ This alert is triggered in warning state when the number of filesystem errors is

 ### Useful resources

-[Read more about Netdata DB engine](https://learn.netdata.cloud/docs/agent/database/engine)
+[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)

--- a/src/health/guides/dbengine/10min_dbengine_global_io_errors.md
+++ b/src/health/guides/dbengine/10min_dbengine_global_io_errors.md
@ -10,5 +10,5 @@ This alert is triggered in critical state when the number of IO errors is greate

 ### Useful resources

-[Read more about Netdata DB engine](https://learn.netdata.cloud/docs/agent/database/engine)
+[Read more about Netdata DB engine](https://github.com/netdata/netdata/blob/master/src/database/README.md/engine)

--- a/src/health/guides/entropy/lowest_entropy.md
+++ b/src/health/guides/entropy/lowest_entropy.md
@ -4,7 +4,7 @@ This alert presents the minimum amount of entropy in the kernel entropy pool in

 The Netdata Agent checks for the minimum entropy value in the last 5 minutes. The alert gets raised into warning if the value < 100, and cleared if the value > 200.  

-For further information on how our alerts are calculated, please have a look at our [Documentation](https://learn.netdata.cloud/docs/agent/health/reference#expressions).
+For further information on how our alerts are calculated, please have a look at our [Documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#expressions).

 ### What is entropy and why do we need it?

--- a/src/health/guides/exporting/exporting_last_buffering.md
+++ b/src/health/guides/exporting/exporting_last_buffering.md
@ -26,4 +26,4 @@ This alert is related to the Netdata Exporting engine, which calculates the numb

 ### Useful resources

-1. [Netdata Exporting Engine](https://learn.netdata.cloud/docs/exporting-data-to-other-systems/exporting-reference)
+1. [Netdata Exporting Reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md)
--- a/src/health/guides/exporting/exporting_metrics_sent.md
+++ b/src/health/guides/exporting/exporting_metrics_sent.md
@ -43,4 +43,4 @@ To troubleshoot this alert, follow these steps:

 ### Useful resources

-1. [Netdata Exporting Engine documentation](https://learn.netdata.cloud/docs/exporting-data-to-other-systems/exporting-reference)
+1. [Netdata Exporting Reference](https://github.com/netdata/netdata/blob/master/src/exporting/README.md)
--- a/src/health/guides/httpcheck/httpcheck_web_service_bad_content.md
+++ b/src/health/guides/httpcheck/httpcheck_web_service_bad_content.md
@ -27,4 +27,4 @@ sudo ./edit-config go.d/httpcheck.conf

 ### Useful resources

-1. [HTTP endpoint monitoring with Netdata](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/httpcheck)
+1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
--- a/src/health/guides/httpcheck/httpcheck_web_service_bad_status.md
+++ b/src/health/guides/httpcheck/httpcheck_web_service_bad_status.md
@ -18,4 +18,4 @@ root@netdata # curl -v <your_http_endpoint>:<port>/<path>

 ### Useful resources

-1. [HTTP endpoint monitoring with Netdata](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/httpcheck)
+1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
--- a/src/health/guides/httpcheck/httpcheck_web_service_slow.md
+++ b/src/health/guides/httpcheck/httpcheck_web_service_slow.md
@ -14,5 +14,5 @@ To troubleshoot this issue, check for:

 ### Useful resources

-1. [HTTP endpoint monitoring with Netdata](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/httpcheck)
+1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)

--- a/src/health/guides/httpcheck/httpcheck_web_service_timeouts.md
+++ b/src/health/guides/httpcheck/httpcheck_web_service_timeouts.md
@ -15,7 +15,7 @@ An HTTP request timeout occurs when a client (such as a web browser) sends a req

 - Verify the issue

-Check the HTTP endpoint to see if it is responsive and reachable. You can use tools like `curl` or online services like [https://www.isitdownrightnow.com/](https://www.isitdownrightnow.com/) to check the availability of the website or service.
+Check the HTTP endpoint to see if it is responsive and reachable. You can use tools like `curl` or online services like <https://www.isitdownrightnow.com/> to check the availability of the website or service.

 - Analyze server logs

@ -36,4 +36,3 @@ Make sure your web server configurations are optimized for performance. For inst
 - Verify network configurations

 Examine the network configurations for potential issues that can lead to HTTP request timeouts. Check for misconfigured firewalls or faulty load balancers that may be interfering with traffic to the HTTP endpoint.
-
--- a/src/health/guides/httpcheck/httpcheck_web_service_unreachable.md
+++ b/src/health/guides/httpcheck/httpcheck_web_service_unreachable.md
@ -30,4 +30,4 @@ To troubleshoot this error, check the following:

 ### Useful resources

-1. [HTTP endpoint monitoring with Netdata](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/httpcheck)
+1. [HTTP endpoint monitoring with Netdata](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/modules/httpcheck/integrations/http_endpoints.md)
--- a/src/health/guides/ipc/semaphores_used.md
+++ b/src/health/guides/ipc/semaphores_used.md
@ -44,5 +44,4 @@ This alert monitors the percentage of allocated `System V IPC semaphores`. If yo
 ### Useful resources

 1. [Interprocess Communication](https://docs.oracle.com/cd/E19455-01/806-4750/6jdqdfltn/index.html)
-2. [IPC: Semaphores](https://users.cs.cf.ac.uk/Dave.Marshall/C/node26.html)
-3. [Linux Kernel Documentation - IPC Semaphores](https://www.kernel.org/doc/Documentation/ipc/semaphore.txt)
+2. [IPC: Semaphores](https://users.cs.cf.ac.uk/Dave.Marshall/C/node26.html)
--- a/src/health/guides/load/load_average_15.md
+++ b/src/health/guides/load/load_average_15.md
@ -4,7 +4,7 @@ This alarm calculates the system `load average` (CPU and I/O demand) over the pe

 The alert gets raised into warning if the metric is 2 times the expected value and cleared if the value is 1.75 times the expected value.

-For further information on how our alerts are calculated, please have a look at our [Documentation](https://learn.netdata.cloud/docs/agent/health/reference#expressions).
+For further information on how our alerts are calculated, please have a look at our [Documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#expressions).

 ### What does "load average" mean?

--- a/src/health/guides/load/load_average_5.md
+++ b/src/health/guides/load/load_average_5.md
@ -4,7 +4,7 @@ This alarm calculates the system `load average` (CPU and I/O demand) over the pe

 The alert gets raised into warning if the metric is 4 times the expected value and cleared if the value is 3.5 times the expected value.

-For further information on how our alerts are calculated, please have a look at our [Documentation](https://learn.netdata.cloud/docs/agent/health/reference#expressions).
+For further information on how our alerts are calculated, please have a look at our [Documentation](https://github.com/netdata/netdata/blob/master/src/health/REFERENCE.md#expressions).


 ### What does "load average" mean?
--- a/src/health/guides/mdstat/mdstat_nonredundant_last_collected.md
+++ b/src/health/guides/mdstat/mdstat_nonredundant_last_collected.md
@ -52,4 +52,4 @@ The md (multiple device) driver is responsible for managing software RAID arrays
 ### Useful resources

 1. [Linux RAID: A Quick Guide](https://www.cyberciti.biz/tips/linux-raid-increase-resync-rebuild-speed.html)
-2. [Netdata Agent Configuration Guide](https://learn.netdata.cloud/docs/agent/daemon/config)
+2. [Netdata Agent Configuration Guide](https://github.com/netdata/netdata/blob/master/src/daemon/config/README.md)
--- a/src/health/guides/ml/ml_1min_node_ar.md
+++ b/src/health/guides/ml/ml_1min_node_ar.md
@ -1,8 +1,8 @@
 ### Understand the alert

-This alert is triggered when the [node anomaly rate](https://learn.netdata.cloud/docs/ml-and-troubleshooting/machine-learning-ml-powered-anomaly-detection#node-anomaly-rate) exceeds the threshold defined in the [alert configuration](https://github.com/netdata/netdata/blob/master/src/health/health.d/ml.conf) over the most recent 1 minute window evaluated. 
+This alert is triggered when the [node anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md) exceeds the threshold defined in the [alert configuration](https://github.com/netdata/netdata/blob/master/src/health/health.d/ml.conf) over the most recent 1 minute window evaluated. 

-For example, with the default of `warn: $this > 1`, this means that 1% or more of the metrics collected on the node have across the most recent 1 minute window been flagged as [anomalous](https://learn.netdata.cloud/docs/ml-and-troubleshooting/machine-learning-ml-powered-anomaly-detection) by Netdata.
+For example, with the default of `warn: $this > 1`, this means that 1% or more of the metrics collected on the node have across the most recent 1 minute window been flagged as [anomalous](https://github.com/netdata/netdata/blob/master/src/ml/README.md) by Netdata.

 ### Troubleshoot the alert

@ -12,15 +12,15 @@ This alert is a signal that some significant percentage of metrics within your i

 2. **Highlight the area of interest**: Highlight the timeframne of interest where you see an elevated anomaly rate.

-3. **Check the anomalies tab**: Check the [Anomaly Advisor](https://learn.netdata.cloud/docs/ml-and-troubleshooting/anomaly-advisor) ("Anomalies" tab) to see an ordered list of what metrics were most anomalous in the highlighted window.
+3. **Check the anomalies tab**: Check the [Anomaly Advisor tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md) to see an ordered list of what metrics were most anomalous in the highlighted window.

 4. **Press the AR% button on Overview**: You can also press the "[AR%](https://blog.netdata.cloud/anomaly-rates-in-the-menu/)" button on the Overview or single node dashboard to see what parts of the menu have the highest chart anomaly rates. Pressing the AR% button should add some "pills" to each menu item and if you hover over it you will see that chart within each menu section that was most anomalous during the highlighted timeframe. 

-5. **Use Metric Correlations**: Use [metric correlations](https://learn.netdata.cloud/docs/ml-and-troubleshooting/metric-correlations) to see what metrics may have changed most significantly comparing before to the highlighted timeframe.
+5. **Use Metric Correlations**: Use [metric correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md) to see what metrics may have changed most significantly comparing before to the highlighted timeframe.

 ### Useful resources

-1. [Machine learning (ML) powered anomaly detection](https://learn.netdata.cloud/docs/ml-and-troubleshooting/machine-learning-ml-powered-anomaly-detection)
-2. [Anomaly Advisor](https://learn.netdata.cloud/docs/ml-and-troubleshooting/anomaly-advisor)
-3. [Metric Correlations](https://learn.netdata.cloud/docs/ml-and-troubleshooting/metric-correlations)
+1. [Machine learning (ML) powered anomaly detection](https://github.com/netdata/netdata/blob/master/src/ml/README.md)
+2. [Anomaly Advisor tab](https://github.com/netdata/netdata/blob/master/docs/dashboards-and-charts/anomaly-advisor-tab.md)
+3. [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/metric-correlations.md)
 4. [Anomaly Rates in the Menu!](https://blog.netdata.cloud/anomaly-rates-in-the-menu/)
--- a/src/health/guides/net/outbound_packets_dropped.md
+++ b/src/health/guides/net/outbound_packets_dropped.md
@ -14,7 +14,7 @@ Check the alert message for the `${label:device}` placeholder. It indicates the

 2. Verify network congestion or excessive traffic:

-Excessive traffic or network congestion can lead to dropped packets. To check network traffic, use the `nload` tool. If it isn't installed, you can follow the instructions given [here](https://www.howtoforge.com/tutorial/install-nload-on-linux/).
+Excessive traffic or network congestion can lead to dropped packets. To check network traffic, use the `nload` tool.

 ```bash
 nload ${label:device}
@ -22,7 +22,7 @@ nload ${label:device}

 This will display the current network bandwidth usage on the specified interface. Look for unusually high or fluctuating usage patterns, which could indicate congestion or excessive traffic.

-3. Verify hardware issues:
+1. Verify hardware issues:

 Check the network interface and related hardware components (such as the network card, cables, and switches) for visible damage, loose connections, or other issues. Replace any defective components as needed.

--- a/src/health/guides/portcheck/portcheck_connection_timeouts.md
+++ b/src/health/guides/portcheck/portcheck_connection_timeouts.md
@ -37,5 +37,4 @@ This alert triggers a warning state when the ratio of timeouts is between 10-40%
 ### Useful resources

 1. [Netstat Command in Linux](https://www.tecmint.com/20-netstat-commands-for-linux-network-management/)
-2. [Iostat Command Usage and Examples](https://www.thomas-krenn.com/en/wiki/Iostat_command_usage_and_examples)
-3. [Iftop Guide](https://www.tecmint.com/iftop-linux-network-bandwidth-monitoring-tool/)
+2. [Iftop Guide](https://www.tecmint.com/iftop-linux-network-bandwidth-monitoring-tool/)
--- a/src/health/guides/postgres/postgres_table_cache_io_ratio.md
+++ b/src/health/guides/postgres/postgres_table_cache_io_ratio.md
@ -28,5 +28,4 @@ Keep monitoring cache hit ratios after making changes to your configuration or o

 ### Useful resources

-1. [Tuning Your PostgreSQL Server](https://www.postgresql.org/docs/current/runtime-config-resource.html)
-2. [Performance Monitoring and Tuning in PostgreSQL](https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/postgres#monitoring)
+1. [Tuning Your PostgreSQL Server](https://www.postgresql.org/docs/current/runtime-config-resource.html)
--- a/src/health/guides/riakkv/riakkv_kv_get_slow.md
+++ b/src/health/guides/riakkv/riakkv_kv_get_slow.md
@ -17,6 +17,5 @@ The `riakkv_kv_get_slow` alert is related to Riak KV, a distributed NoSQL key-va
 ### Useful resources

 1. [Riak KV documentation](https://riak.com/documentation/)
-2. [Monitoring Riak KV with Netdata](https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/riakkv/)
-3. [Riak Control: Monitoring and Administration Interface](https://docs.riak.com/riak/kv/2.2.3/configuring/reference/riak-vars/#riak-control)
-4. [Riak KV Monitoring and Metrics](https://docs.riak.com/riak/kv/2.2.3/using/performance/monitoring/index.html)
+2. [Riak Control: Monitoring and Administration Interface](https://docs.riak.com/riak/kv/2.2.3/configuring/reference/riak-vars/#riak-control)
+3. [Riak KV Monitoring and Metrics](https://docs.riak.com/riak/kv/2.2.3/using/performance/monitoring/index.html)
--- a/src/health/guides/vernemq/vernemq_mqtt_pubcomp_unexpected.md
+++ b/src/health/guides/vernemq/vernemq_mqtt_pubcomp_unexpected.md
@ -25,5 +25,5 @@ In MQTT, the PUBCOMP packet is used when QoS (Quality of Service) 2 is applied.

 ### Useful resources

-1. [VerneMQ Documentation](https://vernemq.com/documentation/)
+1. [VerneMQ Documentation](https://docs.vernemq.com/)
 2. [MQTT Specification - MQTT Control Packets](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901046)
--- a/src/health/guides/vernemq/vernemq_mqtt_pubrec_sent_reason_unsuccessful.md
+++ b/src/health/guides/vernemq/vernemq_mqtt_pubrec_sent_reason_unsuccessful.md
@ -25,6 +25,6 @@ In the MQTT protocol, when a client sends a PUBLISH message with Quality of Serv

 ### Useful resources

-1. [VerneMQ Documentation](https://vernemq.com/documentation.html)
+1. [VerneMQ Documentation](https://docs.vernemq.com/)
 2. [MQTT Essentials – All Core MQTT Concepts explained](https://www.hivemq.com/mqtt-essentials/)
 3. [Understanding QoS Levels in MQTT](https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/)
--- a/src/health/guides/vernemq/vernemq_mqtt_pubrel_sent_reason_unsuccessful.md
+++ b/src/health/guides/vernemq/vernemq_mqtt_pubrel_sent_reason_unsuccessful.md
@ -45,5 +45,4 @@ This alert is related to VerneMQ, a high-performance MQTT broker. It monitors th
 ### Useful resources

 1. [VerneMQ - Official Documentation](https://docs.vernemq.com/)
-2. [MQTT Essentials: Quality of Service 2 (QoS 2)](https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/)
-3. [Netdata - VerneMQ monitoring](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/vernemq)
+2. [MQTT Essentials: Quality of Service 2 (QoS 2)](https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/)
--- a/src/health/guides/vernemq/vernemq_queue_message_expired.md
+++ b/src/health/guides/vernemq/vernemq_queue_message_expired.md
@ -50,4 +50,3 @@ Expired messages are removed from the queue and are not delivered to subscribers
 ### Useful resources

 1. [VerneMQ Documentation](https://vernemq.com/docs/)
-2. [How to Monitor VerneMQ MQTT broker with Netdata](https://learn.netdata.cloud/guides/monitor/vernemq.html)
--- a/src/health/guides/vsphere/vsphere_host_mem_usage.md
+++ b/src/health/guides/vsphere/vsphere_host_mem_usage.md
@ -28,6 +28,5 @@ The `vsphere_host_mem_usage` alert is triggered when the memory utilization of a

 ### Useful resources

-1. [Understanding Memory Utilization in VMware vSphere Host](https://www.altaro.com/vmware/memory-utilization-vmware-esxi/)
-2. [vSphere Monitoring and Performance Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-115861E6-810A-43BB-8CDB-EE99CF8F3250.html)
-3. [Optimizing Memory Performance in VMware vSphere](https://blogs.vmware.com/performance/2021/04/optimizing-memory-performance-in-vmware-vsphere.html)
+1. [vSphere Monitoring and Performance Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-115861E6-810A-43BB-8CDB-EE99CF8F3250.html)
+2. [Optimizing Memory Performance in VMware vSphere](https://blogs.vmware.com/performance/2021/04/optimizing-memory-performance-in-vmware-vsphere.html)
--- a/src/health/guides/web_log/web_log_1m_total_requests.md
+++ b/src/health/guides/web_log/web_log_1m_total_requests.md
@ -30,7 +30,4 @@ An increase in workload means that your web server is handling more traffic than

 ### Useful resources

-1. [Analyzing Web server logs with ApacheTop](https://www.howtoforge.com/how-to-analyze-apache-web-server-logs-apachetop)
-2. [Logstash Guide: Analyzing Logs](https://www.elastic.co/guide/en/logstash/current/logstash-intro.html)
-3. [Web Application Performance Monitoring with New Relic](https://newrelic.com/platform/web-application-monitoring)
-4. [Vertically or Horizontally Scaling Your Web Server](https://www.digitalocean.com/community/tutorials/5-common-server-setups-for-your-web-application)
+1. [Vertically or Horizontally Scaling Your Web Server](https://www.digitalocean.com/community/tutorials/5-common-server-setups-for-your-web-application)
--- a/src/health/guides/web_log/web_log_1m_unmatched.md
+++ b/src/health/guides/web_log/web_log_1m_unmatched.md
@ -12,14 +12,4 @@ Web servers like NGINX and Apache2 give you the ability to modify the log patter

 You must create a new job in the `web_log` collector for your Agent.

-1. See how you can [configure this collector](https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/web_log#configuration)
-
-2. Follow the job template specified in the [default web_log.conf file](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/web_log/web_log.conf#L53-L86), focus on the lines [83:85](https://github.com/netdata/netdata/blob/e6d9fbc4a53f1d35363e9b342231bb11627bafbd/collectors/python.d.plugin/web_log/web_log.conf#L83-L85) where you can see how you define a `custom_log_format`.
-
-3. Restart the Netdata Agent
-   ```
-   systemctl restart netdata
-   ```
-
-
-
+1. See how you can [configure this collector](https://github.com/netdata/netdata/tree/master/src/go/collectors/go.d.plugin/modules/weblog#configuration)
--- a/src/health/guides/web_log/web_log_5m_successful.md
+++ b/src/health/guides/web_log/web_log_5m_successful.md
@ -31,6 +31,4 @@ A successful HTTP request is one that receives a response with an HTTP status co
 ### Useful resources

 1. [Apache Log Files](https://httpd.apache.org/docs/current/logs.html)
-2. [Nginx Log Files](https://nginx.org/en/docs/ngx_core_module.html#error_log)
-3. [Introduction to Identifying Security Vulnerabilities in Web Servers](https://www.acunetix.com/blog/articles/introduction-identifying-security-vulnerabilities-web-servers)
-4. [Web Application Performance Analysis and Monitoring](https://www.site24x7.com/learning/web-application-performance.html)
+2. [Nginx Log Files](https://nginx.org/en/docs/ngx_core_module.html#error_log)
--- a/src/health/guides/web_log/web_log_web_slow.md
+++ b/src/health/guides/web_log/web_log_web_slow.md
@ -41,8 +41,7 @@ There are several factors that can cause slow web server performance. To trouble

 ### Useful resources

-1. [Optimizing NGINX for Performance](https://easyengine.io/tutorials/nginx/performance/)
-2. [Apache Performance Tuning](https://httpd.apache.org/docs/2.4/misc/perf-tuning.html)
-3. [Top 10 MySQL Performance Tuning Tips](https://www.databasejournal.com/features/mysql/top-10-mysql-performance-tuning-tips.html)
-4. [10 Tips for Optimal PostgreSQL Performance](https://www.digitalocean.com/community/tutorials/10-tips-for-optimizing-postgresql-performance-on-a-digitalocean-droplet)
-5. [A Beginner's Guide to HTTP Cache Headers](https://www.keycdn.com/blog/http-cache-headers)
+1. [Apache Performance Tuning](https://httpd.apache.org/docs/2.4/misc/perf-tuning.html)
+2. [Top 10 MySQL Performance Tuning Tips](https://www.databasejournal.com/features/mysql/top-10-mysql-performance-tuning-tips.html)
+3. [10 Tips for Optimal PostgreSQL Performance](https://www.digitalocean.com/community/tutorials/10-tips-for-optimizing-postgresql-performance-on-a-digitalocean-droplet)
+4. [A Beginner's Guide to HTTP Cache Headers](https://www.keycdn.com/blog/http-cache-headers)
--- a/src/health/guides/wifi/wifi_inbound_packets_dropped_ratio.md
+++ b/src/health/guides/wifi/wifi_inbound_packets_dropped_ratio.md
@ -47,6 +47,5 @@ sudo tcpdump -i <interface_name>

 1. [Top 20 Netstat Command Examples in Linux](https://www.tecmint.com/20-netstat-commands-for-linux-network-management/)
 2. [iftop command in Linux to monitor network traffic](https://www.tecmint.com/iftop-linux-network-bandwidth-monitoring-tool/)
-3. [An Overview of Packet Sniffing using Tcpdump](https://www.ubuntupit.com/tcpdump-useful-unix-packet-sniffer-command/)

 Remember to replace `<interface_name>` with the actual name of the WiFi network interface causing the alert.
--- a/src/health/guides/wifi/wifi_outbound_packets_dropped_ratio.md
+++ b/src/health/guides/wifi/wifi_outbound_packets_dropped_ratio.md
@ -49,6 +49,4 @@ You can adjust network settings, like buffers or queues, to mitigate dropped pac
 ### Useful resources

 1. [ifconfig command in Linux](https://www.geeksforgeeks.org/ifconfig-command-in-linux-with-examples/)
-2. [How to monitor network usage with iftop](https://www.binarytides.com/monitor-network-usage-with-iftop/)
-3. [nload – Monitor Network Traffic and Bandwidth Usage in Real Time](https://www.tecmint.com/nload-monitor-linux-network-traffic-bandwidth-usage/)
-4. [VNstat – A Network Traffic Monitor](https://www.tecmint.com/vnstat-monitor-network-traffic-in-linux/)
+2. [nload – Monitor Network Traffic and Bandwidth Usage in Real Time](https://www.tecmint.com/nload-monitor-linux-network-traffic-bandwidth-usage/)
--- a/src/health/guides/windows/windows_10min_cpu_usage.md
+++ b/src/health/guides/windows/windows_10min_cpu_usage.md
@ -30,7 +30,6 @@ This alert calculates the average total `CPU utilization` on a Windows system ov

 ### Useful resources

-1. [How to Monitor CPU Usage on Windows](https://www.tomsguide.com/how-to/how-to-monitor-cpu-usage-on-windows)
-2. [Windows Task Manager: A Troubleshooting Guide](https://www.howtogeek.com/66622/stupid-geek-tricks-6-ways-to-open-windows-task-manager/)
-3. [How to Use the Performance Monitor on Windows](https://www.digitalcitizen.life/how-use-performance-monitor-windows/)
-4. [Understanding Process Explorer](https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer)
+1. [Windows Task Manager: A Troubleshooting Guide](https://www.howtogeek.com/66622/stupid-geek-tricks-6-ways-to-open-windows-task-manager/)
+2. [How to Use the Performance Monitor on Windows](https://www.digitalcitizen.life/how-use-performance-monitor-windows/)
+3. [Understanding Process Explorer](https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer)
--- a/src/health/guides/windows/windows_disk_in_use.md
+++ b/src/health/guides/windows/windows_disk_in_use.md
@ -30,5 +30,4 @@ Disk space utilization is crucial for the stable and efficient operation of your
 ### Useful resources

 1. [Windows 10 Tips & Tricks: Analyze Disk Space & Free Space - YouTube](https://www.youtube.com/watch?v=NolLC9tBP_Y)
-2. [5 Free Tools to Visualize Disk Space Usage on Windows](https://www.hongkiat.com/blog/visualize-hard-disk-usage-free-tools-for-windows/)
-3. [10 Ways to Free Up Hard Drive Space on Windows](https://www.howtogeek.com/125923/7-ways-to-free-up-hard-disk-space-on-windows/)
+2. [10 Ways to Free Up Hard Drive Space on Windows](https://www.howtogeek.com/125923/7-ways-to-free-up-hard-disk-space-on-windows/)
--- a/src/health/guides/windows/windows_inbound_packets_discarded.md
+++ b/src/health/guides/windows/windows_inbound_packets_discarded.md
@ -35,5 +35,4 @@ Packet corruption can be caused by faulty hardware, software issues, or even cyb
 ### Useful resources

 1. [Windows Performance Monitor](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/perfmon)
-2. [Windows Event Viewer](https://docs.microsoft.com/en-us/windows/win32/eventlog/event-log-reference)
-3. [How to troubleshoot networking problems on the Windows platform](https://support.microsoft.com/en-us/help/10267)
+2. [Windows Event Viewer](https://docs.microsoft.com/en-us/windows/win32/eventlog/event-log-reference)
--- a/src/health/guides/windows/windows_inbound_packets_errors.md
+++ b/src/health/guides/windows/windows_inbound_packets_errors.md
@ -37,5 +37,4 @@ To troubleshoot this alert, you can perform the following steps:
 ### Useful resources

 1. [How to use Network Monitor in Windows](https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-tcpip-network-monitor)
-2. [Network Troubleshooting Guide for Windows](https://techcommunity.microsoft.com/t5/networking-blog/network-troubleshooting-guide-for-windows/ba-p/428114)
-3. [How to Troubleshoot Network Connections with Ping and Tracert](https://www.windowscentral.com/how-troubleshoot-network-connection-ping-and-traceroute)
+2. [Network Troubleshooting Guide for Windows](https://techcommunity.microsoft.com/t5/networking-blog/network-troubleshooting-guide-for-windows/ba-p/428114)
--- a/src/health/guides/windows/windows_outbound_packets_discarded.md
+++ b/src/health/guides/windows/windows_outbound_packets_discarded.md
@ -44,5 +44,4 @@ If your network is congested, it can cause an increase in discarded packets. Con
 ### Useful resources

 1. [Using Performance Monitor to monitor network performance](https://techcommunity.microsoft.com/t5/ask-the-performance-team/using-perfmon-to-monitor-your-servers-network-performance/ba-p/373944)
-2. [Monitoring Network Performance with Resource Monitor](https://www.online-tech-tips.com/computer-tips/monitoring-network-performance-with-resource-monitor/)
-3. [Event Viewer in Windows](https://www.dummies.com/computers/operating-systems/windows-10/how-to-use-event-viewer-in-windows-10/)
+2. [Event Viewer in Windows](https://www.dummies.com/computers/operating-systems/windows-10/how-to-use-event-viewer-in-windows-10/)
--- a/src/health/guides/windows/windows_outbound_packets_errors.md
+++ b/src/health/guides/windows/windows_outbound_packets_errors.md
@ -40,7 +40,6 @@ Ensure that your network interface card (NIC) drivers and firmware are up-to-dat

 ### Useful resources

-1. [Netstat Command Usage on Windows](https://www.computerhope.com/issues/ch001/stat.htm)
-2. [Wireshark - A Network Protocol Analyzer](https://www.wireshark.org/)
-3. [Tcpdump - A Packet Analyzer](https://www.tcpdump.org/)
-4. [Network Performance Monitoring and Diagnostics Guide](https://docs.microsoft.com/en-us/windows-server/networking/technologies/npmd/npmd)
+1. [Wireshark - A Network Protocol Analyzer](https://www.wireshark.org/)
+2. [Tcpdump - A Packet Analyzer](https://www.tcpdump.org/)
+3. [Network Performance Monitoring and Diagnostics Guide](https://docs.microsoft.com/en-us/windows-server/networking/technologies/npmd/npmd)
--- a/src/health/guides/windows/windows_ram_in_use.md
+++ b/src/health/guides/windows/windows_ram_in_use.md
@ -33,6 +33,4 @@ Memory utilization refers to the percentage of a system's RAM that is currently

 ### Useful resources

-1. [How to use Task Manager to monitor Windows PC's performance](https://support.microsoft.com/en-us/windows/how-to-use-task-manager-to-monitor-windows-pc-s-performance-171100cb-5e7d-aaba-29abfedfb06f)
-2. [How to use Performance Monitor on Windows 10](https://www.windowscentral.com/how-use-performance-monitor-windows-10)
-3. [How to fix high memory usage in Windows](https://pureinfotech.com/reduce-ram-memory-usage-windows/)
+1. [How to use Performance Monitor on Windows 10](https://www.windowscentral.com/how-use-performance-monitor-windows-10)
--- a/src/health/guides/windows/windows_swap_in_use.md
+++ b/src/health/guides/windows/windows_swap_in_use.md
@ -36,6 +36,5 @@ Swap memory is a virtual memory management technique where a portion of the disk

 ### Useful resources

-1. [How to Manage Virtual Memory (Pagefile) in Windows 10](https://www.techbout.com/manage-virtual-memory-pagefile-windows-10-29638/)
-2. [Troubleshooting Windows Performance Issues Using the Resource Monitor](https://docs.microsoft.com/en-us/archive/blogs/askcore/troubleshooting-windows-performance-issues-using-the-resource-monitor)
-3. [Windows Performance Monitor](https://docs.microsoft.com/en-us/windows-server/administration/windows-server-2008-help/troubleshoot/windows-rel-performance-monitor)
+1. [Troubleshooting Windows Performance Issues Using the Resource Monitor](https://docs.microsoft.com/en-us/archive/blogs/askcore/troubleshooting-windows-performance-issues-using-the-resource-monitor)
+2. [Windows Performance Monitor](https://docs.microsoft.com/en-us/windows-server/administration/windows-server-2008-help/troubleshoot/windows-rel-performance-monitor)
--- a/src/health/guides/x509check/x509check_days_until_expiration.md
+++ b/src/health/guides/x509check/x509check_days_until_expiration.md
@ -41,5 +41,4 @@ If there are still issues or the alert persists, double-check your certificate m
 ### Useful resources

 1. [Sectigo: What is an X.509 certificate?](https://sectigo.com/resource-library/what-is-x509-certificate)
-2. [Netdata: x509 certificate monitoring](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/x509check)
-3. [OpenSSL: X.509 Certificate Commands](https://www.openssl.org/docs/man1.1.1/man1/x509.html)
+2. [OpenSSL: X.509 Certificate Commands](https://www.openssl.org/docs/man1.1.1/man1/x509.html)
--- a/src/health/guides/x509check/x509check_revocation_status.md
+++ b/src/health/guides/x509check/x509check_revocation_status.md
@ -28,8 +28,6 @@ This alert indicates that the X.509 certificate has been revoked, meaning that i

 ### Useful resources

-1. [X.509 Certificate Monitoring with Netdata](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/x509check)
-2. [How to use OpenSSL to verify a certificate against a CRL](https://raymii.org/s/tutorials/OpenSSL_command_line_Root_and_Intermediate_CA_including_OCSP_CRL_Signed_Certs.html)
-3. [SSL Shopper's SSL Checker](https://www.sslshopper.com/ssl-checker.html)
-4. [Renewing certificates with Certbot](https://certbot.eff.org/docs/using.html#renewing-certificates)
-5. [Creating a Self-Signed SSL Certificate](https://www.akadia.com/services/ssh_test_certificate.html)
+1. [SSL Shopper's SSL Checker](https://www.sslshopper.com/ssl-checker.html)
+2. [Renewing certificates with Certbot](https://certbot.eff.org/docs/using.html#renewing-certificates)
+3. [Creating a Self-Signed SSL Certificate](https://www.akadia.com/services/ssh_test_certificate.html)
--- a/src/streaming/README.md
+++ b/src/streaming/README.md
@ -491,7 +491,7 @@ You can monitor the replication process in two ways:
 ### Replication history

 Replication history in [dbengine](https://github.com/netdata/netdata/blob/master/src/database/README.md) mode is limited
-by [Tier 0 retention](https://learn.netdata.cloud/docs/configuring/optimizing-metrics-database/change-how-long-netdata-stores-metrics#effect-of-storage-tiers-and-disk-space-on-retention):
+by [Tier 0 retention](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md#effect-of-storage-tiers-and-disk-space-on-retention):

 - Child instances replicate only Tier 0 data.
 - Parent instance calculates higher-level tiers using Tier 0 as the basis.
--- a/src/web/README.md
+++ b/src/web/README.md
@ -15,9 +15,7 @@ There are two primary ways to view Netdata's dashboards on the agent:

 2.  The [`dashboard.js` JavaScript library](#dashboardjs), which helps you
   [customize the standard dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/README.md#customizing-the-local-dashboard)
-   using JavaScript, or create entirely new [custom dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md) or
-   [Atlassian Confluence dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/confluence/README.md).
-
+   using JavaScript, or create entirely new [custom dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md)
 You can also view all the data Netdata collects through the [REST API v1](https://github.com/netdata/netdata/blob/master/src/web/api/README.md#netdata-rest-api).

 ## dashboard.js
--- a/src/web/gui/README.md
+++ b/src/web/gui/README.md
@ -161,5 +161,4 @@ file](https://user-images.githubusercontent.com/1153921/62798924-570e6c80-ba94-1

 ## Custom dashboards

-For information on creating custom dashboards from scratch, see the [custom dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md) or
-[Atlassian Confluence dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/confluence/README.md) guides.
+For information on creating custom dashboards from scratch, see the [custom dashboards](https://github.com/netdata/netdata/blob/master/src/web/gui/custom/README.md) guide.