@cryptotaxi247 / netdata-1 / commits / f63f41f54

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

Hugo Valente committed Apr 22, 2024 at 06:13 UTC f63f41f54d5295ec77fbca3ea097f447fb8ffab2
2 files changed +21 -9
docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md
+10 -9
@@ -46,13 +46,14 @@ To manage your **personal alert notification silencing rule settings**, you will
46
47 ## Silencing rules examples
48
49 -| Rule name | War Rooms | Nodes | Host Label | Alert name | Alert context | Alert role | Description |
50 -| :-- | :-- | :-- | :-- | :-- | :-- | :-- | :--|
49 +| Rule name | War Rooms | Nodes | Host Label | Alert name | Alert context | Alert instance | Alert role | Description |
50 +| :-- | :-- | :-- | :-- | :-- | :-- | :-- | :-- | :--|
51 | Space silencing | All Rooms | * | * | * | * | * | This rule silences the entire space, targets all nodes and for all users. E.g. infrastructure wide maintenance window. |
52 -| DB Servers Rooms | PostgreSQL Servers | * | * | * | * | * | This rules silences the nodes in the room named PostgreSQL Servers, for example it doesn't silence the `All Nodes` room. E.g. My team with membership to this room doesn't want to receive notifications for these nodes. |
53 -| Node child1 | All Rooms | `child1` | * | * | * | * | This rule silences all alert state transitions for node `child1` on all rooms and for all users. E.g. node could be going under maintenance. |
54 -| Production nodes | All Rooms | * | `environment:production` | * | * | * | This rule silences all alert state transitions for nodes with the host label key-value pair `environment:production`. E.g. Maintenance window on nodes with specific host labels. |
55 -| Third party maintenance | All Rooms | * | * | `httpcheck_posthog_netdata_cloud.request_status` | * | * | This rule silences this specific alert since third party partner will be undergoing maintenance. |
56 -| Intended stress usage on CPU | All Rooms | * | * | * | `system.cpu` | * | This rule silences specific alerts across all nodes and their CPU cores. |
57 -| Silence role webmaster | All Rooms | * | * | * | * | `webmaster` | This rule silences all alerts configured with the role `webmaster`. |
58 -| Silence alert on node | All Rooms | `child1` | * | `httpcheck_posthog_netdata_cloud.request_status` | * | * | This rule silences the specific alert on the `child1` node. |
52 +| DB Servers Rooms | PostgreSQL Servers | * | * | * | * | * | * | This rules silences the nodes in the room named PostgreSQL Servers, for example it doesn't silence the `All Nodes` room. E.g. My team with membership to this room doesn't want to receive notifications for these nodes. |
53 +| Node child1 | All Rooms | `child1` | * | * | * | * | * | This rule silences all alert state transitions for node `child1` on all rooms and for all users. E.g. node could be going under maintenance. |
54 +| Production nodes | All Rooms | * | `environment:production` | * | * | * | * | This rule silences all alert state transitions for nodes with the host label key-value pair `environment:production`. E.g. Maintenance window on nodes with specific host labels. |
55 +| Third party maintenance | All Rooms | * | * | `httpcheck_posthog_netdata_cloud.request_status` | * | * | * | This rule silences this specific alert since third party partner will be undergoing maintenance. |
56 +| Intended stress usage on CPU | All Rooms | * | * | * | `system.cpu` | * | * | This rule silences specific alerts across all nodes and their CPU cores. |
57 +| Silence role webmaster | All Rooms | * | * | * | * | * | `webmaster` | This rule silences all alerts configured with the role `webmaster`. |
58 +| Silence alert on node | All Rooms | `child1` | * | `httpcheck_posthog_netdata_cloud.request_status` | * | * | * | This rule silences the specific alert on the `child1` node. |
59 +| Disk Space alerts on mount point | All Rooms | * | * | `disk_space_usage` | `disk.space` | `disk_space_opt_baddisk` | * | This rule silences the specific alert instance on all nodes `/opt/baddisk`. |
src/claim/README.md
+11
@@ -554,6 +554,17 @@ To remove a node from you Space in Netdata Cloud, and connect it to another Spac
554 If you are using a `docker-compose.yml` file, you will have to overwrite it with the new claiming token.
555 The node should now appear online in that Space.
556
557 +### Regenerate Claiming Token
558 +
559 +If in case of some security reason, or other, you need to revoke your previous claiming token and generate a new
560 +one you can achieve that from the Netdata Cloud UI.
561 +
562 +On any screen where you see the connect the node to Netdata Cloud command you'll see above it, next to the
563 +[updates channel](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/versions-and-platforms.md), a
564 +button to **Regenerate token**. This action will invalidate your previous token and generate a fresh new one.
565 +
566 +Only the administrators of a Space in Netdata Cloud can trigger this action.
567 +
568 ## Connecting reference
569
570 In the sections below, you can find reference material for the kickstart script, claiming script, connecting via the Agent's command line