Move/refactor docs to accomodate new Guides section on Learn (netdata#9266)

* Move directories and change verbiage to guide

* Move health guides

* Quick fix to collectors quickstart

* Fix broken links

* Remove health/tutorials dir

* Fix links in collectors quickstart

* Fix links to go.d pages

Author: joelhans

collectors/QUICKSTART.md

@@ -35,16 +35,18 @@ and `python.d`.
 > If there is a collector written in both Go and Python, it's better to choose the Go-based version, as we will
 > eventually deprecate most Python-based collectors.
 
-From here on out, this quickstart guide will use the [Nginx collector](go.d.plugin/modules/nginx/README.md) as an
-example to showcase the process of configuring and enabling one of Netdata's pre-installed collectors.
+From here on out, this quickstart guide will use the [Nginx
+collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/nginx) as an example to showcase the
+process of configuring and enabling one of Netdata's pre-installed collectors.
 
 ## Configure your application or service for monitoring
 
 Every collector's documentation comes with instructions on how to configure your app/service to make it available to
 Netdata's collector. Our [collector support list](COLLECTORS.md) contains links to each collector's documentation page
 so you can learn more.
 
-For example, the [Nginx collector documentation](go.d.plugin/modules/nginx/README.md) states that your Nginx
+For example, the [Nginx collector
+documentation](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/nginx) states that your Nginx
 installation must have the `stub_status` module configured correctly, in addition to an active `stub_status/` page, for
 Netdata to monitor it. You can confirm whether you have the module enabled with the following command:
 
@@ -82,13 +84,14 @@ Despite Netdata's auto-detection capabilities, it's important to know how to edi
 
 You should always edit configuration files with the `edit-config` script that comes with every installation of Netdata.
 To edit a collector configuration file, navigate to your [Netdata configuration
-directory](/docs/step-by-step/step-04.md#find-your-netdataconf-file). Launch `edit-config` with the path to the
+directory](/docs/guides/step-by-step/step-04.md#find-your-netdataconf-file). Launch `edit-config` with the path to the
 collector's configuration file.
 
 How do you find that path to the collector's configuration file? Look under the **Configuration** heading in the
 collector's documentation. Each file contains a short code block with the relevant command.
 
-For example, the [Nginx collector](go.d.plugin/modules/nginx/README.md) has its configuration file at `go.d/nginx.conf`.
+For example, the [Nginx collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/nginx) has its
+configuration file at `go.d/nginx.conf`.
 
 ```bash
 cd /etc/netdata # Replace this path with your Netdata config directory
@@ -115,7 +118,7 @@ entry in the menu and new interactive charts!
 Collector not working? Learn about collector troubleshooting in our [collector
 reference](REFERENCE.md#troubleshoot-a-collector).
 
-View our [collectors tutorials](/collectors/README.md#tutorials) to get specific instructions on enabling new and
+View our [collectors guides](/collectors/README.md#guides) to get specific instructions on enabling new and
 popular collectors.
 
 Finally, learn more advanced collector features, such as disabling plugins or developing a custom collector, in our

collectors/README.md

@@ -30,15 +30,15 @@ guide](/collectors/QUICKSTART.md).
 
 [Collectors configuration reference](/collectors/REFERENCE.md)
 
-## Tutorials
+## Guides
 
-[Monitor Nginx or Apache web server log files with Netdata](/docs/tutorials/collect-apache-nginx-web-logs.md)
+[Monitor Nginx or Apache web server log files with Netdata](/docs/guides/collect-apache-nginx-web-logs.md)
 
-[Monitor CockroadchDB metrics with Netdata](/docs/tutorials/monitor-cockroachdb.md)
+[Monitor CockroadchDB metrics with Netdata](/docs/guides/monitor-cockroachdb.md)
 
-[Monitor Unbound DNS servers with Netdata](/docs/tutorials/collect-unbound-metrics.md)
+[Monitor Unbound DNS servers with Netdata](/docs/guides/collect-unbound-metrics.md)
 
-[Monitor a Hadoop cluster with Netdata](/docs/tutorials/monitor-hadoop-cluster.md)
+[Monitor a Hadoop cluster with Netdata](/docs/guides/monitor-hadoop-cluster.md)
 
 ## Related features
 

docs/Performance.md

@@ -196,8 +196,8 @@ following settings in the `[global]` section of `netdata.conf`:
 	# dbengine disk space = 256
 ```
 
-See the [database engine documentation](/database/engine/README.md) or our [tutorial on metrics
-retention](tutorials/longer-metrics-storage.md) for more details on lowering the database engine's memory requirements.
+See the [database engine documentation](/database/engine/README.md) or our [guide on metrics
+retention](/docs/guides/longer-metrics-storage.md) for more details on lowering the database engine's memory requirements.
 
 ### 6. Disable gzip compression of responses
 

docs/configuration-guide.md

@@ -63,8 +63,8 @@ it there.
 #### Increase the long-term metrics retention period
 
 Increase the values for the `page cache size` and `dbengine disk space` settings in the [`[global]`
-section](/daemon/config/README.md#global-section-options) of `netdata.conf`. Read our tutorial on [increasing
-long-term metrics storage](/docs/tutorials/longer-metrics-storage.md) and the [memory requirements for the database
+section](/daemon/config/README.md#global-section-options) of `netdata.conf`. Read our guide on [increasing
+long-term metrics storage](/docs/guides/longer-metrics-storage.md) and the [memory requirements for the database
 engine](/database/engine/README.md#memory-requirements).
 
 #### Reduce the data collection frequency
@@ -198,7 +198,7 @@ Beginning with  1.20, Netdata accepts user-defined **host labels**. These labels
 labels]`.
 
 Read more about how these labels work and why they're an effective way to organize complex infrasturctures in our
-tutorial: [Use host labels to organize systems, metrics, and alarms](/docs/tutorials/using-host-labels.md).
+guide: [Use host labels to organize systems, metrics, and alarms](/docs/guides/using-host-labels.md).
 
 To define a label inside this section, some rules needs to be followed, or Netdata will reject the label. The following
 restrictions are applied for label names:

docs/contributing/style-guide.md

@@ -330,7 +330,7 @@ of the Agent repository (`/`). Links should also always end with the filename of
 Avoid relative links or traversing up directories using `../`.
 
 For example, if you want to link to our installation guide, you should link to `/packaging/installer/README.md`. To
-reference the guide for increasing metrics storage, use `/docs/tutorials/longer-metrics-storage.md`.
+reference the guide for increasing metrics storage, use `/docs/guides/longer-metrics-storage.md`.
 
 ### References to UI elements
 

docs/export/README.md

@@ -25,7 +25,7 @@ be applied to other connectors as well.
 > If you are migrating from the deprecated backends system, this quickstart will also help you update your configuration
 > to the new format. For the most part, the configurations are identical, but there are two exceptions. First,
 > `exporting.conf` uses a new `[<type>:<name>]` format for defining connector instances. Second, the `host tags` setting
-> is deprecated. Instead, use [host labels](/docs/tutorials/using-host-labels.md) to tag exported metrics.
+> is deprecated. Instead, use [host labels](/docs/guides/using-host-labels.md) to tag exported metrics.
 
 Open the `exporting.conf` file with `edit-config`.
 
@@ -94,8 +94,8 @@ collected, you should start seeing data in your external database after only a f
 
 -   [Exporting reference guide](/exporting/README.md)
 -   [Backends (deprecated)](/backends/README.md)
--   [Use host labels to organize systems, metrics, and alarms](/docs/tutorials/using-host-labels.md)
+-   [Use host labels to organize systems, metrics, and alarms](/docs/guides/using-host-labels.md)
 -   [Database engine](/database/engine/README.md)
--   [Change how long Netdata stores metrics (long-term storage)](/docs/tutorials/longer-metrics-storage.md)
+-   [Change how long Netdata stores metrics (long-term storage)](/docs/guides/longer-metrics-storage.md)
 
 [![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fexporting%2FREADME.md&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

docs/getting-started.md

@@ -15,7 +15,7 @@ The Agent can collect thousands of metrics in real-time and use its database for
 configuration, but there are some valuable things to know to get the most out of Netdata based on your needs.
 
 We'll skip right into some technical details, so if you're brand-new to monitoring the health and performance of systems
-and applications, our [**step-by-step tutorial**](/docs/step-by-step/step-00.md) might be a better fit.
+and applications, our [**step-by-step guide**](/docs/guides/step-by-step/step-00.md) might be a better fit.
 
 > If you haven't installed Netdata yet, visit the [installation instructions](/packaging/installer/README.md) for
 > details, including our one-liner script, which automatically installs Netdata on almost all Linux distributions.
@@ -67,7 +67,7 @@ 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 guide on [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/guides/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.
 

docs/tutorials/collect-apache-nginx-web-logs.md renamed to docs/guides/collect-apache-nginx-web-logs.md

@@ -1,8 +1,6 @@
 <!--
----
 title: "Monitor Nginx or Apache web server log files with Netdata"
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/tutorials/collect-apache-nginx-web-logs.md
----
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/collect-apache-nginx-web-logs.md
 -->
 
 # Monitor Nginx or Apache web server log files with Netdata
@@ -22,10 +20,10 @@ You can now use the [LTSV log format](http://ltsv.org/), track TLS and cipher us
 ever. In one test on a system with SSD storage, the collector consistently parsed the logs for 200,000 requests in
 200ms, using ~30% of a single core. To learn more about these improvements, see our [v1.19 release post](https://blog.netdata.cloud/posts/release-1.19/).
 
-The [go.d plugin](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/weblog/) is currently compatible with
-[Nginx](https://nginx.org/en/) and [Apache](https://httpd.apache.org/).
+The [go.d plugin](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/weblog/) is currently compatible
+with [Nginx](https://nginx.org/en/) and [Apache](https://httpd.apache.org/).
 
-This tutorial will walk you through using the new Go-based web log collector to turn the logs these web servers
+This guide will walk you through using the new Go-based web log collector to turn the logs these web servers
 constantly write to into real-time insights into your infrastructure.
 
 ## Set up your web servers
@@ -128,7 +126,7 @@ web server's access log and begin showing real-time charts!
 ### Custom log formats and fields
 
 The web log collector is capable of parsing custom Nginx and Apache log formats and presenting them as charts, but we'll
-leave that topic for a separate tutorial.
+leave that topic for a separate guide.
 
 We do have [extensive
 documentation](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/weblog/#custom-log-format) on how
@@ -160,4 +158,4 @@ into powerful real-time tools for keeping your servers happy.
 Don't forget to give GitHub user [Wing924](https://github.com/Wing924) a big 👍 for his hard work in starting up the Go
 refactoring effort.
 
-[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Ftutorials%2Fweb-log-collector&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)
+[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fguides%2Fcollect-apache-nginx-web-logs&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

docs/tutorials/collect-unbound-metrics.md renamed to docs/guides/collect-unbound-metrics.md

@@ -1,9 +1,7 @@
 <!--
----
 title: "Monitor Unbound DNS servers with Netdata"
 date: 2020-03-31
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/tutorials/collect-unbound-metrics.md
----
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/collect-unbound-metrics.md
 -->
 
 # Monitor Unbound DNS servers with Netdata
@@ -16,7 +14,7 @@ Unbound runs on FreeBSD, OpenBSD, NetBSD, macOS, Linux, and Windows, and support
 queries and answers are all encrypted with TLS. In theory, that should reduce the risk of eavesdropping or
 man-in-the-middle attacks when communicating to DNS servers.
 
-This tutorial will show you how to collect dozens of essential metrics from your Unbound servers with minimal
+This guide will show you how to collect dozens of essential metrics from your Unbound servers with minimal
 configuration.
 
 ## Set up your Unbound installation
@@ -137,4 +135,4 @@ for improvement or refinement based on real-world use cases. Feel free to [file
 issue](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&template=bug_report.md) with your
 thoughts.
 
-[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Ftutorials%2Funbound-metrics&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)
+[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fguides%2Funbound-metrics&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

docs/tutorials/longer-metrics-storage.md renamed to docs/guides/longer-metrics-storage.md

@@ -1,7 +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
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/longer-metrics-storage.md
 -->
 
 # Change how long Netdata stores metrics
@@ -13,7 +13,7 @@ Many people think Netdata can only store about an hour's worth of real-time metr
 more. With the right settings, Netdata is quite capable of efficiently storing hours or days worth of historical,
 per-second metrics without having to rely on an [exporting engine](/exporting/README.md).
 
-This tutorial gives two options for configuring Netdata to store more metrics. **We recommend the default [database
+This guide gives two options for configuring Netdata to store more metrics. **We recommend the default [database
 engine](#using-the-database-engine)**, but you can stick with or switch to the round-robin database if you prefer.
 
 Let's get started.
@@ -155,4 +155,4 @@ charts](/web/README.md#using-charts).
 And if you'd now like to reduce Netdata's resource usage, view our [performance guide](/docs/Performance.md) for
 our best practices on optimization.
 
-[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Ftutorials%2Flonger-metrics-storage&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)
+[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fguides%2Flonger-metrics-storage&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

docs/tutorials/monitor-cockroachdb.md renamed to docs/guides/monitor-cockroachdb.md

@@ -1,8 +1,6 @@
 <!--
----
 title: "Monitor CockroachDB metrics with Netdata"
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/tutorials/monitor-cockroachdb.md
----
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/monitor-cockroachdb.md
 -->
 
 # Monitor CockroachDB metrics with Netdata
@@ -134,3 +132,5 @@ Also, be sure to check out these useful resources:
     docs](https://www.cockroachlabs.com/docs/stable/monitoring-and-alerting.html#prometheus-endpoint)
 -   [Monitor CockroachDB with
     Prometheus](https://www.cockroachlabs.com/docs/stable/monitor-cockroachdb-with-prometheus.html)
+
+[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fguides%2Fmonitor-cockroachdb&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)

docs/tutorials/monitor-hadoop-cluster.md renamed to docs/guides/monitor-hadoop-cluster.md

@@ -1,8 +1,6 @@
 <!--
----
 title: "Monitor a Hadoop cluster with Netdata"
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/tutorials/monitor-hadoop-cluster.md
----
+custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/monitor-hadoop-cluster.md
 -->
 
 # Monitor a Hadoop cluster with Netdata
@@ -17,16 +15,16 @@ implementations.
 
 Netdata comes with built-in and pre-configured support for monitoring both HDFS and Zookeeper.
 
-This tutorial assumes you have a Hadoop cluster, with HDFS and Zookeeper, running already. If you don't, please follow
+This guide assumes you have a Hadoop cluster, with HDFS and Zookeeper, running already. If you don't, please follow
 the [official Hadoop
 instructions](http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html) or an
 alternative, like the guide available from
 [DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-install-hadoop-in-stand-alone-mode-on-ubuntu-18-04).
 
-For more specifics on the collection modules used in this tutorial, read the respective pages in our documentation:
+For more specifics on the collection modules used in this guide, read the respective pages in our documentation:
 
--   [HDFS](/collectors/go.d.plugin/modules/hdfs/README.md)
--   [Zookeeper](/collectors/go.d.plugin/modules/zookeeper/README.md)
+-   [HDFS](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/hdfs)
+-   [Zookeeper](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/zookeeper)
 
 ## Set up your HDFS and Zookeeper installations
 
@@ -203,4 +201,4 @@ issue](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&
     file](https://github.com/netdata/go.d.plugin/blob/master/config/go.d/zookeeper.conf) to understand how to configure
     global options or per-job options, timeouts, TLS certificates, and more.
 
-[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Ftutorials%2Fmonitor-hadoop-cluster&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)
+[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fguides%2Fmonitor-hadoop-cluster&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>)