From aa2fe8ccbfcb117efa207d10229eeeac5d0f97c7 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Mon, 6 Feb 2023 17:11:30 +0100
Subject: Adding upstream version 1.38.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 docs/store/change-metrics-storage.md | 24 ++++++++++++++----------
 1 file changed, 14 insertions(+), 10 deletions(-)

(limited to 'docs/store/change-metrics-storage.md')

diff --git a/docs/store/change-metrics-storage.md b/docs/store/change-metrics-storage.md
index c4b77d9af..e82393a65 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)
 
 
-- 
cgit v1.2.3