Adding upstream version 1.38.0.upstream/1.38.0

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

2 files changed, 26 insertions, 18 deletions

diff --git a/docs/store/change-metrics-storage.md b/docs/store/change-metrics-storage.md
index c4b77d9a..e82393a6 100644
--- a/docs/store/change-metrics-storage.md
+++ b/docs/store/change-metrics-storage.md
@@ -1,12 +1,16 @@
 <!--
 title: "Change how long Netdata stores metrics"
 description: "With a single configuration change, the Netdata Agent can store days, weeks, or months of metrics at its famous per-second granularity."
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/store/change-metrics-storage.md
+custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/store/change-metrics-storage.md"
+sidebar_label: "Change how long Netdata stores metrics"
+learn_status: "Published"
+learn_topic_type: "Tasks"
+learn_rel_path: "Setup"
 -->
 
 # Change how long Netdata stores metrics
 
-The Netdata Agent uses a custom made time-series database (TSDB), named the [`dbengine`](/database/engine/README.md), to store metrics.
+The Netdata Agent uses a custom made time-series database (TSDB), named the [`dbengine`](https://github.com/netdata/netdata/blob/master/database/engine/README.md), to store metrics.
 
 The default settings retain approximately two day's worth of metrics on a system collecting 2,000 metrics every second,
 but the Netdata Agent is highly configurable if you want your nodes to store days, weeks, or months worth of per-second
@@ -39,7 +43,7 @@ if you want to store more metrics _specifically in memory_, you can increase the
 
 :::tip
 
-We advise you to visit the [tiering mechanism](/database/engine/README.md#tiering) reference. This will help you
+We advise you to visit the [tiering mechanism](https://github.com/netdata/netdata/blob/master/database/engine/README.md#tiering) reference. This will help you
 configure the Agent to retain metrics for longer periods.
 
 :::
@@ -57,7 +61,7 @@ data retention according to your preferences.
 ## Edit `netdata.conf` with recommended database engine settings
 
 Now that you have a recommended setting for your Agent's `dbengine`, open `netdata.conf` with
-[`edit-config`](/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) and look for the `[db]`
+[`edit-config`](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) and look for the `[db]`
 subsection. Change it to the recommended values you calculated from the calculator. For example:
 
 ```conf
@@ -76,23 +80,23 @@ subsection. Change it to the recommended values you calculated from the calculat
 ```
 
 Save the file and restart the Agent with `sudo systemctl restart netdata`, or
-the [appropriate method](/docs/configure/start-stop-restart.md) for your system, to change the database engine's size.
+the [appropriate method](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md) for your system, to change the database engine's size.
 
 ## What's next?
 
 If you have multiple nodes with the Netdata Agent installed, you
-can [stream metrics](/docs/metrics-storage-management/how-streaming-works.mdx) from any number of _child_ nodes to a _
+can [stream metrics](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.mdx) from any number of _child_ nodes to a _
 parent_ node and store metrics using a centralized time-series database. Streaming allows you to centralize your data,
 run Agents as headless collectors, replicate data, and more.
 
 Storing metrics with the database engine is completely interoperable
-with [exporting to other time-series databases](/docs/export/external-databases.md). With exporting, you can use the
-node's resources to surface metrics when [viewing dashboards](/docs/visualize/interact-dashboards-charts.md), while also
+with [exporting to other time-series databases](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md). With exporting, you can use the
+node's resources to surface metrics when [viewing dashboards](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md), while also
 archiving metrics elsewhere for further analysis, visualization, or correlation with other tools.
 
 ### Related reference documentation
 
-- [Netdata Agent · Database engine](/database/engine/README.md)
-- [Netdata Agent · Database engine configuration option](/daemon/config/README.md#[db]-section-options)
+- [Netdata Agent · Database engine](https://github.com/netdata/netdata/blob/master/database/engine/README.md)
+- [Netdata Agent · Database engine configuration option](https://github.com/netdata/netdata/blob/master/daemon/config/README.md#[db]-section-options)
 
 
diff --git a/docs/store/distributed-data-architecture.md b/docs/store/distributed-data-architecture.md
index 62933cfe..96ae4d99 100644
--- a/docs/store/distributed-data-architecture.md
+++ b/docs/store/distributed-data-architecture.md
@@ -1,7 +1,11 @@
 <!--
 title: "Distributed data architecture"
 description: "Netdata's distributed data architecture stores metrics on individual nodes for high performance and scalability using all your granular metrics."
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/store/distributed-data-architecture.md
+custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/store/distributed-data-architecture.md"
+sidebar_label: "Distributed data architecture"
+learn_status: "Published"
+learn_topic_type: "Concepts"
+learn_rel_path: "Concepts"
 -->
 
 # Distributed data architecture
@@ -10,7 +14,7 @@ Netdata uses a distributed data architecture to help you collect and store per-s
 Every node in your infrastructure, whether it's one or a thousand, stores the metrics it collects.
 
 Netdata Cloud bridges the gap between many distributed databases by _centralizing the interface_ you use to query and
-visualize your nodes' metrics. When you [look at charts in Netdata Cloud](/docs/visualize/interact-dashboards-charts.md)
+visualize your nodes' metrics. When you [look at charts in Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md)
 , the metrics values are queried directly from that node's database and securely streamed to Netdata Cloud, which
 proxies them to your browser.
 
@@ -18,7 +22,7 @@ Netdata's distributed data architecture has a number of benefits:
 
 - **Performance**: Every query to a node's database takes only a few milliseconds to complete for responsiveness when
   viewing dashboards or using features
-  like [Metric Correlations](https://learn.netdata.cloud/docs/cloud/insights/metric-correlations).
+  like [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md).
 - **Scalability**: As your infrastructure scales, install the Netdata Agent on every new node to immediately add it to
   your monitoring solution without adding cost or complexity.
 - **1-second granularity**: Without an expensive centralized data lake, you can store all of your nodes' per-second
@@ -53,17 +57,17 @@ of the Netdata Agent, without affecting disk space or memory requirements.
 Any node running the Netdata Agent can store long-term metrics for any retention period, given you allocate the
 appropriate amount of RAM and disk space.
 
-Read our document on changing [how long Netdata stores metrics](/docs/store/change-metrics-storage.md) on your nodes for
+Read our document on changing [how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md) on your nodes for
 details.
 
-You can also stream between nodes using [streaming](/streaming/README.md), allowing to replicate databases and create
+You can also stream between nodes using [streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md), allowing to replicate databases and create
 your own centralized data lake of metrics, if you choose to do so.
 
 While a distributed data architecture is the default when monitoring infrastructure with Netdata, you can also configure
 its behavior based on your needs or the type of infrastructure you manage.
 
 To archive metrics to an external time-series database, such as InfluxDB, Graphite, OpenTSDB, Elasticsearch,
-TimescaleDB, and many others, see details on [integrating Netdata via exporting](/docs/export/external-databases.md).
+TimescaleDB, and many others, see details on [integrating Netdata via exporting](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md).
 
 When you use the database engine to store your metrics, you can always perform a quick backup of a node's
 `/var/cache/netdata/dbengine/` folder using the tool of your choice.
@@ -72,7 +76,7 @@ When you use the database engine to store your metrics, you can always perform a
 
 Netdata Cloud does not store metric values.
 
-To enable certain features, such as [viewing active alarms](/docs/monitor/view-active-alarms.md)
+To enable certain features, such as [viewing active alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md)
 or [filtering by hostname/service](https://learn.netdata.cloud/docs/cloud/war-rooms#node-filter), Netdata Cloud does
 store configured alarms, their status, and a list of active collectors.
 
@@ -81,7 +85,7 @@ Netdata does not and never will sell your personal data or data about your deplo
 ## What's next?
 
 You can configure the Netdata Agent to store days, weeks, or months worth of distributed, per-second data by
-[configuring the database engine](/docs/store/change-metrics-storage.md). Use our calculator to determine the system
+[configuring the database engine](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md). Use our calculator to determine the system
 resources required to retain your desired amount of metrics, and expand or contract the database by editing a single
 setting.