merged spaces, war rooms and invite your team to one place (#15289)
* merged spaces, war rooms and invite your team to one place * Update docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> * Update docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> * fix from review comments * delete invite your team file * Apply suggestions from code review --------- Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Hugo Valente committed
Jun 30, 2023 at 11:45 UTC
9511dc0bfb83c23d66e05cdd0c27184a731cda9a
17 files changed
+201
-192
claim/README.md
+1
-1
@@ -22,7 +22,7 @@ identity of the Netdata Agent when it connects to the Cloud. While the data does
22
from Agents to the browser, we do not store or log it.
23
24
You can connect a node during the Netdata Cloud onboarding process, or after you created a Space by clicking on **Connect
25
-Nodes** in the [Spaces management area](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md#manage-spaces).
25
+Nodes** in the [Spaces management area](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces#manage-spaces).
26
27
There are two important notes regarding connecting nodes:
28
docs/cloud/manage/invite-your-team.md
deleted
-24
@@ -1,24 +0,0 @@
1
-# Invite your team
2
-
3
-Invite your entire SRE, DevOPs, or ITOps team to Netdata Cloud, to give everyone insights into your infrastructure from a single pane of glass.
4
-
5
-Invite new users to your Space by clicking on **Invite Users** in
6
-the [Space](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md) management area.
7
-
8
-
9
-
10
-
11
-You will be prompted to enter the email addresses for the users you want to invite to your Space. You can enter any number of email addresses, separated by a comma, to send multiple invitations at once.
12
-
13
-Next, choose the War Rooms you want to invite these users to. Once logged in, these users are not restricted only to
14
-these War Rooms. They can be invited to others, or join any that are public.
15
-
16
-Next, pick a role for the invited user. You can read more about [which roles are available](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md#what-roles-are-available) based on your [subscription plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md).
17
-
18
-Click the **Send** button to send an email invitation, which will prompt them
19
-to [sign up](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/sign-in.md) and join your Space.
20
-
21
-
22
-
23
-Any unaccepted invitations remain under **Invitations awaiting response**. These invitations can be rescinded at any
24
-time by clicking the trash can icon.
docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md
new
+170
@@ -0,0 +1,170 @@
1
+# Organize Your Infrastructure and Invite your Team
2
+
3
+Netdata Cloud provides you with features such as [Spaces](#netdata-cloud-spaces) and [War Rooms](#netdata-cloud-war-rooms) that allow you to better organize your infrastructure and ensure your team can also have access to it through invites.
4
+
5
+## Netdata Cloud Spaces
6
+
7
+Organize your multi-organization infrastructure monitoring on Netdata Cloud by creating Spaces to completely isolate access to your Agent-monitored nodes.
8
+
9
+A Space is a high-level container. It's a collaboration space where you can organize team members, access levels and the
10
+nodes you want to monitor.
11
+
12
+Let's talk through some strategies for creating the most intuitive Cloud experience for your team.
13
+
14
+### How to organize your Netdata Cloud
15
+
16
+You can use any number of Spaces you want, but as you organize your Cloud experience, keep in mind that _you can only
17
+add any given node to a single Space_. This 1:1 relationship between node and Space may dictate whether you use one
18
+encompassing Space for your entire team and separate them by War Rooms, or use different Spaces for teams monitoring
19
+discrete parts of your infrastructure.
20
+
21
+If you have been invited to Netdata Cloud by another user by default you will able to see that space. If you are a new
22
+user the first space is already created.
23
+
24
+The other consideration for the number of Spaces you use to organize your Netdata Cloud experience is the size and
25
+complexity of your organization.
26
+
27
+For smaller teams and infrastructures, we recommend sticking to a single Space so that you can keep all your nodes and their
28
+respective metrics in one place. You can then use
29
+multiple [War Rooms](#netdata-cloud-war-rooms)
30
+to further organize your infrastructure monitoring.
31
+
32
+Enterprises may want to create multiple Spaces for each of their larger teams, particularly if those teams have
33
+different responsibilities or parts of the overall infrastructure to monitor. For example, you might have one SRE team
34
+for your user-facing SaaS application and a second team for infrastructure tooling. If they don't need to monitor the
35
+same nodes, you can create separate Spaces for each team.
36
+
37
+### Navigate between spaces
38
+
39
+Click on any of the boxes to switch between available Spaces.
40
+
41
+Netdata Cloud abbreviates each Space to the first letter of the name, or the first two letters if the name is two words
42
+or more. Hover over each icon to see the full name in a tooltip.
43
+
44
+To add a new Space click on the green **+** button. Enter the name of the Space and click **Save**.
45
+
46
+
47
+)
48
+
49
+### Manage Spaces
50
+
51
+Manage your spaces by selecting a particular space and clicking on the small gear icon in the lower left corner. This
52
+will open a side tab in which you can:
53
+
54
+1. _Configure this Space*_, in the first tab (**Space**) you can change the name, description or/and some privilege
55
+ options of this space
56
+
57
+2. _Edit the War Rooms*_, click on the **War rooms** tab to add or remove War Rooms.
58
+
59
+3. _Connect nodes*_, click on **Nodes** tab. Copy the claiming script to your node and run it. See the
60
+ [connect to Cloud doc](https://github.com/netdata/netdata/blob/master/claim/README.md) for details.
61
+
62
+4. _Manage the users*_, click on **Users**.
63
+ The [invitation doc](#invite-your-team)
64
+ details the invitation process.
65
+
66
+5. _Manage notification setting*_, click on **Notifications** tab to turn off/on notification methods.
67
+
68
+6. _Manage your bookmarks*_, click on the **Bookmarks** tab to add or remove bookmarks that you need.
69
+
70
+> #### Note
71
+>
72
+> \* This action requires admin rights for this space
73
+
74
+### Obsoleting offline nodes from a Space
75
+
76
+Netdata admin users now have the ability to remove obsolete nodes from a space.
77
+
78
+- Only admin users have the ability to obsolete nodes
79
+- Only offline nodes can be marked obsolete (Live nodes and stale nodes cannot be obsoleted)
80
+- Node obsoletion works across the entire space, so the obsoleted node will be removed from all rooms belonging to the
81
+ space
82
+- If the obsoleted nodes eventually become live or online once more they will be automatically re-added to the space
83
+
84
+
85
+
86
+## Netdata Cloud War rooms
87
+
88
+Netdata Cloud uses War Rooms to organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
89
+
90
+Once you add nodes to a Space, all of your nodes will be visible in the **All nodes** War Room. This is a special War Room
91
+which gives you an overview of all of your nodes in this particular Space. Then you can create functional separations of
92
+your nodes into more War Rooms. Every War Room has its own dashboards, navigation, indicators, and management tools.
93
+
94
+
95
+
96
+### War Room organization
97
+
98
+We recommend a few strategies for organizing your War Rooms.
99
+
100
+- **Service, purpose, location, etc.**
101
+ You can group War Rooms by a service (Nginx, MySQL, Pulsar, and so on), their purpose (webserver, database, application), their physical location, whether they're "bare metal" or a Docker container, the PaaS/cloud provider it runs on, and much more.
102
+ This allows you to see entire slices of your infrastructure by moving from one War Room to another.
103
+
104
+- **End-to-end apps/services**
105
+ If you have a user-facing SaaS product, or an internal service that this said product relies on, you may want to monitor that entire stack in a single War Room. This might include Kubernetes clusters, Docker containers, proxies, databases, web servers, brokers, and more.
106
+ End-to-end War Rooms are valuable tools for ensuring the health and performance of your organization's essential services.
107
+
108
+- **Incident response**
109
+ You can also create new War Rooms as one of the first steps in your incident response process.
110
+ For example, you have a user-facing web app that relies on Apache Pulsar for a message queue, and one of your nodes using the [Pulsar collector](https://github.com/netdata/go.d.plugin/blob/master/modules/pulsar/README.md) begins reporting a suspiciously low messages rate.
111
+ You can create a War Room called `$year-$month-$day-pulsar-rate`, add all your Pulsar nodes in addition to nodes they connect to, and begin diagnosing the root cause in a War Room optimized for getting to resolution as fast as possible.
112
+
113
+### Add War Rooms
114
+
115
+To add new War Rooms to any Space, click on the green plus icon **+** next to the **War Rooms** heading on the left (Space's) sidebar.
116
+
117
+In the panel, give the War Room a name and description, and choose whether it's public or private.
118
+Anyone in your Space can join public War Rooms, but can only join private War Rooms with an invitation.
119
+
120
+### Manage War Rooms
121
+
122
+All the users and nodes involved in a particular Space can be part of a War Room.
123
+
124
+Any user can change simple settings of a War room, like the name or the users participating in it.
125
+Click on the gear icon of the War Room's name in the top of the page to do that. A sidebar will open with options for this War Room:
126
+
127
+1. To **change a War Room's name, description, or public/private status**, click on **War Room** tab.
128
+
129
+2. To **include an existing node** to a War Room or **connect a new node\*** click on **Nodes** tab. Choose any connected node you want to add to this War Room by clicking on the checkbox next to its hostname, then click **+ Add** at the top of the panel.
130
+
131
+3. To **add existing users to a War Room**, click on **Add Users**.
132
+ See our [invite doc](#invite-your-team.md) for details on inviting new users to your Space in Netdata Cloud.
133
+
134
+> #### Note
135
+>
136
+>\* This action requires **admin** rights for this Space
137
+
138
+#### More actions
139
+
140
+To **view or remove nodes** in a War Room, click on the **Nodes tab**. To remove a node from the current War Room, click on
141
+the **🗑** icon.
142
+
143
+> #### Info
144
+>
145
+> Removing a node from a War Room does not remove it from your Space.
146
+
147
+## Invite your team
148
+
149
+Invite your entire SRE, DevOPs, or ITOps team to Netdata Cloud, to give everyone insights into your infrastructure from a single pane of glass.
150
+
151
+Invite new users to your Space by clicking on **Invite Users** in
152
+the [Space](#netdata-cloud-spaces) management area.
153
+
154
+
155
+
156
+
157
+You will be prompted to enter the email addresses of the users you want to invite to your Space. You can enter any number of email addresses, separated by a comma, to send multiple invitations at once.
158
+
159
+Next, choose the War Rooms you want to invite these users to. Once logged in, these users are not restricted only to
160
+these War Rooms. They can be invited to others, or join any that are public.
161
+
162
+Next, pick a role for the invited user. You can read more about [which roles are available](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md#what-roles-are-available) based on your [subscription plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md).
163
+
164
+Click the **Send** button to send an email invitation, which will prompt them
165
+to [sign up](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/sign-in.md) and join your Space.
166
+
167
+
168
+
169
+Any unaccepted invitations remain under **Invitations awaiting response**. These invitations can be rescinded at any
170
+time by clicking the trash can icon.
docs/cloud/manage/plans.md
+1
-1
@@ -113,7 +113,7 @@ For more details check the documentation under [Alert Notifications](https://git
113
114
#### **Related Concepts**
115
116
-* [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)
116
+* [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces)
117
* [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
118
* [Events feed](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/events-feed.md)
119
* [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md)
docs/cloud/spaces.md
deleted
-79
@@ -1,79 +0,0 @@
1
-# Netdata Cloud Spaces
2
-
3
-Organize your multi-organization infrastructure monitoring on Netdata Cloud by creating Spaces to completely isolate access to your Agent-monitored nodes.
4
-
5
-A Space is a high-level container. It's a collaboration space where you can organize team members, access levels and the
6
-nodes you want to monitor.
7
-
8
-Let's talk through some strategies for creating the most intuitive Cloud experience for your team.
9
-
10
-## How to organize your Netdata Cloud
11
-
12
-You can use any number of Spaces you want, but as you organize your Cloud experience, keep in mind that _you can only
13
-add any given node to a single Space_. This 1:1 relationship between node and Space may dictate whether you use one
14
-encompassing Space for your entire team and separate them by War Rooms, or use different Spaces for teams monitoring
15
-discrete parts of your infrastructure.
16
-
17
-If you have been invited to Netdata Cloud by another user by default you will able to see this space. If you are a new
18
-user the first space is already created.
19
-
20
-The other consideration for the number of Spaces you use to organize your Netdata Cloud experience is the size and
21
-complexity of your organization.
22
-
23
-For small team and infrastructures we recommend sticking to a single Space so that you can keep all your nodes and their
24
-respective metrics in one place. You can then use
25
-multiple [War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md)
26
-to further organize your infrastructure monitoring.
27
-
28
-Enterprises may want to create multiple Spaces for each of their larger teams, particularly if those teams have
29
-different responsibilities or parts of the overall infrastructure to monitor. For example, you might have one SRE team
30
-for your user-facing SaaS application and a second team for infrastructure tooling. If they don't need to monitor the
31
-same nodes, you can create separate Spaces for each team.
32
-
33
-## Navigate between spaces
34
-
35
-Click on any of the boxes to switch between available Spaces.
36
-
37
-Netdata Cloud abbreviates each Space to the first letter of the name, or the first two letters if the name is two words
38
-or more. Hover over each icon to see the full name in a tooltip.
39
-
40
-To add a new Space click on the green **+** button . Enter the name of the Space and click **Save**.
41
-
42
-
43
-
44
-## Manage Spaces
45
-
46
-Manage your spaces by selecting in a particular space and clicking in the small gear icon in the lower left corner. This
47
-will open a side tab in which you can:
48
-
49
-1. _Configure this Space*_, in the first tab (**Space**) you can change the name, description or/and some privilege
50
- options of this space
51
-
52
-2. _Edit the War Rooms*_, click on the **War rooms** tab to add or remove War Rooms.
53
-
54
-3. _Connect nodes*_, click on **Nodes** tab. Copy the claiming script to your node and run it. See the
55
- [connect to Cloud doc](https://github.com/netdata/netdata/blob/master/claim/README.md) for details.
56
-
57
-4. _Manage the users*_, click on **Users**.
58
- The [invitation doc](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md)
59
- details the invitation process.
60
-
61
-5. _Manage notification setting*_, click on **Notifications** tab to turn off/on notification methods.
62
-
63
-6. _Manage your bookmarks*_, click on the **Bookmarks** tab to add or remove bookmarks that you need.
64
-
65
-> ### Note
66
->
67
-> \* This action requires admin rights for this space
68
-
69
-## Obsoleting offline nodes from a Space
70
-
71
-Netdata admin users now have the ability to remove obsolete nodes from a space.
72
-
73
-- Only admin users have the ability to obsolete nodes
74
-- Only offline nodes can be marked obsolete (Live nodes and stale nodes cannot be obsoleted)
75
-- Node obsoletion works across the entire space, so the obsoleted node will be removed from all rooms belonging to the
76
- space
77
-- If the obsoleted nodes eventually become live or online once more they will be automatically re-added to the space
78
-
79
-
docs/cloud/visualize/dashboards.md
+1
-1
@@ -106,6 +106,6 @@ Because of the visual complexity of individual charts, dashboards require a mini
106
## What's next?
107
108
Once you've designed a dashboard or two, make sure
109
-to [invite your team](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md) if
109
+to [invite your team](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#invite-your-team) if
110
you haven't already. You can add these new users to the same War Room to let them see the same dashboards without any
111
effort.
docs/cloud/visualize/kubernetes.md
+1
-1
@@ -79,7 +79,7 @@ and `k8s_node_name`. The default is `k8s_controller_name`.
79
80
### Filtering
81
82
-Filtering behaves identically to the [node filter in War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md#node-filter), with the ability to
82
+Filtering behaves identically to the [node filter in War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/node-filter.md), with the ability to
83
filter pods/containers by `container_id` and `namespace`.
84
85
### Detailed information
docs/cloud/visualize/nodes.md
+3
-3
@@ -14,9 +14,9 @@ real-time charts.
14
Use the [Overview](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/overview.md) for monitoring an infrastructure in real time using
15
composite charts and Netdata's familiar dashboard UI.
16
17
-Check the [War Room docs](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md) for details on the utility bar, which contains the [node
18
-filter](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md#node-filter) and the [timeframe
19
-selector](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md#play-pause-force-play-and-timeframe-selector).
17
+Check the [node
18
+filter](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/node-filter.md) and the [Visualization date time controls
19
+selector](https://github.com/netdata/netdata/blob/master/docs/dashboard/visualization-date-and-time-controls.md) for tools available on the utility bar.
20
21
## Add and customize metrics columns
22
docs/cloud/war-rooms.md
deleted
-60
@@ -1,60 +0,0 @@
1
-# Netdata Cloud War rooms
2
-
3
-Netdata Cloud uses War Rooms to organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
4
-
5
-Once you add nodes to a Space, all of your nodes will be visible in the **All nodes** War Room. This is a special War Room
6
-which gives you an overview of all of your nodes in this particular Space. Then you can create functional separations of
7
-your nodes into more War Rooms. Every War Room has its own dashboards, navigation, indicators, and management tools.
8
-
9
-
10
-
11
-## War Room organization
12
-
13
-We recommend a few strategies for organizing your War Rooms.
14
-
15
-- **Service, purpose, location, etc.**
16
- You can group War Rooms by a service (Nginx, MySQL, Pulsar, and so on), their purpose (webserver, database, application), their physical location, whether they're "bare metal" or a Docker container, the PaaS/cloud provider it runs on, and much more.
17
- This allows you to see entire slices of your infrastructure by moving from one War Room to another.
18
-
19
-- **End-to-end apps/services**
20
- If you have a user-facing SaaS product, or an internal service that this said product relies on, you may want to monitor that entire stack in a single War Room. This might include Kubernetes clusters, Docker containers, proxies, databases, web servers, brokers, and more.
21
- End-to-end War Rooms are valuable tools for ensuring the health and performance of your organization's essential services.
22
-
23
-- **Incident response**
24
- You can also create new War Rooms as one of the first steps in your incident response process.
25
- For example, you have a user-facing web app that relies on Apache Pulsar for a message queue, and one of your nodes using the [Pulsar collector](https://github.com/netdata/go.d.plugin/blob/master/modules/pulsar/README.md) begins reporting a suspiciously low messages rate.
26
- You can create a War Room called `$year-$month-$day-pulsar-rate`, add all your Pulsar nodes in addition to nodes they connect to, and begin diagnosing the root cause in a War Room optimized for getting to resolution as fast as possible.
27
-
28
-## Add War Rooms
29
-
30
-To add new War Rooms to any Space, click on the green plus icon **+** next the **War Rooms** heading on the left (Space's) sidebar.
31
-
32
-In the panel, give the War Room a name and description, and choose whether it's public or private.
33
-Anyone in your Space can join public War Rooms, but can only join private War Rooms with an invitation.
34
-
35
-## Manage War Rooms
36
-
37
-All the users and nodes involved in a particular Space can be part of a War Room.
38
-
39
-Any user can change simple settings of a War room, like the name or the users participating in it.
40
-Click on the gear icon of the War Room's name in the top of the page to do that. A sidebar will open with options for this War Room:
41
-
42
-1. To **change a War Room's name, description, or public/private status**, click on **War Room** tab.
43
-
44
-2. To **include an existing node** to a War Room or **connect a new node\*** click on **Nodes** tab. Choose any connected node you want to add to this War Room by clicking on the checkbox next to its hostname, then click **+ Add** at the top of the panel.
45
-
46
-3. To **add existing users to a War Room**, click on **Add Users**.
47
- See our [invite doc](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md) for details on inviting new users to your Space in Netdata Cloud.
48
-
49
-> ### Note
50
->
51
->\* This action requires **admin** rights for this Space
52
-
53
-### More actions
54
-
55
-To **view or remove nodes** in a War Room, click on the **Nodes tab**. To remove a node from the current War Room, click on
56
-the **🗑** icon.
57
-
58
-> ### Info
59
->
60
-> Removing a node from a War Room does not remove it from your Space.
docs/glossary.md
+5
-5
@@ -27,7 +27,7 @@ Use the alphabatized list below to find the answer to your single-term questions
27
28
## B
29
30
-- [**Bookmarks**](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md#manage-spaces): Netdata Cloud's bookmarks put your tools in one accessible place. Bookmarks are shared between all War Rooms in a Space, so any users in your Space will be able to see and use them.
30
+- [**Bookmarks**](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#manage-spaces): Netdata Cloud's bookmarks put your tools in one accessible place. Bookmarks are shared between all War Rooms in a Space, so any users in your Space will be able to see and use them.
31
32
## C
33
@@ -126,7 +126,7 @@ metrics, troubleshoot complex performance problems, and make data interoperable
126
127
## O
128
129
-- [**Obsoletion**(of nodes)](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md#obsoleting-offline-nodes-from-a-space): Removing nodes from a space.
129
+- [**Obsoletion**(of nodes)](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#obsoleting-offline-nodes-from-a-space): Removing nodes from a space.
130
131
- [**Orchestrators**](https://github.com/netdata/netdata/blob/master/collectors/README.md#collector-architecture-and-terminology): External plugins that run and manage one or more modules. They run as independent processes.
132
@@ -146,7 +146,7 @@ metrics, troubleshoot complex performance problems, and make data interoperable
146
147
- [**Replication Streaming**](https://github.com/netdata/netdata/blob/master/streaming/README.md): Streaming configuration where child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
148
149
-- [**Room** or **War Room**](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
149
+- [**Room** or **War Room**](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
150
151
## S
152
@@ -154,7 +154,7 @@ metrics, troubleshoot complex performance problems, and make data interoperable
154
155
<!-- No link for this file in current structure. - **Snapshots** https://github.com/netdata/netdata/blob/master/docs/tasks/miscellaneous/snapshot-data.md: An image of your dashboard at any given time, whicn can be imiported into any other node running Netdata or used to genereated a PDF file for your records. -->
156
157
-- [**Space**](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md): A high-level container and virtual collaboration area where you can organize team members, access levels,and the nodes you want to monitor.
157
+- [**Space**](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces): A high-level container and virtual collaboration area where you can organize team members, access levels,and the nodes you want to monitor.
158
159
## T
160
@@ -173,7 +173,7 @@ even thousands of nodes. There are no actual bottlenecks especially if you retai
173
174
## W
175
176
-- [**War Room** or **Room**](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
176
+- [**War Room** or **Room**](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
177
178
## Z
179
docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+1
-1
@@ -248,7 +248,7 @@ from any number of distributed nodes to see how your application interacts with
248
systems.
249
250
Now that you can see eBPF metrics in Netdata Cloud, you can [invite your
251
-team](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md) and share your findings with others.
251
+team](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#invite-your-team) and share your findings with others.
252
253
254
docs/guides/using-host-labels.md
+1
-1
@@ -5,7 +5,7 @@ Netdata allows to organize your observability infrastructure with spaces, war ro
5
6
## Spaces and war rooms
7
8
-[Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md) are used for organization-level or infrastructure-level
8
+[Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces) are used for organization-level or infrastructure-level
9
grouping of nodes and people. A node can only appear in a single space, while people can have access to multiple spaces.
10
11
The [war rooms](https://github.com/netdata/netdata/edit/master/docs/cloud/war-rooms.md) in a space bring together nodes and people in
docs/quickstart/infrastructure.md
+10
-10
@@ -41,11 +41,11 @@ SRE team for the user-facing SaaS application, and a second IT team for managing
41
don't monitor the same nodes, they can work in separate Spaces and then further organize their nodes into War Rooms.
42
43
Next, set up War Rooms. Netdata Cloud creates dashboards and visualizations based on the nodes added to a given War
44
-Room. You can [organize War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md#war-room-organization) in any way
44
+Room. You can [organize War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#war-room-organization) in any way
45
you want, such as by the application type, for end-to-end application monitoring, or as an incident response tool.
46
47
-Learn more about [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md) and [War
48
-Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md), including how to manage each, in their respective reference
47
+Learn more about [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces) and [War
48
+Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms), including how to manage each, in their respective reference
49
documentation.
50
51
### Invite your team
@@ -55,7 +55,7 @@ inviting others, you can better synchronize with your team or colleagues to unde
55
When something goes wrong, you'll be ready to collaboratively troubleshoot complex performance problems from a single
56
pane of glass.
57
58
-To [invite new users](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md), click on **Invite Users** in the
58
+To [invite new users](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#invite-your-team), click on **Invite Users** in the
59
Space management Area. Choose which War Rooms to add this user to, then click **Send**.
60
61
If your team members have trouble signing in, direct them to the [Netdata Cloud sign
@@ -165,8 +165,8 @@ collect from across your infrastructure with Netdata.
165
<Box
166
title="Spaces and War Rooms">
167
<BoxList>
168
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)" title="Spaces" />
169
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md)" title="War Rooms" />
168
+ <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces)" title="Spaces" />
169
+ <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms)" title="War Rooms" />
170
</BoxList>
171
</Box>
172
<Box
@@ -195,7 +195,7 @@ collect from across your infrastructure with Netdata.
195
title="Management and settings">
196
<BoxList>
197
<BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/sign-in.md)" title="Sign in with email, Google, or GitHub" />
198
- <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md)" title="Invite your team" />
198
+ <BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#invite-your-team)" title="Invite your team" />
199
<BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/themes.md)" title="Choose your Netdata Cloud theme" />
200
<BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md)" title="Role-Based Access" />
201
<BoxListItemRegexLink to="[](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md)" title="Paid Plans" />
@@ -204,8 +204,8 @@ collect from across your infrastructure with Netdata.
204
</Grid>
205
206
- Spaces and War Rooms
207
- - [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)
208
- - [War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md)
207
+ - [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces)
208
+ - [War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms)
209
- Dashboards
210
- [Overview](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/overview.md)
211
- [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/nodes.md)
@@ -220,7 +220,7 @@ collect from across your infrastructure with Netdata.
220
- [Events Feed](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/events-feed.md)
221
- Management and settings
222
- [Sign in with email, Google, or GitHub](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/sign-in.md)
223
- - [Invite your team](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md)
223
+ - [Invite your team](hhttps://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#invite-your-team)
224
- [Choose your Netdata Cloud theme](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/themes.md)
225
- [Role-Based Access](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md)
226
- [Paid Plans](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md)
docs/store/distributed-data-architecture.md
+1
-1
@@ -69,7 +69,7 @@ When you use the database engine to store your metrics, you can always perform a
69
Netdata Cloud does not store metric values.
70
71
To enable certain features, such as [viewing active alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md)
72
-or [filtering by hostname/service](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md), Netdata Cloud does
72
+or [filtering by hostname](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/node-filter.md), Netdata Cloud does
73
store configured alarms, their status, and a list of active collectors.
74
75
Netdata does not and never will sell your personal data or data about your deployment.
docs/visualize/overview-infrastructure.md
+3
-3
@@ -36,8 +36,8 @@ Let's walk through some examples of using the Overview to monitor and troublesho
36
### Filter nodes and pick relevant times
37
38
While not exclusive to Overview, you can use two important features, [node
39
-filtering](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md#node-filter) and the [time & date
40
-picker](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md#time--date-picker), to widen or narrow your infrastructure
39
+filtering](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/node-filter.md) and the [time & date
40
+picker](https://github.com/netdata/netdata/blob/master/docs/dashboard/visualization-date-and-time-controls.md), to widen or narrow your infrastructure
41
monitoring focus.
42
43
By default, the Overview shows composite charts aggregated from every node in the War Room, but you can change that
@@ -52,7 +52,7 @@ establishing a baseline of infrastructure performance or targeted root cause ana
52
For example, use the **Quick Selector** options to pick the 12-hour option first thing in the morning to check your
53
infrastructure for any odd behavior overnight. Use the 7-day option to observe trends between various days of the week.
54
55
-See the [War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md) docs for more details on both features.
55
+See the [War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms) docs for more details on both features.
56
57
### Configure composite charts to identify problems
58
packaging/installer/README.md
+2
@@ -7,6 +7,8 @@ import TabItem from '@theme/TabItem';
7
8
This document will guide you through installing the open-source Netdata monitoring Agent on Linux, Docker, Kubernetes, and many others, often with one command.
9
10
+Netdata is very flexible and can be used to monitor all kinds of infrastructure. Read more about possible [Deployment strategies](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/deployment-strategies.md) to understand what better suites your needs.
11
+
12
## Get started
13
14
Netdata is a free and open-source (FOSS) monitoring agent that collects thousands of hardware and software metrics from
packaging/installer/methods/macos.md
+1
-1
@@ -38,7 +38,7 @@ The Netdata Agent is installed under `/usr/local/netdata`. Dependencies are hand
38
The `kickstart.sh` script accepts additional parameters to automatically [connect](https://github.com/netdata/netdata/blob/master/claim/README.md) your node to Netdata
39
Cloud immediately after installation. Find the `token` and `rooms` strings by [signing in to Netdata
40
Cloud](https://app.netdata.cloud/sign-in?cloudRoute=/spaces), then clicking on **Connect Nodes** in the [Spaces management
41
-area](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md).
41
+area](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces).
42
43
- `--claim-token`: Specify a unique claiming token associated with your Space in Netdata Cloud to be used to connect to the node
44
after the install.