diff options
Diffstat (limited to 'src/claim/README.md')
| -rw-r--r-- | src/claim/README.md | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/src/claim/README.md b/src/claim/README.md index d274496a8e..d6526e5c4f 100644 --- a/src/claim/README.md +++ b/src/claim/README.md @@ -36,7 +36,7 @@ There will be three main flows from where you might want to connect a node to Ne - when you are on a [War Room](#empty-war-room) and you want to connect your first node - when you are at the [Manage Space](#manage-space-or-war-room) area and you select **Connect Nodes** to connect a node, coming from Manage Space or Manage War Room -- when you are on the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/nodes.md) and want to connect a node - this process falls into the [Manage Space](#manage-space-or-war-room) flow +- when you are on the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboard/nodes-tab.md) and want to connect a node - this process falls into the [Manage Space](#manage-space-or-war-room) flow Please note that only the administrators of a Space in Netdata Cloud can view the claiming token and accompanying script, generated by Netdata Cloud, to trigger the connection process. @@ -62,7 +62,7 @@ finished onboarding. To connect a node, select which War Rooms you want to add this node to with the dropdown, then copy and paste the script given by Netdata Cloud into your node's terminal. -When coming from the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/nodes.md) the room parameter is already defined to current War Room. +When coming from the [Nodes tab](https://github.com/netdata/netdata/blob/master/docs/dashboard/nodes-tab.md) the room parameter is already defined to current War Room. ### Connect an agent running in Linux @@ -554,6 +554,17 @@ To remove a node from you Space in Netdata Cloud, and connect it to another Spac If you are using a `docker-compose.yml` file, you will have to overwrite it with the new claiming token. The node should now appear online in that Space. +### Regenerate Claiming Token + +If in case of some security reason, or other, you need to revoke your previous claiming token and generate a new +one you can achieve that from the Netdata Cloud UI. + +On any screen where you see the connect the node to Netdata Cloud command you'll see above it, next to the +[updates channel](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md), a +button to **Regenerate token**. This action will invalidate your previous token and generate a fresh new one. + +Only the administrators of a Space in Netdata Cloud can trigger this action. + ## Connecting reference In the sections below, you can find reference material for the kickstart script, claiming script, connecting via the Agent's command line |