Docs edits on Cloud versions and On Prem (#19104)
Co-authored-by: ilyam8 <ilya@netdata.cloud>
Fotis Voutsas committed
Nov 29, 2024 at 16:05 UTC
8dea7e47029580720bc42987387e0c068b919ffc
4 files changed
+140
-243
docs/DICTIONARY.md
+3
-2
@@ -11,7 +11,7 @@ When the context is clear, we can omit the "Netdata" prefix for brevity.
11
| **Agent** (**Agents**) | The core monitoring software that collects, processes and stores metrics |
12
| **Daemon** | The main Netdata process |
13
| **Collector(s)** | The various collectors of Netdata |
14
-| **Registry** | The default Netdata Registry, or any Agent acting as one ||
14
+| **Registry** | The default Netdata Registry, or any Agent acting as one |
15
16
## Cloud
17
@@ -20,6 +20,7 @@ When the context is clear, we can omit the "Netdata" prefix for brevity.
20
| **Cloud** | The centralized platform for managing and visualizing Netdata metrics |
21
| **Claim(ing) Token** | The token used to Connect the Agent to the Cloud |
22
| **Connect(ing)(ion)** | The process of connecting the Agent to the Cloud. Do not use the word "claim" instead |
23
+| **Cloud On Prem** | The version of Cloud we ship for Businesses that want to run it on premises |
24
25
## Database
26
@@ -43,4 +44,4 @@ When the context is clear, we can omit the "Netdata" prefix for brevity.
44
| **Model(s)** | | Uppercase when referring to the ML Models Netdata uses |
45
| **Anomaly Detection** | | The capability to identify unusual patterns in metrics |
46
| **Metric Correlations** | | Filters dashboard to show metrics with the most significant changes in the selected time window |
46
-| **Anomaly Advisor** | | The interface and tooling for analyzing detected anomalies |
\ No newline at end of file
47
+| **Anomaly Advisor** | | The interface and tooling for analyzing detected anomalies |
docs/netdata-cloud/netdata-cloud-on-prem/README.md
-22
@@ -53,25 +53,3 @@ flowchart TD
53
%% auth ~~~ spaceroom
54
emqx <.-> bridges o-..-o pulsar
55
```
56
-
57
-## Requirements
58
-
59
-The following components are required to run Netdata Cloud On-Prem:
60
-
61
-- **Kubernetes cluster** version 1.23+
62
-- **Kubernetes metrics server** (for autoscaling)
63
-- **TLS certificate** for secure connections. A single endpoint is required but there is an option to split the frontend, api, and MQTT endpoints. The certificate must be trusted by all entities connecting to it.
64
-- Default **storage class configured and working** (persistent volumes based on SSDs are preferred)
65
-
66
-The following 3rd party components are used, which can be pulled with the `netdata-cloud-dependency` package we provide:
67
-
68
-- **Ingress controller** supporting HTTPS
69
-- **PostgreSQL** version 13.7 (main database for all metadata Netdata Cloud maintains)
70
-- **EMQX** version 5.11 (MQTT Broker that allows Agents to send messages to the On-Prem Cloud)
71
-- **Apache Pulsar** version 2.10+ (message broken for inter-container communication)
72
-- **Traefik** version 2.7.x (internal API Gateway)
73
-- **Elasticsearch** version 8.8.x (stores the feed of events)
74
-- **Redis** version 6.2 (caching)
75
-- imagePullSecret (our ECR repos are secured)
76
-
77
-Keep in mind though that the pulled versions are not configured properly for production use. Customers of Netdata Cloud On-Prem are expected to configure these applications according to their needs and policies for production use. Netdata Cloud On-Prem can be configured to use all these applications as a shared resource from other existing production installations.
docs/netdata-cloud/netdata-cloud-on-prem/installation.md
+124
-209
@@ -1,227 +1,142 @@
1
# Netdata Cloud On-Prem Installation
2
3
-This installation guide assumes the prerequisites for installing Netdata Cloud On-Prem as satisfied. For more information please refer to the [requirements documentation](/docs/netdata-cloud/netdata-cloud-on-prem/README.md#requirements).
3
+## System Requirements
4
5
-## Installation Requirements
5
+**Core Infrastructure**:
6
7
-The following components are required to install Netdata Cloud On-Prem:
7
+| Requirement | Details |
8
+|:----------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------|
9
+| **Kubernetes** | - Version 1.23 or newer<br/>- Metrics server installed (for autoscaling)<br/>- Default storage class configured (SSD-based preferred) |
10
+| **TLS certificate** | - Single certificate for all endpoints, or separate certificates for frontend, API, and MQTT<br/>- Must be trusted by all connecting entities. |
11
+| **Minimum Resources** | - 4 CPU cores<br/>- 15GiB memory<br/>- Note: Cloud services are ephemeral |
12
9
-- **AWS** CLI
10
-- **Helm** version 3.12+ with OCI Configuration (explained in the installation section)
11
-- **Kubectl**
12
-
13
-The minimum requirements for Netdata-Cloud are:
14
-
15
-- 4 CPU cores
16
-- 15GiB of memory
17
-- Cloud services are ephemeral
18
-
19
-The requirements for the non-production Dependencies helm chart:
13
+**Non-Production Dependencies Requirements**:
14
15
- 8 CPU cores
22
-- 14GiB of memory
23
-- 160GiB for PVCs (SSD)
24
-
25
-> **_NOTE:_** Values for each component may vary depending on the type of load. The most compute-intensive task that the On-Prem needs to perform is the initial sync of directly connected Agents. The testing for these requirements was conducted with 1,000 nodes directly connected to the On-Prem. If you plan on spawning hundreds of new nodes within a few minutes, Postgres will be the first bottleneck. For example, a 2 vCPU / 8 GiB memory / 1k IOPS database can handle 1,000 nodes without any problems if your environment is fairly steady, adding nodes in batches of 10-30 (directly connected).
26
-
27
-## Preparations for Installation
16
+- 14GiB memory
17
+- 160GiB SSD storage for PVCs
18
29
-### Configure AWS CLI
19
+> **Note**:
20
+>
21
+> These requirements were tested with 1,000 directly connected nodes.
22
+> Resource needs may vary based on your workload.
23
+> The initial sync of directly connected Agents is the most compute-intensive operation.
24
+> For example, a Postgres instance with 2 vCPU, 8GiB memory, and 1k IOPS can handle 1,000 nodes in a steady environment when adding nodes in batches of 10–30.
25
31
-Install [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html).
26
+## Required Components
27
33
-There are 2 options for configuring `aws cli` to work with the provided credentials. The first one is to set the environment variables:
28
+### Third-Party Services
29
35
-```bash
36
-export AWS_ACCESS_KEY_ID=<your_secret_id>
37
-export AWS_SECRET_ACCESS_KEY=<your_secret_key>
38
-```
30
+All components below are included in the `netdata-cloud-dependency` package:
31
40
-The second one is to use an interactive shell:
32
+| Component | Version | Purpose |
33
+|------------------------|---------|-------------------------------------|
34
+| **PostgreSQL** | 13.7 | Main metadata database |
35
+| **EMQX** | 5.11 | MQTT Broker for Agent communication |
36
+| **Apache Pulsar** | 2.10+ | Inter-container message broker |
37
+| **Traefik** | 2.7.x | Internal API Gateway |
38
+| **Elasticsearch** | 8.8.x | Events feed storage |
39
+| **Redis** | 6.2 | Caching layer |
40
+| **Ingress Controller** | - | HTTPS support |
41
+| **imagePullSecret** | - | Secured ECR repository access |
42
42
-```bash
43
-aws configure
44
-```
43
+> **Important**:
44
+>
45
+> The provided dependency versions require additional configuration for production use.
46
+> Customers should configure these applications according to their production requirements and policies.
47
46
-### Configure helm to use secured ECR repository
48
+### Installation Tools
49
48
-Using `aws` command we will generate a token for helm to access the secured ECR repository:
49
-
50
-```bash
51
-aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com
52
-```
53
-
54
-After this step you should be able to add the repository to your helm or just pull the helm chart:
55
-
56
-```bash
57
-helm pull oci://362923047827.dkr.ecr.us-east-1.amazonaws.com/netdata-cloud-dependency --untar #optional
58
-helm pull oci://362923047827.dkr.ecr.us-east-1.amazonaws.com/netdata-cloud-onprem --untar
59
-```
60
-
61
-Local folders with the newest versions of helm charts should appear on your working dir.
50
+- [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
51
+- Helm (version 3.12+ with OCI Configuration)
52
+- Kubectl
53
54
## Installation
55
65
-Netdata provides access to two helm charts:
66
-
67
-1. `netdata-cloud-dependency` - required applications for `netdata-cloud-onprem`.
68
-2. `netdata-cloud-onprem` - the application itself + provisioning
69
-
70
-### netdata-cloud-dependency
71
-
72
-This helm chart is designed to install the necessary applications:
73
-
74
-- Redis
75
-- Elasticsearch
76
-- EMQX
77
-- Apache Pulsar
78
-- PostgreSQL
79
-- Traefik
80
-- Mailcatcher
81
-- k8s-ecr-login-renew
82
-- kubernetes-ingress
83
-
84
-Although we provide an easy way to install all these applications, we expect users of Netdata Cloud On-Prem to provide production quality versions for them. Therefore, every configuration option is available through `values.yaml` in the folder that contains your netdata-cloud-dependency helm chart. All configuration options are described in `README.md` which is a part of the helm chart.
85
-
86
-Each component can be enabled/disabled individually. It is done by true/false switches in `values.yaml`. This way, it is easier to migrate to production-grade components gradually.
87
-
88
-Unless you prefer otherwise, `k8s-ecr-login-renew` is responsible for calling out the `AWS API` for token regeneration. This token is then injected into the secret that every node is using for authentication with secured ECR when pulling the images.
89
-
90
-The default setting in `values.yaml` of `netdata-cloud-onprem` - `.global.imagePullSecrets` is configured to work out of the box with the dependency helm chart.
91
-
92
-For helm chart installation - save your changes in `values.yaml` and execute:
93
-
94
-```shell
95
-cd [your helm chart location]
96
-helm upgrade --wait --install netdata-cloud-dependency -n netdata-cloud --create-namespace -f values.yaml .
97
-```
98
-
99
-Keep in mind that `netdata-cloud-dependency` is provided only as a proof of concept. Users installing Netdata Cloud On-Prem should properly configure these components.
100
-
101
-### netdata-cloud-onprem
102
-
103
-Every configuration option is available in `values.yaml` in the folder that contains your `netdata-cloud-onprem` helm chart. All configuration options are described in the `README.md` which is a part of the helm chart.
104
-
105
-#### Installing Netdata Cloud On-Prem
106
-
107
-```shell
108
-cd [your helm chart location]
109
-helm upgrade --wait --install netdata-cloud-onprem -n netdata-cloud --create-namespace -f values.yaml .
110
-```
111
-
112
-##### Important notes
113
-
114
-1. Installation takes care of provisioning the resources with migration services.
115
-
116
-2. During the first installation, a secret called the `netdata-cloud-common` is created. It contains several randomly generated entries. Deleting helm chart is not going to delete this secret, nor reinstalling the whole On-Prem, unless manually deleted by kubernetes administrator. The content of this secret is extremely relevant - strings that are contained there are essential parts of encryption. Losing or changing the data that it contains will result in data loss.
117
-
118
-## Short description of Netdata Cloud microservices
119
-
120
-### cloud-accounts-service
121
-
122
-Responsible for user registration & authentication. Manages user account information.
123
-
124
-### cloud-agent-data-ctrl-service
125
-
126
-Forwards request from the Cloud to the relevant Agents.
127
-The requests include:
128
-
129
-- Fetching chart metadata from the Agent
130
-- Fetching chart data from the Agent
131
-- Fetching function data from the Agent
132
-
133
-### cloud-agent-mqtt-input-service
134
-
135
-Forwards MQTT messages emitted by the Agent related to the Agent entities to the internal Pulsar broker. These include Agent connection state updates.
136
-
137
-### cloud-agent-mqtt-output-service
138
-
139
-Forwards Pulsar messages emitted in the Cloud related to the Agent entities to the MQTT broker. From there, the messages reach the relevant Agent.
140
-
141
-### cloud-alarm-config-mqtt-input-service
142
-
143
-Forwards MQTT messages emitted by the Agent related to the alarm-config entities to the internal Pulsar broker. These include the data for the alarm configuration as seen by the Agent.
144
-
145
-### cloud-alarm-log-mqtt-input-service
146
-
147
-Forwards MQTT messages emitted by the Agent related to the alarm-log entities to the internal Pulsar broker. These contain data about the alarm transitions that occurred in an Agent.
148
-
149
-### cloud-alarm-mqtt-output-service
150
-
151
-Forwards Pulsar messages emitted in the Cloud related to the alarm entities to the MQTT broker. From there, the messages reach the relevant Agent.
152
-
153
-### cloud-alarm-processor-service
154
-
155
-Persists latest alert statuses received from the Agent in the Cloud.
156
-Aggregates alert statuses from relevant node instances.
157
-Exposes API endpoints to fetch alert data for visualization on the Cloud.
158
-Determines if notifications need to be sent when alert statuses change and emits relevant messages to Pulsar.
159
-Exposes API endpoints to store and return notification-silencing data.
160
-
161
-### cloud-alarm-streaming-service
162
-
163
-Responsible for starting the alert stream between the Agent and the Cloud.
164
-Ensures that messages are processed in the correct order, and starts a reconciliation process between the Cloud and the Agent if out-of-order processing occurs.
165
-
166
-### cloud-charts-mqtt-input-service
167
-
168
-Forwards MQTT messages emitted by the Agent related to the chart entities to the internal Pulsar broker. These include the chart metadata that is used to display relevant charts on the Cloud.
169
-
170
-### cloud-charts-mqtt-output-service
171
-
172
-Forwards Pulsar messages emitted in the Cloud related to the charts entities to the MQTT broker. From there, the messages reach the relevant Agent.
173
-
174
-### cloud-charts-service
175
-
176
-Exposes API endpoints to fetch the chart metadata.
177
-Forwards data requests via the `cloud-agent-data-ctrl-service` to the relevant Agents to fetch chart data points.
178
-Exposes API endpoints to call various other endpoints on the Agent, for instance, functions.
179
-
180
-### cloud-custom-dashboard-service
181
-
182
-Exposes API endpoints to fetch and store custom dashboard data.
183
-
184
-### cloud-environment-service
185
-
186
-Serves as the first contact point between the Agent and the Cloud.
187
-Returns authentication and MQTT endpoints to connecting Agents.
188
-
189
-### cloud-feed-service
190
-
191
-Processes incoming feed events and stores them in Elasticsearch.
192
-Exposes API endpoints to fetch feed events from Elasticsearch.
193
-
194
-### cloud-frontend
195
-
196
-Contains the on-prem Cloud website. Serves static content.
197
-
198
-### cloud-iam-user-service
199
-
200
-Acts as a middleware for authentication on most of the API endpoints. Validates incoming token headers, injects the relevant ones, and forwards the requests.
201
-
202
-### cloud-metrics-exporter
203
-
204
-Exports various metrics from an On-Prem Cloud installation. Uses the Prometheus metric exposition format.
205
-
206
-### cloud-netdata-assistant
207
-
208
-Exposes API endpoints to fetch a human-friendly explanation of various netdata configuration options, namely the alerts.
209
-
210
-### cloud-node-mqtt-input-service
211
-
212
-Forwards MQTT messages emitted by the Agent related to the node entities to the internal Pulsar broker. These include the node metadata as well as their connectivity state, either direct or via parents.
213
-
214
-### cloud-node-mqtt-output-service
215
-
216
-Forwards Pulsar messages emitted in the Cloud related to the charts entities to the MQTT broker. From there, the messages reach the relevant Agent.
217
-
218
-### cloud-notifications-dispatcher-service
219
-
220
-Exposes API endpoints to handle integrations.
221
-Handles incoming notification messages and uses the relevant channels(email, slack...) to notify relevant users.
222
-
223
-### cloud-spaceroom-service
224
-
225
-Exposes API endpoints to fetch and store relations between Agents, nodes, spaces, users, and rooms.
226
-Acts as a provider of authorization for other Cloud endpoints.
227
-Exposes API endpoints to authenticate Agents connecting to the Cloud.
56
+1. **AWS CLI Configuration**
57
+
58
+ Configure AWS credentials using either environment variables:
59
+
60
+ ```bash
61
+ export AWS_ACCESS_KEY_ID=<your_secret_id>
62
+ export AWS_SECRET_ACCESS_KEY=<your_secret_key>
63
+ ```
64
+
65
+ Or through interactive setup:
66
+
67
+ ```bash
68
+ aws configure
69
+ ```
70
+
71
+2. **Configure Helm for ECR Access**
72
+
73
+ Generate token for ECR access:
74
+
75
+ ```bash
76
+ aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com
77
+ ```
78
+
79
+3. **Pull Required Helm Charts**
80
+
81
+ ```bash
82
+ helm pull oci://362923047827.dkr.ecr.us-east-1.amazonaws.com/netdata-cloud-dependency --untar # Optional
83
+ helm pull oci://362923047827.dkr.ecr.us-east-1.amazonaws.com/netdata-cloud-onprem --untar
84
+ ```
85
+ The charts will be extracted to your current working directory.
86
+
87
+4. **Install Dependencies**
88
+
89
+ The `netdata-cloud-dependency` chart installs all required third-party applications. While we provide this for easy setup, **production environments should use their own configured versions of these components**:
90
+
91
+ - Configure the installation by editing `values.yaml` in your `netdata-cloud-dependency` chart directory.
92
+ - Install the dependencies:
93
+ ```bash
94
+ cd [your helm chart location]
95
+ helm upgrade --wait --install netdata-cloud-dependency -n netdata-cloud --create-namespace -f values.yaml .
96
+ ```
97
+5. **Install Netdata Cloud On-Prem**
98
+
99
+ - Configure the installation by editing `values.yaml` in your `netdata-cloud-onprem` chart directory.
100
+ - Install the application:
101
+ ```bash
102
+ cd [your helm chart location]
103
+ helm upgrade --wait --install netdata-cloud-onprem -n netdata-cloud --create-namespace -f values.yaml .
104
+ ```
105
+
106
+ > **Important**:
107
+ >
108
+ > Installation includes resource provisioning with migration services.
109
+ >
110
+ > During the first installation, a `netdata-cloud-common` secret is created containing critical encryption data. This secret persists through reinstalls and should never be deleted, as this will result in data loss.
111
+
112
+## Architecture Components
113
+
114
+<details><summary>View detailed microservices description</summary>
115
+
116
+| Microservice | Description |
117
+|:---------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
118
+| cloud-accounts-service | Handles user registration & authentication |
119
+| cloud-agent-data-ctrl-service | Forwards request from the OCP to the relevant Agents. The requests include fetching Chart metadata, Chart data and Function data from the Agents. |
120
+| cloud-agent-mqtt-input-service | Forwards MQTT messages emitted by the Agent to the internal Pulsar broker. They are related to the Agent entities and include Agent connection state updates. |
121
+| cloud-agent-mqtt-output-service | Forwards Pulsar messages emitted on the OCP to the MQTT broker. They are related to the Agent entities. From there, the messages reach the relevant Agent. |
122
+| cloud-alarm-config-mqtt-input-service | Forwards MQTT messages emitted by the Agent to the internal Pulsar broker. They related to the alarm-config entities like data for the alarm configuration as seen by the Agent. |
123
+| cloud-alarm-log-mqtt-input-service | Forwards MQTT messages emitted by the Agent to the internal Pulsar broker. They are related to the alarm-log entities containing data about the alarm transitions that occurred in an Agent. |
124
+| cloud-alarm-mqtt-output-service | Forwards Pulsar messages emitted in the Cloud to the MQTT broker. They are related to the alarm entities and from there, the messages reach the relevant Agent. |
125
+| cloud-alarm-processor-service | Persists latest Alert status received from the Agent in the OCP<br/>Aggregates Alert statuses from relevant node instances<br/>Exposes API endpoints to fetch Alert data for visualization on the Cloud<br/>Determines if notifications need to be sent when Alert statuses change and emits relevant messages to Pulsar<br/>Exposes API endpoints to store and return notification-silencing data |
126
+| cloud-alarm-streaming-service | Responsible for starting the Alert stream between the Agent and the OCP<br/>Ensures that messages are processed in the correct order, and starts a reconciliation process between the Cloud and the Agent if out-of-order processing occurs |
127
+| cloud-charts-mqtt-input-service | Forwards MQTT messages emitted by the Agent related to the chart entities to the internal Pulsar broker. These include the chart metadata that is used to display relevant charts on the Cloud. |
128
+| cloud-charts-mqtt-output-service | Forwards Pulsar messages emitted in the Cloud related to the charts entities to the MQTT broker. From there, the messages reach the relevant Agent. |
129
+| cloud-charts-service | Exposes API endpoints to fetch the chart metadata<br/>Forwards data requests via the `cloud-agent-data-ctrl-service` to the relevant Agents to fetch chart data points<br/>Exposes API endpoints to call various other endpoints on the Agent, for instance, functions |
130
+| cloud-custom-dashboard-service | Exposes API endpoints to fetch and store custom dashboard data |
131
+| cloud-environment-service | Serves as the first contact point between the Agent and the OCP<br/>Returns authentication and MQTT endpoints to connecting Agents |
132
+| cloud-feed-service | Processes incoming feed events and stores them in Elasticsearch<br/>Exposes API endpoints to fetch feed events from Elasticsearch |
133
+| cloud-frontend | Contains the OCP website. Serves static content. |
134
+| cloud-iam-user-service | Acts as a middleware for authentication on most of the API endpoints<br/>Validates incoming token headers, injects the relevant ones, and forwards the requests |
135
+| cloud-metrics-exporter | Exports various metrics from an OCP installation<br/>Uses the Prometheus metric exposition format |
136
+| cloud-netdata-assistant | Exposes API endpoints to fetch a human-friendly explanation of various Netdata configuration options, namely the Alerts. |
137
+| cloud-node-mqtt-input-service | Forwards MQTT messages emitted by the Agent related to the node entities to the internal Pulsar broker<br/>These include the node metadata as well as their connectivity state, either direct or via Parents |
138
+| cloud-node-mqtt-output-service | Forwards Pulsar messages emitted in the OCP related to the charts entities to the MQTT broker<br/>From there, the messages reach the relevant Agent |
139
+| cloud-notifications-dispatcher-service | Exposes API endpoints to handle integrations<br/>Handles incoming notification messages and uses the relevant channels(email, slack...) to notify relevant users |
140
+| cloud-spaceroom-service | Exposes API endpoints to fetch and store relations between Agents, nodes, spaces, users, and rooms<br/>Acts as a provider of authorization for other Cloud endpoints<br/>Exposes API endpoints to authenticate Agents connecting to the Cloud |
141
+
142
+</details>
docs/netdata-cloud/versions.md
+13
-10
@@ -1,19 +1,22 @@
1
# Netdata Cloud Versions
2
3
-Netdata Cloud is provided in two versions:
3
+Netdata Cloud is available in two versions:
4
5
-- **SaaS**, we run and maintain Netdata Cloud and users use it to complement their observability with the additional features it provides.
5
+| Version | Description |
6
+|:-----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
7
+| **Cloud Service** | The fully-managed service hosted at [app.netdata.cloud](https://app.netdata.cloud). [Connect](/src/claim/README.md) your Agents to access comprehensive infrastructure monitoring, real-time dashboards, and advanced features. |
8
+| **Enterprise On-Prem** | A self-hosted version of Netdata Cloud for businesses requiring complete control over their monitoring infrastructure. Includes all features of our Cloud offering, deployed within your own environment. |
9
7
-- **On Prem**, we provide a licensed copy of the Netdata Cloud software, that users can install and run at their premises.
10
+Visit our [Pricing](https://www.netdata.cloud/pricing/) page to compare features and options.
11
9
-The pricing of both versions is similar, with the On-Prem version introducing a monthly fixed-fee for the extra support and packaging required when users are running Netdata Cloud by themselves.
12
+## Using Netdata Cloud Service
13
11
-For more information check our [Pricing](https://www.netdata.cloud/pricing/) page.
14
+1. [Create an account](https://app.netdata.cloud) on Netdata Cloud.
15
+2. Follow the provided setup instructions to install and connect Agents to your Space automatically
16
13
-## SaaS Version
17
+## Installing On-Prem
18
15
-[Sign-up to Netdata Cloud](https://app.netdata.cloud) and start connecting your Netdata Agents. The commands provided once you have signed up, include all the information to install and automatically connect (claim) Netdata Agents to your Netdata Cloud space.
19
+To learn more about installing Netdata Cloud in your own infrastructure:
20
17
-## On-Prem Version
18
-
19
-To deploy Netdata Cloud On-premises, take a look at the [related section](/docs/netdata-cloud/netdata-cloud-on-prem/README.md) on our Documentation.
21
+1. Review the [Architecture Diagram](/docs/netdata-cloud/netdata-cloud-on-prem/README.md) to understand the system components.
22
+2. Follow the [Deployment Guide](/docs/netdata-cloud/netdata-cloud-on-prem/installation.md) for detailed installation instructions