change api.netdata.cloud to app.netdata.cloud (#15538)
Ilya Mashchenko committed
Jul 26, 2023 at 12:38 UTC
a14983c7eea9dc76d28f097f9bb7e48681550263
11 files changed
+29
-29
aclk/README.md
+3
-3
@@ -12,7 +12,7 @@ The Cloud App lives at app.netdata.cloud which currently resolves to the followi
12
13
> ### Caution
14
>
15
->This list of IPs can change without notice, we strongly advise you to whitelist following domains `api.netdata.cloud`, `mqtt.netdata.cloud`, if this is not an option in your case always verify the current domain resolution (e.g via the `host` command).
15
+>This list of IPs can change without notice, we strongly advise you to whitelist following domains `app.netdata.cloud`, `mqtt.netdata.cloud`, if this is not an option in your case always verify the current domain resolution (e.g via the `host` command).
16
17
For a guide to connecting a node using the ACLK, plus additional troubleshooting and reference information, read our [connect to Cloud
18
documentation](https://github.com/netdata/netdata/blob/master/claim/README.md).
@@ -35,7 +35,7 @@ configuration uses two settings:
35
```conf
36
[global]
37
enabled = yes
38
- cloud base url = https://api.netdata.cloud
38
+ cloud base url = https://app.netdata.cloud
39
```
40
41
If your Agent needs to use a proxy to access the internet, you must [set up a proxy for
@@ -96,7 +96,7 @@ must contain only `EOF`.
96
```bash
97
[global]
98
enabled = no
99
- cloud base url = https://api.netdata.cloud
99
+ cloud base url = https://app.netdata.cloud
100
EOF
101
```
102
claim/README.md
+9
-9
@@ -69,7 +69,7 @@ When coming from the [Nodes tab](https://github.com/netdata/netdata/blob/master/
69
If you want to connect a node that is running on a Linux environment, the script that will be provided to you by Netdata Cloud is the [kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#automatic-one-line-installation-script) which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata Cloud. It should be similar to:
70
71
```bash
72
-wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://api.netdata.cloud
72
+wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud
73
```
74
75
The script should return `Agent was successfully claimed.`. If the connecting to Netdata Cloud process returns errors, or if you don't see
@@ -98,7 +98,7 @@ The default user is `netdata`. Yours may be different, so pay attention to the o
98
and run the script.
99
100
```bash
101
-wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://api.netdata.cloud
101
+wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud
102
```
103
104
### Connect an agent running in Docker
@@ -209,7 +209,7 @@ docker run -d --name=netdata \
209
--cap-add SYS_PTRACE \
210
--security-opt apparmor=unconfined \
211
-e NETDATA_CLAIM_TOKEN=TOKEN \
212
- -e NETDATA_CLAIM_URL="https://api.netdata.cloud" \
212
+ -e NETDATA_CLAIM_URL="https://app.netdata.cloud" \
213
-e NETDATA_CLAIM_ROOMS=ROOM1,ROOM2 \
214
-e NETDATA_CLAIM_PROXY=PROXY \
215
netdata/netdata
@@ -254,7 +254,7 @@ services:
254
- /etc/os-release:/host/etc/os-release:ro
255
environment:
256
- NETDATA_CLAIM_TOKEN=TOKEN
257
- - NETDATA_CLAIM_URL="https://api.netdata.cloud"
257
+ - NETDATA_CLAIM_URL="https://app.netdata.cloud"
258
- NETDATA_CLAIM_ROOMS=ROOM1,ROOM2
259
260
volumes:
@@ -275,7 +275,7 @@ Connect a _running Netdata Agent container_, where you don't want to recreate th
275
`netdata` with the name of your running container:
276
277
```bash
278
-docker exec -it netdata netdata-claim.sh -token=TOKEN -rooms=ROOM1,ROOM2 -url=https://api.netdata.cloud
278
+docker exec -it netdata netdata-claim.sh -token=TOKEN -rooms=ROOM1,ROOM2 -url=https://app.netdata.cloud
279
```
280
281
The values for `ROOM1,ROOM2` can be found by by going to Netdata Cloud, clicking the **Nodes** tab, clicking **Connect Nodes**, selecting **Docker**, and copying the `rooms=` value in the command provided.
@@ -288,7 +288,7 @@ you don't see the node in your Space after 60 seconds, see the [troubleshooting
288
To connect a node that is running on a macOS environment the script that will be provided to you by Netdata Cloud is the [kickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/macos.md#install-netdata-with-our-automatic-one-line-installation-script) which will install the Netdata Agent on your node, if it isn't already installed, and connect the node to Netdata Cloud. It should be similar to:
289
290
```bash
291
-curl https://my-netdata.io/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh --install-prefix /usr/local/ --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://api.netdata.cloud
291
+curl https://my-netdata.io/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh --install-prefix /usr/local/ --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud
292
```
293
294
The script should return `Agent was successfully claimed.`. If the connecting to Netdata Cloud process returns errors, or if you don't see
@@ -329,7 +329,7 @@ You can now move on to connecting. When you connect with the [kickstart](https:/
329
append the same proxy setting you added to `netdata.conf`.
330
331
```bash
332
-wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://api.netdata.cloud --claim-proxy http://[user:pass@]host:ip
332
+wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud --claim-proxy http://[user:pass@]host:ip
333
```
334
335
Hit **Enter**. The script should return `Agent was successfully claimed.`. If the connecting to Netdata Cloud process returns errors, or if
@@ -566,7 +566,7 @@ using the [ACLK](https://github.com/netdata/netdata/blob/master/aclk/README.md).
566
567
| setting | default | info |
568
|:-------------- |:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- |
569
-| cloud base url | <https://api.netdata.cloud> | The URL for the Netdata Cloud web application. You should not change this. If you want to disable Cloud, change the `enabled` setting. |
569
+| cloud base url | <https://app.netdata.cloud> | The URL for the Netdata Cloud web application. You should not change this. If you want to disable Cloud, change the `enabled` setting. |
570
| enabled | yes | The runtime option to disable the [Agent-Cloud link](https://github.com/netdata/netdata/blob/master/aclk/README.md) and prevent your Agent from connecting to Netdata Cloud. |
571
572
### Claiming script
@@ -580,7 +580,7 @@ using `sudo`, or as the user running the Agent (typically `netdata`), and passin
580
-rooms=ROOM1,ROOM2,...
581
where ROOMX is the War Room this node should be added to. This list is optional.
582
-url=URL_BASE
583
- where URL_BASE is the Netdata Cloud endpoint base URL. By default, this is https://api.netdata.cloud.
583
+ where URL_BASE is the Netdata Cloud endpoint base URL. By default, this is https://app.netdata.cloud.
584
-id=AGENT_ID
585
where AGENT_ID is the unique identifier of the Agent. This is the Agent's MACHINE_GUID by default.
586
-hostname=HOSTNAME
claim/netdata-claim.sh.in
+1
-1
@@ -136,7 +136,7 @@ MACHINE_GUID_FILE="@registrydir_POST@/netdata.public.unique.id"
136
CLAIMING_DIR="${NETDATA_VARLIB_DIR}/cloud.d"
137
TOKEN="unknown"
138
URL_BASE=$(get_config_value cloud global "cloud base url")
139
-[ -z "$URL_BASE" ] && URL_BASE="https://api.netdata.cloud" # Cover post-install with --dont-start
139
+[ -z "$URL_BASE" ] && URL_BASE="https://app.netdata.cloud" # Cover post-install with --dont-start
140
ID="unknown"
141
ROOMS=""
142
[ -z "$HOSTNAME" ] && HOSTNAME=$(hostname)
daemon/README.md
+1
-1
@@ -104,7 +104,7 @@ The command line options of the Netdata 1.10.0 version are the following:
104
-W simple-pattern pattern string
105
Check if string matches pattern and exit.
106
107
- -W "claim -token=TOKEN -rooms=ROOM1,ROOM2 url=https://api.netdata.cloud"
107
+ -W "claim -token=TOKEN -rooms=ROOM1,ROOM2 url=https://app.netdata.cloud"
108
Connect the agent to the workspace rooms pointed to by TOKEN and ROOM*.
109
110
Signals netdata handles:
docs/cloud/alerts-notifications/add-webhook-notification-configuration.md
+2
-2
@@ -140,7 +140,7 @@ server {
140
ssl_client_certificate /path/to/Netdata_CA.pem;
141
142
location / {
143
- if ($ssl_client_s_dn !~ "CN=api.netdata.cloud") {
143
+ if ($ssl_client_s_dn !~ "CN=app.netdata.cloud") {
144
return 403;
145
}
146
# ... existing location configuration ...
@@ -158,7 +158,7 @@ Listen 443
158
SSLCACertificateFile "/path/to/Netdata_CA.pem"
159
</VirtualHost>
160
<Directory /var/www/>
161
- Require expr "%{SSL_CLIENT_S_DN_CN} == 'api.netdata.cloud'"
161
+ Require expr "%{SSL_CLIENT_S_DN_CN} == 'app.netdata.cloud'"
162
# ... existing directory configuration ...
163
</Directory>
164
```
docs/guides/troubleshoot/troubleshooting-agent-with-cloud-connection.md
+7
-7
@@ -19,17 +19,17 @@ If the claiming process fails, the node will not appear at all in Netdata Cloud.
19
20
First ensure that you:
21
- Use the newest possible stable or nightly version of the agent (at least v1.32).
22
-- Your node can successfully issue an HTTPS request to https://api.netdata.cloud
22
+- Your node can successfully issue an HTTPS request to https://app.netdata.cloud
23
24
Other possible causes differ between kickstart installations and Docker installations.
25
26
### Verify your node can access Netdata Cloud
27
28
-If you run either `curl` or `wget` to do an HTTPS request to https://api.netdata.cloud, you should get
28
+If you run either `curl` or `wget` to do an HTTPS request to https://app.netdata.cloud, you should get
29
back a 404 response. If you do not, check your network connectivity, domain resolution,
30
and firewall settings for outbound connections.
31
32
-If your firewall is configured to completely prevent outbound connections, you need to whitelist `api.netdata.cloud` and `mqtt.netdata.cloud`. If you can't whitelist domains in your firewall, you can whitelist the IPs that the hostnames resolve to, but keep in mind that they can change without any notice.
32
+If your firewall is configured to completely prevent outbound connections, you need to whitelist `app.netdata.cloud` and `mqtt.netdata.cloud`. If you can't whitelist domains in your firewall, you can whitelist the IPs that the hostnames resolve to, but keep in mind that they can change without any notice.
33
34
If you use an outbound proxy, you need to [take some extra steps]( https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy).
35
@@ -100,7 +100,7 @@ process, but not have enough time to establish the ACLK connection.
100
101
### Verify that your firewall allows websockets
102
103
-The agent initiates an SSL connection to `api.netdata.cloud` and then upgrades that connection to use secure
103
+The agent initiates an SSL connection to `app.netdata.cloud` and then upgrades that connection to use secure
104
websockets. Some firewalls completely prevent the use of websockets, even for outbound connections.
105
106
## Previously connected agent that can no longer connect
@@ -110,7 +110,7 @@ that it is currently not connected.
110
111
### Verify that network connectivity is still possible
112
113
-Verify that you can still issue HTTPS requests to api.netdata.cloud and that no firewall or proxy changes were made.
113
+Verify that you can still issue HTTPS requests to app.netdata.cloud and that no firewall or proxy changes were made.
114
115
### Verify that the claiming info is persisted
116
@@ -124,7 +124,7 @@ work this way, as we have unique node identification information under `/var/lib
124
125
### Verify that your IP is not blocked by Netdata Cloud
126
127
-Most of the nodes change IPs dynamically. It is possible that your current IP has been restricted from accessing `api.netdata.cloud` due to security concerns, usually because it was spamming Netdata Coud with too many
127
+Most of the nodes change IPs dynamically. It is possible that your current IP has been restricted from accessing `app.netdata.cloud` due to security concerns, usually because it was spamming Netdata Coud with too many
128
failed requests (old versions of the agent).
129
130
To verify this:
@@ -135,7 +135,7 @@ To verify this:
135
sudo netdatacli aclk-state | grep "Banned By Cloud"
136
```
137
138
- The output will contain a line indicating if the IP is banned from `api.netdata.cloud`:
138
+ The output will contain a line indicating if the IP is banned from `app.netdata.cloud`:
139
140
```bash
141
Banned By Cloud: yes
packaging/installer/kickstart.sh
+1
-1
@@ -50,7 +50,7 @@ SELECTED_INSTALL_METHOD="none"
50
INSTALL_TYPE="unknown"
51
INSTALL_PREFIX=""
52
NETDATA_AUTO_UPDATES="default"
53
-NETDATA_CLAIM_URL="https://api.netdata.cloud"
53
+NETDATA_CLAIM_URL="https://app.netdata.cloud"
54
NETDATA_COMMAND="default"
55
NETDATA_DISABLE_CLOUD=0
56
NETDATA_INSTALLER_OPTIONS=""
packaging/installer/methods/kickstart.md
+1
-1
@@ -98,7 +98,7 @@ The `kickstart.sh` script accepts a number of optional parameters to control how
98
- `--claim-rooms`: Specify a comma-separated list of tokens for each War Room this node should appear in.
99
- `--claim-proxy`: Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy.
100
See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy) for details.
101
-- `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://api.netdata.cloud`.
101
+- `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://app.netdata.cloud`.
102
- `--override-distro`: Override the distro detection logic and assume the system is using a specific Linux distribution and release. Takes a single argument consisting of the values of the `ID`, `VERSION_ID`, and `VERSION_CODENAME` fields from `/etc/os-release` for the desired distribution.
103
104
The following options are mutually exclusive and specifiy special operations other than trying to install Netdata normally or update an existing install:
packaging/installer/methods/macos.md
+2
-2
@@ -45,11 +45,11 @@ area](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-
45
- `--claim-rooms`: Specify a comma-separated list of tokens for each War Room this node should appear in.
46
- `--claim-proxy`: Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy.
47
See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy) for details.
48
-- `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://api.netdata.cloud`.
48
+- `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://app.netdata.cloud`.
49
50
For example:
51
```bash
52
-curl https://my-netdata.io/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh --install-prefix /usr/local/ --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://api.netdata.cloud
52
+curl https://my-netdata.io/kickstart.sh > /tmp/netdata-kickstart.sh && sh /tmp/netdata-kickstart.sh --install-prefix /usr/local/ --claim-token TOKEN --claim-rooms ROOM1,ROOM2 --claim-url https://app.netdata.cloud
53
```
54
The Netdata Agent is installed under `/usr/local/netdata` on your machine. Your machine will also show up as a node in your Netdata Cloud.
55
tests/alarm_repetition/netdata.conf_with_repetition
+1
-1
@@ -51,4 +51,4 @@
51
allow from = *
52
53
[cloud]
54
- cloud base url = https://api.netdata.cloud
54
+ cloud base url = https://app.netdata.cloud
tests/alarm_repetition/netdata.conf_without_repetition
+1
-1
@@ -51,4 +51,4 @@
51
allow from = *
52
53
[cloud]
54
- cloud base url = https://api.netdata.cloud
54
+ cloud base url = https://app.netdata.cloud