61366a441 · cryptotaxi247/netdata-1

@@ -1,133 +0,0 @@

1 -<!--

2 -title: "Get started with Netdata Cloud"

3 -description: >-

4 - "Ready to get real-time visibility into your entire infrastructure? This guide will help you get started on

5 - Netdata Cloud."

6 -image: "/img/seo/cloud_get-started.png"

7 -custom_edit_url: "https://github.com/netdata/learn/blob/master/docs/cloud/get-started.mdx"

8 --->

9 -

10 -import Link from '@docusaurus/Link'

11 -import Callout from '@site/src/components/Callout'

12 -

13 -Ready to get real-time visibility into your entire infrastructure with Netdata Cloud? This guide will walk you through

14 -the onboarding process, such as setting up your Space and War Room and connecting your first nodes.

15 -

16 -## Before you start

17 -

18 -Before you get started with Netdata Cloud, you should have the open-source Netdata monitoring agent installed. See our

19 -[installation guide](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx) for details.

20 -

21 -If you already have the Netdata agent running on your node(s), make sure to update it to v1.32 or higher. Read the

22 -[updating documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md) for information

23 -on how to update based on the method you used to install Netdata on that node.

24 -

25 -## Begin the onboarding process

26 -

27 -Get started by signing in to Netdata. Read

28 -the [sign in](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/sign-in.mdx) doc for details on the

29 -authentication methods we use.

30 -

31 -<Link to="https://app.netdata.cloud" className="group">

32 - <button className="relative text-text bg-gray-200 px-4 py-2 rounded">

33 - <span className="z-10 relative font-semibold group-hover:text-gray-100">Sign in to Netdata</span>

34 - <div className="opacity-0 group-hover:opacity-100 transition absolute z-0 inset-0 bg-gradient-to-r from-green to-green-lighter rounded"></div>

35 - </button>

36 -</Link>

37 -

38 -Once signed in with your preferred method, a

39 -General [War Room](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md) and

40 -a [Space](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)

41 -named for your login email are automatically created. You can configure more Spaces and War Rooms to help you you

42 -organize your team

43 -and the many systems that make up your infrastructure. For example, you can put product and infrastructure SRE teams in

44 -separate

45 -Spaces, and then use War Rooms to group nodes by their service (`nginx`), purpose (`webservers`), or physical

46 -location (`IAD`).

47 -

48 -Don't worry! You can always add more Spaces and War Rooms later if you decide to reorganize how you use Netdata Cloud.

49 -

50 -## Connect your nodes

51 -

52 -From within the created War Rooms, Netdata Cloud prompts you

53 -to [connect](https://github.com/netdata/netdata/blob/master/claim/README.md) your nodes to Netdata Cloud. Non-admin

54 -users can users can select from existing nodes already connected to the space or select an admin from a provided list to

55 -connect node.

56 -You can connect any node running Netdata, whether it's a physical or virtual machine, a Docker container, IoT device,

57 -and more.

58 -

59 -The connection process securely connects any node to Netdata Cloud using

60 -the [Agent-Cloud link](https://github.com/netdata/netdata/blob/master/aclk/README.md). By

61 -connecting a node, you prove you have write and administrative access to that node. Connecting to Cloud also prevents

62 -any third party

63 -from connecting a node that you control. Keep in mind:

64 -

65 -- _You can only connect any given node in a single Space_. You can, however, add that connected node to multiple War

66 - Rooms

67 - within that one Space.

68 -- You must repeat the connection process on every node you want to add to Netdata Cloud.

69 -

70 -<Callout type="notice">

71 -

72 -**Netdata Cloud ensures your data privacy by not storing metrics data from your nodes**. See our statement on Netdata

73 -Cloud [data privacy](https://github.com/netdata/netdata/blob/master/aclk/README.md/#data-privacy) for details on the

74 -data that's streamed from your nodes and the

75 -[connecting to cloud](https://github.com/netdata/netdata/blob/master/claim/README.md) doc for details about why we

76 -implemented the connection process and the encryption methods we use to secure your data in transit.

77 -

78 -</Callout>

79 -

80 -To connect a node, select which War Rooms you want to add this node to with the dropdown, then copy the script given by

81 -Netdata Cloud into your node's terminal.

82 -

83 -Hit **Enter**. The script should return `Agent was successfully claimed.`. If the claiming script returns errors, or if

84 -you don't see the node in your Space after 60 seconds, see

85 -the [troubleshooting information](https://github.com/netdata/netdata/blob/master/claim/README.md#troubleshooting).

86 -

87 -Repeat this process with every node you want to add to Netdata Cloud during onboarding. You can also add more nodes once

88 -you've finished onboarding by clicking the **Connect Nodes** button in

89 -the [Space management area](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md/#manage-spaces).

90 -

91 -### Alternatives and other operating systems

92 -

93 -**Docker**: You can execute the claiming script Netdata running as a Docker container, or attach the claiming script

94 -when creating the container for the first time, such as when you're spinning up ephemeral containers. See

95 -the [connect an agent running in Docker](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-an-agent-running-in-docker)

96 -documentation for details.

97 -

98 -**Without root privileges**: If you want to connect an agent without using root privileges, see our [connect

99 -documentation](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-an-agent-without-root-privileges).

100 -

101 -**With a proxy**: If your node uses a proxy to connect to the internet, you need to configure the node's proxy settings.

102 -See

103 -our [connect through a proxy](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy)

104 -doc for details.

105 -

106 -## Add bookmarks to essential resources

107 -

108 -When an anomaly or outage strikes, your team needs to access other essential resources quickly. You can use Netdata

109 -Cloud's bookmarks to put these tools in one accessible place. Bookmarks are shared between all War Rooms in a Space, so

110 -any users in your Space will be able to see and use them.

111 -

112 -Bookmarks can link to both internal and external resources. You can bookmark your app's status page for quick updates

113 -during an outage, a messaging system on your organization's intranet, or other tools your team uses to respond to

114 -changes in your infrastructure.

115 -

116 -To add a new bookmark, click on the **Add bookmark** link. In the panel, name the bookmark, include its URL, and write a

117 -short description for your team's reference.

118 -

119 -## What's next?

120 -

121 -You finish onboarding

122 -by [inviting members of your team](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md)

123 -to your Space. You

124 -can also invite them later. At this point, you're ready to use Cloud.

125 -

126 -Next, learn about the organization and interfaces

127 -behind [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)

128 -and [War

129 -Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md).

130 -

131 -If you're ready to explore, check out how to use

132 -the [Overview dashboard](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/overview.md), which is the

133 -default view for each new War Room you create.

Delete docs/cloud/get-started.mdx (#14382)