@cryptotaxi247 / netdata-1 / commits / 0ed5a8c76

Add text to claiming doc about reclaiming with id= (#9027)

* Add text about reclaiming * Changed some wording * Address Andrew's comments

Joel Hans committed May 14, 2020 at 05:29 UTC 0ed5a8c76f37d57e11e412137cc61db1fab2f0a3
1 file changed +11 -5
claim/README.md
+11 -5
@@ -261,18 +261,24 @@ If you are certain firewall and proxy settings are not the issue, you should con
261 GitHub](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage%2C+ACLK&template=bug_report.md&title=ACLK-available-is-false)
262 with details about your system and relevant output from `error.log`.
263
264 -### Unclaim (remove) an Agent from Netdata Cloud
264 +### Remove and reclaim a node
265
266 -The best method to remove an Agent from Netdata Cloud is to unclaim it by deleting the `cloud.d/` directory in your
267 -Netdata library directory.
266 +To remove a node from your Space in Netdata Cloud, delete the `cloud.d/` directory in your Netdata library directory.
267
268 ```bash
269 cd /var/lib/netdata # Replace with your Netdata library directory, if not /var/lib/netdata/
270 sudo rm -rf cloud.d/
271 ```
272
274 -Once you delete the `cloud.d/` directory, the ACLK will not connect to Cloud the next time the Agent starts, and Cloud
275 -will show it as **unreachable**. You can then remove it from your War Rooms.
273 +This node no longer has access to the credentials it was claimed with and cannot connect to Netdata Cloud via the ACLK.
274 +You will still be able to see this node in your War Rooms in an **unreachable** state.
275 +
276 +If you want to reclaim this node into a different Space, you need to create a new identity by adding `-id=$(uuidgen)` to
277 +the claiming script parameters. For example, using the default claiming script:
278 +
279 +```bash
280 +sudo netdata-claim.sh -token=TOKEN -rooms=ROOM1,ROOM2 -url=https://app.netdata.cloud -id=$(uuidgen)
281 +```
282
283 ## Claiming reference
284