f66c74e0a · cryptotaxi247/netdata-1

collectors/README.md

+1 -1

@@ -34,7 +34,7 @@ If the collector finds compatible metrics exposed on the configured endpoint, it

34 Netdata Agent gathers these metrics, sends them to the

35 [database engine for storage](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md)

36 , and immediately

37 -[visualizes them meaningfully](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md)

37 +[visualizes them meaningfully](https://github.com/netdata/netdata/blob/master/docs/dashboard/interact-charts.md)

38 on dashboards.

39

40 Each collector comes with a pre-defined configuration that matches the default setup for that application. This endpoint

docs/guides/monitor/lamp-stack.md

+1 -1

@@ -171,7 +171,7 @@ If the Netdata Agent isn't already open in your browser, open a new tab and navi

171 Netdata automatically organizes all metrics and charts onto a single page for easy navigation. Peek at gauges to see

172 overall system performance, then scroll down to see more. Click-and-drag with your mouse to pan _all_ charts back and

173 forth through different time intervals, or hold `SHIFT` and use the scrollwheel (or two-finger scroll) to zoom in and

174 -out. Check out our doc on [interacting with charts](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md) for all the details.

174 +out. Check out our doc on [interacting with charts](https://github.com/netdata/netdata/blob/master/docs/dashboard/interact-charts.md) for all the details.

175

176 ![The Netdata

177 dashboard](https://user-images.githubusercontent.com/1153921/109520555-98e17800-7a69-11eb-86ec-16f689da4527.png)

docs/metrics-storage-management/how-streaming-works.md

+1 -1

@@ -19,7 +19,7 @@ replicate metrics data across multiple nodes, or centralize all your metrics dat

19 (TSDB).

20

21 When one node streams metrics to another, the node receiving metrics can visualize them on the

22 -[dashboard](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md), run health checks to [trigger

22 +[dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboard/interact-charts.md), run health checks to [trigger

23 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

24 [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

25 Netdata, the receiving one is able to perform everything a Netdata instance is capable of.

docs/quickstart/infrastructure.md

+1 -1

@@ -91,7 +91,7 @@ historical data, and see like metrics presented meaningfully to help you trouble

91

92 Read about the process in the [infrastructure

93 overview](https://github.com/netdata/netdata/blob/master/docs/visualize/overview-infrastructure.md#drill-down-with-single-node-dashboards) doc, then learn about [interacting with

94 -dashboards and charts](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md) to get the most from all of Netdata's real-time

94 +dashboards and charts](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md) to get the most from all of Netdata's real-time

95 metrics.

96

97 ### Create new dashboards

docs/store/distributed-data-architecture.md

+1 -1

@@ -14,7 +14,7 @@ Netdata uses a distributed data architecture to help you collect and store per-s

14 Every node in your infrastructure, whether it's one or a thousand, stores the metrics it collects.

15

16 Netdata Cloud bridges the gap between many distributed databases by _centralizing the interface_ you use to query and

17 -visualize your nodes' metrics. When you [look at charts in Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md)

17 +visualize your nodes' metrics. When you [look at charts in Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md)

18 , the metrics values are queried directly from that node's database and securely streamed to Netdata Cloud, which

19 proxies them to your browser.

20

docs/visualize/create-dashboards.md

+2 -2

@@ -28,7 +28,7 @@ respond

28 node](https://user-images.githubusercontent.com/1153921/102650776-a654ba80-4128-11eb-9a65-4f9801b03d4b.png)

29

30 Charts in dashboards

31 -are [fully interactive](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md) and

31 +are [fully interactive](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md) and

32 synchronized. You can

33 pan through time, zoom, highlight specific timeframes, and more.

34

@@ -44,7 +44,7 @@ more detail when troubleshooting an issue. Quickly jump to any node's dashboard

44 of any card to open a menu. Hit the **Go to Chart** item.

45

46 Netdata Cloud takes you to the same chart on that node's dashboard. You can now navigate all that node's metrics and

47 -[interact with charts](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md) to

47 +[interact with charts](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md) to

48 further investigate anomalies or troubleshoot

49 complex performance problems.

50

docs/visualize/overview-infrastructure.md

+1 -21

@@ -84,7 +84,7 @@ given node to quickly _jump to the same chart in that node's single-node dashboa

84

85 You can use single-node dashboards in Netdata Cloud to drill down on specific issues, scrub backward in time to

86 investigate historical data, and see like metrics presented meaningfully to help you troubleshoot performance problems.

87 -All of the familiar [interactions](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md) are available, as is adding any chart

87 +All of the familiar [interactions](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md) are available, as is adding any chart

88 to a [new dashboard](https://github.com/netdata/netdata/blob/master/docs/visualize/create-dashboards.md).

89

90 ## Nodes view

@@ -93,23 +93,3 @@ You can also use the **Nodes view** to monitor the health status and user-config

93 in a War Room. Read the [Nodes view doc](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/nodes.md) for details.

94

95 ![The Nodes view](https://user-images.githubusercontent.com/1153921/108733066-5fe65800-74eb-11eb-98e0-abaccd36deaf.png)

96 -

97 -## What's next?

98 -

99 -To troubleshoot complex performance issues using Netdata, you need to understand how to interact with its meaningful

100 -visualizations. Learn more about [interaction](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md) to see historical metrics,

101 -highlight timeframes for targeted analysis, and more.

102 -

103 -If you're a Kubernetes user, read about Netdata's [Kubernetes

104 -visualizations](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/kubernetes.md) for details about the health map and

105 -time-series k8s charts, and our tutorial, [_Kubernetes monitoring with Netdata: Overview and

106 -visualizations_](https://github.com/netdata/netdata/blob/master/docs/guides/monitor/kubernetes-k8s-netdata.md), for a full walkthrough.

107 -

108 -### Related reference documentation

109 -

110 -- [Netdata Cloud · War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md)

111 -- [Netdata Cloud · Overview](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/overview.md)

112 -- [Netdata Cloud · Nodes view](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/nodes.md)

113 -- [Netdata Cloud · Kubernetes visualizations](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/kubernetes.md)

114 -

115 -

packaging/installer/README.md

+1 -1

@@ -68,7 +68,7 @@ community, but you may want to [edit alarms](https://github.com/netdata/netdata/

68

69 #### Make your deployment production ready

70

71 -Both [securing Netdata](https://github.com/netdata/netdata/blob/master/docs/configure/secure-nodes.md) and [setting up replication](https://github.com/netdata/netdata/blob/master/streaming/README.md) are strongly recommended.

71 +Both [securing Netdata](https://github.com/netdata/netdata/blob/master/docs/netdata-security.md) and [setting up replication](https://github.com/netdata/netdata/blob/master/streaming/README.md) are strongly recommended.

72

73

74 ## Install on Linux with one-line installer

packaging/installer/methods/ansible.md

+1 -24

@@ -130,7 +130,7 @@ hostname of the node, the playbook disables that local dashboard by setting `web

130 security boost by not allowing any unwanted access to the local dashboard.

131

132 You can read more about this decision, or other ways you might lock down the local dashboard, in our [node security

133 -doc](https://github.com/netdata/netdata/blob/master/docs/configure/secure-nodes.md).

133 +doc](https://github.com/netdata/netdata/blob/master/docs/netdata-security.md).

134

135 > Curious about why Netdata's dashboard is open by default? Read our [blog

136 > post](https://www.netdata.cloud/blog/netdata-agent-dashboard/) on that zero-configuration design decision.

@@ -154,26 +154,3 @@ task results in a changed, failure, or was skipped entirely.

154

155 The task to install Netdata will take a few minutes per node, so be patient! Once the playbook reaches the connect to Cloud

156 task, your nodes start populating your Space in Netdata Cloud.

157 -

158 -## What's next?

159 -

160 -Go use Netdata!

161 -

162 -If you need a bit more guidance for how you can use Netdata for health monitoring and performance troubleshooting, see

163 -our [documentation](https://learn.netdata.cloud/docs). It's designed like a comprehensive guide, based on what you might

164 -want to do with Netdata, so use those categories to dive in.

165 -

166 -Some of the best places to start:

167 -

168 -- [Collectors configuration reference](https://github.com/netdata/netdata/blob/master/collectors/README.md)

169 -- [Supported collectors list](https://github.com/netdata/netdata/blob/master/collectors/COLLECTORS.md)

170 -- [See an overview of your infrastructure](https://github.com/netdata/netdata/blob/master/docs/visualize/overview-infrastructure.md)

171 -- [Interact with dashboards and charts](https://github.com/netdata/netdata/blob/master/docs/visualize/interact-dashboards-charts.md)

172 -- [Change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md)

173 -

174 -We're looking for more deployment and configuration management strategies, whether via Ansible or other

175 -provisioning/infrastructure as code software, such as Chef or Puppet, in our [community

176 -repo](https://github.com/netdata/community). Anyone is able to fork the repo and submit a PR, either to improve this

177 -playbook, extend it, or create an entirely new experience for deploying Netdata across entire infrastructure.

178 -

179 -

packaging/installer/methods/source.md

+1 -1

@@ -233,7 +233,7 @@ using glibc or musl. To use one of these:

233

234 Alternatively, you may wish to build the eBPF code locally yourself. For

235 instructions, please consult [the README file for our kernel-collector

236 -repository](https://github.com/netdata/kernel-collector/blob/master/README.md),

236 +repository](https://github.com/netdata/kernel-collector/#readme),

237 which outlines both the required dependencies, as well as multiple

238 options for building the code.

239

Fix broken links (#14605)