Improve core documentation to align with recent Netdata Cloud releases (#10318)
* Change overview doc with group by node * Add hash to link * Update core documentation with latest from Cloud * Fix link * Fixes for Amy * Fixes for Odysseas
Joel Hans committed
Dec 7, 2020 at 14:48 UTC
a80af1b120af6504c1b42f4c80882c5efc461a8d
8 files changed
+104
-220
docs/configure/invite-collaborate.md
deleted
-58
@@ -1,58 +0,0 @@
1
-<!--
2
-title: "Invite your team and collaborate"
3
-description: "Invite your SRE, DevOPs, or ITOps teams to Netdata Cloud to give everyone insights into your infrastructure from a single pane of glass."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/configure/invite-collaborate.md
5
--->
6
-
7
-# Invite your team and collaborate
8
-
9
-Netdata is designed to make an infrastructure's real-time metrics available and actionable to all organization members.
10
-By inviting others, you can better synchronize with your team or colleagues to understand your infrastructure's
11
-heartbeat. When something goes wrong, you'll be ready to collaboratively troubleshoot complex performance problems from
12
-a single pane of glass.
13
-
14
-## Invite new members
15
-
16
-Invite new users by clicking on your Space's name in the top navigation, and then **Invite more users**, to open the
17
-invitation pane. Admins manage user permissions and have control over who can access specific Spaces and War Rooms.
18
-
19
-
21
-
22
-Enter their email address and name. They can change this name once they accept your invitation.
23
-
24
-Choose which War Rooms you want to add this user to, then click the plus **+** button to add the invitation to the
25
-**New invitations to be sent** queue. Repeat the process with everyone you want to invite to your Space.
26
-
27
-When you're ready to send the new invitations you created, hit the **Send** button. Netdata Cloud sends these
28
-invitations and moves them to the **Invitations awaiting response** category.
29
-
30
-Your team will receive their email invitations momentarily with a prompt to sign in to join your Space.
31
-
32
-## Collaboration with Netdata Cloud
33
-
34
-Netdata Cloud gives teams a single interface to view real-time metrics across their entire infrastructure. Having all
35
-the metrics, alarm statuses, dashboards, and people in one place is a powerful asset for any infrastructure monitoring
36
-team.
37
-
38
-Assets like dashboards and bookmarks are shared between members of a War Room. As soon as one member creates a
39
-dashboard, for example, other members of the same War Room can see it in the War Room's dropdown and supplement it with
40
-additional charts/text.
41
-
42
-Let's say you get an alert from your nodes about an excess of 500-type errors in your Nginx logs. Your team can hop on a
43
-Slack call to begin working together. While one engineer handles creating a new dashboard with a half-dozen relevant
44
-Nginx log metrics, another can dive into the real-time node dashboard and investigate correlated charts in granular
45
-detail.
46
-
47
-## What's next?
48
-
49
-If your team members have trouble signing in, direct them to the [Netdata Cloud sign in
50
-doc](https://learn.netdata.cloud/docs/cloud/manage/sign-in). Or, find answers to other common questions about Netdata
51
-Cloud in our [FAQ](https://learn.netdata.cloud/docs/cloud/faq-glossary).
52
-
53
-Next, we recommend you learn the [basics of node configuration](/docs/configure/nodes.md). While the Netdata Agent is
54
-proudly zero-configuration in most cases, you should understand how to tweak its settings to give you the best Netdata,
55
-for example, to [increase metrics retention](/docs/store/change-metrics-storage.md) and [improve
56
-security](/docs/configure/secure-nodes.md).
57
-
58
-[](<>)
docs/configure/nodes.md
+4
-3
@@ -1,13 +1,14 @@
1
<!--
2
-title: "Configure your nodes"
2
+title: "Configure the Netdata Agent"
3
description: "Netdata is zero-configuration for most users, but complex infrastructures may require you to tweak some of the Agent's granular settings."
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/configure/nodes.md
5
-->
6
7
-# Configure your nodes
7
+# Configure the Netdata Agent
8
9
Netdata's zero-configuration collection, storage, and visualization features work for many users, infrastructures, and
10
-use cases, but there are some situations where you might want to configure your nodes.
10
+use cases, but there are some situations where you might want to configure the Netdata Agent running on your node(s),
11
+which can be a physical or virtual machine (VM), container, cloud deployment, or edge/IoT device.
12
13
For example, you might want to increase metrics retention, configure a collector based on your infrastructure's unique
14
setup, or secure the local dashboard by restricting it to only connections from `localhost`.
docs/configure/secure-nodes.md
+1
-3
@@ -1,8 +1,6 @@
1
<!--
2
title: "Secure your nodes"
3
-description: "Your data and systems are safe with Netdata, but
4
-
5
-we recommend a few easy ways to improve the security of your infrastructure."
3
+description: "Your data and systems are safe with Netdata, but we recommend a few easy ways to improve the security of your infrastructure."
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/configure/secure-nodes.md
5
-->
6
docs/configure/spaces-war-rooms.md
deleted
-87
@@ -1,87 +0,0 @@
1
-<!--
2
-title: "Set up Spaces and War Rooms"
3
-description: "Netdata Cloud allows people and teams of all sizes to organize their infrastructure and collaborate on anomalies or incidents."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/configure/spaces-war-rooms.md
5
--->
6
-
7
-# Set up Spaces and War Rooms
8
-
9
-Spaces and War Rooms help you organize your real-time infrastructure monitoring experience in Netdata Cloud. You already
10
-created a Space and War Room when you first signed in to Cloud, assuming you weren't invited to an existing Space by
11
-someone else.
12
-
13
-In either case, you can always create new Spaces and War Rooms based on your changing needs or a scaled-up
14
-infrastructure. Let's talk through some strategies for building the most intuitive Cloud experience for your team.
15
-
16
-> This guide assumes you've already [signed in](https://app.netdata.cloud) to Netdata Cloud and finished creating your
17
-> account. If you're not interested in Netdata Cloud's features, you can skip ahead to [node configuration
18
-> basics](/docs/configure/nodes.md).
19
-
20
-## Spaces
21
-
22
-Spaces are high-level containers to help you organize your team members and the nodes they can view in each War Room.
23
-You already have at least one Space in your Netdata Cloud account.
24
-
25
-To create a new Space, click the **+** icon, enter its name, and click **Save**. Netdata Cloud distinguishes between
26
-Spaces with abbreviated versions of their name. Click on any of the icons to switch between them.
27
-
28
-
30
-
31
-The organization you choose will likely be based on two factors:
32
-
33
-1. The fact that any node can be claimed to a single Space.
34
-2. The size of your team and the complexity of the infrastructure you monitor.
35
-
36
-A single Space puts all your metrics in one easily-accessible place, while multiple Spaces creates logical division
37
-between different users and different pieces of a large infrastructure.
38
-
39
-For example, a large organization might have one SRE team for the user-facing SaaS application, and a second IT team for
40
-managing employees' hardware. Since these teams don't monitor the same nodes, they can work in separate Spaces and then
41
-further organize their nodes into War Rooms.
42
-
43
-You can also use multiple Spaces for different aspects of your monitoring "life," such as your work infrastructure
44
-versus your homelab.
45
-
46
-## War Rooms
47
-
48
-War Rooms are granular containers for organizing nodes, viewing key metrics in real-time, and monitoring the health and
49
-alarm status of many nodes.
50
-
51
-War Rooms organize the [at-a-glance Node view](/docs/visualize/view-all-nodes.md) and any [new
52
-dashboards](/docs/visualize/create-dashboards.md) you build.
53
-
54
-We recommend a few strategies for organizing your War Rooms.
55
-
56
-**Service, purpose, location, etc.**: You can group War Rooms by a service (think Nginx, MySQL, Pulsar, and so on),
57
-their purpose (webserver, database, application), their physical location, whether they're baremetal or a Docker
58
-container, the PaaS/cloud provider it runs on, and much more. This allows you to see entire slices of your
59
-infrastructure by moving from one War Room to another.
60
-
61
-**End-to-end apps/services**: If you have a user-facing SaaS product, or an internal service that said product relies
62
-on, you may want to monitor that entire stack in a single War Room. This might include Kubernetes clusters, Docker
63
-containers, proxies, databases, web servers, brokers, and more. End-to-end War Rooms are valuable tools for ensuring the
64
-health and performance of your organization's essential services.
65
-
66
-**Incident response**: You can also create new War Rooms as one of the first steps in your incident response process.
67
-For example, you have a user-facing web app that relies on Apache Pulsar for a message queue, and one of your nodes
68
-using the [Pulsar collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/pulsar) begins
69
-reporting a suspiciously low messages rate. You can create a War Room called `$year-$month-$day-pulsar-rate`, add all
70
-your Pulsar nodes in addition to nodes they connect to, and begin diagnosing the root cause in a War Room optimized for
71
-getting to resolution as fast as possible.
72
-
73
-For example, here is a War Room based on the node's provider and physical location (**us-east-1**).
74
-
75
-
77
-
78
-## What's next?
79
-
80
-Once you've figured out an organizational structure that works for your infrastructure, it's time to [invite your
81
-team](/docs/configure/invite-collaborate.md). You can invite any number of colleagues to help you collectively
82
-troubleshoot the most complex of infrastructure-wide performance issues.
83
-
84
-If you don't have a team or aren't ready to invite them, you can skip ahead to learn the [basics of node
85
-configuration](/docs/configure/nodes.md).
86
-
87
-[](<>)
docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+1
-1
@@ -246,7 +246,7 @@ Click **Save** to add the chart for all your claimed nodes. Now you can see how
246
Linux kernels on multiple Linux systems.
247
248
Now that you can see these metrics in Netdata Cloud, you can [invite your
249
-team](https://learn.netdata.cloud/docs/cloud/collaborate/invite-your-team) and share your findings with others.
249
+team](https://learn.netdata.cloud/docs/cloud/manage/invite-your-team) and share your findings with others.
250
251
## What's next?
252
docs/quickstart/infrastructure.md
+80
-37
@@ -7,50 +7,83 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/quickstart/
7
8
# Infrastructure monitoring with Netdata
9
10
-Together, the Netdata Agent and Netdata Cloud create a powerful, infinitely-scalable infrastructure monitoring solution.
10
+[Netdata Cloud](https://app.netdata.cloud) provides scalable infrastructure monitoring for any number of distributed
11
+nodes running the Netdata Agent. A node is any system in your infrastructure that you want to monitor, whether it's a
12
+physical or virtual machine (VM), container, cloud deployment, or edge/IoT device.
13
14
The Netdata Agent uses zero-configuration collectors to gather metrics from every application and container instantly,
15
and uses Netdata's [distributed data architecture](/docs/store/distributed-data-architecture.md) to store metrics
16
locally. Without a slow and troublesome centralized data lake for your infrastructure's metrics, you reduce the
17
resources you need to invest in, and the complexity of, monitoring your infrastructure.
18
17
-Netdata Cloud unifies monitoring your infrastructure by _centralizing the interface_ you use to query and visualize your
19
+Netdata Cloud unifies infrastructure monitoring by _centralizing the interface_ you use to query and visualize your
20
nodes' metrics, not the data. By streaming metrics values to your browser, with Netdata Cloud acting as the secure proxy
21
between them, you can monitor your infrastructure using customizable, interactive, and real-time visualizations from any
22
numbe of distributed nodes.
23
22
-In this quickstart guide, you'll learn how to see key metrics from all your nodes in one interface and build your first
23
-dashboard for aggregating like metrics from many distributed nodes. You'll then take a peek into configuring individual
24
-nodes and get helpful pointers about collecting all the metrics from every critical application in your infrastructure.
24
+In this quickstart guide, you'll learn the basics of using Netdata Cloud to monitor an infrastructure with dashboards,
25
+composite charts, and alarm viewing. You'll then learn about the most critical ways to configure the Agent on each of
26
+your nodes to maximize the value you get from Netdata.
27
26
-> This quickstart assumes you've installed the Netdata Agent on more than one node in your infrastructure, and claimed
27
-> those nodes to your Space in Netdata Cloud. If you haven't yet, see the [_Get Netdata_ doc](/docs/get/README.md) for
28
-> details on installation and claiming.
28
+This quickstart assumes you've installed the Netdata Agent on more than one node in your infrastructure, and claimed
29
+those nodes to your Space in Netdata Cloud. If you haven't yet, see the [_Get Netdata_ doc](/docs/get/README.md) for
30
+details on signing up for Netdata Cloud, installation, and claiming.
31
32
> If you want to monitor a Kubernetes cluster with Netdata, see our [k8s installation
33
> doc](/packaging/installer/methods/kubernetes.md) for setup details, and then read our guide, [_Monitor a Kubernetes
34
> cluster with Netdata_](/docs/guides/monitor/kubernetes-k8s-netdata.md).
35
34
-## See an overview of your infrastructure
36
+## Set up your Netdata Cloud experience
37
36
-To see all your nodes from a single pane of glass, first [sign in](https://app.netdata.cloud) to Netdata Cloud. As you
37
-navigate to a particular War Room, Netdata Cloud pings each claimed node to start on-demand streaming from your nodes to
38
-your browser.
38
+Start your infrastructure monitoring experience by setting up your Netdata Cloud account.
39
40
-Netdata Cloud then visualizes all these metrics, from any number of distributed nodes, in the War Room's **Overview**.
41
-The Overview features composite charts, which display aggregated metrics from multiple nodes.
40
+### Organize Spaces and War Rooms
41
+
42
+Spaces are high-level containers to help you organize your team members and the nodes they can view in each War Room.
43
+You already have at least one Space in your Netdata Cloud account.
44
+
45
+A single Space puts all your metrics in one easily-accessible place, while multiple Spaces creates logical division
46
+between different users and different pieces of a large infrastructure. For example, a large organization might have one
47
+SRE team for the user-facing SaaS application, and a second IT team for managing employees' hardware. Since these teams
48
+don't monitor the same nodes, they can work in separate Spaces and then further organize their nodes into War Rooms.
49
+
50
+Next, set up War Rooms. Netdata Cloud creates dashboards and visualizations based on the nodes added to a given War
51
+Room. You can [organize War Rooms](https://learn.netdata.cloud/docs/cloud/war-rooms#war-room-organization) in any way
52
+you want, such as by the application type, for end-to-end application monitoring, or as an incident response tool.
53
+
54
+Learn more about [Spaces](https://learn.netdata.cloud/docs/cloud/spaces) and [War
55
+Rooms](https://learn.netdata.cloud/docs/cloud/war-rooms), including how to manage each, in their respective reference
56
+documentation.
57
+
58
+### Invite your team
59
+
60
+Netdata Cloud makes an infrastructure's real-time metrics available and actionable to all organization members. By
61
+inviting others, you can better synchronize with your team or colleagues to understand your infrastructure's heartbeat.
62
+When something goes wrong, you'll be ready to collaboratively troubleshoot complex performance problems from a single
63
+pane of glass.
64
+
65
+To invite new users, click on **Invite Users** in the left-hand navigation panel beneath your Space's name. Choose which
66
+War Rooms to add this user to, then click **Send**.
67
+
68
+If your team members have trouble signing in, direct them to the [Netdata Cloud sign
69
+in](https://learn.netdata.cloud/docs/cloud/manage/sign-in) doc.
70
+
71
+### See an overview of your infrastructure
72
+
73
+The default way to visualize the health and performance of an infrastructure with Netdata Cloud is the
74
+[**Overview**](/docs/visualize/overview-infrastructure.md), which is the default interface of every War Room. The
75
+Overview features composite charts, which display aggregated metrics from every node in a given War Room. These metrics
76
+are streamed on-demand from individual nodes and composited onto a single, familiar dashboard.
77
78
80
46
-Netdata Cloud also features the **Nodes view**, which you can use to configure and see a few key metrics from every node
47
-in the War Room, view health status, and more.
48
-
49
-
81
+Read more about the Overview in the [infrastructure overview](/docs/visualize/overview-infrastructure.md) doc.
82
51
-Read more about both features in the [infrastructure overview](/docs/visualize/overview-infrastructure.md) doc.
83
+Netdata Cloud also features the [**Nodes view**](https://learn.netdata.cloud/docs/cloud/visualize/nodes), which you can
84
+use to configure and see a few key metrics from every node in the War Room, view health status, and more.
85
53
-## Drill down to specific nodes
86
+### Drill down to specific nodes
87
88
Both the Overview and Nodes view offer easy access to **single-node dashboards** for targeted analysis. You can use
89
single-node dashboards in Netdata Cloud to drill down on specific issues, scrub backward in time to investigate
@@ -61,7 +94,7 @@ overview](/docs/visualize/overview-infrastructure.md#single-node-dashboards) doc
94
dashboards and charts](/docs/visualize/interact-dashboards-charts.md) to get the most from all of Netdata's real-time
95
metrics.
96
64
-## Create new dashboards
97
+### Create new dashboards
98
99
You can use Netdata Cloud to create new dashboards that match your infrastructure's topology or help you diagnose
100
complex issues by aggregating correlated charts from any number of nodes. For example, you could monitor the system CPU
@@ -69,12 +102,21 @@ from every node in your infrastructure on a single dashboard.
102
103
72
-)
105
106
Read more about [creating new dashboards](/docs/visualize/create-dashboards.md) for more details about the process and
107
additional tips on best leveraging the feature to help you troubleshoot complex performance problems.
108
77
-## Configure your nodes
109
+## Set up your nodes
110
+
111
+You get the most value out of Netdata Cloud's infrastructure monitoring capabilities if each node collects every
112
+possible metric. For example, if a node in your infrastructure is responsible for serving a MySQL database, you should
113
+ensure that the Netdata Agent on that node is properly collecting and streaming all MySQL-related metrics.
114
+
115
+In most cases, collectors autodetect their data source and require no configuration, but you may need to configure
116
+certain behaviors based on your infrastructure. Or, you may want to enable/configure advanced functionality, such as
117
+longer metrics retention or streaming.
118
+
119
+### Configure the Netdata Agent on your nodes
120
121
You can configure any node in your infrastructure if you need to, although most users will find the default settings
122
work extremely well for monitoring their infrastructures.
@@ -95,21 +137,15 @@ After you've learned the basics, you should [secure your infrastructure's nodes]
137
one of our recommended methods. These security best practices ensure no untrusted parties gain access to the metrics
138
collected on any of your nodes.
139
98
-## Collect metrics from your systems and applications
140
+### Collect metrics from systems and applications
141
142
Netdata has [300+ pre-installed collectors](/collectors/COLLECTORS.md) that gather thousands of metrics with zero
143
configuration. Collectors search each of your nodes in default locations and ports to find running applications and
144
gather as many metrics as they can without you having to configure them individually.
145
104
-In fact, Netdata is already collecting thousands of metrics per second from your webservers, databases, containers, and
105
-much more, on each node in your infrastructure.
106
-
107
-These metrics enrich your Netdata Cloud experience. You can see metrics from systems, containers, and applications in
108
-the individual node dashboards, and you can create new dashboards around very specific charts, such as the real-time
109
-volume of 503 responses from each of your webserver nodes.
110
-
146
Most collectors work without configuration, but you should read up on [how collectors
112
-work](/docs/collect/how-collectors-work.md) and [how to enable/configure](/docs/collect/enable-configure.md) them.
147
+work](/docs/collect/how-collectors-work.md) and [how to enable/configure](/docs/collect/enable-configure.md) them so
148
+that you can see metrics from those applications in Netdata Cloud.
149
150
In addition, find detailed information about which [system](/docs/collect/system-metrics.md),
151
[container](/docs/collect/container-metrics.md), and [application](/docs/collect/application-metrics.md) metrics you can
@@ -121,11 +157,9 @@ Netdata has many features that help you monitor the health of your nodes and tro
157
Once you have a handle on configuration and are collecting all the right metrics, try out some of Netdata's other
158
infrastructure-focused features:
159
124
-- [Organize your nodes](/docs/configure/spaces-war-rooms.md) into **War Rooms** based on your preferred strategy.
125
-- [See an overview of your infrastructure](/docs/visualize/overview-infrastructure.md) using Netdata Cloud's various
126
- preconfigured dashboards.
127
-- [Invite your team](/docs/configure/invite-collaborate.md) to collaborate on identifying anomalies or troubleshooting
128
- complex performance problems.
160
+- [See an overview of your infrastructure](/docs/visualize/overview-infrastructure.md) using Netdata Cloud's composite
161
+ charts and real-time visualizations.
162
+- [Create new dashboards](/docs/visualize/create-dashboards.md) from any number of nodes and metrics in Netdata Cloud.
163
164
To change how the Netdata Agent runs on each node, dig in to configuration files:
165
@@ -138,4 +172,13 @@ To change how the Netdata Agent runs on each node, dig in to configuration files
172
- [Export metrics](/docs/export/external-databases.md) to an external time-series database to use Netdata alongside
173
other monitoring and troubleshooting tools.
174
175
+### Related reference documentation
176
+
177
+- [Netdata Cloud · Spaces](https://learn.netdata.cloud/docs/cloud/spaces)
178
+- [Netdata Cloud · War Rooms](https://learn.netdata.cloud/docs/cloud/war-rooms)
179
+- [Netdata Cloud · Invite your team](https://learn.netdata.cloud/docs/cloud/manage/invite-your-team)
180
+- [Netdata Cloud · Sign in or sign up with email, Google, or
181
+ GitHub](https://learn.netdata.cloud/docs/cloud/manage/sign-in)
182
+- [Netdata Cloud · Nodes view](https://learn.netdata.cloud/docs/cloud/visualize/nodes)
183
+
184
[](<>)
docs/visualize/interact-dashboards-charts.md
+1
-1
@@ -81,7 +81,7 @@ height](https://user-images.githubusercontent.com/1153921/93497272-1acb5380-f8c5
81
82
Netdata Cloud now supports composite charts in the Overview interface. Composite charts come with a few additional UI
83
elements and varied interactions, such as the location of dimensions and a utility bar for configuring the state of
84
-individual composite charts. All of these de4tails are covered in the [Overview
84
+individual composite charts. All of these details are covered in the [Overview
85
reference](https://learn.netdata.cloud/docs/cloud/visualize/overview) doc.
86
87
## What's next?
docs/visualize/overview-infrastructure.md
+17
-30
@@ -53,53 +53,40 @@ See the [War Rooms](https://learn.netdata.cloud/docs/cloud/war-rooms) docs for m
53
54
### Configure composite charts to identify problems
55
56
-Let's say you notice an interesting spike in disk I/O between `14:42:56` and `14:47:08`. Highlight the anomalous area
57
-using `ALT/⌘ + mouse selection`, then zoom in with `SHIFT + mouse selection` to synchronize all composite charts around
58
-this potentially problematic area.
56
+Let's say you notice a sharp decrease in available RAM for applications, as seen in the example screenshot below. In
57
+this situation, you can see when the anomalous behavior began and that it affects the average available and committed
58
+RAM across your infrastructure. However, when _grouped by dimension_, composite charts cannot show whether an anomaly
59
+affects a single node, a subset of nodes, or an entire infrastructure.
60
60
-
61
+
63
63
-By default, the **Disk I/O Bandwidth (disk.io)** composite chart displays the **sum** of all dimensions (`reads` and
64
-`writes`) from all nodes in that War Room. This smart default helps you identify anomalous behavior, but doesn't
65
-necessarily provide the full picture. Let's say you want to understand the severity of disk writes. Use the definition
66
-bar to change the aggregate function to **min** (because the `writes` dimension is on the negative axis), and display
67
-only the `writes` dimension.
64
+Use [_group by node_](https://learn.netdata.cloud/docs/cloud/visualize/overview#group-by-dimension-or-node) to visualize
65
+a single metric across all contributing nodes. If the composite chart has 5 contributing nodes, there will be 5
66
+lines/areas, one for the most relevant dimension from each node.
67
69
-
68
+
70
72
-Because you're now looking at the largest magnitude of change on your infrastructure, you know a single node experienced
73
-31 MiB/s in disk writes. By first using the Overview to gather baseline data, identify anomalies, and use aggregate
74
-functions to your advantage, you've proactively recognized single-node issues using an infrastructure-wide interface.
71
+After grouping by node, it's clear that the `Composite-Charts-01` node is experiencing anomalous behavior and should be
72
+investigated further by jumping to its [single-node dashboard](#drill-down-with-single-node-dashboards) in Netdata
73
+Cloud.
74
76
-### Drill down to single-node dashboards
77
-
78
-Overview helps you take the investigation further with quick access to single-node dashboards in Netdata Cloud.
75
+### Drill down with single-node dashboards
76
77
Click on **X Charts** of any composite chart's definition bar to display a dropdown of contributing contexts and nodes
78
contributing. Click on the link icon <img class="img__inline img__inline--link"
79
src="https://user-images.githubusercontent.com/1153921/95762109-1d219300-0c62-11eb-8daa-9ba509a8e71c.png" /> next to a
80
given node to quickly _jump to the same chart in that node's single-node dashboard_ in Netdata Cloud.
81
85
-)
82
+
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](/docs/visualize/interact-dashboards-charts.md) are available, as is adding any chart
88
to a [new dashboard](/docs/visualize/create-dashboards.md).
89
93
-Using the above example, one of the single-node dashboards reveals similar spike in disk I/O. Interestingly enough, it
94
-also shows a maximum disk write of 31 MiB/s at the exact same moment as the composite chart in Overview.
95
-
96
-
98
-
99
-You now know that this particular node, during this particular time, experienced anomalous behavior. In this case, the
100
-root cause of the disk I/O spike was due to updating the Netdata Agent itself, which is also the cause of the subsequent
101
-gap in metrics history.
102
-
90
## Nodes view
91
92
You can also use the **Nodes view** to monitor the health status and user-configurable key metrics from multiple nodes