Adding upstream version 1.38.0.upstream/1.38.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

3 files changed, 29 insertions, 27 deletions

diff --git a/docs/overview/netdata-monitoring-stack.md b/docs/overview/netdata-monitoring-stack.md
index ae9252272..36f5b5f06 100644
--- a/docs/overview/netdata-monitoring-stack.md
+++ b/docs/overview/netdata-monitoring-stack.md
@@ -22,7 +22,7 @@ Here are a few ways to enrich your existing monitoring and troubleshooting stack
 ## Collect metrics from Prometheus endpoints
 
 Netdata automatically detects 600 popular endpoints and collects per-second metrics from them via the [generic
-Prometheus collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus). This even
+Prometheus collector](https://github.com/netdata/go.d.plugin/blob/master/modules/prometheus/README.md). This even
 includes support for Windows 10 via [`windows_exporter`](https://github.com/prometheus-community/windows_exporter).
 
 This collector is installed and enabled on all Agent installations by default, so you don't need to waste time
@@ -35,8 +35,8 @@ troubleshoot anomalies.
 Netdata can send its per-second metrics to external time-series databases, such as InfluxDB, Prometheus, Graphite,
 TimescaleDB, ElasticSearch, AWS Kinesis Data Streams, Google Cloud Pub/Sub Service, and many others.
 
-To [export metrics to external time-series databases](/docs/export/external-databases.md), you configure an [exporting
-_connector_](/docs/export/enable-connector.md). These connectors support filtering and resampling for granular control
+To [export metrics to external time-series databases](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md), you configure an [exporting
+_connector_](https://github.com/netdata/netdata/blob/master/docs/export/enable-connector.md). These connectors support filtering and resampling for granular control
 over which metrics you export, and at what volume. You can export resampled metrics as collected, as averages, or the
 sum of interpolated values based on your needs and other monitoring tools.
 
@@ -57,6 +57,6 @@ charts, or use Netdata's health watchdog to send notifications whenever an anoma
 ## What's next?
 
 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).
+Netdata**](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx).
 
 
diff --git a/docs/overview/what-is-netdata.md b/docs/overview/what-is-netdata.md
index 3df1d949b..f8e67159b 100644
--- a/docs/overview/what-is-netdata.md
+++ b/docs/overview/what-is-netdata.md
@@ -18,7 +18,8 @@ Netdata's distributed monitoring Agent collects thousands of metrics from system
 configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT
 devices.
 
-You can [install](/docs/get-started.mdx) Netdata on most Linux distributions (Ubuntu, Debian, CentOS, and more),
+You can [install](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx) Netdata on most Linux
+distributions (Ubuntu, Debian, CentOS, and more),
 container/microservice platforms (Kubernetes clusters, Docker), and many other operating systems (FreeBSD, macOS), with
 no `sudo` required.
 
@@ -46,29 +47,30 @@ you're viewing the Netdata Cloud interface.
 Netdata is designed to be both simple to use and flexible for every monitoring, visualization, and troubleshooting use
 case:
 
--   **Collect**: Netdata collects all available metrics from your system and applications with 300+ collectors,
-    Kubernetes service discovery, and in-depth container monitoring, all while using only 1% CPU and a few MB of RAM. It
-    even collects metrics from Windows machines.
--   **Visualize**: The dashboard meaningfully presents charts to help you understand the relationships between your
-    hardware, operating system, running apps/services, and the rest of your infrastructure. Add nodes to Netdata Cloud
-    for a complete view of your infrastructure from a single pane of glass.
--   **Monitor**: Netdata's health watchdog uses hundreds of preconfigured alarms to notify you via Slack, email,
-    PagerDuty and more when an anomaly strikes. Customize with dynamic thresholds, hysteresis, alarm templates, and
-    role-based notifications.
--   **Troubleshoot**: 1s granularity helps you detect and analyze anomalies other monitoring platforms might have
-    missed. Interactive visualizations reduce your reliance on the console, and historical metrics help you trace issues
-    back to their root cause.
--   **Store**: Netdata's efficient database engine efficiently stores per-second metrics for days, weeks, or even
-    months. Every distributed node stores metrics locally, simplifying deployment, slashing costs, and enriching
-    Netdata's interactive dashboards.
--   **Export**: Integrate per-second metrics with other time-series databases like Graphite, Prometheus, InfluxDB,
-    TimescaleDB, and more with Netdata's interoperable and extensible core.
--   **Stream**: Aggregate metrics from any number of distributed nodes in one place for in-depth analysis, including
-    ephemeral nodes in a Kubernetes cluster.
+- **Collect**: Netdata collects all available metrics from your system and applications with 300+ collectors,
+  Kubernetes service discovery, and in-depth container monitoring, all while using only 1% CPU and a few MB of RAM. It
+  even collects metrics from Windows machines.
+- **Visualize**: The dashboard meaningfully presents charts to help you understand the relationships between your
+  hardware, operating system, running apps/services, and the rest of your infrastructure. Add nodes to Netdata Cloud
+  for a complete view of your infrastructure from a single pane of glass.
+- **Monitor**: Netdata's health watchdog uses hundreds of preconfigured alarms to notify you via Slack, email,
+  PagerDuty and more when an anomaly strikes. Customize with dynamic thresholds, hysteresis, alarm templates, and
+  role-based notifications.
+- **Troubleshoot**: 1s granularity helps you detect and analyze anomalies other monitoring platforms might have
+  missed. Interactive visualizations reduce your reliance on the console, and historical metrics help you trace issues
+  back to their root cause.
+- **Store**: Netdata's efficient database engine efficiently stores per-second metrics for days, weeks, or even
+  months. Every distributed node stores metrics locally, simplifying deployment, slashing costs, and enriching
+  Netdata's interactive dashboards.
+- **Export**: Integrate per-second metrics with other time-series databases like Graphite, Prometheus, InfluxDB,
+  TimescaleDB, and more with Netdata's interoperable and extensible core.
+- **Stream**: Aggregate metrics from any number of distributed nodes in one place for in-depth analysis, including
+  ephemeral nodes in a Kubernetes cluster.
 
 ## What's next?
 
-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).
+Learn more
+about [why you should use Netdata](https://github.com/netdata/netdata/blob/master/docs/overview/why-netdata.md),
+or [how Netdata works with your existing monitoring stack](https://github.com/netdata/netdata/blob/master/docs/overview/netdata-monitoring-stack.md).
 
 
diff --git a/docs/overview/why-netdata.md b/docs/overview/why-netdata.md
index 9a308f25c..158bc50df 100644
--- a/docs/overview/why-netdata.md
+++ b/docs/overview/why-netdata.md
@@ -58,6 +58,6 @@ open-source tools.
 
 Whether you already have a monitoring stack you want to integrate Netdata into, or are building something from the
 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).
+stack](https://github.com/netdata/netdata/blob/master/docs/overview/netdata-monitoring-stack.md).