Fixing sneaky broken links (#11175)
Joel Hans committed
May 24, 2021 at 05:38 UTC
56dfb07605c2e82699779f9597164856cf790250
10 files changed
+34
-27
docs/configure/nodes.md
+4
-3
@@ -18,9 +18,10 @@ anomaly, or change in infrastructure affects how their Agents should perform.
18
19
## The Netdata config directory
20
21
-On most Linux systems, using our [recommended one-line installation](/docs/get/README.md#install-the-netdata-agent), the
22
-**Netdata config directory** is `/etc/netdata/`. The config directory contains several configuration files with the
23
-`.conf` extension, a few directories, and a shell script named `edit-config`.
21
+On most Linux systems, using our [recommended one-line
22
+installation](/docs/get-started.mdx#install-on-linux-with-one-line-installer-recommended), the **Netdata config
23
+directory** is `/etc/netdata/`. The config directory contains several configuration files with the `.conf` extension, a
24
+few directories, and a shell script named `edit-config`.
25
26
> Some operating systems will use `/opt/netdata/etc/netdata/` as the config directory. If you're not sure where yours
27
> is, navigate to `http://NODE:19999/netdata.conf` in your browser, replacing `NODE` with the IP address or hostname of
docs/dashboard/customize.mdx
+1
-1
@@ -25,7 +25,7 @@ Here are a few popular settings:
25
### Change chart legend position
26
27
Find this setting under the **Visual** tab. By default, Netdata places the [legend of
28
-dimensions](/docs/dashboards/charts-dimensions-contexts-families.mdx#dimensions) _below_ charts. Click this toggle to
28
+dimensions](/docs/dashboard/dimensions-contexts-families.mdx#dimensions) _below_ charts. Click this toggle to
29
move the legend to the _right_ of charts.
30
31
### Change theme
docs/dashboard/import-export-print-snapshot.mdx
+2
-2
@@ -13,8 +13,8 @@ paper.
13
14
Snapshots can be incredibly useful for diagnosing anomalies after they've already happened. Let's say Netdata triggered
15
a warning alarm while you were asleep. In the morning, you can [pick the
16
-timeframe](/docs/dashboards/pick-timeframes.mdx) when the alarm triggered, export a snapshot, and send it to a colleague
17
-for further analysis.
16
+timeframe](/docs/dashboard/select-timeframes.mdx) when the alarm triggered, export a snapshot, and send it to a
17
+colleague for further analysis.
18
19
Or, send the Netdata team a snapshot of your dashboard when [filing a bug
20
report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2C+needs+triage&template=bug_report.md) on
docs/guides/deploy/ansible.md
+3
-3
@@ -7,9 +7,9 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/depl
7
8
# Deploy Netdata with Ansible
9
10
-Netdata's [one-line kickstart](https://learn.netdata.cloud/docs/get) is zero-configuration, highly adaptable, and
11
-compatible with tons of different operating systems and Linux distributions. You can use it on bare metal, VMs,
12
-containers, and everything in-between.
10
+Netdata's [one-line kickstart](/docs/get-started.mdx) is zero-configuration, highly adaptable, and compatible with tons
11
+of different operating systems and Linux distributions. You can use it on bare metal, VMs, containers, and everything
12
+in-between.
13
14
But what if you're trying to bootstrap an infrastructure monitoring solution as quickly as possible. What if you need to
15
deploy Netdata across an entire infrastructure with many nodes? What if you want to make this deployment reliable,
docs/guides/monitor/statsd.md
+3
-2
@@ -22,14 +22,15 @@ In general, the process for creating a StatsD collector can be summarized in 2 s
22
23
- Run an experiment by sending StatsD metrics to Netdata, without any prior configuration. This will create a chart per metric (called private charts) and will help you verify that everything works as expected from the application side of things.
24
- Make sure to reload the dashboard tab **after** you start sending data to Netdata.
25
-- Create a configuration file for your app using [edit-config](https://learn.netdata.cloud/guides/step-by-step/step-04): `sudo ./edit-config statsd.d/myapp.conf`
25
+- Create a configuration file for your app using [edit-config](/docs/configure/nodes.md): `sudo ./edit-config
26
+ statsd.d/myapp.conf`
27
- Each app will have it's own section in the right-hand menu.
28
29
Now, let's see the above process in detail.
30
31
## Prerequisites
32
32
-- A node with the [Netdata Agent](https://learn.netdata.cloud/docs/get#install-the-netdata-agent) installed.
33
+- A node with the [Netdata](/docs/get-started.mdx) installed.
34
- An application to instrument. For this guide, that will be [k6](https://k6.io/docs/getting-started/installation).
35
36
## Understanding the metrics
docs/guides/using-host-labels.md
+1
-1
@@ -27,7 +27,7 @@ sudo ./edit-config netdata.conf
27
```
28
29
Create a new `[host labels]` section defining a new host label and its value for the system in question. Make sure not
30
-to violate any of the [host label naming rules](/docs/configuration-guide.md#netdata-labels).
30
+to violate any of the [host label naming rules](/docs/configure/common-changes.md#organize-nodes-with-host-labels).
31
32
```conf
33
[host labels]
docs/monitor/enable-notifications.md
+9
-7
@@ -25,10 +25,11 @@ response process.
25
26
## Netdata Cloud
27
28
-Netdata Cloud's [centralized alarm notifications](https://learn.netdata.cloud/docs/cloud/monitoring/notifications/) is a
29
-zero-configuration way to get notified when an anomaly or incident strikes any node or application in your
30
-infrastructure. The advantage of using centralized alarm notifications from Netdata Cloud is that you don't have to
31
-worry about configuring each node in your infrastructure.
28
+Netdata Cloud's [centralized alarm
29
+notifications](https://learn.netdata.cloud/docs/cloud/alerts-notifications/notifications) is a zero-configuration way to
30
+get notified when an anomaly or incident strikes any node or application in your infrastructure. The advantage of using
31
+centralized alarm notifications from Netdata Cloud is that you don't have to worry about configuring each node in your
32
+infrastructure.
33
34
To enable centralized alarm notifications for a Space, click on **Manage Space** in the left-hand menu, then click on
35
the **Notifications** tab. Click the toggle switch next to **E-mail** to enable this notification method.
@@ -40,8 +41,9 @@ choose what types of notifications to receive from each War Room.
41
43
43
-See the [centralized alarm notifications](https://learn.netdata.cloud/docs/cloud/monitoring/notifications/) reference
44
-doc for further details about what information is conveyed in an email notification, flood protection, and more.
44
+See the [centralized alarm notifications](https://learn.netdata.cloud/docs/cloud/alerts-notifications/notifications)
45
+reference doc for further details about what information is conveyed in an email notification, flood protection, and
46
+more.
47
48
## Netdata Agent
49
@@ -138,7 +140,7 @@ architecture](/docs/store/distributed-data-architecture.md) for the best-in-clas
140
141
### Related reference documentation
142
141
-- [Netdata Cloud · Alarm notifications](https://learn.netdata.cloud/docs/cloud/monitoring/notifications/)
143
+- [Netdata Cloud · Alarm notifications](https://learn.netdata.cloud/docs/cloud/alerts-notifications/notifications)
144
- [Netdata Agent · Notifications](/health/notifications/README.md)
145
146
[](<>)
docs/monitor/view-active-alarms.md
+4
-3
@@ -11,9 +11,10 @@ performance issue affects your node or the applications it runs.
11
12
## Netdata Cloud
13
14
-A War Room's [alarms indicator](https://learn.netdata.cloud/docs/cloud/war-rooms#indicators) displays the number of active `critical` (red) and
15
-`warning` (yellow) alerts for the nodes in this War Room. Click on either the critical or warning badges to open a
16
-pre-filtered modal displaying only those types of [active alarms](https://learn.netdata.cloud/docs/cloud/monitoring/alarms).
14
+A War Room's [alarms indicator](https://learn.netdata.cloud/docs/cloud/war-rooms#indicators) displays the number of
15
+active `critical` (red) and `warning` (yellow) alerts for the nodes in this War Room. Click on either the critical or
16
+warning badges to open a pre-filtered modal displaying only those types of [active
17
+alarms](https://learn.netdata.cloud/docs/cloud/alerts-notifications/view-active-alerts).
18
19
docs/overview/what-is-netdata.md
+2
-4
@@ -32,10 +32,8 @@ Cloud, you can view key metrics, insightful charts, and active alarms from all y
32
When an anomaly strikes, seamlessly navigate to any node to troubleshoot and discover the root cause with the familiar
33
Netdata dashboard.
34
35
-**[Netdata Cloud is
36
-free](https://learn.netdata.cloud/docs/cloud/faq-glossary#how-much-does-netdata-cost-how-and-why-is-it-free)**! You can
37
-add an entire infrastructure of nodes, invite all your colleagues, and visualize any number of metrics, charts, and
38
-alarms entirely for free.
35
+**[Netdata Cloud is free](https://www.netdata.cloud/blog/why-netdata-is-free/)**! You can add an entire infrastructure
36
+of nodes, invite all your colleagues, and visualize any number of metrics, charts, and alarms entirely for free.
37
38
While Netdata Cloud offers a centralized method of monitoring your Agents, your metrics data is not stored or
39
centralized in any way. Metrics data remains with your nodes and is only streamed to your browser, through Cloud, when
health/notifications/custom/README.md
+5
-1
@@ -7,7 +7,11 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notificat
7
8
Netdata allows you to send custom notifications to any endpoint you choose.
9
10
-To configure custom notifications, you will need to customize `health_alarm_notify.conf`. You can look at the other senders in `/usr/libexec/netdata/plugins.d/alarm-notify.sh` for examples of how to modify the `custom_sender()` function in `health_alarm_notify.conf`. Ensure you follow the instructions of changing any configuration file to [persist your configuration](/docs/configuration-guide.md#persist-my-configuration).
10
+To configure custom notifications, you will need to customize `health_alarm_notify.conf`. Open the file for editing
11
+using [`edit-config`](/docs/configure/nodes.md#use-edit-config-to-edit-configuration-files) from the [Netdata config
12
+directory](/docs/configure/nodes.md#the-netdata-config-directory), which is typically at `/etc/netdata`.
13
+
14
+You can look at the other senders in `/usr/libexec/netdata/plugins.d/alarm-notify.sh` for examples of how to modify the `custom_sender()` function in `health_alarm_notify.conf`.
15
16
As with other notifications, you will also need to define the recipient list in `DEFAULT_RECIPIENT_CUSTOM` and/or the `role_recipients_custom` array.
17