docs: Update kickstart URL to canonical get.netdata.cloud (#21938)
Fotis Voutsas committed
Mar 12, 2026 at 13:24 UTC
d9109347fe6a576f8d2898ec3fd2743f2a75b5f3
2 files changed
+9
-9
docs/getting-started-netdata/guide.md
+4
-4
@@ -100,7 +100,7 @@ Once logged into Netdata Cloud, you'll see connection instructions. There are th
100
All methods will show you a command like this:
101
102
```bash
103
-bash <(curl -Ss https://my-netdata.io/kickstart.sh) --claim-token YOUR_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
103
+bash <(curl -Ss https://get.netdata.cloud/kickstart.sh) --claim-token YOUR_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
104
```
105
106
:::
@@ -228,7 +228,7 @@ Click "Invite Users" in your Space sidebar to add team members. Set appropriate
228
**Organize by Your Needs:**
229
230
| **Category** | **Examples** |
231
-|--------------------|--------------------------------------|
231
+| ------------------ | ------------------------------------ |
232
| **By Service** | Web servers, databases, applications |
233
| **By Location** | Data centers, cloud regions |
234
| **By Team** | DevOps, SRE, development teams |
@@ -248,7 +248,7 @@ Click "Invite Users" in your Space sidebar to add team members. Set appropriate
248
### Traditional Monitoring vs Netdata Business
249
250
| **Traditional Monitoring** | | **Netdata Business** |
251
-|--------------------------------------------------|:------:|----------------------------------------------------|
251
+| ------------------------------------------------ | :----: | -------------------------------------------------- |
252
| **Navigate complex interfaces** during incidents | | **Get instant analysis** with natural language |
253
| **Build dashboards** during incidents | **VS** | **Automatic dashboards** with zero configuration |
254
| **Manually correlate data** across systems | | **AI-powered correlation** and root cause analysis |
@@ -262,7 +262,7 @@ Experience the future of infrastructure monitoring with AI that actually works.
262
**AI Features Overview:**
263
264
| **Capability** | **What It Does** | **Access** |
265
-|--------------------------|-------------------------------------|--------------------------------------|
265
+| ------------------------ | ----------------------------------- | ------------------------------------ |
266
| **AI Chat with Netdata** | Ask questions in natural language | Available now for all deployments |
267
| **AI DevOps Copilot** | CLI-based AI automation | Available now with MCP tools |
268
| **AI Insights** | Professional reports in 2-3 minutes | Business plans get unlimited reports |
docs/learn/unclaim-reclaim-node.md
+5
-5
@@ -5,7 +5,7 @@
5
**What's the difference between unclaiming/reclaiming and removing a node?**
6
7
| Action | What it does | Agent status |
8
-|-----------------------|-------------------------------------------------------|-----------------------------------------|
8
+| --------------------- | ----------------------------------------------------- | --------------------------------------- |
9
| **Unclaim & Reclaim** | Disconnect from current Space, connect to a new Space | Agent keeps running |
10
| **Remove** | Permanently delete node from Netdata Cloud | Agent may keep running but disconnected |
11
@@ -65,7 +65,7 @@ sudo systemctl restart netdata
65
Run the standard claim command with your new Space's token:
66
67
```bash
68
-bash <(curl -Ss https://my-netdata.io/kickstart.sh) --claim-token YOUR_NEW_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
68
+bash <(curl -Ss https://get.netdata.cloud/kickstart.sh) --claim-token YOUR_NEW_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
69
```
70
71
### Option 2: Configuration File
@@ -109,9 +109,9 @@ After reclaiming, verify the node appears in:
109
- Verify the claim token is correct for the new Space
110
- Check `/var/lib/netdata/cloud.d/` was removed before reclaiming
111
- Review agent logs using:
112
- - `journalctl --namespace netdata -b 0 | grep -i CLAIM`
113
- - or:
114
- - `grep -i CLAIM /var/log/netdata/daemon.log`
112
+ - `journalctl --namespace netdata -b 0 | grep -i CLAIM`
113
+ - or:
114
+ - `grep -i CLAIM /var/log/netdata/daemon.log`
115
116
**Reconnection fails:**
117