diff options
| author | Hugo Valente <82235632+hugovalente-pm@users.noreply.github.com> | 2024-04-22 06:13:59 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-22 08:13:59 +0300 |
| commit | f63f41f54d5295ec77fbca3ea097f447fb8ffab2 (patch) | |
| tree | 767eacfde6a98860dd75691158adebee1a24edab /src/claim | |
| parent | bdbf369d6f6fca3ad9238dccee3db8f1bf41aac1 (diff) | |
add section for regenerate claiming token (#17457)
* add section for regenerate claiming token
* missing h
* missing If at begh
* missing If at n on token
* add example of silencing alert instance
Diffstat (limited to 'src/claim')
| -rw-r--r-- | src/claim/README.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/src/claim/README.md b/src/claim/README.md index b6f7857802..d6526e5c4f 100644 --- a/src/claim/README.md +++ b/src/claim/README.md @@ -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 |