Add links to promote database engine calculator (#9067)

* Add links and calculator .md

* Refactor to Learn

* Remove erroneous paragraph

3 files changed, 11 insertions, 17 deletions

diff --git a/docs/getting-started.md b/docs/getting-started.md
index 6a3e9ca633..696d62a997 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -67,8 +67,9 @@ configuration keeps RAM usage low while allowing for long-term, on-disk metrics
 You can tweak this custom _database engine_ to store a much larger dataset than your system's available RAM,
 particularly if you allow Netdata to use slightly more RAM and disk space than the default configuration.
 
-Read our tutorial, [**Changing how long Netdata stores metrics**](/docs/tutorials/longer-metrics-storage.md), to learn
-more.
+Read our guide on [changing how long Netdata stores metrics](/docs/tutorials/longer-metrics-storage.md) to learn more
+and use our [database engine calculator](https://learn.netdata.cloud/docs/agent/database/calculator) to figure
+out the exact settings you'll need to store historical metrics right in the Agent's database.
 
 **What's next?**:
 
diff --git a/docs/step-by-step/step-09.md b/docs/step-by-step/step-09.md
index 8b1301a283..7664211c43 100644
--- a/docs/step-by-step/step-09.md
+++ b/docs/step-by-step/step-09.md
@@ -54,9 +54,9 @@ the database engine to use. The higher those values, the more metrics Netdata wi
 512, respectively, the database engine should store about four day's worth of data on a system collecting 2,000 metrics
 every second.
 
-> Before you make changes, we recommended you read up on the [database
-> engine's](/database/engine/README.md#memory-requirements) to ensure you don't overwhelm your system. Out of memory
-> errors are no fun!
+[**See our database engine calculator**](https://learn.netdata.cloud/docs/agent/database/calculator) to help you
+correctly set `dbengine disk space` based on your needs. The calculator gives an accurate estimate based on how many
+slave nodes you have, how many metrics your Agent collects, and more.
 
 ```conf
 [global]
diff --git a/docs/tutorials/longer-metrics-storage.md b/docs/tutorials/longer-metrics-storage.md
index 80cc08ea44..9a36b1c94d 100644
--- a/docs/tutorials/longer-metrics-storage.md
+++ b/docs/tutorials/longer-metrics-storage.md
@@ -1,8 +1,7 @@
 <!--
----
 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/tutorials/longer-metrics-storage.md
----
 -->
 
 # Change how long Netdata stores metrics
@@ -37,9 +36,6 @@ using, check out your `netdata.conf` file and look for the `memory mode` setting
 If `memory mode` is set to anything but `dbengine`, change it and restart Netdata using the standard command for
 restarting services on your system. You're now using the database engine!
 
-> Learn more about how we implemented the database engine, and our vision for its future, on our blog: [_How and why
-> we're bringing long-term storage to Netdata_](https://blog.netdata.cloud/posts/db-engine/).
-
 What makes the database engine efficient? While it's structured like a traditional database, the database engine splits
 data between RAM and disk. The database engine caches and indexes data on RAM to keep memory usage low, and then
 compresses older metrics onto disk for long-term storage.
@@ -58,14 +54,11 @@ size` and `dbengine disk space`.
 
 `page cache size` sets the maximum amount of RAM (in MiB) the database engine will use for caching and indexing.
 `dbengine disk space` sets the maximum disk space (again, in MiB) the database engine will use for storing compressed
-metrics.
-
-Based on our testing, these default settings will retain about a day's worth of metrics when Netdata collects roughly
-4,000 metrics every second. If you increase either `page cache size` or `dbengine disk space`, Netdata will retain even
-more historical metrics.
+metrics. The default settings retain about two day's worth of metris on a system collecting 2,000 metrics every second.
 
-But before you change these options too dramatically, read up on the [database engine's memory
-footprint](/database/engine/README.md#memory-requirements).
+[**See our database engine calculator**](https://learn.netdata.cloud/docs/agent/database/calculator) to help you
+correctly set `dbengine disk space` based on your needs. The calculator gives an accurate estimate based on how many
+slave nodes you have, how many metrics your Agent collects, and more.
 
 With the database engine active, you can back up your `/var/cache/netdata/dbengine/` folder to another location for
 redundancy.