Skip to content

Commit f2143ad

Browse files
authored
Merge branch 'main' into docs-684-add-new-tab-preference
2 parents 4ec47fa + d02e35f commit f2143ad

38 files changed

+197
-205
lines changed

.clabot

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@
55
"JV0812",
66
"jpipkin1",
77
"JainM6",
8+
"@dependabot[bot]",
9+
"dependabot[bot]",
810
"docsSeema",
911
"angadrandhawa1",
1012
"kkujawa-sumo",

docs/alerts/monitors/alert-response.md

Lines changed: 65 additions & 83 deletions
Large diffs are not rendered by default.

docs/alerts/monitors/create-monitor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ When you create a monitor and open the metrics search query in the Metrics Explo
7070

7171
## Step 1. Set trigger conditions
7272

73-
The first step when creating a new monitor is setting the **Trigger Conditions**.
73+
The first step when creating a new monitor is setting the **Trigger Conditions**, a thresholds value that must met to trigger an alert. Applicable values include Critical, Warning, and Missing Data. These values are set when you create a monitor and can be based on a variety of metrics such as CPU usage, network latency, application response time.
7474

7575
### Monitor Type
7676

docs/alerts/monitors/settings.md

Lines changed: 66 additions & 67 deletions
Large diffs are not rendered by default.

docs/alerts/monitors/use-playbooks-with-monitors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ For more information, see [Add an automated playbook to a monitor](/docs/alerts/
3232

3333
### When viewing an alert
3434

35-
1. On the [alert page](/docs/alerts/monitors/alert-response/#alert-page), open an alert.
35+
1. Go to your **Alert List** and click on any alert to open its [details page](/docs/alerts/monitors/alert-response/#alert-details).
3636
1. Click the **Playbook** button. The attached playbooks, if assigned during Monitor configuration, are displayed along with their execution status.
3737
1. Click the name of an attached playbook. <br/>The playbook is opened in the Automation Service.
3838

@@ -58,7 +58,7 @@ After you add playbooks to the monitor, when the monitor triggers an alert, the
5858

5959
Once a monitor triggers an alert with one or more attached playbooks, you can view the playbooks for the alert.
6060

61-
1. On the [alert page](/docs/alerts/monitors/alert-response/#alert-page), open an alert that has attached playbooks.
61+
1. Go to your **Alert List** and click on any alert to open its [details page](/docs/alerts/monitors/alert-response/#alert-details).
6262
1. Click the **Playbook** button. The attached playbooks are displayed. <br/><img src={useBaseUrl('img/alerts/monitors/view-playbooks-on-alert.png')} alt="View playbooks for an alert" style={{border: '1px solid gray'}} width="800" />
6363
1. Hover your mouse over the icon to the right of the playbook name to view the status of the playbooks:
6464

docs/get-started/account-settings-preferences.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ Keep this option selected if you'd like to run a saved search as soon as you sel
162162

163163
### Alerts
164164

165-
Select these preferences to manage how alerts are handled. For more information, see [Notification preferences](/docs/alerts/monitors/alert-response/#notification-preferences).
165+
Click any of the following checkboxes to enable your desired preferences:<br/><img src={useBaseUrl('img/alerts/alert-preferences.png')} alt="Alert preferences" style={{border: '1px solid gray'}} width="500" />
166166

167167
#### Display alert badge when my subscribed monitors are triggered
168168

@@ -174,11 +174,11 @@ Select this option to receive notifications only for monitors you're subscribed
174174

175175
#### Enable "Active alerts only" as default filter
176176

177-
By default, your alerts list only displays alerts with an active status. Alerts with a resolved status are excluded.
177+
By default, your alerts list only displays alerts with an active status. Alerts with a resolved status are excluded.<br/> <img src={useBaseUrl('img/alerts/filter-active.png')} alt="alert-preferences" style={{border: '1px solid gray'}} width="500" />
178178

179179
#### Enable "My subscriptions" as default filter
180180

181-
By default, alerts you are subscribed to will appear in your alerts list.
181+
By default, alerts you are subscribed to will appear in your alerts list.<br/> <img src={useBaseUrl('img/alerts/filter-subscribe.png')} alt="alert-preferences" style={{border: '1px solid gray'}} width="500" />
182182

183183
### New UI
184184

docs/integrations/databases/redis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -459,7 +459,7 @@ There are limits for how many alerts can be enabled - please see the [Alerts FAQ
459459
4. Click **Import** to import monitors from the JSON above.
460460
461461
:::note
462-
Monitors are disabled by default. Once you have installed the alerts via this method, navigate to the Redis folder under **Monitors** to configure them. See [Monitor Settings](/docs/alerts/monitors/settings/#monitor-details-pane) to enable monitors. To send notifications to teams or connections, see the instructions detailed in Step 4 of [Create a Monitor](/docs/alerts/monitors/create-monitor).
462+
Monitors are disabled by default. Once you have installed the alerts via this method, navigate to the Redis folder under **Monitors** to configure them. See [Monitor Settings](/docs/alerts/monitors/settings/#monitor-details) to enable monitors. To send notifications to teams or connections, see the instructions detailed in Step 4 of [Create a Monitor](/docs/alerts/monitors/create-monitor).
463463
:::
464464
465465
### Method B: Using a Terraform script

docs/manage/ingestion-volume/monitor-ingestion-receive-alerts.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ _index=sumologic_volume and sizeInBytes and _sourceCategory="sourcename_volume"
8080
After completing the setup, schedule the search to run: 
8181
8282
1. Schedule Query you created in Setup. For details, see [Schedule a Search](../../alerts/scheduled-searches/schedule-search.md).
83-
1. Set the frequency to **Daily**.
83+
1. Set the **Run frequency** to **Daily**.
8484
1. Enter **-32d** for the time range.<br/> ![time range monthly plan.png](/img/manage/ingestion-volume/daily-32d.png)
8585
1. Make sure Alert Condition is set to **Send Notification** if the **Alert Condition** is met: **Number of results** greater than **0.**
8686
@@ -125,7 +125,7 @@ _index=sumologic_volume sizeInBytes
125125
After completing the setup steps above, schedule the search to run, as follows.  
126126

127127
1. Schedule the query you created in the previous step (**Query**). For details, see [Schedule a Search](../../alerts/scheduled-searches/schedule-search.md).
128-
1. Set the run frequency to **Daily**.
128+
1. Set the **Run frequency** to **Daily**.
129129
1. Set time range value to **Last 24 Hours**.<br/> ![time range daily plan limit.png](/img/manage/ingestion-volume/daily-last-24.png)
130130
1. Make sure Alert Condition is set to **Send Notification** if the **Alert Condition** is met: **Number of results** greater than **0.**
131131

@@ -174,7 +174,7 @@ _index=sumologic_volume sizeInBytes _sourceCategory="sourcecategory_volume"
174174
After completing the setup steps above, schedule the search to run, as follows.  
175175
176176
1. Schedule the query you just created in Setup. For details, see [Schedule a Search](../../alerts/scheduled-searches/schedule-search.md).
177-
1. Set the run frequency to **Hourly**.
177+
1. Set the **Run frequency** to **Hourly**.
178178
1. Enter **-65m -5m** for the time range.<br/> ![time range usage spike.png](/img/manage/ingestion-volume/hourly-65.png)
179179
1. Make sure Alert Condition is set to **Send Notification** if the **Alert Condition** is met: **Number of results** greater than **0.**
180180
@@ -265,6 +265,6 @@ _index=sumologic_audit _sourceCategory=account_management _sourceName=VOLUME_QUO
265265
After completing the setup steps above, schedule the search to run, as follows.  
266266

267267
1. Schedule the query you just created in Setup. For details, see [Schedule a Search](../../alerts/scheduled-searches/schedule-search.md).
268-
1. Set the run frequency to **Every 15 Minutes.**
268+
1. Set the **Run frequency** to **Every 15 Minutes**.
269269
1. Set the time range to the **Last 15 Minutes**.<br/> ![time range throttling alert.png](/img/manage/ingestion-volume/time-throttling.png)
270-
1. Make sure Alert Condition is set to **Send Notification** if the **Alert Condition** is met: **Number of results** greater than **0.**
270+
1. Make sure Alert Condition is set to **Send Notification** if the **Alert Condition** is met: **Number of results** greater than **0**.

docs/manage/partitions/data-tiers/infrequent-tier-monitors.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ Previously, monitors and alert response page (ARP) were only supported in Sumo L
1616

1717
Monitors track your Metrics, Logs, or SLO data in real time and send notifications when noteworthy changes happen in your production applications. To create Monitors, you can refer to the [Create a Monitor](/docs/alerts/monitors/create-monitor/).
1818

19-
## Alert Response Page
20-
21-
The Alert Response page is where you can view granular details about an individual alert. [Learn more](/docs/alerts/monitors/alert-response/#alert-page).
19+
## Alert Response page
2220

21+
The Alert Response page is where you can view granular details about an individual alert. [Learn more](/docs/alerts/monitors/alert-response/#alert-details).

docs/manage/users-roles/roles/role-capabilities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ Folder-level permissions are available if your org has fine-grained Monitor perm
104104
| View Monitors | If [monitors folder permissions](/docs/alerts/monitors/settings/#monitor-folder-permissions) are enabled for your org, users with this capability can view folders on the [Monitors](/docs/alerts/monitors) page to which they've been granted View access, and the Monitors contained in those folders.|
105105
| Manage Monitors | Users with this capability can create new folders and [monitors](/docs/alerts/monitors), and grant other roles permissions to the folders they create. If [monitors folder permissions](/docs/alerts/monitors/settings/#monitor-folder-permissions) are enabled for your org, users with this capability can also create, edit, delete, update and grant permissions to folders to which another user has granted them those permissions.|
106106
| Admin Monitors | If [monitors folder permissions](/docs/alerts/monitors/settings/#monitor-folder-permissions) are enabled for your org, users with this capability have full access (Create, Edit, Delete, Update, and grant permissions) to ALL folders and monitors on the Monitors page. This is similar to the Content Administrator capability of the Content Library.|
107-
| View Alerts | View alerts on the [Alert page](/docs/alerts/monitors/alert-response#alert-page).|
107+
| View Alerts | View alerts on the [Alert page](/docs/alerts/monitors/alert-response).|
108108
| View Muting Schedules | Required for viewing the [Muting Schedules](/docs/alerts/monitors/muting-schedules) page and schedule definitions.|
109109
| Manage Muting Schedules | Required for creating, editing, and deleting Muting Schedules.|
110110

0 commit comments

Comments
 (0)