summaryrefslogtreecommitdiffstats
path: root/docs/metrics-storage-management/how-streaming-works.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/metrics-storage-management/how-streaming-works.md')
-rw-r--r--docs/metrics-storage-management/how-streaming-works.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/metrics-storage-management/how-streaming-works.md b/docs/metrics-storage-management/how-streaming-works.md
index f09b13b4cc..1934a3362e 100644
--- a/docs/metrics-storage-management/how-streaming-works.md
+++ b/docs/metrics-storage-management/how-streaming-works.md
@@ -19,7 +19,7 @@ replicate metrics data across multiple nodes, or centralize all your metrics dat
(TSDB).
When one node streams metrics to another, the node receiving metrics can visualize them on the
-[dashboard](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md), run health checks to [trigger
+[dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboard/interact-charts.md), run health checks to [trigger
alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md) and [send notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md), and
[export](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md) all metrics to an external TSDB. When Netdata streams metrics to another
Netdata, the receiving one is able to perform everything a Netdata instance is capable of.