grammar pass on alerts and notifications dir (#17729)
Fotis Voutsas committed
May 22, 2024 at 13:53 UTC
0c8277f8d935809a00db4ac2726706956c61716b
4 files changed
+123
-122
docs/alerts-and-notifications/creating-alerts-with-netdata-alerts-configuration-manager.md
+17
-18
@@ -1,45 +1,44 @@
1
# Creating Alerts with Netdata Alerts Configuration Manager
2
3
-The Netdata Alerts Configuration Manager enables subscribers to easily set up alerts directly from the Netdata Dashboard. More details on subscriptions can be found [here](https://www.netdata.cloud/pricing/).
3
+The Netdata Alerts Configuration Manager enables subscribers to easily set up Alerts directly from the Netdata Dashboard. More details on subscriptions can be found [here](https://www.netdata.cloud/pricing/).
4
5
## Using the Alerts Configuration Manager
6
7
-1. Navigate to the **Metrics** tab and select the chart you want to configure for alerts.
7
+1. Navigate to the **Metrics** tab and select the chart you want to configure for Alerts.
8
2. Click the **Alert icon** in the top right corner of the chart.
9
-3. The Alert Configuration Manager will open, showing the default thresholds. Modify these thresholds as needed, the alert definition on the right will update automatically.
9
+3. The Alert Configuration Manager will open, showing the default thresholds. Modify these thresholds as needed; the Alert definition on the right will update automatically.
10
4. For additional settings, toggle **Show advanced**.
11
-5. After configuring the alert, copy the generated alert definition from the code box. Paste this into an existing or new custom health configuration file located at `<path to netdata install>/etc/netdata/health.d/` on a Parent Agent or a Standalone Child Agent. The guide to edit health configuration files is available [here](/src/health/REFERENCE.md#edit-health-configuration-files).
12
-6. To activate the new alert, run the command `<path to netdata install>/usr/sbin/netdatacli reload-health`.
11
+5. After configuring the Alert, copy the generated Alert definition from the code box. Paste this into an existing or new custom health configuration file located at `<path to netdata install>/etc/netdata/health.d/` on a Parent Agent or a Standalone Child Agent. The guide to edit health configuration files is available [here](/src/health/REFERENCE.md#edit-health-configuration-files).
12
+6. To activate the new Alert, run the command `<path to netdata install>/usr/sbin/netdatacli reload-health`.
13
14
## Alerts Configuration Manager Sections
15
16
### Alert Detection Method
17
18
-An alert is triggered whenever a metric crosses a threshold:
18
+An Alert is triggered whenever a metric crosses a threshold:
19
20
- **Standard Threshold**: Triggered when a metric crosses a predefined value.
21
- **Metric Variance**: Triggered based on the variance of the metric.
22
- **Anomaly Rate**: Triggered based on the anomaly rate of the metric.
23
24
-### Metrics Lookup, Filtering and Formula Section
24
+### Metrics Lookup, Filtering, and Formula Section
25
26
-You can read more about the different options in the [Alerts reference documentation](/src/health/REFERENCE.md)
26
+You can read more about the different options in the [Alerts reference documentation](/src/health/REFERENCE.md).
27
28
- **Metrics Lookup**: Adjust the database lookup parameters directly in the UI, including method (`avg`, `sum`, `min`, `max`, etc.), computation style, dimensions, duration, and options like `absolute` or `percentage`.
29
-- **Alert Filtering**: The **show advanced** checkbox allows filtering of alert health checks for specific infrastructure components. Options include selecting hosts, nodes, instances, chart labels, and operating systems.
30
-- **Formula / Calculation**: The **show advanced** checkbox allows defining a formula for the metric value, which is then used to set alert thresholds.
29
+- **Alert Filtering**: The **show advanced** checkbox allows filtering of Alert health checks for specific infrastructure components. Options include selecting hosts, nodes, instances, chart labels, and operating systems.
30
+- **Formula / Calculation**: The **show advanced** checkbox allows defining a formula for the metric value, which is then used to set Alert thresholds.
31
32
### Alerting Conditions
33
34
-- **Thresholds**: Set thresholds for warning and critical alert states, specifying whether the alert should trigger above or below these thresholds. Advanced settings allow for custom formulas.
35
- - **Recovery Thresholds**: Set thresholds for downgrading the alert from critical to warning or from warning to clear.
34
+- **Thresholds**: Set thresholds for warning and critical Alert states, specifying whether the Alert should trigger above or below these thresholds. Advanced settings allow for custom formulas.
35
+ - **Recovery Thresholds**: Set thresholds for downgrading the Alert from critical to warning or from warning to clear.
36
- **Check Interval**: Define how frequently the health check should run.
37
-- **Delay Notifications**: Manage notification delays for alert escalations or de-escalations.
37
+- **Delay Notifications**: Manage notification delays for Alert escalations or de-escalations.
38
- **Agent Specific Options**: Options exclusive to the Netdata Agent, like repeat notification frequencies and notification recipients.
39
- - **Custom Exec Script**: Define custom scripts to execute when an alert triggers.
39
+ - **Custom Exec Script**: Define custom scripts to execute when an Alert triggers.
40
41
-### Alert Name, Description and Summary Section
41
+### Alert Name, Description, and Summary Section
42
43
-- **Alert Template Name**: Provide a unique name for the alert.
44
-- **Alert Template Description**: Offer a brief explanation of what the alert monitors.
45
-- **Alert Summary**: Create a custom title for alert notifications, which can be integrated with centralized notification systems available [here](https://learn.netdata.cloud/docs/alerts-&-notifications/notifications/centralized-cloud-notifications).
43
+- **Alert Template Name**: Provide a unique name for the Alert.
44
+- **Alert Template Description**: Offer a brief explanation of what the Alert
docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md
+18
-16
@@ -1,24 +1,26 @@
1
# Centralized Cloud Notifications Reference
2
3
-Netdata Cloud sends alert notifications for nodes in warning, critical, or unreachable states, ensuring alerts are managed centrally and efficiently.
3
+Netdata Cloud sends Alert notifications for nodes in warning, critical, or unreachable states, ensuring Alerts are managed centrally and efficiently.
4
5
## Benefits of Centralized Notifications
6
7
- Consolidate health status views across all infrastructure in one place.
8
-- Set up and [manage your alert notifications easily](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md).
8
+- Set up and [manage your Alert notifications easily](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md).
9
- Expedite troubleshooting with tools like [Metric Correlations](/docs/metric-correlations.md) and the [Anomaly Advisor](/docs/dashboards-and-charts/anomaly-advisor-tab.md).
10
11
-To avoid notification overload, **flood protection** is triggered when a node frequently disconnects or sends excessive alerts, highlighting potential issues.
11
+> **Note**
12
+>
13
+> To avoid notification overload, **flood protection** is triggered when a node frequently disconnects or sends excessive Alerts, highlighting potential issues.
14
13
-Admins must [enable alert notifications](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-space-notification-settings) for their Space(s). All users can then customize their notification preferences through their [account menu](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-user-notification-settings).
15
+Administrators must [enable Alert notifications](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-space-notification-settings) for their Space(s). All users can then customize their notification preferences through their [account menu](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md#manage-user-notification-settings).
16
17
> **Note**
18
>
17
-> Centralized alerts in Netdata Cloud are separate from the [Netdata Agent](/docs/alerts-and-notifications/notifications/README.md) notifications. Alerts must be [configured individually](/src/health/REFERENCE.md) on each node.
19
+> Centralized Alerts in Netdata Cloud are separate from the [Netdata Agent](/docs/alerts-and-notifications/notifications/README.md) notifications. Agent Alerts must be [configured individually](/src/health/REFERENCE.md) on each node.
20
21
## Alert Notifications
22
21
-Notifications can be sent via email or through third-party services like PagerDuty or Slack. Admins manage notification settings for the entire Space, while individual users can personalize settings in their profile.
23
+Notifications can be sent via email or through third-party services like PagerDuty or Slack. Administrators can manage notification settings for the entire Space, while individual users can personalize settings in their profile.
24
25
### Service Level
26
@@ -28,7 +30,7 @@ Notifications are sent to user-specific destinations, such as email, which are m
30
31
#### System
32
31
-These notifications go to general targets like a Slack channel, with admins setting rules for notification targets based on workspace or alert level.
33
+These notifications go to general targets like a Slack channel, with administrators setting rules for notification targets based on workspace or Alert level.
34
35
### Service Classification
36
@@ -42,11 +44,11 @@ Exclusive to [paid plans](/docs/netdata-cloud/netdata-subscription-plans.md), in
44
45
## Alert Notification Silencing Rules
46
45
-Netdata Cloud offers a silencing rule engine to mute alert notifications based on specific conditions related to nodes or alert types. Learn how to manage these settings [here](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md).
47
+Netdata Cloud offers a silencing rule engine to mute Alert notifications based on specific conditions related to nodes or Alert types. Learn how to manage these settings [here](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md).
48
49
## Flood Protection
50
49
-If a node repeatedly changes state or fires alerts, flood protection limits notifications to prevent overload. You can still access node details through Netdata Cloud or directly via the local Agent dashboard.
51
+If a node repeatedly changes state or raises Alerts, flood protection limits notifications to prevent overload. You can still access node details through Netdata Cloud or directly via the local Agent dashboard.
52
53
## Anatomy of an Email Alert Notification
54
@@ -55,13 +57,13 @@ Email notifications provide comprehensive details:
57
- The Space's name
58
- The node's name
59
- Alert status: critical, warning, cleared
58
-- Previous alert status
59
-- Time at which the alert triggered
60
-- Chart context that triggered the alert
61
-- Name and information about the triggered alert
60
+- Previous Alert status
61
+- Time at which the Alert triggered
62
+- Chart context that triggered the Alert
63
+- Name and information about the triggered Alert
64
- Alert value
63
-- Total number of warning and critical alerts on that node
64
-- Threshold for triggering the given alert state
65
+- Total number of warning and critical Alerts on that node
66
+- Threshold for triggering the given Alert state
67
- Calculation or database lookups that Netdata uses to compute the value
66
-- Source of the alert, including which file you can edit to configure this alert on an individual node
68
+- Source of the Alert, including which file you can edit to configure this Alert on an individual node
69
- Direct link to the node’s chart in Cloud dashboards.
docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md
+42
-41
@@ -1,59 +1,60 @@
1
-# Manage alert notification silencing rules
1
+# Manage Alert Notification Silencing Rules
2
3
-From the Cloud interface, you can manage your space's alert notification silencing rules settings as well as allow users to define their personal ones.
3
+From the Cloud interface, you can manage your space's Alert notification silencing rules settings as well as allow users to define their personal ones.
4
5
## Prerequisites
6
7
-To manage **space's alert notification silencing rule settings**, you will need the following:
7
+To manage **space's Alert notification silencing rule settings**, you will need the following:
8
9
- A Netdata Cloud account
10
- Access to the space as an **administrator** or **manager** (**troubleshooters** can only view space rules)
11
12
-
13
-To manage your **personal alert notification silencing rule settings**, you will need the following:
12
+To manage your **personal Alert notification silencing rule settings**, you will need the following:
13
14
- A Netdata Cloud account
16
-- Access to the space with any roles except **billing**
15
+- Access to the space with any role except **billing**
16
17
### Steps
18
20
-1. Click on the **Space settings** cog (located above your profile icon)
21
-1. Click on the **Alert & Notification** tab on the left hand-side
22
-1. Click on the **Notification Silencing Rules** tab
23
-1. You will be presented with a table of the configured alert notification silencing rules for:
24
- * the space (if aren't an **observer**)
25
- * yourself
26
-
27
- You will be able to:
28
- 1. **Add a new** alert notification silencing rule configuration.
29
- - Choose if it applies to **All users** or **Myself** (All users is only available for **administrators** and **managers**)
30
- - You need to provide a name for the configuration so you can easily refer to it
31
- - Define criteria for Nodes: To which Rooms will this apply? What Nodes? Does it apply to host labels key-value pairs?
32
- - Define criteria for Alerts: Which alert name is being targeted? What alert context? Will it apply to a specific alert role?
19
+1. Click on the **Space settings** cog (located above your profile icon).
20
+2. Click on the **Alert & Notification** tab on the left-hand side.
21
+3. Click on the **Notification Silencing Rules** tab.
22
+4. You will be presented with a table of the configured Alert notification silencing rules for:
23
+
24
+ - The space (if you aren't an **observer**)
25
+ - Yourself
26
+
27
+ You will be able to:
28
+
29
+ 1. **Add a new** Alert notification silencing rule configuration.
30
+ - Choose if it applies to **All users** or **Myself** (All users is only available for **administrators** and **managers**).
31
+ - You need to provide a name for the configuration so you can easily refer to it.
32
+ - Define criteria for Nodes, to which Rooms will the rule apply, on what Nodes and whether or not it applies to host labels key-value pairs.
33
+ - Define criteria for Alerts, such as Alert name is being targeted and on what Alert context. You can also specify if it will apply to a specific Alert role.
34
- Define when it will be applied:
34
- - Immediately, from now till until it is turned off or until a specific duration (start and end date automatically set)
35
- - Scheduled, you specify the start and end time for when the rule becomes active and then inactive (time is set according to your browser local timezone)
36
- Note: You are only able to add a rule if your space is on a [paid plan](https://github.com/netdata/netdata/edit/master/docs/netdata-cloud/netdata-subscription-plans.md).
37
- 1. **Edit an existing** alert notification silencing rule configurations. You will be able to change:
35
+ - Immediately, from now until it is turned off or until a specific duration (start and end date automatically set).
36
+ - Scheduled, you can specify the start and end time for when the rule becomes active and then inactive (time is set according to your browser's local timezone).
37
+ Note: You are only able to add a rule if your space is on a [paid plan](/docs/netdata-cloud/netdata-subscription-plans.md).
38
+ 2. **Edit an existing** Alert notification silencing rule configuration. You will be able to change:
39
- The name provided for it
40
- Who it applies to
40
- - Selection criteria for Nodes and Alert
41
+ - Selection criteria for Nodes and Alerts
42
- When it will be applied
42
- 1. **Enable/Disable** a given alert notification silencing rule configuration.
43
+ 3. **Enable/Disable** a given Alert notification silencing rule configuration.
44
- Use the toggle to enable or disable
44
- 1. **Delete an existing** alert notification silencing rule.
45
- - Use the trash icon to delete your configuration
46
-
47
-## Silencing rules examples
48
-
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. |
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`. |
45
+ 4. **Delete an existing** Alert notification silencing rule.
46
+ - Use the trash icon to delete your configuration
47
+
48
+## Silencing Rules Examples
49
+
50
+| Rule name | War Rooms | Nodes | Host Label | Alert name | Alert context | Alert instance | Alert role | Description |
51
+|:---------------------------------|:-------------------|:---------|:-------------------------|:-------------------------------------------------|:--------------|:-------------------------|:------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
52
+| Space silencing | All Rooms | * | * | * | * | * | * | This rule silences the entire space, targets all nodes, and for all users. E.g. infrastructure-wide maintenance window. |
53
+| DB Servers Rooms | PostgreSQL Servers | * | * | * | * | * | * | This rule 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. |
54
+| Node child1 | All Rooms | `child1` | * | * | * | * | * | This rule silences all Alert state transitions for node `child1` in all rooms and for all users. E.g. node could be going under maintenance. |
55
+| 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. |
56
+| Third party maintenance | All Rooms | * | * | `httpcheck_posthog_netdata_cloud.request_status` | * | * | * | This rule silences this specific Alert since the third-party partner will be undergoing maintenance. |
57
+| Intended stress usage on CPU | All Rooms | * | * | * | `system.cpu` | * | * | This rule silences specific Alerts across all nodes and their CPU cores. |
58
+| Silence role webmaster | All Rooms | * | * | * | * | * | `webmaster` | This rule silences all Alerts configured with the role `webmaster`. |
59
+| Silence Alert on node | All Rooms | `child1` | * | `httpcheck_posthog_netdata_cloud.request_status` | * | * | * | This rule silences the specific Alert on the `child1` node. |
60
+| 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`. |
docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md
+46
-47
@@ -1,73 +1,72 @@
1
-# Manage notification methods
1
+# Manage Notification Methods
2
3
-From the Cloud interface, you can manage your space's notification settings as well as allow users to personalize their notifications setting
3
+From the Cloud interface, you can manage your Space's notification settings as well as allow users to personalize their notification settings.
4
5
-## Manage space notification settings
5
+## Manage Space Notification Settings
6
7
### Prerequisites
8
9
-To manage space notification settings, you will need the following:
9
+To manage Space notification settings, you will need the following:
10
11
- A Netdata Cloud account
12
-- Access to the space as an **administrator**
12
+- Access to the Space as an **administrator**
13
14
-### Available actions per notification methods based on service level
14
+### Available Actions per Notification Method Based on Service Level
15
16
-| **Action** | **Personal service level** | **System service level** |
17
-| :- | :-: | :-: |
18
-| Enable / Disable | X | X |
19
-| Edit | | X | |
20
-| Delete | X | X |
21
-| Add multiple configurations for same method | | X |
16
+| **Action** | **Personal Service Level** | **System Service Level** |
17
+|:------------------------------------------------|:--------------------------:|:------------------------:|
18
+| Enable / Disable | X | X |
19
+| Edit | | X |
20
+| Delete | X | X |
21
+| Add multiple configurations for the same method | | X |
22
23
-Notes:
24
-* For Netadata provided ones you can't delete the existing notification method configuration.
25
-* Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-classification))
23
+> **Notes**
24
+>
25
+> - For Netdata provided ones, you can't delete the existing notification method configuration.
26
+> - Enable, Edit, and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-classification)).
27
28
### Steps
29
29
-1. Click on the **Space settings** cog (located above your profile icon)
30
-1. Click on the **Alerts & Notification** tab on the left hand-side
31
-1. Click on the **Notification Methods** tab
32
-1. You will be presented with a table of the configured notification methods for the space. You will be able to:
30
+1. Click on the **Space settings** cog (located above your profile icon).
31
+2. Click on the **Alerts & Notifications** tab on the left-hand side.
32
+3. Click on the **Notification Methods** tab.
33
+4. You will be presented with a table of the configured notification methods for the Space. You will be able to:
34
1. **Add a new** notification method configuration.
34
- - Choose the service from the list of the available ones, you'll may see a list of unavailable options if your plan doesn't allow some of them (you will see on the
35
- card the plan level that allows a specific service)
36
- - You can optionally provide a name for the configuration so you can easily refer to what it
37
- - Define filtering criteria. To which Rooms will this apply? What notifications I want to receive? (All Alerts and unreachable, All Alerts, Critical only)
38
- - Depending on the service different inputs will be present, please note that there are mandatory and optional inputs
39
- - If you doubts on how to configure the service you can find a link at the top of the modal that takes you to the specific documentation page to help you
40
- 1. **Edit an existing** notification method configuration. Personal level ones can't be edited here, see [Manage user notification settings](#manage-user-notification-settings). You will be able to change:
35
+ - Choose the service from the list of available ones. The available options will depend on your subscription plan.
36
+ - You can optionally provide a name for the configuration so you can easily refer to it.
37
+ - You can define the filtering criteria, regarding which Rooms the method will apply, and what notifications you want to receive (All Alerts and unreachable, All Alerts, Critical only).
38
+ - Depending on the service, different inputs will be present. Please note that there are mandatory and optional inputs.
39
+ - If you have doubts on how to configure the service, you can find a link at the top of the modal that takes you to the specific documentation page to help you.
40
+ 2. **Edit an existing** notification method configuration. Personal level ones can't be edited here, see [Manage User Notification Settings](#manage-user-notification-settings). You will be able to change:
41
- The name provided for it
42
- Filtering criteria
43
- - Service specific inputs
44
- 1. **Enable/Disable** a given notification method configuration.
45
- - Use the toggle to enable or disable the notification method configuration
46
- 1. **Delete an existing** notification method configuration. Netdata provided ones can't be deleted, e.g. Email
47
- - Use the trash icon to delete your configuration
43
+ - Service-specific inputs
44
+ 3. **Enable/Disable** a given notification method configuration.
45
+ - Use the toggle to enable or disable the notification method configuration.
46
+ 4. **Delete an existing** notification method configuration. Netdata provided ones can't be deleted, e.g., Email.
47
+ - Use the trash icon to delete your configuration.
48
49
-## Manage user notification settings
49
+## Manage User Notification Settings
50
51
### Prerequisites
52
53
-To manage user specific notification settings, you will need the following:
53
+To manage user-specific notification settings, you will need the following:
54
55
- A Cloud account
56
-- Have access to, at least, a space
56
+- Access to, at least, a Space
57
58
-Note: If an administrator has disabled a Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification method this will override any user specific setting.
58
+Note: If an administrator has disabled a Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification method, this will override any user-specific setting.
59
60
### Steps
61
62
-1. Click on the **User notification settings** shortcut on top of the help button
63
-1. You are presented with:
64
- - The Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification methods you can manage
65
- - The list spaces and rooms inside those where you have access to
66
- - If you're an administrator, Manager or Troubleshooter you'll also see the Rooms from a space you don't have access to on **All Rooms** tab and you can activate notifications for them by joining the room
67
-1. On this modal you will be able to:
68
- 1. **Enable/Disable** the notification method for you, this applies accross all spaces and rooms
69
- - Use the toggle enable or disable the notification method
70
- 1. **Define what notifications you want** to per space/room: All Alerts and unreachable, All Alerts, Critical only or No notifications
71
- 1. **Activate notifications** for a room you aren't a member of
72
- - From the **All Rooms** tab click on the Join button for the room(s) you want
73
-
62
+1. Click on the **User notification settings** shortcut on top of the help button.
63
+2. You are presented with:
64
+ - The Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification methods you can manage.
65
+ - The list of Spaces and Rooms inside those where you have access to.
66
+ - If you're an Administrator, Manager, or Troubleshooter, you'll also see the Rooms from a Space you don't have access to on the **All Rooms** tab, and you can activate notifications for them by joining the Room.
67
+3. On this modal you will be able to:
68
+ 1. **Enable/Disable** the notification method for you; this applies across all Spaces and Rooms.
69
+ - Use the toggle to enable or disable the notification method.
70
+ 2. **Define what notifications you want** per Space/room: All Alerts and unreachable, All Alerts, Critical only, or No notifications.
71
+ 3. **Activate notifications** for a Room you aren't a member of.
72
+ - From the **All Rooms** tab, click on the Join button for the Room(s) you want.